Solved

Quest Vworkspace error when connecting from the AppPortal

Posted on 2014-09-29
6
430 Views
Last Modified: 2014-10-11
When users initiate a connection to a VM using Quest VWorkspace AppPortal they receive the attached error.  It leaves the VM state on the Connection broker as "pending".  When you initiate the connection for the second time it connects to the sane VM and logs the users on successfully.

The Windows 7 VM's are running on Hyper V servers

All servers are running Server 2008 R2
0
Comment
Question by:matt white
  • 4
  • 2
6 Comments
 
LVL 79

Expert Comment

by:David Johnson, CD, MVP
ID: 40351383
no attachment
0
 

Author Comment

by:matt white
ID: 40351651
Please see attached.

Just to add to above.  As mentioned the second connection to the VM is successful, when I finally get logged in I have noticed the following 2 event log entries on the VM (see attached)

Many thanks
Matt
Error-from-Vworkspace-App-Portal.PNG
eventLog.PNG
0
 
LVL 79

Expert Comment

by:David Johnson, CD, MVP
ID: 40351718
Open Remote Desktop Session Host Configuration and double-click RDP-Tcp in the Connections block.  In the General tab, change the Security layer pulldown box from Negotiate to RDP Security Layer.

http://bit.ly/1vsghO5
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:matt white
ID: 40351893
Hi david, Thanks for your suggestion but this is not a Terminal Services configuration.

There are 10 x Hyper V services hosting Virtuaol Desktop Machines.  Users connect to the VM's via the Quest Vworkspace servers which act as connection Brokers to the Hyper V hosted Virtual Desktops.  The Quest implementation still utilizes standard RDP.

The problem would appear to be similar to the Terminal services issue but obviously we do not have the settings that you specify above that reside on Terminal Server setup.
0
 

Accepted Solution

by:
matt white earned 0 total points
ID: 40363145
The problem was due to the version of Quest PNTOOLS.  The following version was causing the issue:

Quest Tools for the managed desktop 8.0306.1530

Downgrading the version to 8.0.306.1510 fixed the issue.  I have logged this with Dell support and it is with their Development Team who will be advising of a hotfix.
0
 

Author Closing Comment

by:matt white
ID: 40374577
This reason was accepted by Dell support
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Veeam Backup & Replication has added a new integration – Veeam Backup for Microsoft Office 365.  In this blog, we will discuss how you can benefit from Office 365 email backup with the Veeam’s new product and try to shed some light on the needs and …
Is your company's data protection keeping pace with virtualization? Here are 7 dynamic ways to adapt to rapid breakthroughs in technology.
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
In this video tutorial I show you the main steps to install and configure  a VMware ESXi6.0 server. The video has my comments as text on the screen and you can pause anytime when needed. Hope this will be helpful. Verify that your hardware and BIO…

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question