Knowledgebase: Meeting Maker
Pim login failure
Posted by - NA - on 06 July 2009 10:28 AM
Meeting Maker:

Issue: Pim login failure showing in the Admin Console under User Statistics.

Open the Pim log (nlpim.log) and look for the following errors:

2/28/2007 10:31:27 AM[0][LogonMBox: Login failed, Http status=2009261398]

2/28/2007 10:32:04 AM[0][LogonMbox: processing user: johndoe, deviceSAKey = 135253]

2/28/2007 10:32:04 AM[0][LogonMbox: Pim username: johndoe]

2/28/2007 10:32:04 AM[0][LogonMBox: TearWeb Caused Unknown Error Code 12005]

2/28/2007 10:32:04 AM[0][Display Error caused Cannot create a file when that file already exists.

Resolution:  The Servlet is not configured properly.  Verify that the Tomcat service when communicating to the Meeting Maker server is functioning on the correct port.  By default NotifyLink will connect to the servlet and tomcat via port 8080, however Meeting Maker does have configured ports in which tomcat/servlet will communicate to. 

In order to verify:

  1. Retrieve the comparam.ini file from the Meeting Maker directory. 
  2. Retrieve the MeetingMaker.Properties file which is located in the MM Servlet directory. 
  3. Server IP/DNS, Server Name, and Ports must match within both files.  View the fields in the comparam.ini and verify these fields match in the MeetingMaker.Properties file (edit the MeetingMaker.Properties file to match if applicable). 
  4. Once these changes have been made, Save the MeetingMaker.Properties file.
  5. Restart both the Apache Tomcat service where the Servlet is located, as well as the NLPIMService on the NotifyLink server.