You might have problems connecting to the SAS Workspace Server because
the Object Spawner does not have the correct command to start the
Workspace Server. And the variety of error messages in the
object spawner log do not provide adequate cues for troublehshooting.

Begin troubleshooting by checking the following in the SAS
Management Console:

   1. Right-click on SASMain - Workspace server.
   2. Select Properties.
   3. Select the Options tab.
   4. Delete the SAS command and copy and paste the correct SAS command
      from instructions.html.

      Note: Check your work carefully. An ending || around the path to
            your *.cfg file can be hard to spot but will stop the server
            from invoking.

   5. Be sure to stop and re-start the Object Spawner before testing
      again.

If the problem occurs when you connect to the workspace server from
one of the client applications, the problem could be with the metadata
identity or login information for the specific user. Depending on
the client application, the error message for this problem varies. In
order to troubleshoot this problem, perform the following:

   1. Assume that you have successfully logged into the application as
      a particular user but cannot connect to the workspace server as
      that user.

   2. In the SAS Management Console, verify that you have specified the
      login information for the user correctly, including machine\user
      ID, password, and authentication domain*

      Note: A good approach for verifying the password is to modify the
            login and re-type the password correctly. If you correct the
            login information and still cannot log in, you must verify
            that the user ID and password that you defined in the
            operating system matches what you specified in your metadata
            login information. A good check for this is to verify that
you can
            log into your local machine by using the user ID and
password
            that you stored in the metadata login.

      Warning: Beware of adding the -LOG option to your command for the
               workspace server. After doing so, the first ID to connect
               creates and owns the log file.  This will cause any other
               ID to fail, due to the fact that they are not allowed to
               overwrite the log. This can be corrected by giving the
               EVERYONE group in the operating system full permissions
               to the log file using the Windows Explorer.

Operating System and Release Information