Showing results for 
Search instead for 
Did you mean: 

LMS3.0 upgrade - webserver access issue

Just upgraded from LMS2.6 to 3.0. Not able to login to application via browser. Have changed https port to no avail. Apache is running as are all LMS services as per Cisco doco. Any ideas?


Accepted Solutions
Joe Clarke
Hall of Fame Cisco Employee

Okay. Based on what I've seen of your configuration, you should be able to restart dmgtd, and everything should now work:

net stop crmdmgtd

net start crmdmgtd

View solution in original post

Joe Clarke
Hall of Fame Cisco Employee

What error do you get trying to login?

The error is the standard "internet explorer cannot display the webpage" . The address box changes to http://lms_netmgr:1741/CSCOnm/servlet/login/login.jsp

Joe Clarke
Hall of Fame Cisco Employee

Please post screenshots of your Services control panel, the output of pdreg -l Apache, the output of "set" from a DOS prompt, the outpu of pdshow, the NMSROOT\MDC\etc\regdaemon.xml file, and the NMSROOT\MDC\Apache\logs\error.log. If the data in these outputs is too sensitive to post, then please open a TAC service request with all of this information.

See attached pdreg, set, pdshow - others to follow

See attached regdaemon.xml, error.log

My services screenshot uploads are being blocked at present due to size and if I change to .zip for file type. Is there something specific you want me to check there?

Joe Clarke
Hall of Fame Cisco Employee

Please zip them, and send them.

I also notice quite a few problems in what you've sent so far. The biggest being that DCRServer is in a waiting to initialize state. This could be due to a certificate problem. Based on your screenshots, I should be able to give you some steps to correct the problem, but I would now also like to see the NMSROOT\MDC\tomcat\logs\stdout.log.

See attached stdout.log

See attached Services screenshot page 1

See attached Services screenshot page 2

Joe Clarke
Hall of Fame Cisco Employee

The problem points to the SSL port, 1050 according to your regdaemon.xml, not being properly bound. The Apache error.log mentions 1026, so I will need to see NMSROOT\MDC\Apache\conf\httpd.conf to see what is actually configured.

Thanks, I think a few attempted changes have muddied the picture here so I have attached fresh copies of some of the files.

I suspect that when using v2.6 we were using the standard https port however as we have IIS running we changed the port to 1026 during the upgrade. Apache would not run with this port hence the errors in the error.log file. We have since changed the port and Apache now runs. The latest files have the port as 1150. sorry about any confusion

Fresh copy of Apache error.log

Joe Clarke
Hall of Fame Cisco Employee

Okay, this looks a little better. However, I would like to see the new pdreg output as well as the NMSROOT/lib/classpath/ file, the new stdout.log, and the NMSROOT/lib/classpath/