Right-click the Call Stack Information box, click Select All, and then select Copy. This trace provides debug-level information for the error. To see the actual error, select Stack Trace. (In the preceding figure, the error string is sync-rule-error-function-triggered.) You are first presented with an overview of the object. When you have errors, Synchronization Service Manager shows both the object in error and the error itself as links that provide more information. If you have objects with errors, those errors show up under the Synchronization Errors heading. Select the links to get a list of the changed objects. Under the Synchronization Statistics heading, you can find more information about the number of changes that were processed. The domain name can be found under the heading Partition. This list appears only if you have multiple domains in your forest and each domain is represented by a step. On the far-left side of this area, you might have a list titled Step #. When you select a row, the bottom of the Operations tab is updated to show the details of that run. Don't investigate warnings until you have addressed errors. If you have errors, this message is usually only a symptom. The run finished, but some data is not in the expected state. The run finished, but there are errors (fewer than 5,000) that should be investigated. The run was automatically stopped due to the large number of errors. This might happen, for example, if the remote system is down and cannot be contacted.
Here's a quick summary of the most common statuses in order of investigation priority (where * indicates several possible error strings). The Status column contains the most important information and shows the most severe problem for a run. You can change the sorting by clicking the headers. Look for any run that does not show a success status. By default, the operations log keeps information about the last seven days, but this setting can be changed with the scheduler. The top half of the Operations tab shows all runs in chronological order. This tab shows the results from the most recent operations. The Operations tab in Synchronization Service Manager is where you should start your troubleshooting. Start Synchronization Service Manager before you begin these steps. The metaverse to find data-related problems.The connector space to find missing objects and synchronization errors.The operation logs to find errors identified by the synchronization engine during import and synchronization.To find the errors, look at a few different places, in the following order: The outbound synchronization rules move data from MV to CS.Įxport to AD: After syncing, objects are exported from the Active Directory CS to Active Directory.Įxport to Azure AD: After syncing, objects are exported from the Azure AD CS to Azure AD. The inbound synchronization rules bring in data from CS to MV. To view the synchronization rules, go to the Synchronization Rules Editor from the desktop applications. Synchronization: Inbound synchronization rules and outbound synchronization rules are run in the order of precedence number, from lower to higher. Import from Azure AD: Azure AD objects are brought into the Azure AD CS. Import from AD: Active Directory objects are brought into the Active Directory CS. The syncing process involves following steps: CS: Connector space, a table in a database.Synchronization processīefore we investigate syncing issues, let’s understand the Azure AD Connect syncing process: For Azure AD Connect deployment with version 1.1.749.0 or higher, use the troubleshooting task in the wizard to troubleshoot object syncing issues.
0 kommentar(er)
