I am having trouble with License Server / Daemon Manager when running LMS 3.1..
I have looked through this forum and checked that the following services are set correctly to Manual
CiscoWorks ANI database engine
CiscoWorks RME NG database engine
CiscoWorks Tomcat Servlet engine
CiscoWorks Web Server
CWAWFEngine database engine
CWCS Cmf database engine
DFM dfmEpm database engine
DFM dfmInv database engine
DFM dfmFh database engine
I have triedshutting down the Daemon Manager and forcing the databases to close down (hoping that the transaction log might be the problem but so far no joy.. Was running okay for some months on Windows 2003 as a VM.
Packages installed are as follows...
Just about to give up and do a fresh install....any assistance would be appreciated.
Many thanks, Peter.
|CiscoWorks Common Services||3.2.0||Licensed||Not applicable|
|CiscoWorks Assistant||1.1.0||Licensed||Not applicable|
|Device Fault Manager||3.1.0||Purchased||100|
|Internetwork Performance Monitor||4.1.0||Purchased||100|
|Integration Utility||1.8.0||Licensed||Not applicable|
|LMS Portal||1.1.0||Licensed||Not applicable|
|Resource Manager Essentials||4.2.0||Purchased||100|
It looks like you're seeing CSCte49301. Follow the release note steps to solve this:
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.
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.
Shutdown CiscoWorks Daemon Manager with the following command from the server's command prompt:
net stop crmdmgtd
Delete the following two files:
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.