nGenius won't allow login after edit of serverprivate.properties

ODNspt · ‎07-23-2002

We are running CW2000 LMS on a Widows 2000 platform, with SP2 installed. During install of NGenius we made sure it was running and we could log in to nGenius, prior to resetting the listening port. We opened the serverprivate.properties file with WordPad to delete the listener port 162, and forgot to clear the "always use this program for this file type" box. The file was saved with devicelistener.portlist=395 as in the install guide. All properties files are now associated with WordPad (previously no association?) and nGenius seems not to be running - certainly can't log in.

Any bright ideas?

rmushtaq · ‎07-24-2002

Any specific reasons as to why would you edit the serverprivate.properties file?. Was there any problems after the RTM isntall that made you change this?. You can try doing a reinit to the db to see if it helps:

http://www.cisco.com/warp/public/477/RTM/rtm_faq.shtml

ODNspt · ‎07-24-2002

The Read Me First for LMS tells you to edit serverprivate.properties and change "devicelistener.portlist=162,395" to "devicelistener.portlist=395" if you have DRF & RTM on the same server. (We have)

We have totally de-installed RTM (&packet decode) and re-installed, (after getting rid of association between wordpad and ".properties" but no difference.

Still can't log in - attempt at login says it can't connect to the database.

rcullum · ‎07-29-2002

When you totally de-installed, did you remove the nGenius directories left behind (uninstall does not remove all components), before re-installing? Additionally, I would strongly recommend you apply the latest consolidated patch after you have initially created the database. Try stopping/restarting the nGenius server and logging in locally.

ODNspt · ‎07-29-2002

Many thanks for the input. We now have nGenius running OK. After re-installing (and having deleted all directories before doing so), my technical team initially tried to log in directly, but then found that while they can't run it from a web browser, they can from inside "Connection". Before the removal of the association between "properties" file type and re-installtion it didn't run in either environment. Odd, but at least we have it sorted out.

Many thanks for the help.

rmushtaq · ‎07-29-2002

This is because of CSCdt62297. Make sure that you install the latest RTM patch from CCO once you re-install RTM again.