LMS 2.6 Unable to start the CiscoWorks Daemon Manager

Answered Question
Feb 6th, 2007

Good morning,

I have a big problem with LMS 2.6, I have installed it onto a COMPAQ DL360, I have configured the application but after a reboot the CiscoWorks Daemon Manager won't start ????

Last week I have the same problem so I have re-installed completly the LMS 2.6 but yesterday the problem appear again.

I'm very desapointed because I'm at the customer office in Africa and I leave tomorrow the country to go back in France and I need to solve the problem before I leave.

So many thanks in advance because this problem is very CRITICAL.

Olivier

I have this problem too.
0 votes
Correct Answer by frankzehrer about 9 years 7 months ago

Hi Olivier,

do you have any message in the windows eventlog??

please try the following:

Install Drive\Program Files\CSCOpx\setup\support\resetcasuser.exe

Where drive is the driveletter where CW is installed.

Hope that helps,

Best regards,

Frank

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
frankzehrer Tue, 02/06/2007 - 01:04

Hi Olivier,

what OS Version are you using?

What did you configure?

Lets assume a Windows System: If you changed the password for the casuser the services wont start.

Do you have any message of the eventlog?

Did you setup some securtiy features within the LMS??

Is a ACS Server integrated for authentication?

Best regards,

Frank

ogor Tue, 02/06/2007 - 01:09

Hi,

thanks for your quick reply.

I'm in Win2003 SP1

No password was changed.

No new install like security features

for the moment no ACS auth.

I have only configured the different discovery, data collection etc ...

Olivier

Correct Answer
frankzehrer Tue, 02/06/2007 - 01:42

Hi Olivier,

do you have any message in the windows eventlog??

please try the following:

Install Drive\Program Files\CSCOpx\setup\support\resetcasuser.exe

Where drive is the driveletter where CW is installed.

Hope that helps,

Best regards,

Frank

ogor Tue, 02/06/2007 - 01:48

I have done this :

One of the reasons this can happen is if there was a change made for the casuser account on the box. This is the internal user account Ciscoworks uses for all its internal processes. There is no way to check if the causer password has been changed. However, we can always reset it.

Do the following to reset the casuser account.

- From the Server-CLI (command line) , cd to \CSCOpx\setup\support

- try to run, resetCasuser.exe

- restart your server, net start crmdmgtd

- or try rebooting the box

and it's working.

I have installed the application on the D: do you think it is a problem ?

many thanks

Olivier

frankzehrer Tue, 02/06/2007 - 01:52

Hi Olivier,

i have all my installation running on D: without any problem.

Seems we had the same ideas.

;-)

Best regards,

Frank

ogor Tue, 02/06/2007 - 01:58

I have done this :

One of the reasons this can happen is if there was a change made for the casuser account on the box. This is the internal user account Ciscoworks uses for all its internal processes. There is no way to check if the causer password has been changed. However, we can always reset it.

Do the following to reset the casuser account.

- From the Server-CLI (command line) , cd to \CSCOpx\setup\support

- try to run, resetCasuser.exe

- restart your server, net start crmdmgtd

- or try rebooting the box

and it's working.

I have installed the application on the D: do you think it is a problem ?

many thanks

Olivier

Actions

This Discussion