Steps to help resolve Synchronization problems
- What is the state of the node(s)? (check the administrative console)
- Unknown or unavailable
- Is the nodeagent running?
- Yes, this is a discovery problem not a
synchronization problem, see discovery TroubleShooting
- No, start the nodeagent, this process is required
for synchronization to work.
- Not synchronized, continue to step 2.
- Is the "filetransfer" application installed and running? (Go to
Applications > Enterprise Applications in the administration
console to view installed and running applications)
- If not installed, follow this technote
to reinstall.
- If stopped, start the "filetransfer" application. Continue
to step 3 if problem is not resolved
- If you just enabled security, were all WebSphere Application Server
processes (dmgr, nodes, appservers) recycled enabled?
- Yes, continue to step 5.
- No, recycle all processes then attempt to
synchronize the node with the syncNode
command. If the problem continues, go to step 5.
- Do you see the following error within the NodeAgent
SystemOut.log file?
NodeSyncTask A
ADMS0016I: Configuration synchronization
failed.NodeSync E ADMS0005E: Unable to generate
synchronization request: javax.management.RuntimeMBeanException at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.
handleAdminFault(SOAPConnectorClient.java(Compiled Code)).... |
|
- Yes, see this technote
on how to correct the problem.
- No, go to the next step.
|
|
- Do you see the following error within the NodeAgent
SystemOut.log file?
ADMD0012E: Unable to
initialize the transport of type: TCP
ADMS0012E: Unable to create administrative
client connection:
com.ibm.websphere.management.exception.AdminException: Admin client
connection to deployment manager is unavailable |
|
- Yes, see this technote.
- No, go to the next step.
|
|
- Do you see the following error within the NodeAgent
SystemOut.log file?
ADFS0119E: An
unexpected exception occurred: java.io.EOFException: Unexpected end of
ZLIB input stream |
|
- Yes, see this technote.
- No, go to the next step.
|
|
- Do you see the following error within the NodeAgent
SystemOut.log file?
ADMS0005E: Unable to
generate synchronization request:
javax.management.RuntimeMBeanException: Prefix string too
short |
|
- Yes, see this technote.
- No, go to next step.
|
|
- Do you see the following error within the NodeAgent
SystemOut.log file?
ADMS0005E: Unable
to generate synchronization request:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0009E: Failed to make the SOAP RPC
call: invoke |
|
- Yes, see this technote
- No, see the following What to do next?
section.
|
|
What to do next?
If the preceding troublehooting steps did not solve your problem, see the
MustGather
for synchronization problems to continue investigation. |