RME 4.3.1 can't add new config task

Answered Question
Dec 14th, 2009
User Badges:

hello,


Trying to add a new User Defined Task in a fresh install of LMS 3.2 and am getting "DCMA0055: Error adding the task XXXX".

If I try to modify an existing task that was imported, same task, different parameter, from LMS 2.6. It saves Ok but then I can't create any jobs as the task list pane is empty.


Anyone have this issue?


thanks!

Correct Answer by Joe Clarke about 7 years 3 months ago

It appears the upgrade from LMS 3.1 to 3.2 was not successful.  The RME database schema was not properly converted.  If you still have an LMS 3.1 backup, you can try restoring it as a local Administrator, and after disabling anti-virus.  If not, you will need to reinitialize your RME database using the following command:


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=rmeng dmprefix=RME
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Mon, 12/14/2009 - 13:06
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the netconfigclient.log and dcmaclient.log.

js88888888 Tue, 12/29/2009 - 09:24
User Badges:

Ok, just wanted to follow up. I am seeing a few other things that seem to be similar in nature.

If I try to add an image from device in software repository, no devices show up. Also under RME Device Management, there is nothing listed in RME Devices, Normal Devices, etc.

Do you still need these logs or should I include anything else?


thanks Joe

Correct Answer
Joe Clarke Tue, 12/29/2009 - 09:47
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

It appears the upgrade from LMS 3.1 to 3.2 was not successful.  The RME database schema was not properly converted.  If you still have an LMS 3.1 backup, you can try restoring it as a local Administrator, and after disabling anti-virus.  If not, you will need to reinitialize your RME database using the following command:


NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=rmeng dmprefix=RME
js88888888 Tue, 12/29/2009 - 09:58
User Badges:

Thanks Joe, I had done a 2.6 to 3.2 remote upgrade and figured this was the problem. I will be re-initializing as advised, just to make sure I don't bring over any more issues.

Actions

This Discussion