Changing External DNS Name On Secure Global Desktop Server Can Cause General Exception Error

(Doc ID 2060607.1)

Last updated on MAY 05, 2017

Applies to:

Oracle Secure Global Desktop - Version 5.2 to 5.2 [Release 5.0]
Information in this document applies to any platform.


A Secure Global Desktop (SGD) Administrator changes the Server External DNS name as mentioned on the SGD Admin Manual.

Once the External DNS name has been changed, testing shows that the user is able to login into SGD Workspace by using an old external DNS name (= peer DNS name) but the login is failing with the new external DNS name.

Here is what an SGD user will see:

1) SGD Login is sitting on LOADING... screen


2) SGD User is gets a General Exception popup window:



3) If an SGD user has enabled a Java Console with Debug settings like this:

   [v] Enable tracing
   [v] Enable logging
   [v] Show applet lifecycle exceptions
Java Console:
   (*) Show Console

  General instructions for enabling the Java Console can be found here:


The Java Console may show the following error:




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms