topic SAS9.4M8 With Windows Server 2019 Configuration Error in Object Spawner in Administration and Deployment

SAS9.4M8 With Windows Server 2019 Configuration Error in Object Spawner

eddieleung305 — Tue, 02 May 2023 21:35:54 GMT

May I know if anyone can share in a new SAS9.4M8 installation on Windows Server 2019, any special tips and tricks can share? I encounter this error in configuring Object Spawner where this error I haven't encountered before. There is no problem resolving the server hostname to the correct IP so I have no idea why the Object Spawner cannot start

checkForErrors:

BUILD FAILED
D:\SASInstall\SASFoundation\9.4\core\sasmisc\sasconf\objectspawnr\config\objectspawnr_config.xml:959: A problem was encountered attempting to start the requested server. rc:8 log directory:<a href="file:///D:\DevMetadata\Lev1\ObjectSpawner\Logs">D:\DevMetadata\Lev1\ObjectSpawner\Logs</a> output:after 1031ms, checkpoint 0 wait hint = 0ms
unexpected service status SERVICE_STOPPED
at org.apache.tools.ant.taskdefs.Exit.execute(Exit.java:162)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299)
at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401)
at org.apache.tools.ant.Project.executeTarget(Project.java:1374)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1264)
at org.apache.tools.ant.Main.runBuild(Main.java:818)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)

Total time: 5 seconds

Re: SAS9.4M8 With Windows Server 2019 Configuration Error in Object Spawner

SASKiwi — Tue, 02 May 2023 21:55:52 GMT

Looks like some type of Java-related problem. I'd suggest opening a track with Tech Support if you haven't yet done so as they are in the best position to investigate further.

Re: SAS9.4M8 With Windows Server 2019 Configuration Error in Object Spawner

ronf_sas — Wed, 03 May 2023 11:50:26 GMT

Check the object spawner logs at D:\DevMetadata\Lev1\ObjectSpawner\Logs for more clues.

Re: SAS9.4M8 With Windows Server 2019 Configuration Error in Object Spawner

eddieleung305 — Wed, 03 May 2023 12:09:01 GMT

This is the main section of the error message. My server is a single-tier server and is configured with metadata and an object spawner. No issue found to resolve the hostname

2023-05-03T10:55:55,447 INFO [00000030] :SYSTEM@SL19VM95 - Also known as:
2023-05-03T10:55:55,447 INFO [00000030] :SYSTEM@SL19VM95 - localhost
2023-05-03T10:55:55,447 INFO [00000030] :SYSTEM@SL19VM95 - SL19VM95
2023-05-03T10:55:55,447 INFO [00000030] :SYSTEM@SL19VM95 - ::1
2023-05-03T10:55:55,447 INFO [00000030] :SYSTEM@SL19VM95 - 172.31.62.59
2023-05-03T10:55:55,447 INFO [00000030] :SYSTEM@SL19VM95 - 127.0.0.1
2023-05-03T10:55:55,448 INFO [00000030] :SYSTEM@SL19VM95 - Processing parsed configuration results.
2023-05-03T10:55:55,448 INFO [00000030] :SYSTEM@SL19VM95 - Objspawn is proceeding with the configuration results processing utilizing the A5DZHT30.AY000002 spawner definition.
2023-05-03T10:55:55,448 INFO [00000030] :SYSTEM@SL19VM95 - Reserved IPv6 port 8581 for administrator listen (connection 2).
2023-05-03T10:55:55,448 INFO [00000030] :SYSTEM@SL19VM95 - Reserved IPv6 port 58988 for launched server connect back listen (connection 3).
2023-05-03T10:55:55,448 INFO [00000030] :SYSTEM@SL19VM95 - Activated listen on IPv6 port 58988 (connection 3).
2023-05-03T10:55:55,448 INFO [00000030] :SYSTEM@SL19VM95 - Activated listen on IPv6 port 8581 (connection 2).
2023-05-03T10:55:55,450 ERROR [00000030] :SYSTEM@SL19VM95 - Objspawn was unable to locate a server definition. Objspawn is exiting.
2023-05-03T10:55:55,450 ERROR [00000030] :SYSTEM@SL19VM95 - CLASSFACTORY cannot be instantiated.
2023-05-03T10:55:55,451 INFO [00000007] :SYSTEM@SL19VM95 - Client connection 1 for user sastrust@saspw closed.
2023-05-03T10:55:55,451 INFO [00000009] :SYSTEM@SL19VM95 - Bridge PE SAM listen thread is exiting (0).
2023-05-03T10:55:55,451 INFO [00000007] :SYSTEM@SL19VM95 - For the IOM thread puddle, there were 26 requests processed. The maximum number of requests queued was 0. The maximum number of worker threads was 2.
2023-05-03T10:55:55,451 INFO [00000007] :SYSTEM@SL19VM95 - Bridge protocol engine has quiesced.
2023-05-03T10:55:55,451 INFO [00000007] :SYSTEM@SL19VM95 - Bridge protocol engine is unloading.
2023-05-03T10:55:55,453 ERROR [00000003] :SYSTEM@SL19VM95 - Unable to initiate the IOM run-time.

Re: SAS9.4M8 With Windows Server 2019 Configuration Error in Object Spawner

gwootton — Wed, 03 May 2023 14:36:52 GMT

Looks like it's saying there are no servers defined for the object spawner, so it has no reason to run. For example in Metadata the Object Spawner is defined for host A but no servers like a workspace server associated with that Object Spawner are also associated with host A (or there are no servers associated with the object spawner at all).