The following message may be displayed in the Object Spawner Log when
attempting to start the Object Spawner:

   ERROR:  A valid sasSpawner definition cannot be found.
   ERROR:  Objspawn encountered errors during results processing.
or
   ERROR:  Objspawn was unable to locate a server definition. Objspawn
           is exiting.

The following are tips on resolving these errors:

   1.) Matching host_names.  At the top of the Object Spawner log file,
       the fully qualified host name, host alias name, or the IP address
       will be listed as the host in which the Object Spawner is
       started.  For example,

         Objspawn is executing on host myhost.sas.com

       This "host_name" is the value that should match the Host Name
       field of the Server properties window in SAS Management Console.

   2.) Identical host_names.  All of the host names specified in the SAS
       Management Console definitions should be identical.  Make
       sure that all of the server definitions use the fully qualified
       name, alias name, or IP address.  It is important that all host
       names are consistent and match.

   3.) Case sensitivity.  All of the Server Names must match EXACTLY
       (especially on UNIX) as defined in the SAS Management Console and
       the ObjectSpawner start file.

   4.) ReadMetadata granted.  In the SAS Management Console, the SAS
       System Services group must have the ReadMetadata permission
       granted.  User Manager => SAS System Services => properties =>
       Authorization Tab

   5.) Selected Server.  Either the Workspace Server or Stored Process
       Server must be selected on the Servers tab of the SASMain -
       Spawner (i.e, Object Spawner) properties in the SAS Management
       Console.  Open the server properties window and verify that the
       launch command contains a reference to SAS and to the BI
       configuration file.

   6.) The SAS Trusted User login status.  Login to SAS Management
       Console with the SAS Trusted user (SASTRUST) account.  If the
       Login status (bottom right corner of SAS Management Console
       screen) shows that the Trusted user is logged in as PUBLIC, then
       SASTRUST has access to the machine but not as a user with an
       account in the Metadata.  Most likely, the Metadata does not
       match with the SASTRUST account that is set in the OMRConfig.xml
       file.

       A common problem is when the SAS Trusted user is referenced as
       domain\SASTRUST in the OMRConfig.xml file, but is either missing
       or not referenced with a domain or machine_name in SAS
       Management Console.  Adding the domain or machine_name to the SAS
       Trusted user account in SAS Management Console usually corrects
       the problem.

Operating System and Release Information