Coexisting with Previous Versions

Logging Level - Minimum

The Minimum logging level logs events, which include the success or failure of adding or removing a user account, errors that occur when establishing LDAP sessions, and errors that occur when updating the directory. When you select this logging level, None logging level events are also logged.

In addition to the None logging level events, the following events are logged when the logging level is set to Minimum:

Message Event ID Explanation User Action
The service is starting. 8003 Informational message only. No user action required.
The service is stopping. 8004 Informational message only. No user action required.
The service received an unsupported request. 8005 The Service Control Manager has returned an invalid request. If the problem persists, create a new Connection Agreement.
LDAP Search of directory <directory name> at base '<value>' using filter '<value>' was unsuccessful. Directory returned the LDAP error: [0x<error code>] <error code> 8020 If the accompanying LDAP message refers to LDAP_OTHER, the directory service may be out of disk space. Check network connectivity. Verify that the user name, password, and port address are correct, and try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
LDAP Modify on directory <directory name> for entry '<entry name>' was unsuccessfull with error: [0x<error code>] <error code> 8022 If the accompanying LDAP message refers to LDAP_OTHER, the directory service may be out of disk space. Check network connectivity. Verify that the user name, password, and port address are correct, and then try again. If the problem persists, verify that the remote Exchange server is configured to support LDAP.
LDAP Delete on directory <directory name> for entry '<entry name>' was unsuccessful with error: [0x<error code>] <error code> 8023 Check network connectivity. Verify that the user name, password, and port address are correct, and try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
LDAP Search Initial Page on directory <directory name> at base '<value>' with filter '<value>' was unsuccessful. Directory returned the LDAP error: [0x<error code>] <error code> 8024 Check network connectivity. Verify that the user name, password, and port address are correct, and try again. If the problem persists, verify that the remote Exchange server is configured to support LDAP.
LDAP Get Next Page call on directory <directory name> for pagesize <value>, was unsuccessful with error: [0x<error code>] <error code> 8025 Check network connectivity. Verify that the user name, password, and port address are correct, and then try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
LDAP Bind was unsuccessful on directory <directory name> for distinguished name '<value>'. Directory returned error: [0x<error code>] <error code>. <Connection Aggreement> 8026 LDAP allows you to query and manage directory information using a TCP/IP connection. Check network connectivity. Verify that the user name, password, and port address are correct, and then try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
The LDAP Bind to the global catalog on <server name> for distinguished name '<recipient name>' was unsuccessful. The Directory returned error: [0x<value>] <value> The Active Directory Server that the ADC binds to must be a global catalog. Please correct the configuration, or promote the Active Directory Server to be a global catalog. 8027 Either promote the Active Directory server to which the Connection Agreement points to a global catalog, or modify the Connection Agreement to point to a global catalog.
LDAP ModifyRDN on directory <directory name> for entry '<entry name>' was unsuccessful with error: [0x<error code>] <error code> 8028 If the accompanying LDAP message refers to LDAP_OTHER, the directory service may be out of disk space. Check network connectivity. Verify that the user name, password, and port address are correct, and then try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
LDAP Extended result on directory <directory name> for entry '<entry name>' was unsuccessful with error: [0x<error code>] <error code> 8030 Informational message only. No user action required.
Unable to open LDAP session on directory '<directory name>' using port number <value>. Directory returned the LDAP error: [0x<error code>] <error code> 8031 LDAP allows you to query and manage directory information using a TCP/IP connection. Check network connectivity. Verify that the user name, password, and port address are correct, and then try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
LDAP search result on directory <directory name> for entry '<entry name>' was unsuccessful with error: [0x<error code>] <error code> 8033 If the accompanying LDAP message refers to LDAP_OTHER, the directory service may be out of disk space. Check network connectivity. Verify that the user name, password, and port address are correct, and then try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
Successfully modified entry '<entry name>' on directory <directory name>. 8035 Informational message only. No user action required.
Successfully added new entry '<entry name>' on directory '<directory name>'. 8038 Informational message only. No user action required.
LDAP Unbind on directory <directory name> was unsuccessful. Directory returned error: [0x<error code>] <error code> 8054 If the accompanying LDAP message refers to LDAP_OTHER, the directory service may be out of disk space. Check network connectivity. Verify that the user name, password, and port address are correct, and then try again. If the problem persists, verify that the remote server running Exchange is configured to support LDAP.
Stopped replication for Connection Agreement '<Connection Agreement>'. 8058 Synchronization was canceled No user action required.
The Connection Agreement '<value>' on directory <directory name> could not be loaded due to an error. Make sure that the Connection Agreement is configured properly. 8070 There may be a network problem, or you may not have the appropriate permissions to perform this operation. Check network connectivity. If you do not have the appropriate permissions, ask someone with administrative permissions to modify them. If the error persists, restart the server running Exchange.
Object has no attributes, object is: <object name>, destination object is: <object name> 8095 The attribute tree is empty or all attributes in the attribute map are turned off. If all attributes in the attribute map are turned off, turn them on.
The authentication package value (<value>) is not supported on server <server name>. Check the Connections tab on the Connection Agreement. 8112 The type of authentication being used is not supported on the specified server. The credentials can not be processed. On the Connections tab of the Connection Agreement, modify the authentication options for logging onto the Windows 2000 server, and then try again. Verify that the directory service on the remote server is running. Possible options are: Basic using SSL, NTLM, and NTLM using SSL. Check the port number.
The Connection Agreement '<value>' has been signaled to start replication immediately. 8116 Informational message only. No user action required.
The entry with distinguished name '<value>' will not be written to the directory because it is missing the following mandatory attributes: '<attributes>' 8121 Add the required attributes, and make sure the attributes are enabled in the schema map.
The entry with distinguished name '<value>' will not be written to the directory because it has invalid attributes: '<attributes>' 8122 ADC could not write the proposed attributes to the directory. Disable the invalid attributes in the schema map.
The entry with distinguished name '<value>' will not be written to the directory because it is trying to delete the mandatory attributes: '<attributes>' 8123 ADC cannot remove the attribute specified because it is required to exist by the target directory. No user action required.
This version of ADC cannot run the Connection Agreement '<value>'. Either upgrade ADC on this server, or change the ADC service on the General tab to a different server. 8137 Make sure that the Connection Agreement was created using the Windows 2000 version of ADC. ADC cannot run Connection Agreements created by other versions ADC.
The server '<server name>' is not available. Check for network problems and make sure that the server is running. All directory updates to or from the server can not be replicated unless the server is available. 8138 Follow the advice in the message.
An operation on server '<server name>' returned [0x<error code>] <error code>. The Connection Agreement <Connection Agreement> stopped. 8145 Restart the service. Check for sufficient disk space and memory. Check that the target directory and source directories are running.
Synchronization summary for Connection Agreement '<value>' --- %n [Destination Server: <server name>] %n [Start Time: <value>] %n [End Time: <value>] %n [Number of entries processed successfully: <value>] %n [Number of adds: <value>, Number of modifications: <value>] %n [Number of entries failed: <value>] 8147 Informational message only. No user action required.
The directory schema on server '<service name>' is missing the following attribute types required for Connection Agreement '<Connection Agreement name>' to work properly: '<Connection Agreement name>'. Make sure that the directory service on '<server name>' was restarted after the Connection Agreement was created. If it was, either the Connection Agreement is not configured properly or the directory service on the server was re-installed after the Connection Agreement was setup. Please re-create the Connection Agreement. 8148 Follow the advice in the error message.
Unable to create or open the transaction file '<file name>' for writing a deleted entry. If the file exists, make sure that it's writable by the ADC service, else make sure that the parent directory is writable and that the disk is not full. 8149 The transaction file is in the same directory in which ADC is installed. User account and passwords are shown on the Connection tab in the Connection Agreement Properties dialog box. Make sure that these credentials allow writing, that the file is writable, and that the disk is not full.
The Connection Agreement '<value>' has paused the replication after <number> seconds. The replication will resume in <number> seconds. 8150 Informational message only. No user action required.
The Connection Agreement '<value>' is resuming its replication. 8151 Informational message only. No user action required.

Related Topics

Understanding Event Logging Catagories and Levels Choose Which Replication Events to Log