11-09-2012 11:18 PM
From last 1 month LMS is not coming up.
C:\Documents and Settings\Administrator>net start crmdmgtd
The service is not responding to the control function.
More help is available by typing NET HELPMSG 2186.
-------------------
This one from Event viewer- applications.
Faulting application ccraccess.exe, version 0.0.0.0, faulting module xerces.dll, version 1.5.1.0, fault address 0x00046913.
Solved! Go to Solution.
11-10-2012 01:58 AM
Make sure the antivirus onaccess scan excludes the LMS application. \CSCOpx\ and below. Perhaps reboot the machine.
If that does not help, make sure only the daemon manager service is on automatic. (also TFTP, SYSLOG and RCP services are on auto, but no other LMS services should be)
Another thing might be that the machine run in a domain with policies for local users. These policies mus not apply to the casuser of LMS. If the already have, then you can fix this using the resecasuser.exe in \CSCOpx\setup\suppport\
Cheers,
Michel
11-10-2012 01:58 AM
Make sure the antivirus onaccess scan excludes the LMS application. \CSCOpx\ and below. Perhaps reboot the machine.
If that does not help, make sure only the daemon manager service is on automatic. (also TFTP, SYSLOG and RCP services are on auto, but no other LMS services should be)
Another thing might be that the machine run in a domain with policies for local users. These policies mus not apply to the casuser of LMS. If the already have, then you can fix this using the resecasuser.exe in \CSCOpx\setup\suppport\
Cheers,
Michel
11-13-2012 02:04 AM
Hi MIchel,
I tried all 3 solutions mentioned by you, still same error.
Regards
11-13-2012 03:36 AM
What LMS version do you (try to) run?
Can you post the output of the systeminfo command.
It is possible the hostname of the server has been changed?
Cheers,
Michel
11-13-2012 08:46 PM
Hi,
No changes were done (domain, hostname, ip...nothing was changed).
Systeminfo :
Host Name: XXXXXXXXXXXXXXXXXX
OS Name: Microsoft(R) Windows(R) Server 2003, Standard Edition
OS Version: 5.2.3790 Service Pack 2 Build 3790
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: EndUser
Registered Organization: XXXXXXXXXXXXXXXXXX
Product ID: XXXXXXXXXXXXXXXXXX
Original Install Date: XXXXXXXXXXXXXXXXXX
System Up Time: 0 Days, 18 Hours, 34 Minutes, 42 Seconds
System Manufacturer: HP
System Model: ProLiant DL380 G5
System Type: X86-based PC
Processor(s): 8 Processor(s) Installed.
[01]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
[02]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
[03]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
[04]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
[05]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
[06]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
[07]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
[08]: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3166 Mhz
BIOS Version: HP - 2
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: XXXXXXXXXXXXXXXXXX
Total Physical Memory: 3,326 MB
Available Physical Memory: 2,643 MB
Page File: Max Size: 5,222 MB
Page File: Available: 4,337 MB
Page File: In Use: 885 MB
Page File Location(s): e:\pagefile.sys
Domain: XXXXXXXXXXXXXXXXXX
Logon Server: XXXXXXXXXXXXXXXXXX
Hotfix(s): 269 Hotfix(s) Installed.
[01]: File 1
[02]: File 1
[03]: File 1
[04]: File 1
[05]: File 1
[06]: File 1
[07]: File 1
[08]: File 1
[09]: File 1
[10]: File 1
[11]: File 1
[12]: File 1
[13]: File 1
[14]: File 1
[15]: File 1
[16]: File 1
[17]: File 1
[18]: File 1
[19]: File 1
[20]: File 1
[21]: File 1
[22]: File 1
[23]: File 1
[24]: File 1
[25]: File 1
[26]: File 1
[27]: File 1
[28]: File 1
[29]: File 1
[30]: File 1
[31]: File 1
[32]: File 1
[33]: File 1
[34]: File 1
[35]: File 1
[36]: File 1
[37]: File 1
[38]: File 1
[39]: File 1
[40]: File 1
[41]: File 1
[42]: File 1
[43]: File 1
[44]: File 1
[45]: File 1
[46]: File 1
[47]: File 1
[48]: File 1
[49]: File 1
[50]: File 1
[51]: File 1
[52]: File 1
[53]: File 1
[54]: File 1
[55]: File 1
[56]: File 1
[57]: File 1
[58]: File 1
[59]: File 1
[60]: File 1
[61]: File 1
[62]: File 1
[63]: File 1
[64]: File 1
[65]: File 1
[66]: File 1
[67]: File 1
[68]: File 1
[69]: File 1
[70]: File 1
[71]: File 1
[72]: File 1
[73]: File 1
[74]: File 1
[75]: File 1
[76]: File 1
[77]: File 1
[78]: File 1
[79]: File 1
[80]: File 1
[81]: File 1
[82]: File 1
[83]: File 1
[84]: File 1
[85]: File 1
[86]: File 1
[87]: File 1
[88]: File 1
[89]: File 1
[90]: File 1
[91]: File 1
[92]: File 1
[93]: File 1
[94]: File 1
[95]: File 1
[96]: File 1
[97]: File 1
[98]: File 1
[99]: File 1
[100]: File 1
[101]: File 1
[102]: File 1
[103]: File 1
[104]: File 1
[105]: File 1
[106]: File 1
[107]: File 1
[108]: File 1
[109]: File 1
[110]: File 1
[111]: File 1
[112]: File 1
[113]: File 1
[114]: File 1
[115]: File 1
[116]: File 1
[117]: File 1
[118]: File 1
[119]: File 1
[120]: File 1
[121]: File 1
[122]: File 1
[123]: File 1
[124]: File 1
[125]: File 1
[126]: File 1
[127]: File 1
[128]: File 1
[129]: File 1
[130]: File 1
[131]: File 1
[132]: File 1
[133]: File 1
[134]: File 1
[135]: File 1
[136]: File 1
[137]: File 1
[138]: File 1
[139]: File 1
[140]: File 1
[141]: File 1
[142]: File 1
[143]: File 1
[144]: File 1
[145]: File 1
[146]: Q147222
[147]: KB2416451 - QFE
[148]: KB933854 - QFE
[149]: KB953298 - QFE
[150]: KB979907 - QFE
[151]: KB975558_WM8
[152]: KB925398_WMP64
[153]: KB971513 - Update
[154]: KB2079403 - Update
[155]: KB2115168 - Update
[156]: KB2121546 - Update
[157]: KB2141007 - Update
[158]: KB2229593 - Update
[159]: KB2259922 - Update
[160]: KB2264107 - Update
[161]: KB2296011 - Update
[162]: KB2345886 - Update
[163]: KB2347290 - Update
[164]: KB2360937 - Update
[165]: KB2378111 - Update
[166]: KB2387149 - Update
[167]: KB2388210 - Update
[168]: KB2393802 - Update
[169]: KB2416451 - Update
[170]: KB2419635 - Update
[171]: KB2423089 - Update
[172]: KB2440591 - Update
[173]: KB2443105 - Update
[174]: KB2443685 - Update
[175]: KB2476687 - Update
[176]: KB2478960 - Update
[177]: KB2478971 - Update
[178]: KB2479628 - Update
[179]: KB2482017 - Update
[180]: KB2483185 - Update
[181]: KB2485376 - Update
[182]: KB2621440 - Update
[183]: KB923561 - Update
[184]: KB933854 - Update
[185]: KB938464 - Update
[186]: KB942763 - Update
[187]: KB948496 - Update
[188]: KB948881 - Update
[189]: KB950762 - Update
[190]: KB950974 - Update
[191]: KB951066 - Update
[192]: KB951698 - Update
[193]: KB951748 - Update
[194]: KB952004 - Update
[195]: KB952069 - Update
[196]: KB952954 - Update
[197]: KB953298 - Update
[198]: KB954155 - Update
[199]: KB954211 - Update
[200]: KB954600 - Update
[201]: KB955069 - Update
[202]: KB955839 - Update
[203]: KB956390 - Update
[204]: KB956572 - Update
[205]: KB956744 - Update
[206]: KB956802 - Update
[207]: KB956803 - Update
[208]: KB956841 - Update
[209]: KB956844 - Update
[210]: KB957095 - Update
[211]: KB957097 - Update
[212]: KB958215 - Update
[213]: KB958644 - Update
[214]: KB958687 - Update
[215]: KB958690 - Update
[216]: KB958869 - Update
[217]: KB959426 - Update
[218]: KB960225 - Update
[219]: KB960714 - Update
[220]: KB960715 - Update
[221]: KB960803 - Update
[222]: KB960859 - Update
[223]: KB961118 - Update
[224]: KB961501 - Update
[225]: KB967715 - Update
[226]: KB967723 - Update
[227]: KB968389 - Update
[228]: KB969059 - Update
[229]: KB970430 - Update
[230]: KB971029 - Update
[231]: KB97103
Network Card(s): 1 NIC(s) Installed.
[01]: HP NC373i Multifunction Gigabit Server Adapter
Connection Name: XXXXXXXXXXXXXXXXXX
DHCP Enabled: No
IP address(es)
XXXXXXXXXXXXXXXXXX
When the problem started intially, solution was just to stop and start the service, if that doesn't work restarting the machine was enough.
Now after restart it is like this even after 24 hrs.
Regards
11-14-2012 12:59 AM
This indicates some services do start.
Can you post a 'pdshow -brief' so we can see which ones?
Cheers,
Michel
11-14-2012 01:07 AM
You seem to be running a very old version of LMS. Can you tell me hich version?
Can you do an ipconfig, find the hostname it displays and run the command below wit that hostname
NMSROOT\bin\perl NMSROOT\bin\resolver.pl
to see if this name is resolvable.
Cheers,
Michel
12-14-2012 08:31 PM
Sorry for replying late. You are right, version is quite old, it is somewhat in 3.
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>E:\Progra~1\CSCOpx\bin\resolver.pl mus-cms-005.pcd.pdo.pd
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>pdshow -brief
ERROR: connect to dmgtd process on "127.0.0.1" on port 42340 failed:
C:\Documents and Settings\Administrator>
pd-show error is menioned here, after executing the 1st command, the resolver.pl file was displayed.
Regards
12-16-2012 09:40 AM
The output of the pdshow says the the daemon manager is not listening.
Can you take a screenshot of the services, so we can see what ciscoworks services are running.
How much free space do you have on the different drives?
The command to test the resolver is this:
E:\Progra~1\CSCOpx\bin\perl.exe E:\Progra~1\CSCOpx\bin\resolver.pl mus-cms-005.pcd.pdo.pd
It should reply with the hostname and IP address
So you are sure E:\Progra~1\CSCOpx\ is exclude from the onaccess scan?
Cheers,
Michel
12-16-2012 08:37 PM
Free space on root is more than 4GB, on other it is more than 60 GB. When E:\Progra~1\CSCOpx\bin\perl.exe was executed, nothing was displayed, I could perl.exe getting started in task manager, but nothing. For the relover.pl command, resolver.pl pops up, without any hostname and IP address
Yes that path is exculded.
Regards
12-16-2012 10:42 PM
The first thing I notice is that all services you show in the screenshot are on 'automatic'. That won't work.
Only the ciscoworks daemon manager, TFTP, SYSLOG and RCP should be on automatic.
Running perl by itself gives no output, hence the resolver.pl and the hostname are part of the command you should give.
If you type perl -v on a command promt (dos box) what do you see?
In that same dosbox type ping mus-cms-005.pcd.pdo.pd. Show us the results.
Cheers,
Michel
12-18-2012 02:57 AM
Regards
12-19-2012 12:46 AM
OK so name resolution works. That is not your issue then.
Did you fix the services issue? Are the services on manual now?
Cheers,
Michel
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide