If the "sastrust" (SAS Trusted User) account does not have permissions
to access the metadata about the Stored Process Server's login user
account, you will receive the following error message when you run the
"Test Connection" test for the Stored Process Server:

   "sam.S251.ex.msg: A problem occurred while connecting to a load
   balancing spawner."

In addition, when you check the Object Spawner's log file, you will find
that there is no entry for "UserID" (generally, the value should be
"sassrv") in the definition for your Stored Process Server (e.g. under
the section for "SASMain - Stored Process Server").

If you observe this behavior, then check the following:

   1.)  Make sure the "SAS Trusted User" has a login account
        defined (the account is generally "sastrust").

   2.)  Logon to your SAS Management Console using the
        "sastrust" user account.  At the bottom of the SAS
        Management Console window, you should see the below
        note about your "sastrust" logon account:

          sastrust as SAS Trusted User

        Under "Server Manager", drill down to the lowest level for
        your Stored Process Server (for example "SASMain - Stored
        Process Server").  Then, right-click and select "Properties".
        Select the "Options" tab.  Then, click on the "Advanced
        Options" button.  On the "Credentials" window, you should
        see a value specified for "Login".  Generally, this value
        is "sassrv".

If you still have problems, then turn on the "pelevel=3" option for the
Object Spawner in the Object Spawner script file (e.g.
"ObjectSpawner.bat").

   -objectserverparms "pelevel=3"

This will cause additional debugging information to be added to your
Object Spawner's log file.

Operating System and Release Information