Skip to main content
Summary Orbix 6.3 Naming Service fails to start on demand
Article Number 16618
Environment Orbix 6.3 Solaris 10
Question/Problem Description Orbix 6.3 Naming Service fails to start on demand
Unable to start Orbix Naming Service via itadmin tool
Clarifying Information
Error Message Starting the Naming Service on demand fails with the following error: (IT_GIOP:104) W - received exception status from LocateReply: IDL:omg.org/CORBA/TRANSIENT:1.0: minor = 0x49540C00 (IT_POA_LOCATOR:SERVER_NOT_READY), completion status = NO
Defect/Enhancement Number
Cause This is caused by having generated the Orbix domain via itconfigure tool with a different user than the user starting the services.
Resolution Ensure you start the Orbix services with the same user as the one who was used to configure the domain. Alternatively reconfigure your domain to manually startup the Naming Service or modify the Naming Service process via itadmin in such a way that the owner of the process is the one starting the services.
Workaround
Notes
Attachment
Created date: 06 September 2011
Last Modified: 13 February 2013
Last Published: 27 June 2012
First Published date: 10 September 2011

#Orbix
#KnowledgeDocs