UNSOLVED

gwsmith1

updated

16 years ago

G

gwsmith1

8 Posts

0

17513

October 26th, 2010 13:00

Losing connection when minimizing vWorkspace seamless app

"Quest vWorkspace Client"

"Because of a protocol error (code: 0x10de), the remote session will be disconnected. Please try connecting to the remote computer again"

7.1 MR1 on Server 2008 SP1 (SP2 not supported for the published app at this time)

7.1 MR1 client (web client)

When minimizing the published app, we get this message. Reconnecting continues the existing session.

Any ideas?

  • 505

    0

    Posted October 26th, 2010 14:00

    Hello Gregory,

    Can you check to see if you have the Graphics Acceleration option enabled on the client settings, if so disable this option and then test to see if you no longer get the 'Prototcol Error' message.

    This is currently a known issue that is being investigated and is detailed under the Known Issues section of the vWorkspace 7.1 MR1 Release Notes.

    Let me know if you have further questions about this.

  • gwsmith1

    8 Posts

    505

    0

    Posted October 26th, 2010 19:00

    They're connecting using the Secure Access gateway. Is there a way to configure this from the server? or via Group Policy?

  • 505

    0

    Posted October 27th, 2010 07:00

    The setting can be enabled/disabled on the Web Access server, when logging into the admin page. Select the User Experience tab and then the Performance option, there you will see the Graphics Acceleration check box. You can chose to enforce this setting for all users by disabling the 'Allow user to override the performance settings' check box.

  • gwsmith1

    8 Posts

    505

    0

    Posted October 27th, 2010 13:00

    Excellent and many thanks! I have implemented the change and will followup to let you know if this resolved the issue.

    Have disabled:

    EOP Graphics Acceleration
    EOP Xtream (WAN acceleration)
    Bitmap caching

    As EOP was already disabled at the application level on the connection brokers, and based on other research, I believe it's likely to be the "Bitmap Caching" setting.

  • gwsmith1

    8 Posts

    505

    0

    Posted October 28th, 2010 12:00

    No joy - still having this issue. 

  • gwsmith1

    8 Posts

    505

    0

    Posted October 29th, 2010 12:00

    Reply to the original response so you get pinged

  • gwsmith1

    8 Posts

    505

    0

    Posted October 29th, 2010 12:00

    Continued no joy. Same message if using the MR1 fat client; especially when minimizing / maximizing the application. We're using seamless windows to present the apps.

  • yoda-ict

    8 Posts

    505

    0

    Posted November 26th, 2010 12:00

    We experience the same problem. XStream is off. Running 7.1 MR1. This is not a TCP timeout issue as this only occurs on a specific terminal server. Other terminal servers published through the same SSL gateway are fine. Hopefully there will be a solution soon..

    Frans