Azure AD Connect Installation that Stopped Working After Reboot

Azure AD Connect Installation that Stopped Working After Reboot

Hybrid Identity, the partnership among Active Listing and Azure Ad, has benefitted from many advancements in Azure Advertisement Hook up. For the wide vast majority of companies with Hybrid Identification, Azure Ad Hook up supplies the synchronization section of the Hybrid Identification story and can also engage in a vital position in the authentication portion of it.

With the Azure Advertisement Hook up v2 launch in July 2022, Microsoft took its absolutely free synchronization solution to the subsequent amount, at least in terms of software package compatibility. Azure Advertisement Connect v2’s SQL Server 2019-based mostly LocalDB option replaced Azure Advert Link v1’s SQL Server 2012 SP4-dependent LocalDB solution and is additional steady, far better performing and also tends to make Azure Advertisement Join completely ready for the upcoming pair of a long time.

On the other hand, the LocalDB resolution also designed Azure Advertisement Hook up installations go tummy up the final few of months . . . .

Around the earlier couple months, I have been acquiring messages from admins whose Azure Advert Link installations stopped working soon after putting in the most current Home windows Server cumulative update. I’ve dug into quite a few of these installations, only to come across that the Azure Advertisement Link-managed LocalDB alternative could not begin any longer following any reboot Azure Advertisement Join did not split for the reason that of the monthly cumulative update the update was just the lead to for the reboot.

Widespread will cause dominated out

There are many prevalent brings about why Azure Advertisement Connect stops performing and/or is no for a longer period supported:

  • The LocalDB instance has developed greater than 10 GB
  • There is insufficient RAM to get started the community DB instance
  • A Team Plan location is stopping Azure Ad Join or its core factors from starting up
  • The Windows Server installation operating Azure Advert Hook up was upgraded in-place
  • The service account’s permissions or account transformed or the assistance account’s password expires or is adjusted (as these qualifications are applied to join to the database)

All these brings about were being dominated out as the cause of why the specific instances of Azure Advertisement Link I investigated stopped doing work.

What’s much more, Azure Advert Connect staging manner servers suffered the similar destiny. Restoring Azure Advert Connect from a earlier backup also didn’t help, as Azure Advertisement Link would cease doing the job at the subsequent reboot. Microsoft’s option to uninstall and then reinstall Azure Advertisement Join merely alleviated the dilemma as a few of months down the street the LocalDB occasion would just refuse to commence again . . . “

Tests, tests . . . Is this matter on?

In demo environments, a couple of individuals started off investigating Azure Advert Hook up. This led to the understanding that the result in of the non-starting LocalDB is corruption of the LocalDB instance’s design databases. Didier van Hoye documented the finding in the most element.

In all conditions in which the concern was reproduceable, the same two artifacts can be witnessed:

  1. In the mistake.log file, typically located at C:WindowsServiceProfilesADSyncAppDataLocalMicrosoftMicrosoft SQL Server Nearby DBInstancesADSync2019, the pursuing log strains can be study:

    Mistake: 9903, Severity: 20, State: 1. The log scan quantity (x) passed to log scan in database 'model' is not valid. This mistake may well indicate data corruption or that the log file (.ldf) does not match the details file (.mdf). If this error transpired through replication, re-produce the publication. Normally, restore from backup if the issue benefits in a failure for the duration of startup.

  2. An party is logged in the Software log with Event ID 528:

    EventID528

    Event 528 with supply SQLLocalDB 15. Home windows API connect with WaitForMultipleObjects returned mistake code: 575. Windows process mistake information is: Software Mistake The application was unable to start out accurately (0x%lx). Click on Alright to close the application. Reported at line: 3714.

Microsoft also investigated the problem. With 30 million businesses working with Azure Ad Hook up, this difficulty was also raised with them by admins at the close of their ropes.

The induce

The SQL workforce at Microsoft have discovered the root cause of the issue. The difficulty is triggered by a software program error in the backup logic that produces an inconsistent point out in the SQL Server product database begin webpage.

After a backup takes place, the model database is set to Comprehensive restoration method (dbi_position == 0x40010000), and the dbi_dbbackupLSN (the log sequence selection for the database backup) is established to a worth that factors to a log file.

The genuine restoration method that is ruled by the learn database is Very simple. In Easy recovery manner, databases logs are truncated routinely. In contrast, in Full recovery method, logs are truncated only immediately after a backup.

When the LocalDB occasion is restarted immediately after the log file is truncated, it detects a backup log sequence selection which is earlier than the earliest log file. Hence, it would not start out the support.

The remedy

If you practical experience this situation, you can have your Azure Advertisement Connect installation performing all over again with these techniques, working with an elevated Windows PowerShell:

  1. Cease the Microsoft Azure Ad Sync support:

    Set-Service ADSync -StartupType Disabled

    Cease-Support ADSync -power

  2. Duplicate above the acknowledged-excellent product databases template:

    Copy-Merchandise "C:Method FilesMicrosoft SQL
    Server150LocalDBBinnTemplatesmodel.mdf"
    "C:WindowsServiceProfilesADSyncAppDataLocalMicrosoftMicrosoft SQL Server Nearby DBInstancesADSync2019"

    Duplicate-Product “C:Plan FilesMicrosoft SQL
    Server150LocalDBBinnTemplatesmodellog.ldf”
    “C:WindowsServiceProfilesADSyncAppDataLocalMicrosoftMicrosoft SQL Server Local DBInstancesADSync2019”

  3. Start the Microsoft Azure Advert Sync service:

    Established-Services ADSync -StartupType Automatic
    Start out-Provider ADSync

The place of Azure Advertisement Connect’s support profile ("C:WindowsServiceProfilesADSyncAppDataLocalMicrosoftMicrosoft SQL Server Community DBInstancesADSync2019") could be unique in your problem. The earlier mentioned support profile is for a Microsoft Azure Advertisement Sync service that operates as the NT SERVICEADSync digital services account (vSA). This is the default account to operate the support. If you run the company as yet another account or as a team Managed Services Account, change the account name in the provider profile place earlier mentioned.

To no more time expertise this issue, up grade Azure Advert Hook up to model 2.1.1., as the Azure Advert Link crew have additional logic to this edition of Azure Ad Connect to stop the difficulty from taking place.

Lively Directory Checking and Reporting

Active Directory is the foundation of your Hybrid Identification, and the composition that controls access to the most significant means in your business. The ENow Energetic Listing Monitoring and Reporting device uncovers cracks in your Active Listing that can cause a protection breach or inadequate conclude-person working experience and permits you to speedily identify and eliminate end users that have inappropriate obtain to privileged teams (Schema Admins, Area Directors). When ENow is not an auditing program, our reviews cut down the amount of money of work necessary to go over HIPAA, SOX, and other compliance audits.