Coexisting with Previous Versions

Logging Level - None

The None logging level is the default logging level. It logs only critical events and error events, which include starting and stopping the service and component installation.

The following events are logged when the logging level is set to None:

Message Event ID Explanation User Action
The service was started. 8001 Notification message. The initialization process has completed successfully. No user action required.
The service was stopped. 8002 The Service Control Manager has returned this request. The service was shutdown successfully. This message requires no action and is informational only. If the service is shut down unexpectedly because of errors, start the service manually. If the service does not start, check the event log with Event Viewer for more details about related errors.
LDAP Add on directory <directory name> for entry '<entry name>' was unsuccessful with error:[0x<error code>] <error code> 8021 If the accompanying Lightweight Directory Access Protocol (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.
Could not open LDAP session to directory '<server name>' using local service credentials. Cannot access Connection Agreement configuration information. Make sure the server '<server name>' is running. 8062 ADC could not gain access to the Windows 2000 domain controller. Make sure ADCs service account has permissions to read its configuration information from Active Directory.
Could not read the root entry on directory '<directory name>'. Cannot access configuration information. 8063 Unable to read the directory's root entry or its attributes. Verify network connectivity. Attempt to read attributes on the directory.
Could not read entry '<entry name>' on directory <directory name>. Cannot access Connection Agreement information. Make sure that ADC was installed properly. 8064 ADC could not find its service object. Make sure the ADC service account has permissions to read its configuration information from Active Directory.
Could not search under entry '<entry name>' on directory <directory name>. Cannot access Connection Agreement information. 8065 ADC could not find the Connection Agreements container or does not have permissions to read the container. Make sure the ADC service account has permissions to read its configuration information from Active Directory.
Could not load mapping table. 8084 Verify that the ADC account has permission to read the Connection Agreements and all of their attributes. If so, restart your computer and try again. If you still get this message, create a new Connection Agreement.
The service could not be initialized because the necessary file <file name> could not be found. Make sure that the operating system was installed properly. 8113 Could not find the file, or the DllMain entry point returned an error upon loading the DLL. Check the file version and verify that its location is in your executable path.
The service could not be initialized because the necessary entry point '<value>' could not be found in the file <file name>. Make sure that the operating system was installed properly. 8114 Could not find the file or the entry point within the file to initialize this service. Check the file version and verify that its location is in your executable path.
The Win32 API call '<Procedure number>' returned an error. The service could not be initialized. Make sure that the operating system was installed properly. 8115 This is an operating system level error. Follow the advice in the message.
Could not locate the import container <value>. Make sure that the configured container exists, or that the account in the Connection Agreement has permissions to access the container. Replication stopped for this Connection Agreement. 8117 Follow the advice in the message.
Could not locate the export container <value>. Make sure that the configured container exists, or that the account in the Connection Agreement has permissions to access the container. Replication stopped for this Connection Agreement. 8118 Follow the advice in the message.
Processing of the Connection Agreement '<value>' has been stopped due to an invalid configuration. Check the event log for more information. 8124 This message follows a previous, related message. That message usually indicates a missing import or export container, or that the Connection Agreement was created or modified by a different version of ADC. Correct the information on the Connection Agreement.
The operating system has run out of resources. The Connection Agreement will shut down and then restart. If this problem persists, try restarting ADC or the server. 8141 Other applications running on the system share resources. This is a Windows-level error that indicates a shortage of resources for all applications. Follow the advice in the error message. Reduce the load on resources by restricting unnecessary applications from running on the server.
ADC threw an unexpected exception. 8142 Restart the service. Verify that enough disk space and memory is available.
ADC threw an out of memory exception. 8143 Increase the swap file size, close some of the other applications that are running, or restart the service.
Exception <value> was raised at address <value>. 8144 Restart the service. Verify that there is enough disk space and memory.

Related Topics

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