LMS Daemon doesn't starts after 3.2 Update

[phtruchet]

Hi,

We are installing Ciscoworks LMS on a Windows Server 2003 which is on a VMware ESX Server 3i Virtual Machine.

After I have installed LMS 3.0 and update to 3.1 it was still working. But after updating to 3.2 the daemon doesn't starts.

If I try to launch LMS threw the prompt command (net start crmdmgtd) I have a message telling: "the service is not responding to the control function."

I have allready installed LMS on a similar server and it worked well...I don't really know what you need to know to helping resolve my problem.

Thanks for your help !

[Joel Monge]

Check the below:

1. Disable any anti-virus or security software.

2. In Windows, go to Start and click on 'Run...'. Type in services.msc and make sure you have the following services set like this:

CiscoWorks ANI database engine: Manual
CiscoWorks Daemon Manager: Automatic
CiscoWorks RME NG database engine: Manual
CiscoWorks Tomcat Servlet Engine: Manual
CiscoWorks VisiBroker Smart Agent: Manual
CiscoWorks Web Server: Manual
CWCS Cmf database engine: Manual
CWCS rsh/rcp service: Automatic
CWCS syslog service: Automatic
CWCS tftp service: Automatic
DFM dfmEpm database engine: Manual
DFM dfmFh database engine: Manual
DFM dfmInv database engine: Manual

If any of these are different, change them and reboot the server.

3. Configure your virtual memory to be double the size of your RAM.

4. If still no go, try resetting the casuser:

4.1. Issue from a command prompt in the server:

  net stop crmdmgtd 

       This will stop the CiscoWorks daemons.

  4.2. Now go to CSCOpx\setup\support\, type: resetCasuser.exe.
  4.3. Choose a password that applies to your server password policies.
  4.4. Issue the command:

  net start crmdmgtd

  If issue remains, post the CSCOpx\syslog.log.

[phtruchet]

Thanks for the quick answer.

1. There are missing elements: -CiscoWorks VisiBroker Smart Agent

                                             -CiscoWorks Web Server

                                             -DFM dfmEpm database Engine

                                             -DFM dfmFh database Engine

                                             -DFM dfmlnv database Engine

Does that mean that the installation didn't worked correctly ?

For the rest, there are well configured.

2. There is 8 GBytes on the server but we share it between the LMS server and the CSM server, so I have entered 4 GBytes for the LMS virtual machine, is that correct ?

3. I didn't treat that point yet

4. After resetting the casuser, daemon still doesn't launch

I will give send the the CSCOpx\syslog.log file on monday, my working place is closing right now...

[Joel Monge]

If CiscoWorks Web Server is missing there could be a bigger problem. Besides syslog.log, please provide the below on Monday:

- Output of these DOS commands:

pdreg -l Apache

Apache.exe -version

  Locate yourself on C:\Program Files\CSCOpx\MDC\Apache> and then issue:

apache.exe -t -d C:\Progra~1\CSCOpx\MDC\Apache

  This is assuming your LMS install patch is under C:\Program Files\CSCOpx. If not, change accordingly.

Post these files:

- LMS 3.2 install log (usually under C drive).

- CSCOpx\MDC\Apache\conf\httpd.conf.

- CSCOpx\MDC\Apache\logs\error.log

Also post any Windows Event Viewer related errors.

[phtruchet]

Here are all the files you asked for. The error.log is empty, that is why it is not here.

[Joel Monge · Accepted solution]

This installation never completed properly. Looks like it was aborted. I thought we might have been able to just re-install the missing Web Service at first, but in this case you should remove LMS, clean the system with the clean_system script (TAC can provide) and properly re-install. Remember to always follow these steps when installing LMS:

* Set your TEMP and TMP environment variables to C:\TEMP (make sure that directory exists, and everyone has full access).

* Disable anti-virus and security software.

* Set Windows Data Execution Protection to be active for essential windows files only.

* Reboot the server.

* Login on the server's console as a local Administrator.

* Install from locally mounted original media.