Edit

Share via

Table-valued parameter errors after Microsoft Entra Connect is installed on Windows Server 2019

This article describes a problem in which synchronization errors appear after Microsoft Entra Connect is installed on Windows Server 2019-based servers.

Original product version:  Microsoft Entra ID, Windows Server 2019

Symptoms

You experience one or more of various symptoms, such as password hash sync failures or receiving "staging-error" discovery errors during the import cycle (shown in the following screenshot).

Screenshot of Synchronization Service Manager that shows a staging error.

When this problem occurs, Event ID 6301 is logged in the server Application log, as follows:

Log Name: Application
Source: ADSync
Date: 8/22/2019 11:11:17 PM
Event ID: 6301
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: AADConnect.contoso.com
Description: The server encountered an unexpected error in the synchronization engine:

"BAIL: MMS(7996): ..\sql.cpp(7524): 0x80004005 > (Unspecified error)
**BAIL: MMS(7996): x:\bt\1011518\repo\src\dev\sync\server\sqlstore\rcvtvp.h(158): 0x80004005 (Unspecified error)**
**BAIL: MMS(7996): x:\bt\1011518\repo\src\dev\sync\server\sqlstore\rcvtvp.h(52): 0x80004005 (Unspecified error)**
BAIL: MMS(7996): ..\sproc.cpp(1124): 0x80004005 (Unspecified error)
BAIL: MMS(7996): ..\csobj.cpp(15789): 0x80004005 (Unspecified error)
BAIL: MMS(7996): ..\tower.cpp(10511): 0x80004005 (Unspecified error)
BAIL: MMS(7996): x:\bt\1011518\repo\src\dev\sync\server\sqlstore\csobj.h(1379): 0x80004005 (Unspecified error)
BAIL: MMS(7996): ..\csobj.cpp(1368): 0x80004005 (Unspecified error)
BAIL: MMS(7996): ..\nscsimp.cpp(531): 0x80004005 (Unspecified error)
BAIL: MMS(7996): ..\syncstage.cpp(923): 0x80004005 (Unspecified error)
BAIL: MMS(7996): ..\syncstage.cpp(1666): 0x80004005 (Unspecified error)
BAIL: MMS(7996): ..\syncstage.cpp(414): 0x80004005 (Unspecified error)
Azure AD Sync 1.5.45.0"

This event indicates that an error occurs when Microsoft Entra Connect attempts a read or write operation over the LocalDB database by using table-valued parameters.

For more information about table-valued parameters, see Use Table-Valued Parameters (Database Engine).

Cause

This problem is caused by incompatible language settings for programs that do not support Unicode.

Screenshot of the Region settings where the Use Unicode U T F 8 for worldwide language support option is selected.

The service account defaults to UTF-8 for worldwide language support when it is enabled. The LocalDB database version in Windows Server 2019 does not support this format.

Resolution

To resolve this problem, clear the checkbox next to Beta: Use Unicode UTF-8 for worldwide language support (shown in the previous screenshot), and then restart the server.

To change the setting, follow these steps:

  1. On the Microsoft Entra Connect server, open Control Panel, and then select Clock, Language and Region.

    Screenshot of Control Panel with the Clock, Language, and Region option selected.

  2. Select Region.

    Screenshot of Clock, Language, and Region page with the Region item selected.

  3. Select the Administrative tab, and then select Change System locale.

    Screenshot of the Administrative tab of the Region dialog box with the Language for Non-Unicode Programs area highlighted.

  4. If the Use Unicode UTF-8 for worldwide language support setting is enabled, clear it.

    Screenshot of the Region settings where the Use Unicode U T F 8 for worldwide language support is unselected.

  5. Select OK, and then restart the server.

Contact us for help

If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure feedback community.