See for a possible solution:
AD Connect Sync Error
We are receiving an ADD sync error after migrating to a new server. We imported the JSON file and filled in all the correct credentials, but we are receiving the following:
[11:53:16.200] [ 39] [VERB ] Cleanup: Starting cleanup for task 'Configure AAD Sync'
[11:53:16.200] [ 39] [VERB ] Task 'Configure AAD Sync': No cleanup defined
[11:53:16.200] [ 39] [INFO ] Task 'Deploy AAD Sync' has finished execution
[11:53:16.200] [ 52] [ERROR] Task failed without an exception
[11:53:16.200] [ 52] [VERB ] Cleanup: Starting cleanup for task 'Deploy AAD Sync'
[11:53:16.200] [ 52] [VERB ] Task 'Deploy AAD Sync': No cleanup defined
[11:53:16.200] [ 52] [VERB ] Marking task 'Deploy AAD Health Agent' as Skipped
[11:53:16.200] [ 52] [VERB ] Rolling back task Check Installed Components
[11:53:16.200] [ 52] [VERB ] Task 'Check Installed Components': No rollback defined
[11:53:16.200] [ 52] [VERB ] Rolling back task Setting DesktopSso enablement
[11:53:16.200] [ 52] [VERB ] Task 'Setting DesktopSso enablement': No rollback defined
[11:53:16.200] [ 52] [INFO ] Task 'Single Forest Dir Sync Pwd Sync Root Task' has finished execution
[11:53:16.200] [ 47] [ERROR] An error occurred while sending the request.
Exception Data (Raw): System.Management.Automation.CmdletInvocationException: An error occurred while sending the request. ---> Microsoft.IdentityManagement.PowerShell.ObjectModel.SynchronizationConfigurationValidationException: An error occurred while sending the request.
at Microsoft.DirectoryServices.MetadirectoryServices.UI.WebServices.MMSWebService.ValidateConfigurationParameters(Connector connector)
at Microsoft.DirectoryServices.MetadirectoryServices.UI.WebServices.MMSWebService.CreateConnector(Connector connector, Boolean validate)
at Microsoft.IdentityManagement.PowerShell.Cmdlet.AddADSyncConnectorCmdlet.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
at System.Management.Automation.PowerShell.CoreInvokeHelperTInput,TOutput
at System.Management.Automation.PowerShell.CoreInvokeTInput,TOutput
at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
at Microsoft.Online.Deployment.PowerShell.LocalPowerShell.Invoke()
at Microsoft.Online.Deployment.PowerShell.PowerShellAdapter.TypeDependencies.InvokePowerShell(IPowerShell powerShell)
at Microsoft.Online.Deployment.PowerShell.PowerShellAdapter.InvokePowerShellCommand(String commandName, InitialSessionState initialSessionState, IDictionary`2 commandParameters, Boolean isScript)
at Microsoft.Azure.ActiveDirectory.Synchronization.PowerShellConfigAdapter.ConnectorConfigAdapter.AddConnector(Connector connector)
at Microsoft.Azure.ActiveDirectory.Synchronization.Config.ConnectorAdapterBase.CreateOrUpdateConnectorCore()
at Microsoft.Azure.ActiveDirectory.Synchronization.Framework.ActionExecutor.Execute(Action action, String description)
at Microsoft.Azure.ActiveDirectory.Synchronization.Config.ConnectorAdapterBase.CreateOrUpdateConnector(IEnumerable1 objectClassInclusions, IEnumerable
1 attributeNameInclusions, ParameterKeyedCollection connectorGlobalParameters, Boolean createRunProfile)
at Microsoft.Online.Deployment.Types.Providers.SyncDataProvider.CreateConnectorWithRetry(ConnectorAdapterBase connectorAdapter, IEnumerable1 objectClassInclusions, IEnumerable
1 attributeNameInclusions, ParameterKeyedCollection connectorGlobalParameters, Boolean createRunProfile)
at Microsoft.Online.Deployment.PSModule.Tasks.AADSync.ConfigureAADSyncTask`1.CreateNewConnectors(TContext context)
at Microsoft.Online.Deployment.PSModule.Tasks.AADSync.ConfigureAADSyncTask`1.ConfigureSyncEngine(TContext context)
at Microsoft.Online.Deployment.PSModule.Tasks.AADSync.ConfigureAADSyncTask`1.Execute()
at Microsoft.Online.Deployment.Framework.Workflow.WorkflowTask.ExecuteWrapper()
[11:53:16.203] [ 47] [INFO ] MicrosoftOnlinePersistedStateProvider.Save: saving the persisted state file
[11:53:16.204] [ 47] [INFO ] MicrosoftOnlinePersistedStateProvider.UpdateFileProtection: updating file protection from the persisted state file: C:\ProgramData\AADConnect\PersistedState.xml, isAddProtection: False
[11:53:16.206] [ 47] [INFO ] MicrosoftOnlinePersistedStateProvider.UpdateFileProtection: updating file protection from the persisted state file: C:\ProgramData\AADConnect\PersistedState.xml, isAddProtection: True
[11:53:16.207] [ 47] [INFO ] PerformConfigurationPageViewModel.PerformWorkflowInstallationAndUpdateState: result of installation operations - Failed
[11:53:16.207] [ 47] [ERROR] ExecuteADSyncConfiguration: configuration failed. Skipping export of synchronization policy. resultStatus=Failed
[11:53:16.208] [ 47] [ERROR] PerformConfigurationPageViewModel: We encountered a problem and couldn’t complete the integration.
[11:53:16.208] [ 47] [ERROR] PerformConfigurationPageViewModel: An error occurred executing Configure AAD Sync task: An error occurred while sending the request.
[11:57:50.927] [ 1] [INFO ] Opened log file at path C:\ProgramData\AADConnect\trace-20240731-105817.log
Any help would be appreciated!
Windows for business Windows Client for IT Pros Directory services Active Directory
Microsoft Security Microsoft Entra Other
3 answers
Sort by: Most helpful
-
Andy David - MVP 157.4K Reputation points MVP Volunteer Moderator
2024-07-31T16:35:16.53+00:00 -
Neuvi Jiang 1,540 Reputation points Microsoft External Staff
2024-08-01T07:52:10.7433333+00:00 Hi Gaskill, Scott,
Thank you for posting in the Q&A Forums.
Issues such as "Error performing configuration AAD synchronization task: Error sending request" are usually related to configuration or network issues with Azure Active Directory (AAD) synchronization services such as Azure AD Connect. Here are some steps to troubleshoot and resolve this issue:
Check network connectivity:
Ensure that the server running Azure AD Connect has access to the required ports and URLs for Azure AD.Azure AD Connect requires access to specific IP addresses and ports (such as TCP 443).
Use a tool such as telnet or curl to test the network connection. For example, use curl https://login.microsoftonline.com来检查是否能访问Azure AD's login endpoint.
Check proxy and firewall settings:
If your network environment uses a proxy server or firewall, make sure they are properly configured to allow outbound connections to the Azure AD Connect server.
In Azure AD Connect, you can set up a proxy server in the Connect to Azure AD step of the Configuration wizard.
View Azure AD Connect logs:
Azure AD Connect log files are usually located in trace-*.log files in the %ProgramData%\AADConnect\ directory.
Examine these log files for more detailed error information, which can help you locate the problem more accurately.
Update Azure AD Connect:
Make sure you are using the latest version of Azure AD Connect. Older versions may contain bugs that have been fixed or limitations that do not support new features.
You can check for updates under the Help menu in Azure AD Connect.
Reconfigure Azure AD Connect:
If the problem persists, try reconfiguring Azure AD Connect. before reconfiguring, make sure to back up your existing configuration.
Reconfigure Azure AD Connect using the Quick Setup or Custom Setup wizard to ensure that all settings are correct.
Translated with DeepL.com (free version)
Best regards
NeuviJ
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
-
Gaskill, Scott 15 Reputation points
2024-08-01T13:50:49.4866667+00:00 I found the fix to my problem located here:
After I ran the script and rebooted the server, I was good to go!
Thank you for your replies!