Coexisting with Previous Versions

Logging Level - Medium

The Logging level Medium logs events including those associated with the existence of specific objects in the directory and proxy error warnings. When you select this logging level, None and Minimum logging level events are also logged.

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

Message Event ID Explanation User Action
Opening LDAP session to directory <directory name> on port <value>. 8006 Informational message only. No user action required.
Closing LDAP session to directory <directory name>. 8007 Informational message only. No user action required.
Binding to directory <directory name> as user '<user name>'. 8008 Informational message only. No user action required.
Binding to directory <directory name> as service account. 8009 Informational message only. No user action required.
Searching directory <directory name> at base '<value>' using filter '<value>'. 8010 Informational message only. No user action required.
Search of directory <directory name> at base '<value>' returned <value> objects. 8012 Informational message only. No user action required.
Adding entry '<entry name>' to directory <directory name>. 8013 Informational message only. No user action required.
Modifying entry '<entry name>' on directory <directory name>. 8015 Informational message only. No user action required.
Server '<server name>' could not generate e-mail addresses for entry '<entry name>'. Was unsuccessful with error: [0x<error code>] <error code> 8040 The ADC could not contact the System Attendant service on the server running Exchange. Make sure that the domain in which the Exchange server is running has trust with the domain in which the Windows 2000 computer is running, and that the Exchange server's service account is in the same domain as the Windows 2000 computer.
Server '<server name>' could not generate some e-mail addresses for entry '<entry name>'. Was unsuccessful for type(s): <address type name> 8041 A unique e-mail address could not be generated based on the entry name. The service account for the server running Exchange may be in a different domain than the computer running Windows 2000. In the Add-ins or E-Mail Address Generator container, select the connector or address generator being accessed. On the General tab, verify that the specified .dll file is not corrupted and exists in \Exchsrvr\Add-ins or \Exchsrvr\Address in the proper directory on the server.
Found new or changed Connection Agreement '<value>' on directory <directory name>. 8068 Informational message only. No user action required.
Connection Agreement '<value>' was deleted or had its owning service changed on directory <directory name>. Shutting down thread for this Connection Agreement. 8069 Informational message only. No user action required.
The target object '<object name>' was modified after the source object '<object name>' Consequently, the full set of updates will not be applied to the target object. If this warning persists, make sure that the time is set correctly on both the source and target servers. 8139 The service will not replicate changes from the source object to the target object if the target object has been modified more recently than the source object. Make sure that the source and target servers clocks are synchronized.
Delayed processing of group/distribution list: '<value>' 8140 To replicate objects as quickly as possible, distribution lists and groups are delayed until after users, mailboxes, custom recipients, and contacts have been replicated. No user action required.
Changing the relative distinguished name of entry '<entry name>' to '<text>' on directory <directory name>. (Connection Agreement' <Connection Agreement>) 8146 Informational message only. No user action required.
ADC was unable to add the link '<entry name>' to the group '<object name>'. This is because the target group is a global group, and global groups are not allowed to have universal, or domain local groups as members. 8152 By default, ADC creates universal groups. Universal groups can have any object as a member; however, the Windows 2000 administrator can choose to create a global group. Global groups cannot have universal groups or domain local groups as members. Exchange does not have this restriction. If the Windows 2000 global group is to replicate to Exchange, and the Exchange administrator adds a universal group to the global group, the change cannot replicate back to Windows 2000. Consider alternative architectures in which this grouping is not necessary.

Related Topics

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