IBM Support

The Service Registry application fails to start when using a generated server startup script

Technote (troubleshooting)


If you use a WebSphere Application Server generated startup script to start a server, then the Service Registry application may fail to start with a setSchemaNames


The Service Registry application fails to start and the following exception is seen in the SystemOut.log:

E setSchemaNames GSR5000I: Captured exception [#]: <script_location>/config/cells/<cell_name>/nodes/<node_name>/servers/<server_name>/server.xml (No such file or directory)


The Service Registry application startup uses the user.dir system property to load configuration. If a generated script is used to start a server ( -script) then the user.dir is the script directory not the <WAS_PROFILE_HOME>.

Resolving the problem

Add the following line to the generated server startup script:


Related information

WebSphere Application Server startServer command

Product Alias/Synonym


Document information

More support for: WebSphere Service Registry and Repository

Software version: 8.0, 8.5

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: All Editions

Reference #: 1610070

Modified date: 04 August 2014

Translate this page: