Daemon manager lms 3.2 starts and dies

After running OK during several months the lms3.2 daemon manager is going down without starting the lms services.
I have already run resetcasuser and did not helped.
I found that the casusers group had not the proper permissions on the cmd.exe file, I had this problem on an CUOM 2.3 installation, but
even after correcting the cmd.exe permissions the error persists.
I am posting the dmgtd related lines extracted from the syslog.log.
Any help is appreciated.

Hi ,
1.-Please check that the IIS service is not running on the server. (If running stop and disable it)
2.-Please try by adding the casuser to the administrator group :
From My computer click the right button of the mouse and select Manage. Go to local users,
double click on casuser and select tab 'Member of' Add to 'Administrator'
Then :
Go to CSCOpx\setup\support in DOS prompt.
Run the command 'resetcasuser'
provide a password according to the password policies.
Now try to restart:
c:\>net stop crmdmgtd (wait for a couple of minutes after each command)
c:\>net start crmdmgtd (wait full 5 minutes and then log in Cisco works)
I hope this should work !!
Thanks--
Afroj

Similar Messages

IMac G5 tries to start and dies after spinning cog for a minute

iMac G5 tries to start and dies after spinning cog for a minute
I did this;
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.
the result was.
the 'permissions' are sometimes wrong, but they repair
the hard drive is either repaired or OK
the iMac will then restart and work fine and sometimes shut down and restart OK
after replacing the Hard Drive I actually thought I had fixed it and went to bed late but happy,
on waking in the morning, however I was not so happy it fired up and then died after dong -> apple logo -> spinning cog -> dead!!
I would be grateful for any help
Thanks
Pete

