Export (0) Print
Expand All

Event IDs and Error Codes for Directory Synchronization Tool 9.1

 

Applies to: Live@edu, Forefront Online Protection for Exchange

Topic Last Modified: 2012-08-21

This topic provides help for Forefront Online Protection for Exchange (FOPE) Directory Synchronization Tool (DST) 9.1 errors and warning events numbered 1300 through 2011. Event ID 1309 or error code 1309, which is a failure to communicate with the sync web service; along with event ID 1310 or error code 1310, which is a general sync failure; are both explained, along with other event IDs. These solutions and links are intended to help only FOPE users. You can troubleshoot FOPE DST errors with this information after the tool has been installed and run, but your synchronization isn’t working as expected.

If this topic doesn’t solve your DST 9.1 issues, you can find more information by using the links in the See Also section at the end of this topic or contact Microsoft Technical Support as noted in Support Information. To contribute your own expertise and enhance the information available about DST 9.1 errors and events, we encourage you to use the five-star rating system at the top of this page to provide feedback and you can also add a new article or update the content of an existing article in the TechNet Wiki.

The following table describes FOPE DST 9.1 event ID codes and possible solutions.

 

Event ID Event Level Message Solution

1300

Error

Critical error occurred

Extended Properties:

Terminating Application: <True/False>

Exception Details: <exception details>

This general error message doesn’t have a direct solution as the details depend on your individual situation. Use the customized Exception Details information in your error message as keywords to search for more help in the TechNet Library, FOPE TechNet Forums, Microsoft Support online content, or contact a support professional directly as described in Support Information.

1302

Error

Sync web service reports that an internal error occurred while processing a request. This might be due to a service issue. Please contact technical support.

Extended Properties:

Error Type: <error type>

Because the synchronization depends on an internet connection to the web-based synchronization service, you cannot complete the synchronization unless the service is available. If the web service itself isn’t available, it could be resolved before the next scheduled synchronization. To confirm the status of the service or if the issue persists during multiple synchronization cycles, contact a support professional directly as described in Support Information.

1303

Error

The username/password combination is not valid.

Supply a username and password that has domain administrator or company administrator privileges in the FOPE Administration Center for the account you are trying to synchronize. You can check this by logging in to the Administration Center and clicking the Users tab, which is under the Administration tab. For more information about user account settings, see User Account Management. It may be necessary to create a user account with adequate access rights for the account that you are trying to synchronize. Keep in mind that it may take some time for your credentials to replicate through all FOPE data centers.

1304

Error

Sync web service operation has timed out. Several retry attempts have failed and the sync process cannot proceed. Please verify that the network connection is healthy and sync backend server is accessible.

Test your connectivity to the web-based synchronization service. To do this, follow these steps:

  1. After you have confirmed your working connections, restart the synchronization service.
  2. To verify your connectivity, open a new browser instance and attempt to connect to the synchronization service by using the following URL: https://sync.messaging.microsoft.com/dirsync91/syncservice.svc

If you cannot connect, make sure that you have local network access. You may have to change the proxy settings that are set in the Directory Synchronization Tool (DST). You can also review the information in Configuring Hosted Services.

When you change the proxy settings, you must restart synchronization. If you still cannot connect, contact a support professional directly as described in Support Information.

1305

Error

Sync web servers are not available. Please make sure that DST is configured with the correct backend server URL and that the URL is accessible from this machine.

Test your connectivity to the web-based synchronization service. To do this, follow these steps:

  1. After you have confirmed your working connections, restart the synchronization service.
  2. To verify your connectivity, open a new browser instance and attempt to connect to the synchronization service by using the following URL: https://sync.messaging.microsoft.com/dirsync91/syncservice.svc

If you cannot connect, make sure that you have local network access. You may have to change the proxy settings that are set in the Directory Synchronization Tool (DST). You can also review the information in Configuring Hosted Services.

When you change the proxy settings, you must restart synchronization. If you still cannot connect, contact a support professional directly as described in Support Information.

1306

Error

The submitted sync data was rejected as invalid by the sync web service. Please review the settings and make sure all the required sync settings are present and valid.

Extended Properties:

Error Type: <error type>

Setting Name: <setting name>

There is no user-configurable data for the DST settings that cause this error. Contact a support professional directly as described in Support Information.

1307

Error

The provided sync user is not allowed to perform the necessary sync operations. Please review your sync settings and save them again. If the user’s permissions have changed consider applying the correct permissions to the sync user.

Extended Properties:

Error Type: <error type>

The user name in FOPE doesn’t have adequate permissions. In order to access all the resources necessary, the local service account and DST synchronization services must be run by using the appropriate network service account. Review the solution provided for error number 1303.

1308

Error

Sync performed an invalid operation and the request was rejected by the backend. This shouldn’t normally happen and can be due to a bug. Restart the sync and if the problem persists, contact support.

Extended Properties:

Error Type: <error type>

This general error message doesn’t have a direct solution as the details depend on your individual situation. Close all applications that are running and repeat the sync procedure. If the problem persists, record the customized information in your error message and contact a support professional directly as described in Support Information.

