cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1471
Views
0
Helpful
7
Replies

RME - ConfigMgmtServer unable to connect CM0051

i.cristian
Level 1
Level 1

Hi to all

We have a problem with the config management in the RME that we can not sync configuration. When we try to sync de config or try to create a job we get the CM0051 error.

The exact error is:
"CM0051 Unable to connect to ConfigMgmtSever process Cause: Read timed out/Error in received response null Action: Please restart ConfigMgmtSever process. "

Please help...

In the attach i will put:

- pdshow.txt

- ConfigMgmtServer.log

- dcmaservice.zip

1 Accepted Solution

Accepted Solutions

The problem was with ctmregistry corruption.

In order to fix it, we need to delete two files:

  1. NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\ctmregistry
  2. NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\ctmregistry.backup

and restart the daemons

View solution in original post

7 Replies 7

Svetlana Radzevich
Cisco Employee
Cisco Employee

The ConfigMgmtServer is down:

Process= ConfigMgmtServer
    State  = Administrator has shut down this server
    Pid    = 0
    RC     = 0
    Signo  = 0
    Start  = 1/18/2011 5:36:00 PM
    Stop   = 1/18/2011 5:36:16 PM
    Core   = Not applicable
    Info   = Server started by admin request

Try to start it from CLI:

     pdexec ConfigMgmtServer

Hi Svetlana

We did try this but nothing happened ....still no start.

Stillwe found that 2 jar files are missing and maybe this could be a probleme.

The missing jar files are

mdc/tomcat/webapps/rme/web-inf/lib/jdk.jar and jms1.02.b.jar

Thanks

Is it a Solaris box?

Was it worked before? If yes, what did you change before you notice the issue?

it is a windows installation

yes it worked.....and we did not change anything before.

We just wanted to have an update on the configs

Cristian

The problem was with ctmregistry corruption.

In order to fix it, we need to delete two files:

  1. NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\ctmregistry
  2. NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\ctmregistry.backup

and restart the daemons

Hi

The problem is not solved....it reapeared...please see the TAC case.

Hi

The cause of the problem was the IPS Manager Express program installed on the same server.

There was some port conflicts between services of the 2 programs (LMS and IPS Manager)