Hi Miriam,
Thanks yes,
here we go -- after running disc utilities it tells me directory OK and disk OK (or something like that) When I replaced the Hard Drive, I started 'fresh' erased/formatted the hard drive (new Seagate Barracuda 7200 500GB) and it has just got 'tiger' on it (and upgraded to whatever it is now I think I remember 4.11, I can't tell at the moment as I have got the back off) I didn't transfer any data I just took the old drive (Seagate 160GB) out and stuck the new one in.
I've just changed the battery (I didn't really think it would work, but I was still hopeful and I'd bought the battery anyway) I did the LED thing, the internal power button thing, and the resetting the SMU thing (with crossed fingers and bated breath) but -- so I'm thinking is it the power supply? I read some of Jim's weighty, but worthy tome and resolved to remove the power supply and have a look. On opening it up, it does look as though, one (at least) of the capacitors has 'blown' (by the way, just in case I sound like I know what I'm talking about, I don't of course, I'm just quoting Jim's words;-) I'd love to send you a picture of the inside of the power supply showing what I believe to be a 'blown' capacitator (and I'm going to try to send one to Jim as I think it might be useful to him and others. can I attach a photo in any way or would you like to send me your email address <Edited by Moderator>
Thanks
Pete
PS it's still 'weird' to me, why it starts and runs well, when started from tiger (or whatever) and then starts or restarts from the Hard Drive unless I leave it a few hours and come back and try to start it
again? wow it's late nearly 4.00am here in london UK.

Daemon Manager service does not start

Hello,
I have a problem with Ciscoworks LMS 3.1 ... Application was working fine but after a while it started to show errors due to some processes and services that weren't enabled. I looked over the processes and services windows and realized Daemon Manager wasn´t working. I tried to start it but just doesn't happen.
I did it through the services window and also through a windows command prompt but results weren't different.
I attached the screenshots about my issue. Hope they're helpful and will be looking forward your answer.
Thank you,

Hi,
Actually, there is only one server working for all the modules of the application so it has been set up as standalone.
The server has the following features:
- Microsoft Windows Server 2003, Standard Edition, SP1
- Intel(R) XEON(R) CPU
- E5405 @ 2.00 GHz
- 2.00 GHz, 1.97 GB of RAM
Domain has been set up within the server
Antivirus Microsoft Forefront Client Security installed
Is there any bug that fixes that problem about the domain being corrupted??? would it be better if we skip that domain's comfiguration when setting up the server's system (although it would be like server does not belong to the network)??, Antivirus has not to be installed??? Policies from the firewall would need to be all opened (from the server to any device that is to be managed by the application???
According to your comments that is what i am understanding, please let me know if i am wrong and therefore What would you recommend me to do???
Thanks,

Can't start Daemon Manager service on CSM 3.1

Hello dear experts!
After i've installed CSM 3.1 on customer server i found that CSM Daemon Manager service can't start. Next error log appears in MS Event Viewer:
"Faulting application dmgtd.exe, version 1.0.0.1, faulting module dmgtd.exe, version 1.0.0.1, fault address 0x00011f96."
After these i tried to start this service manually, but i got next error:
"Error 1053: The service did not respond to the start or control request in a timely fashion"
I did software installation remotely using Microsoft Terminal connection to server.
I have exactly the same problem with Cisco LMS 2.6 which i've installed on another server. Daemon Manager can't start there too.
Could you give me advices what i need to do?

I tried to reboot server and wait for Windows to load services much times, but it did not help my any way. I found error reason: Daemon Manager couldn't start because there was no swap space on my server. I checked syslog file and found the alert. After i tuned swap settings this service started. But there is one interesting fact during CSM and LMS installation: though swap space setting on my server was as "No paging file", but CSM (LMS) installer shows me that i have sufficient swap space. So always check log files (C:\Program Files\CSCOpx\log) if you can't start your CSM or LMS.

CWMLS daemon manager service could not be started

Hello,
Our server in which we have installed Ciscoworks LMS was restarted due to power supply problems. After that "CiscoWorks Daemon Manager" service is not getting started. I've tried to stop all the ciscoworks related services and restart it, also tried restarting the server machine. Ciscoworks LMS Version 3.0, installed on windows 2000 SP4. The error message is:
E:>net start crmdmgtd
The CiscoWorks Daemon Manager service is starting.
The CiscoWorks Daemon Manager service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
I've changed casuser password using resetCasuser.exe file, but there was no change.
Any clue?

Hi ,
Please attach the syslog.log ( If it is huge in size then truncate and send me some of the Lateste logs..)
--Screen shot of the services.msc winodw ( with all the cisco works service)
--Go to start >control Panel >Administrative Tools > Event Viewer > open the Application logs and send me the screen shot of the lastest event ..
In the mean time try this :
go to services.msc > change the startup type of the Daemon Manager to MAUNAL from Automatic and
ReBoot the Server ... Once server is back online > change the startup type back to Automatic and Try to Restart the Daemon Manager .
Note : Please make sure the IIS Admin service is Disable
Thanks
Afroj

CiscoWorksLMS 4.0 - Service Ciscoworks Daemon Manager does not start

Dear,
After migrating a virtual machine that hosts the CiscoworksLms 4.0, Daemon Manager service does not start.
From what we see this error seems to be a problem in the license.
Following is the error:
ERROR! The license file is invalid. Please click this link for information about Obtaining a valid license or purchase click here for current licensing information Otherwise, please contact your Cisco representative for purchasing information.
I have already entered in the User casuse group of administrators and reset the password but no use Daemon Manager service not up
Thanks for help!

Hi,
From the attached screen shots, I can see the startup type are Incorrect for Many services ,kindly correct their status...
please see below the correct startup type
configuration for LMS Services. As you notice you see that only the
"CiscoWorks Daemon Manager" (except the RSH/Syslog/TFTP services) is set to
start automatically, the Daemon Manager is responsible for starting all the
other CiscoWorks LMS services in a specific order.
So by having the below configuration, LMS will start correctly by itself
after Windows successfully reboots. In fact having any other start up
configuration will cause LMS to not start, because if one of the LMS
services starts before it dependent services, it will not come up and all
subsequent services will fail to start as well.
CiscoWorks ANI database engine - Manual (if Campus Manager installed)
CiscoWorks Daemon Manager - Automatic
CiscoWorks RME NG database engine - Manual (if RME installed)
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 server - Automatic
If DFM installed:
DFM dfmEpm database engine - Manual
DFM dfmFh database engine - Manual
DFM dfmInv database engine - Manual
If IPM installed:
IPM Aging Server - Automatic
IPM DB Server - Automatic
IPM Naming Server - Automatic
IPM PM Server - Automatic
IPM Stopper - Automatic
--Change the statup type Accordingly and then REBOOT the Sever and check the issue again..
Thanks
Afroj

Daemon manager won't start

After doing a fresh install of Cisco Prime 4.1 and rebooting the server 'Cisco Prime Daemon Manager' service won't start. Startup type is 'Auto'. Server has been rebooted twice and I have tried 'net start crmdmgtd' without success.
C:\Users\NetAdmin>net start crmdmgtd
The Cisco Prime Daemon Manager service is starting.
The Cisco Prime Daemon Manager service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
C:\Users\NetAdmin>net helpmsg 3534
The service did not report an error.
C:\Users\NetAdmin>

I need to see following output:
> Output when you enter command : net start crmdmgtd (on command prompt)
> Last 100 lines of NMSROOT/log/syslog.log
> event logs, if anything pertainign to Ciscoworks processes.
Try following things as well:
# Make casuser a member of adminitrators group.
#Make sure you have swap properly and manually configured (twice of RMA):
1. Right click on "Computer" and select "Properties." Click on "Advanced System Settings."
2. Choose the "Advanced" tab and click "Settings," under "Performance."
3. Choose the "Advanced" tab and click "Change" under "Virtual Memory."
4. Uncheck "Automatically Manage Paging File Size" for all drives.
5. Click "Custom Size" and enter the amount of swap space in MB (megabytes). Click "Set" and then "OK" three times to return to the desktop.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Daemon Manager Service

The CiscoWorks Daemon Manager Service is not starting on my server; I tried to start the service in the Services section of My Computer and through the CLI but it still won’t start. I rebooted the server several times with no luck. I don’t know what happened; everything was working fine last week and now this problem occurred. Any help would be appreciated!

Good morning,
Thanks for your suggestion, I'll give it a try!
Please let me give you a little more history on the problem I'm having, Tuesday I tried to open Ciscoworks and I received the following error on the browser after I tried to login.
Error 403: You don't have permission to access /cwhp/LiaisonServlet on this server.
After a reboot of the Ciscoworks server is when the Daemon Manager Service was unable to start at all. I did find a TID on fixing a Tomcat bug and ran it on Wednesday but the service still didn't start. After trying the suggestion this morning on resetting the Casuser password I went back and ran the TID from Wednesday again and this time the service started. Everything appears to be running normally but every time I try to login to the server I receive the error above with no errors being displayed in the syslog file. Hope this extra information helps and I appreciate your help!
Thanks,
Tim Walsh
PS - I am working on the server from a remote desktop connection so getting the log files to you might be tough to do.

Cisco Works Daemon Manager Service down after deleting Syslog files

Dears,
Cisco Works Daemon Manager Service is not comiing up after deleting the syslog.log files from NMSroot, al other services are comes up except this.
please help ...
Rgds
Aslam

Not sure what is happening, but I see several services that should be started by the daemon manager, that are already started!!
You best stop them, make sure the services are set to manual except daemon manager, tftp syslog and rcp who are automatic.
Then I suggest to reboot server. If the daemon manager still can start run the resetcasuser.exe in \CSCOpx\setup\support\ and try again.
Cheers,
Michel

Managed server is not starting....

hi friends,
we have four node weblogic 10.3.5 clustered deployment of oim 11.1.1.5 ....previously everything was working fine....two of the oim managed server is not starting and throwing following error.... two are working fine and all other 4 soa servers also running fine...
####<May 20, 2012 3:43:18 PM AST> <Warning> <RMI> <server2> <WLS_OIM2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1337517798416> <BEA-080004> <An error was thrown by rmi server: weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown()
java.lang.ExceptionInInitializerError.
java.lang.ExceptionInInitializerError
     at weblogic.wsee.runtime.JMSStoreRoutableIDMapper.shutdown(JMSStoreRoutableIDMapper.java:478)
     at weblogic.wsee.runtime.WebServicesRuntime.shutdown(WebServicesRuntime.java:146)
     at weblogic.wsee.runtime.WseeService.haltService(WseeService.java:60)
     at weblogic.server.ServiceActivator.halt(ServiceActivator.java:113)
     at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:504)
     at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:336)
     at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:1120)
     at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:1024)
     at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:351)
     at weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown(RemoteLifeCycleOperationsImpl.java:57)
     at weblogic.server.RemoteLifeCycleOperationsImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.IllegalStateException: Shutdown in progress
     at java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:39)
     at java.lang.Runtime.addShutdownHook(Runtime.java:193)
     at weblogic.wsee.persistence.LogicalStore.<clinit>(LogicalStore.java:192)
     at weblogic.wsee.runtime.JMSStoreRoutableIDMapper.shutdown(JMSStoreRoutableIDMapper.java:478)
     at weblogic.wsee.runtime.WebServicesRuntime.shutdown(WebServicesRuntime.java:146)
     at weblogic.wsee.runtime.WseeService.haltService(WseeService.java:61)
     at weblogic.server.ServiceActivator.halt(ServiceActivator.java:114)
     at weblogic.t3.srvr.ServerServicesManager.haltInternal(ServerServicesManager.java:504)
     at weblogic.t3.srvr.ServerServicesManager.halt(ServerServicesManager.java:336)
     at weblogic.t3.srvr.T3Srvr.shutdown(T3Srvr.java:1120)
     at weblogic.t3.srvr.T3Srvr.forceShutdown(T3Srvr.java:1025)
     at weblogic.t3.srvr.ServerRuntime.forceShutdown(ServerRuntime.java:351)
     at weblogic.server.RemoteLifeCycleOperationsImpl.forceShutdown(RemoteLifeCycleOperationsImpl.java:59)
     at weblogic.server.RemoteLifeCycleOperationsImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:668)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:523)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:119)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Regards
jdev

thanks for the reply....
the managed server is pointing to jrokit_160_22_D1.1.1-3 jdk....the server has enough ram also...while running the managed server showing status 'STARTING' for long period of time...and the admin server health goes 'Warning' because of threadpool....when we stop the managed server then adminserver health becomes ok...

Ciscoworks License Server/Daemon Manager is down.

Hello,
It seems i have a major issue with my Ciscoworks server. Whenever i try to go to Netconfig, or inventory, or basically anything i get this error
"License Server/Daemon Manager is down. Please check license.log for more information."
The license.log file doesn't show much, here is the last few lines
"[ Tue Mar 01 12:01:03 EST 2011 ] [CS_License:LiceneServer-Thread-656] INFO com.cisco.nm.license.server.LicenseServer - Executing GetFeature
[ Tue Mar 01 12:01:03 EST 2011 ] [CS_License:LiceneServer-Thread-656] INFO com.cisco.nm.license.server.LicenseServer - Got VMS features
[ Tue Mar 01 12:01:03 EST 2011 ] [CS_License:LiceneServer-Thread-656] INFO com.cisco.nm.license.server.LicenseServer - Getting CMF features
[ Tue Mar 01 12:07:10 EST 2011 ] [CS_License:LiceneServer-Thread-657] INFO com.cisco.nm.license.server.LicenseServer - Executing GetFeature
[ Tue Mar 01 12:07:10 EST 2011 ] [CS_License:LiceneServer-Thread-657] INFO com.cisco.nm.license.server.LicenseServer - Got VMS features
[ Tue Mar 01 12:07:10 EST 2011 ] [CS_License:LiceneServer-Thread-657] INFO com.cisco.nm.license.server.LicenseServer - Getting CMF features
Can anyone assist with this please?

