Upgrading LMS 3.2 Issues

Answered Question
Jan 13th, 2010
User Badges:

Just upgraded to LMS 3.2 and now have a few problems, I hope they are all related. One problem is the speed of the application as a whole, but especially managing processes within Common Services.  Almost every page takes longer to load than the previous version, but the managing processes page is terrible.  Sometimes it will take 5 minutes for the page to come up.


That brings me to what I hope the problem is.  I have quite a few processes that I can't get to start.  After looking at what they all had in common, they all depend on EssentialsDM.  When I look at EssentialsDM, it is in the "Waiting to Initialize" process state.  I cannot seem to get this process to start.


I included a copy of my EssentialsDM.log

Correct Answer by Joe Clarke about 7 years 5 months ago

Ah, it appears you have the Windows Remote Management service started.  That service listens at tcp/47001 which is the same port that EssentialsDM requires.  To get around this, shutdown Daemon Manager, then shutdown the Windows Remote Management service.  Delete NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib/ctmregistry*.  Then restart Windows Remote Management.  Then restart Daemon Manager.  The EssentialsDM process should come up.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Wed, 01/13/2010 - 09:55
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Ah, it appears you have the Windows Remote Management service started.  That service listens at tcp/47001 which is the same port that EssentialsDM requires.  To get around this, shutdown Daemon Manager, then shutdown the Windows Remote Management service.  Delete NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/lib/ctmregistry*.  Then restart Windows Remote Management.  Then restart Daemon Manager.  The EssentialsDM process should come up.

Actions

This Discussion

Related Content