Lightweight Directory Access Protocol enables desktop messaging and My CallPilot clients to access user information. From these clients, mailbox owners can access CallPilot addresses when they compose messages or manage personal distribution lists.
The CallPilot LDAP server is a Meridian Application Server running as a service.
Severity Major
Description In order to start the service, two operating system resources are required:an event (MS API: CreateEvent) and a thread (MS API: _beginthread). If one of them could not be created, the system would not start. The creation failure reason (as a Windows error) is inserted at the end (as a string).
Impact The LDAP server is not starting. Desktop clients cannot query information about CallPilot users
Recovery Action Check for unnecessary applications running and close them. Attempt to restart the CallPilot LDAP service. If the problem persists, contact Customer Service.
Technical Support Action See Windows errors to get more information about the error type. Increase the size of virtual memory.
Severity Major
Description In order to retrieve the slapd.conf file (for configuration information found in the same place as the program), the full file name for the program should be retrieved (MS API: GetModuleFileName). If the retrieval is not possible, this error is generated.
Impact The LDAP server is not starting. Desktop clients cannot query information about CallPilot users.
Recovery Action Attempt to restart the CallPilot LDAP service. If the problem persists, contact Customer Service.
Technical Support Action See Windows errors to get more information about the error type. Reinstall the LDAP component and reconfigure it. If the problem persists, contact Product Support.
Severity Major
Description The LDAP server is composed of two parts: a front-end and a back-end. The back-end is the interface to the database. At least one back-end must be defined in the slapd.conf file. For CallPilot the following back-end is required: MapleODBC.
Impact The LDAP server is not starting. Desktop clients cannot query information about CallPilot users.
Recovery Action Contact Customer Service.
Technical Support Action Using Notepad, verify the information from the slapd.conf referring to the database field and value. Reinstall the LDAP component and reconfigure it. If the problem persists, contact Product Support.
Severity Major
Description An error was generated when initializing the back-end. The error type was reported in a previous LDAP event code. Almost all the time the error will be database related.
Impact The LDAP server is not starting. Desktop clients cannot query information about CallPilot users.
Recovery Action Contact Customer Service.
Technical Support Action Using Notepad, verify the information from the slapd.odbc.conf (e.g.: database name, user name). Reinstall the LDAP component and reconfigure it. If the problem persists, contact Product Support.
Severity Major
Description The path for the configuration files was not found in the registry. The path is made by resolving two registry values:
LocalMachine\Software\Nortel\Nortel Root (value: d:\nortel)
LocalMachine\Software\Nortel\NMLDAPSRV\ConfigFilesLocation (value: data)
Therefore, the configuration files: slapd.conf, slapd.at.conf, slapd.oc.conf, slapd.odbc.conf will be located at: d:\nortel\data.
Impact The LDAP server is not starting. Desktop clients cannot query information about CallPilot users.
Recovery Action Contact Customer Service.
Technical Support Action Verify the registry entries (check descriptions). Verify if the configuration files exist. If not, reinstall the LDAP component and reconfigure it. If the problem persists, contact Product Support.
Severity Debug
Description This event will be used to report LDAP Trace messages. For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=1'. Note: If eventlog is '0' with 'ldapdebug=1', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report LDAP Packets (commands). For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=2'. Note: If eventlog is '0' with 'ldapdebug=2', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report LDAP command parameters. For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=4'. Note: If eventlog is '0' with 'ldapdebug=4', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report TCP/IP connections. For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=8'. Note: If eventlog is '0' with 'ldapdebug=8', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report BER information (all the LDAP commands are packed in a BER structure to pass over the TCP/IP). For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=16'. Note: If eventlog is '0' with 'ldapdebug=16', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report LDAP filter information (filters are used on search commands). For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=32'. Note: If eventlog is '0' with 'ldapdebug=32', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report configuration messages (when reading the slapd.conf and the associated files). For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=64'. Note: If eventlog is '0' with 'ldapdebug=64', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report acl (access control list) messages. For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=128'. Note: If eventlog is '0' with 'ldapdebug=128', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report LDAP usage information. For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=256'. Note: If eventlog is '0' with 'ldapdebug=256', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report LDAP usage information (for each entry sent as a result of a 'search' command). For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=512'. Note: If eventlog is '0' with 'ldapdebug=512', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report 'shell' messages (not used by CallPilot). For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=1024'. Note: If eventlog is '0' with 'ldapdebug=1024', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report LDIF parsing errors. For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=2048'. Note: If eventlog is '0' with 'ldapdebug=2048', messages are sent only to the NGEN trace window.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Debug
Description This event will be used to report SQL warnings. For this to happen two flags need to be set in slapd.conf: 'eventlog=1' and 'ldapdebug=32768'. Note: If eventlog is '0' with 'ldapdebug=32768', messages are sent only to the NGEN trace window.
Note: Message format: SQL warning: MSG2(NO1) -- MSG3, where:
MSG2: from Microsoft help: SQLSTATE as null-terminated string. For a list of SQLSTATEs, see Appendix A, ODBC Error Codes
NO1: from Microsoft help: Native error code (specific to the data source)
MSG3: the error message text
MSG2, NO1 and MSG3 are generated at the run-time by the OS or ODBC driver
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action If eventlog and ldapdebug have not been modified in the slapd.conf file, call Product Support.
Severity Major
Description This event will be used to report SQL messages.
Note: Message format: SQL error: MSG2(NO1) -- MSG3, where:
MSG2: from Microsoft help: SQLSTATE as null-terminated string. For a list of SQLSTATEs, see Appendix A, ODBC Error Codes
NO1: from Microsoft help: Native error code (specific to the data source)
MSG3: the error message text MSG2, NO1 and MSG3 are generated at the run-time by the OS or ODBC driver
Example: SQL error: IM002(0) -- [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, where:
MSG2: IM002
NO1: 0
MSG3: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. This error is generated when the back-end database is not properly configured (wrong data source name).
Impact The server will not start (if the error is in the configuration file) or the server will not return the requested user information to the desktop client
Recovery Action Attempt to restart the CallPilot LDAP service. If the problem persists, contact Customer Service.
Technical Support Action Verify the configuration in the slapd.conf (the value for the database field) and slapd.odbc.conf (database name, user name).