Consider the following scenario:
- You are attempting to do a /fullsql installation of DirSync according to the instructions given in the MSDN article here. (/fullsql is needed only when more than 50 000 user, group and/or contact objects will be in scope for synchronization from the local Windows Server AD to the Azure AD/Office 365).
- The SQL server you are attempting to use is running Microsoft SQL Server 2008 SP1 or higher.
- The dirsync.exe /fullsql installation completes without any errors.
- The next step of running Install-OnlineCoexistenceTool with all SQL parameters (UseSQLServer etc) fails with the following error:
Install-OnlineCoexistenceTool : The Synchronization Engine installation
returned error code 1603. Please try the installation again, and if this error
persists, contact Technical Support.
Verbose output also gives:
Install-OnlineCoexistenceTool : The Synchronization Engine install returned
FAIL. See the event logs for more detailed information.
At line:1 char:1
+ Install-OnlineCoexistenceTool -UseSQLServer -SqlServer
+ CategoryInfo : NotSpecified: (Microsoft.Onlin…CoexistenceTool
:InstallOnlineCoexistenceTool) [Install-OnlineCoexistenceTool], DirectorySyncInstallException
+ FullyQualifiedErrorId : 5000,Microsoft.Online.Coexistence.PS.Install.InstallOnlineCoexistenceTool
Install-OnlineCoexistenceTool : The install was unable to setup a required
component. Check the event logs for more information. Please try the
installation again, and if this error persists, contact Technical Support.
In Event Viewer on the server, you can find Error Event ID 1013:
Product: Forefront Identity Manager Synchronization Service — Forefront Identity Manager Synchronization Services requires a running instance of Microsoft SQL Server 2008 SP1 or better. Install the correct SQL Server version and make sure the service is running before installing Forefront Identity Manager Synchronization Service.
Taken that the SQL Server actually is running the said version or above, this error indicates that the SQL Native Client is missing on the server. (This requirement is now documented in the MSDN article, but is often missed as part of the DirSync preparation steps).
To resolve this error, download and install the SQL native client on the DirSync server.
Follow these steps:
- Visit this Microsoft Download Center and find the SQL Server Feature Pack for the version of SQL that you are running (Search for SQL Server version Feature Pack). If you are not sure what exact version of SQL Server you are running, you can always use this link (it is compatible with all versions of SQL that are compatible with DirSync): http://www.microsoft.com/en-us/download/details.aspx?id=44277
- Hit the Download link and select this file: ENU\x64\sqlncli.msi (SQL Native Client).
- Run the sqlncli.msi installer on the server to install the SQL Native Client.
- When installed, run the Install-OnlineCoexistenceTool commands again with your appropriate parameters and the installation/configuration will complete successfully.
The SQL Native Client requirement for DirSync /fullsql is documented on MSDN nowadays, but I still often hear about enterprise DirSync deployments that get’s stuck on this issue – perhaps because the link provided in the MSDN article leads to general information about the SQL Native Client and not an actual download link to the feature needed on the server itself. In AADSync (next generation DirSync), the SQL Native Client is always installed as part of the AADSync installation, but that is not the case with DirSync. As DirSync will be around until the GA of AAD Connect (which will include AADSync), I thought it would be a good idea to post this until then – DirSync is and will be the generally preferred directory synchronization tool as long as it is the tool you get when following the Download link in the Setup Directory Synchronization section of the Office 365/AAD Admin Portal.