Quest Vworkspace error when connecting from the AppPortal

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
matt whiteit consultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
no attachment
0
matt whiteit consultantAuthor Commented:
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
David Johnson, CD, MVPOwnerCommented:
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
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

matt whiteit consultantAuthor Commented:
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
matt whiteit consultantAuthor Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
matt whiteit consultantAuthor Commented:
This reason was accepted by Dell support
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.