Problem Note 69419: SAS® Object Spawner fails to start and returns the "Server component not found" error
 |  |  |  |
You might encounter an issue in which SAS Object Spawner fails to start and returns the following error:
This error occurs in the follow scenarios:
- Scenario 1: The SPWNNAME value that the object-spawner service was installed with does not match the name of the object-spawner definition in the metadata.
- Scenario 2: The SAS Trusted User account does not have Read Metadata permission in the object-spawner definition.
Scenario 1
If the name of the object-spawner definition is not Object Spawner - XXXXXXXXX, then you can either change the name that is stored in the metadata or you can change the SPWNNAME value in the ObjectSpawner.bat (for Windows) or ObjectSpawner.sh (for linux/unix) file to the new name from the object-spawner definition. You must re-install the object-spawner service if you elect to change the SPWNNAME value by running either of the following:
ObjectSpawner.bat remove
ObjectSpawner.bat install
or
ObjectSpawner.sh install
Note: The ObjectSpawner.bat or ObjectSpawner.sh file is located in the Lev1\ObjectSpawner subdirectory in your SAS Configuration Directory.
Scenario 2
If the name of the object-spawner definition in the metadata matches Object Spawner - XXXXXXXXX, then you must determine why the SAS Trusted User account does not have Read Metadata permission in the object-spawner definition. SAS System Services and SASUSERS need Read Metadata permission in the object-spawner definition.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Object Spawner | z/OS | 9.4 | 9.4 TS1M0 | ||
| Microsoft® Windows® for x64 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows 8 Enterprise x64 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows 8 Pro x64 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows 8.1 Pro x64 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows 10 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows Server 2008 R2 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows Server 2008 for x64 | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows Server 2012 R2 Std | 9.4 | 9.4 TS1M0 | ||||
| Microsoft Windows Server 2012 Std | 9.4 | 9.4 TS1M0 | ||||
| Windows 7 Enterprise x64 | 9.4 | 9.4 TS1M0 | ||||
| Windows 7 Professional x64 | 9.4 | 9.4 TS1M0 | ||||
| 64-bit Enabled AIX | 9.4 | 9.4 TS1M0 | ||||
| 64-bit Enabled Solaris | 9.4 | 9.4 TS1M0 | ||||
| HP-UX IPF | 9.4 | 9.4 TS1M0 | ||||
| Linux for x64 | 9.4 | 9.4 TS1M0 | ||||
| Solaris for x64 | 9.4 | 9.4 TS1M0 | ||||
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2022-07-27 13:58:26 |
| Date Created: | 2022-07-26 15:32:22 |