IBM WebSphere - Resolve "Could not register with Location Service Daemon"
by
Jeremy Canfield |
Updated: March 08 2022
| IBM WebSphere articles
This error appears in the HPEL or SystemOut.log.
[mm/dd/yy hh:mm:ss:sss CDT] 0000000a WsServerImpl E
WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: com.ibm.ejs.EJSException:
Could not register with Location Service Daemon, which could only reside in the NodeAgent.
Make sure the NodeAgent for this node is up an running
Notice the error states to make sure the node agent is up and running. If the node agent has not been started, start the node agent.
Did you find this article helpful?
If so, consider buying me a coffee over at 
Comments
October 25 2019 by CA
Hi Jeremy, shouldn't the application servers start independently of the nodeagent?
October 26 2019 by Jeremy (moderator)
Yes, the node agent and application servers are started independently. However, if the node is federated into the dmgr, then the node agent will need to be started to establish communication between the dmgr and node. I have cleaned up this article for clarity.