The service was already stopped. I did not stop it. When i tried to start it it stopped striaght away... see below
C:\>net stop crmdmgtd
The CiscoWorks Daemon Manager service is not started.
More help is available by typing NET HELPMSG 3521.
C:\>net start crmdmgtd
The CiscoWorks Daemon Manager service is starting.
The CiscoWorks Daemon Manager service could not be started.
The service did not report an error.

Lms 3.2 and window server 2008 standard: License Server/Daemon Manager is down

LMS 3.2 and window server 2008 standard, get error when we try
Khi truy nhập vào menu chức năng:
License Server/Daemon Manager is down. Please check license.log for more information.
access licensing:
Error communicating with License Server. License Server may be down. Please start the License Server, then refresh the page.
Lincense.txt is file log of LMS
Must I have to active window server 2008 first ?
thank you very much ?

Hi ,
--Add the Casuser to the Administrator Group
and then reset the casuser password:
1. Go to CSCOpx\setup\support> and run the following command:
resetCasuser.exe
2. Restart the daemon manager:
Net stop crmdmgtd
Net start crmdmgtd
Let me know how it works
If above did not help then send me the syslog.log and screen shot of the EventViewer with the latest Application Error that you see there.
--also screen shot of the below directory :
NMSROOT\etc\license
Thanks
Afroj

LMS 3.2 CiscoWorks Daemon Manager does not want to startup in Windows Server 2008 64bit?

I need help concerning the CiscoWorks Daemon Manager that does not want to startup.
I keep on getting the Error 1053. I installed the CiscoWorks LMS 3.2 Evaluation.
I just need the CiscoWorks Daemon Manager started up. I know a solution was posted but the link is invalid.
This was the thread which I found:
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=Network%20Management&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cd47f8d/0#selected_message
Could somebody please assist me in this issue.
Thank You
Irvin

Try the below:
1. Select Control Panel -> System and Maintenance -> System.
2. On the left pane, choose Advanced system settings.
3. Under Performance section, choose Settings.
4. Click the Advanced tab.
5. Under Virtual memory section, click Change.
6. Clear the "Automatically manage paging file size for all drives" checkbox.
7. Then Click Custom and specify at least 2048 MB for the min, and at least 4095 MB for the max.
8. Confirm the services are setup correctly. In Windows, go to Start and click on 'Run...'. Type in services.msc and make sure you have the
following services set like this, change accordingly if not:
CiscoWorks ANI database engine: Manual
CiscoWorks Daemon Manager: Automatic
CiscoWorks RME NG database engine: Manual
CiscoWorks Tomcat Servlet Engine: 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
10. Reboot after and see if this brings daemons up.

Cisco Prime LMS 4.1, "License Server/Daemon Manager is down."

Hello,
We having problem with Cisco Prime LMS running version 4.1.
When open Home page shows the next message: "License Server/Daemon Manager is down. Please check license.log for more information." (see attached)
The daemon server is stopped already and i can't restart it, see below:
C:\>net start crmdmgtd
The Cisco Prime Daemon Manager service is starting.
The Cisco Prime Daemon Manager service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
Thanks

It looks like you're seeing CSCte49301. Follow the release note steps to solve this:
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.

LMS 3.2 CiscoWorks Daemon Manager does not startup

When trying to start CiscoWorks Daemon Manager i get the following message:
"The CiscoWorks Daemon Manager service on local computer started and the stoped. Some services stop automatically if they are not in use by other services or programs."
I have tring starting the service from DOS also and get:
E:\Program Files\CSCOpx\setup\support>net start crmdmgtd
The CiscoWorks Daemon Manager service is starting.
The CiscoWorks Daemon Manager service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
resting the casuser pasword also did not help.
Anyone know of a solution?

Hi
That was the initial problem, we did increase the swap file space and still get an error. See the errors on the 22nd..
Dec 22 07:20:33 127.0.0.1 dmgtd: Http is the port in ssl.properties file and apacheflags to be set is -d E:\PROGRA~1\CSCOpx\MDC\Apache
Dec 22 07:20:33 127.0.0.1 dmgtd: PX_PROTOCOL in registry http
Dec 22 07:20:33 127.0.0.1 dmgtd: Apache Args in registry -d E:\PROGRA~1\CSCOpx\MDC\Apache
Dec 22 07:20:33 127.0.0.1 dmgtd: PX_PROTOCOL in md.properties file is http
Dont know if this means anything to you :-)

Daemon manager lms 3.2 starts and dies

Similar Messages

Maybe you are looking for