Description LDAP has started. No Action required
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description LDAP has stopped. No Action required
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description Unable to create required resources to start the LDAP service. In order to start the service, two OS resources are required: 1) an event (MS API: CreateEvent) and 2) a thread (MS API: _beginthread). If one of them could not be created, the system will not start.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description Unable to access configuration files. 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.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description LDAP could not process data in its configuration files.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description No known LDAP back-end was defined. The LDAP server is composed from 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.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description The LDAP connection to the database could not be established.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description An exception has been handled by LDAP.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description An unsupported data type has been found in the database. Your database can not be used by LDAP.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description An ODBC error has occurred.
Recovery Action Ensure the database service is running. If it is, contact your Customer Service representative
Technical Support Action Contact Product Support.
Description The user address book is now out of date. 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 Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description A component was not notified of a change to the database. The specified component now has out of date configuration information. This could cause improper operation of CallPilot features. Refer to the support tool documentation for the problem component.
Recovery Action Contact Customer Service Representative.
Technical Support Action Contact Product Support.
Description A mailbox has been disabled, likely due to too many login attempts with the wrong password.
Recovery Action Enable the mailbox if the attempts were made by the mailbox owner.
Technical Support Action Not applicable
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 until the database utility is-patch tool (in support tools) is executed.
Recovery Action Execute support tool database utility is-patch tool.
Technical Support Action Not applicable
Description There was a mailbox conflict for this user during migration from Meridian Mail to CallPilot or during the restore.
Recovery Action This event is during migration from Meridian Mail to CallPilot or during the restore. Add user after migration or restore.
Technical Support Action Not applicable
Description There was a duplicate RPL Name during migration from Meridian Mail to CallPilot or during the restore.
Recovery Action This event is during migration from Meridian Mail to CallPilot or during the restore. Add entry with different RPL name that is unique.
Technical Support Action Not applicable
Description There was a networking code conflict during migration from Meridian Mail to CallPilot or during the restore. However, the lLocation was still migrated or restored.
Recovery Action This event is during migration from Meridian Mail to CallPilot or during the restore. Check if given code has to be added after migration or restore.
Technical Support Action Not applicable
Description There was a dialing plan configuration error during migration from Meridian Mail to CallPilot or during the restore. However, the location was still migrated or restored.
Recovery Action This event is during migration from Meridian Mail to CallPilot. Check if given dial plan has to be edited after migration.
Technical Support Action Not applicable