Joe Clarke Mon, 05/17/2010 - 15:17
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the output of the pdshow command from this server.

Joe Clarke Tue, 05/18/2010 - 09:36
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This has to be some kind of record.  Your server has been up for over two years.  It is quite possible that CTMJrmServer has quietly crashed, or ran out of memory.  Try restating Daemon Manager, and see the problem goes away.

Joe Clarke Tue, 05/18/2010 - 10:57
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the new pdshow output, the CTMJrmServer.log, and the jrm.log.

Joe Clarke Tue, 05/18/2010 - 11:57
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Something is not right here.  Is your server clock set to 2008?

Joe Clarke Tue, 05/18/2010 - 12:53
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Your pdshow and CTMJrmServer.log only show dates from 2008.  How are you gathering the pdshow output?

russnash Tue, 05/18/2010 - 12:56
User Badges:

doing a search on the server for those logs.

Joe Clarke Tue, 05/18/2010 - 13:25
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the EssentialsDM.log and EssentialsDM_Server.log.

Joe Clarke Tue, 05/18/2010 - 13:41
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

You're seeing CSCte49301.


Symptom:

The EssentialsDM daemon hangs in a Waiting to initialize state (as seen in the output of the pdshow command).  Additionally, one might see "Error connecting to JRM" in Resource Manager Essentials applications.

Conditions:

This occurs on Windows servers after the patch for KB968930 is installed, and only if the Windows Remote Management service was started prior to starting CiscoWorks Daemon Manager.

Workaround:

Shutdown CiscoWorks Daemon Manager with the following command from the server's command prompt:

net stop crmdmgtd

Delete the following two files:

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

Restart CiscoWorks Daemon Manager with the following command:

net start crmdmgtd

If that does not work, then the Windows Remote Management service must be stopped, and disabled.  Then, CiscoWorks Daemon Manager must be restarted.

russnash Tue, 05/18/2010 - 13:45
User Badges:

thanks, will give it a try and let you know results.

Joe Clarke Wed, 05/19/2010 - 11:57
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib

Actions

This Discussion