The export sync cycle was showing a Stopped server error

AJAY PRAJAPATI 5

Hi All,

We observed Microsoft Entra ID sync with the status last sync less than 3.5 hours,

while troubleshooting on the server, the synchronization service Tool was not responding properly,

also when tried the command: Get-ADSyncSchedular on PowerShell it also didn't show any output,

somehow managed to open the Synchronization service and observed the Contoso.com-AAD (Windows Azure Active Directory(Microsoft) connector was showing in a running state, which should be in an idle state if no sync is running at that movement, whereas the on-prem connector was in idle state,

also in the sync cycle, the export sync cycle was showing a Stopped server, Screenshot 2024-04-22 173422.png, for ref.

any suggestion on what could be the reason and other checks we can perform,

Thank you,

Michael Smith-MSFT 2,831 Reputation points Microsoft Employee

2024-04-22T13:07:04.97+00:00

Hi Ajay,

Thank you for contacting the Q&A Community.

To help us understand the issue

Could you run the following command and screenshot the results?

Import-Module -Name "C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync" -Verbose

get-ADSyncScheduler

Can you go back and check the first sync where stopped server error appeared?

Have you changed the password for your sync account recently?
AJAY PRAJAPATI 5 Reputation points

2024-04-23T06:28:07.96+00:00

Hi Michael,

Thank you for your response :)

I traced down the sync part where the error occurred that was while exporting Screenshot 2024-04-23 113817.png screenshot attached,

at movement when I manually restarted the Microsoft Azure AD sync since then it has been working fine,

No, we haven't changed the password of the sync account.

get-ADSyncScheduler: Screenshot 2024-04-23 114613.png the output

Regarding this command: Import-Module -Name "C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync" -Verbose

Please let me know what it does. is the command to import the Module to run the Azure AD sync commands?

or it will make some changes to the system or environment as the issue occurred on the production Azure AD server hence, hesitating a bit.

if it is not going to make any changes to the current configuration then I can give it a try.

Thank you,

2 answers

AJAY PRAJAPATI 5 Reputation points

2024-04-23T06:26:44.3033333+00:00

Hi Michael,

Thank you for your response :)

I traced down the sync part where the error occurred that was while exporting Screenshot 2024-04-23 113817.png screenshot attached,

at movement when I manually restarted the Microsoft Azure AD sync since then it has been working fine,

No, we haven't changed the password of the sync account.

get-ADSyncScheduler: Screenshot 2024-04-23 114613.png the output

Regarding this command: Import-Module -Name "C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync" -Verbose

Please let me know what it does. is the command to import the Module to run the Azure AD sync commands?

or it will make some changes to the system or environment as the issue occurred on the production Azure AD server hence, hesitating a bit.

if it is not going to make any changes to the current configuration then I can give it a try.

Thank you,
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Michael Smith-MSFT 2,831 Reputation points Microsoft Employee

2024-04-23T07:28:31.5+00:00

Hi Ajay,

Thank you for your update.

The import-module command only imports the powershell module. It does not make any changes to the current configuration. My suggestion to run that command was because in your initial post you mentioned you ran Get-ADSyncSchedular on PowerShell it also didn't show any output.

As its showing the the schedular is running theres no need to run the import-module command.

You need to investigate the delta sync errors before the stopped-server export error.Do you have a staging server?

What version of AD connect do you have installed?
Please sign in to rate this answer.
AJAY PRAJAPATI 5 Reputation points

2024-04-23T11:24:33.0133333+00:00

Hi Michael,

Thank you for the response,Yes, we have the staging server and the current version is 2.3.2.0 and

we have planned to upgrade to the latest MS Entra Connect version on the 25th of April.

Yes, upon reviewing the delta sync error on the sync tool, there are errors related to the service accounts and the common part is an extension attribute1: with noreattestation multiple times Screenshot 2024-04-23 164801.png screenshot for your ref, however, these errors we are observing from a long time.

Thank you

Michael Smith-MSFT 2,831 Reputation points Microsoft Employee

2024-04-23T13:55:26.43+00:00

Hi Ajay,

Can you check your event logs on the sync machine.

Filter the application logs for ADSync and DirectorySynchronization.

You mentioned you manually start the service it works fine.

How long does it work for?

How are you starting the service?

AJAY PRAJAPATI 5 Reputation points

2024-04-24T09:37:18.3266667+00:00

Hi Michael,

I restarted the Azure ADSync service under services.msc, after that the sync started and working as expected now,

just wondered why this happened and to identify the root cause, looking around if someone else had faced the same issue,

checked the event logs as suggested, I found there are a few ADsync errors related to Dn attribute failure,

and unfortunately able to see only the last 2 days' events logs : |

Thank you.

Michael Smith-MSFT 2,831 Reputation points Microsoft Employee

2024-04-24T10:19:59.35+00:00

Hi Ajay,

To find out why it happened we'd need to look at the events before the issue appeared.

If the issue persists i would look at switching over to the staging server and upgrade.

if after that the issue does continue you should raise a support ticket so our engineers can help troubleshoot it.

AJAY PRAJAPATI 5 Reputation points

2024-04-24T10:36:30.9266667+00:00

Hi Michael,

looked into the event logs on a specific day, & no error events were observed at particular times when export sync was stopped, only saw 2 normal events triggered related to MSSQL, (not warning nor error).

Yes, the issue didn't occur again,

we have planned to upgrade the version, let's see how it goes after the upgrade,

if the issue prompts again, will open a case with MS.

Thank you very much for your responses, it means a lot : )
Sign in to comment