1309

Error

Communication to Sync Web Service (backend) failed due to a protocol error. This can be a result of network disruption or service unavailability. If the error continues to happen contact technical support.

Test your connectivity to the web-based synchronization service. Restart the synchronization after you have confirmed your working connections. To check your connectivity, open a new instance of your browser and attempt to connect to the synchronization service directly at the following URL: https://sync.messaging.microsoft.com/dirsync91/syncservice.svc.

If this positively connects, restart the DST. If this doesn’t connect, confirm that you have local network access. You can also review the information in Configuring Hosted Services and then restart your synchronization. If you still cannot connect, contact a support professional directly as described in Support Information.

1310

Error

Synchronization failed. Refer to the error at the bottom of this event log and other events logged during the synchronization run for more information.

The service will try to run the synchronization again according to its configured sync interval.

If the error continues to occur, contact a support professional directly as described in Support Information.

1311

Error

An error occurred while trying to identify Active Directory forest and domains.

Extended Properties:

Reason:<reason>

Additional Data: <additional details>

Ensure that the machine account for the computer running the DST client has access to and can query the Active Directory Domain Service. If the error continues to occur, contact a support professional directly as described in Support Information.

1312

Error

Error occurred while querying active directory

Extended Properties:

Result code: <result code>

Error Message: <error message>

Ensure that the machine account for the computer running the DST client has access to and can query the Active Directory Domain Service, that is, ensure that the computer is jointed to the Active Directory Domain. If the error continues to occur, contact a support professional directly as described in Support Information.

2003

Warning

Sync job was forcefully stopped

Extended Properties:

Job Type: <job type>

The directory synchronization was stopped by the local user. To synchronize, restart the service or manually start a synchronization as documented in Sync Now.

2004

Warning

Looks up a localized string similar to Service configuration is missing or incomplete. This could be because:

1. The sync credentials are missing or invalid. Use DST Admin to provide the credentials.

2. The sync configuration settings are missing. Check DST Admin for missing settings.

3. Service can’t communicate with the sync backend due to a network/setup issue. Refer to other events logged prior to this event for more information on what has failed.

The sync job can’t start until the service configuration is available..

Extended Properties:

Job Type: <job type>

Reason: <missing configuration info>

Ensure that you have provided each item listed in the message for this warning. Follow the solution guidance already provided for error 1303 and error 1304.

If you still cannot connect and synchronize, contact a support professional directly as described in Support Information.

2005

Warning

Invalid entries were found while processing active directory objects for synchronization

Extended Properties:

Error Type: <error type>

Invalid entries: <invalid entries>

A proxy address may not be valid.

Ensure that the reported entries are valid SMTP addresses. If entries that are not valid were reported as nonexistent users, check whether they were added to Administration Center. If they were, ignore this warning.

2006

Warning

There has been a significant change in the number of objects during the last sync compared to the data already in the backend. Please verify that this is a known change and the sync is working properly

Extended Properties:

Error Type: <error type>

New Object Count: <count>

Old Object Count: <count>

Confirm that you expected a significant change to the number of users or objects. If you did not, then check the list of users in the FOPE Administration Center and ensure that it is a complete list. If it isn’t, contact a support professional directly as described in Support Information.

2007

Warning

Trying to connect to a known domain controller failed. A new domain controller will be used instead.

Extended Properties:

Domain Name: <domain name>

Old Domain Controller: <domain controller name>

New Domain Controller: <domain controller name>

Verify that the synchronization was completed successfully by checking the FOPE Administration Center user list to confirm that it contains a complete list of users.

2009

Warning

Service communication to Client UI was aborted. Client UI might not show the latest status of the service. Restarting the Admin UI should resolve this issue.

Restart DST. If this warning persists, contact a support professional directly as described in Support Information.

2010

Warning

Could not retrieve the DirSync cookie from Active Directory in a timely manner. DirSync cookie is required for differential syncs. This will not result in data loss or other problems but next sync run on this naming context may be slower than usual.

Domain DN: <domain DN>

If this warning persists, contact a support professional directly as described in Support Information.

2011

Warning

A transient sync exception occurred. Will retry the operation in a few seconds

The following tips can help you troubleshoot Event ID 2011.

  • Verify that the account used to install and run the Directory Synchronization Tool has appropriate permissions to query for users in Active Directory.
  • Verify that port 443 is open on the firewall to allow communications to and from the server on which the Directory Synchronization Tool is installed.
  • Verify that port 8080 isn’t in use on the local computer. To do this in Windows Server 2003 Service Pack 2, run the following command from the command prompt: netstat -a -b > ports.txt. Open the file to view ports used by other applications.
  • Confirm that your proxy server settings are configured correctly in the DST 9.1 Sync Settings section.
  • Check that the system time is configured to synchronize with a known good time source, such as a public NTP server. To check this, run the following from a command prompt: net time. Compare the result to a known good time source.

If this warning persists or causes a synchronization failure, contact a support professional directly as described in Support Information.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft