Severity INFO
Description LDAP has started.
Impact None - informational
Recovery Action Not applicable
Technical Support Action Not applicable
Severity INFO
Description LDAP has stopped.
Impact None - informational
Recovery Action Not applicable
Technical Support Action Not applicable
Severity MAJOR
Description In order to start the service, two OS resources are required:an event (MS API: CreateEvent) and a thread (MS API: _beginthread). If one of them could not be created, the system will not start.
Impact LDAP server will not run, CallPilot Manager will not be usable.
Recovery Action Check for unnecessary applications and close them. Attempt to restart the CallPilot Server. If the problem persists, contact your Customer Service Representative.
Technical Support Action Try increasing the size of virtual memory.
Severity MAJOR
Description In order to retrieve the "slapd.conf" files (normally located in d:\nortel\data), the full file name should be retrieved (MS API: GetModuleFileName). If the retrieval is not possible, this error is generated.
Impact LDAP server will not run, CallPilot will not function.
Recovery Action Contact your Customer Service representative.
Technical Support Action Obtain all configuration files (slapd.at.conf, slapd.conf, slapd.oc.conf, slapd.odbc.conf) for the installed server version. Copy them into the main data directory, then restart the server. Determine whether the files are corrupt or missing and why.
Severity MAJOR
Description LDAP could not process data in its configuration files.
Impact LDAP server will not run, CallPilot will not function.
Recovery Action Contact your Customer Service representative.
Technical Support Action Obtain all configuration files (slapd.at.conf, slapd.conf, slapd.oc.conf, slapd.odbc.conf) for the installed server version. Copy them into the main data directory, then restart the server. Determine whether the files are corrupt or missing and why.
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: "BlueMaple-ODBC"
Impact LDAP server will not run, CallPilot will not function.
Recovery Action Contact your Customer Service representative.
Technical Support Action Obtain all configuration files (slapd.at.conf, slapd.conf, slapd.oc.conf, slapd.odbc.conf) for the installed server version. Copy them into the main data directory, then restart the server. Determine whether the files are corrupt or missing and why. If problem is not resolved, contact Product Support.
Severity MAJOR
Description The LDAP connection to the database could not be established.
Impact LDAP server will not run, CallPilot will not function.
Recovery Action Contact your Customer Service representative.
Technical Support Action Obtain all configuration files (slapd.at.conf, slapd.conf, slapd.oc.conf, slapd.odbc.conf) for the installed server version. Copy them into the main data directory, then restart the server. Determine whether the files are corrupt or missing and why. If problem is not resolved, contact Product Support.
Severity MAJOR
Description An exception has been handled by LDAP.
Impact Should have no impact, but may be related to other events or unexplained errors.
Recovery Action If this error appears frequently, contact your Customer Service representative.
Technical Support Action Restart and monitor server. If error continues, contact Product Support.
Severity MAJOR
Description An unsupported data type has been found in the database. Your database cannot be used by LDAP.
Impact Some LDAP searches will fail. This may prevent components of CallPilot from functioning.
Recovery Action Contact your Customer Service representative.
Technical Support Action Refer to database documentation. Run utility to verify that the database is valid.
Severity MAJOR
Description An ODBC error has occurred.
Impact An LDAP operation has failed. This may prevent components of CallPilot from functioning.
Recovery Action Ensure the database service is running. If it is, contact your Customer Service representative.
Technical Support Action Contact product support.
Severity MAJOR
Description The user address book is now out of date.
Impact Any access to the address book could display out of date addressing information, specifically, network prefixes that have just been changed will not be updated.
Recovery Action Repeat the recent network configuration change(s). If this error appears again, contact your Customer Service representative. If the error does not appear again, the problem has been resolved.
Technical Support Action Contact product support.
Severity MAJOR
Description A component was not notified of a change to the database.
Impact The specified component now has out of date configuration information. This could cause improper operation of CallPilot features.
Recovery Action Repeat any recent configuration change. If this error happens again, contact your Customer Service representative. If your configuration change is easy to resave and this error does not reappear, then there should be no further problems.
Technical Support Action Refer to the support tool documentation for the problem component to refresh any cache. Stop and restart the problem service. Attempt to duplicate the configuration change that caused this error. If this error is reproducible, contact product support.
Severity MINOR
Description A mailbox has been disabled, likely due to too many login attempts with the wrong password.
Impact The specified mailbox is now disabled.
Recovery Action Verify correct user is trying to login and take appropriate action.
Technical Support Action Not applicable
Severity MINOR
Description The remote user record has been deleted from the data base but failed to delete the record for that remote user from MMFS. The MMFS record will be kept in db until the-patch tool is executed.
Impact Delete commands for MMFS records failed.
Recovery Action Contact Customer Support.
Technical Support Action Run the is-patch tool from support tools.
Severity MAJOR
Description There was a mailbox conflict for this user during migration from Meridian Mail to CallPilot.
Impact User was not added during migration from Meridian Mail to CallPilot.
Recovery Action This event occurs is during migration from Meridian Mail to Call Pilot. Add user after migration.
Technical Support Action This event occurs is during migration from Meridian Mail to CallPilot. Add user after migration. Contact product support.
Severity MAJOR
Description RPL name cannot be a duplicate.
Impact The entry is not added during migration from Meridian Mail to CallPilot.
Recovery Action This event occurs is during migration from Meridian Mail to CallPilot. Add an entry with a different RPL name that is unique.
Technical Support Action This event occurs during migration from Meridian Mail to CallPilot. Add an entry with a different RPL name that is unique or contact product support.
Severity MAJOR
Description Location server is allowed without networking code.
Impact Code is not migrated.
Recovery Action This event occurs during migration from Meridian Mail to CallPilot. Check if given code has to be added after migration.
Technical Support Action This event occurs during migration from Meridian Mail to CallPilot. Check if networking code has to be added after migration or contact product support.
Severity MAJOR
Description Location server is allowed with dial plan error.
Impact Dial plan may not work.
Recovery Action This event occurs during migration from Meridian Mail to CallPilot. Check if given dial plan has to be added/modified after migration.
Technical Support Action This event occurs during migration from Meridian Mail to CallPilot. Check if given dial plan has to be added/modified after migration or contact product support.
Severity MAJOR
Description Customer profile has migrated or restored with a name dial prefix conflict.
Impact The old name dial prefix is lost.
Recovery Action This event occurs during migration from Meridian Mail to CallPilot or during the Restore. Correct the name dial prefix.
Technical Support Action Not applicable