02-01-2010 07:04 AM
LMS 3.2 Upgrade from version 3.1
900 devices
When selecting Transport Settings out of Drop down menu it prompts following error codes:
ConfigEditor = DCMA0042
NetConfig = DCMA0042
NetShow = DCMA0042
Transport Settings of Netconfig not changeable.
Saving Settings ends in Error Msg.
"DCMA0045: Could not save new settings. Check dcmaclient.log for details."
When page refreshes afterwards it prompts for a second error code "DCMA0042: Could not read the settings.Check dcmaclient.log for details."
No Error's on Install. Pagefile was at Installation routine not great enough (manually set to 2042MB - 4092MB)
Now set to 4096 both.
Windows Server 2003 Standard Edition x64
it could be that patches were downloaded from Microsoft because it was not deactivated.
Java is showing correct version when checking on Command Line with 1.6.0.3 but on Control Settings java updates were enabled automatically and updated to 1.6.0.18. was uninstalled afterwards again and installed 1.6.0.3 again.
Did somebody alread had this problem after the upgrade?
Log setting on Debug and shows java nullpointer exception.
Or if somebody has database schema where is the Transport Settings are stored? Maybe DB reinitialize would help?
Thanks in regards for your responses
Cheers
Minh
02-01-2010 07:31 AM
Post the dcmaclient.log and the NMSROOT/MDC/etc/regdaemon.xml file.
02-02-2010 12:53 AM
02-02-2010 07:37 AM
Your regdaemon.xml is corrupt. If you have a known good backup of LMS, you will need to restore it to recover this file. Else, you will need to reinstall all of LMS from scratch (and NOT do a restore from backup). It's more than just the protocol order configuration that is damaged. Most of RME will be broken given this file.
02-04-2010 04:29 AM
Hi Joe
thank you for your advice. It's now replaced with one of the pre upgrade versions of the file and this seems to work fine. So it's nw running with a version of 3.1 and not 3.2. Will that cause any problems? VNM is not used actually. That was the first idea what would be a good backup file.
Thanks for your answer
Minh
02-04-2010 05:08 PM
Yes, this will cause huge amounts of problems since it's more than just VNM which changed. You really need a 3.2 version, or you need to reinstall.
If you restore a full 3.1 backup into 3.2, that would also work.
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