10-08-2009 10:30 AM
The error is a result of attempting to update the Default Device Credentials in Ciscoworks LMS v3.2. Should I proceed to open a TAC case?
Solved! Go to Solution.
10-08-2009 12:01 PM
The hostname in NMSROOT/lib/classpath/md.properties, NMSROOT/MDC/etc/regdaemon.xml, and the output of the hostname command must all match (case is not important).
10-08-2009 11:05 AM
10-08-2009 11:16 AM
Per article, it pertains to a multiserver & certificate set-up, thus,neither are applicable to the set up on our server. FYI....we recently upgrade to v3.2 from v3.01 a few weeks ago.
10-08-2009 11:18 AM
The issues with hostname and anti-virus on-access scanning are valid either in a single-server setup.
10-08-2009 11:43 AM
ok, I'll take a look at anti-virus, however, what about the hostname? Because the hostname on the server has not changed. Unless, the upgrade may have modified the hostname. Would that be possible? Is there somewhere in CSCOpx that I can verify the hostname?
10-08-2009 12:01 PM
The hostname in NMSROOT/lib/classpath/md.properties, NMSROOT/MDC/etc/regdaemon.xml, and the output of the hostname command must all match (case is not important).
10-12-2009 01:14 AM
I have the same problem on all my LMS-installations.
One is a multi-server-installation, the others are single-server.
All installations are LMS 3.2
I get this error sometimes and after restart of all processes it works for a random time.
I checked the hostname and they are all right.
Anti-virus is not installed on the servers.
Which logfiles are important for that problem?
Thanks a lot!
10-12-2009 05:30 AM
Please start a new thread for your issue.
10-12-2009 08:56 AM
I think DEP may be causing this too. (Windows Data Execution Prevention)
You can view the DEP configuration for your computer in System in Control Panel.
To do this, follow these steps:
1. Click Start, click Run, type sysdm.cpl, and then click OK.
2. Click the Advanced tab, and then under Performance, click Settings.
3. In the Performance Options dialog box, click the Data Execution Prevention tab.
10-12-2009 08:59 AM
DEP is a known problem, but I haven't seen it cause this. It is recommended one turn on DEP only for critical Windows processes.
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