none
Unable to configure Azure AD Connect tool on new Windows Server 2012 Datacenter VM

    Question

  • Hi, Greetings for the day! 

    We are trying to configure Azure AD Connect tool on Windows Server 12 Datacenter VM (on client network) to sync profiles from on-premise AD to Azure AD. Tool has been installed successfully. When we try to configure sync with Custom Installation or Express Settings approach, configuration fails with the following errors in event viewer and configuration log. We are using an account with Enterprise admin privileges, an account with global admin privileges on Office365. And its a fresh configuration on new VM. We have tried uninstall/reinstall Azure AD Connect software, but no luck.  

    Please look into the issue and let us know the steps to resolve the issue.

    Thanks in advance!

    Thanks

    -Srini

    Error in Synchronization Service_Install-XXX.log:

    MSI (s) (EC:94) [15:03:22:005]: Executing op: ActionStart(Name=ConfigDB,Description=Configuring SQL database,)
    MSI (s) (EC:94) [15:03:22:005]: Executing op: CustomActionSchedule(Action=ConfigDB,ActionType=9217,Source=BinaryData,Target=**********,CustomActionData=**********)
    MSI (s) (EC:44) [15:03:22:005]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI5953.tmp, Entrypoint: ConfigDB
    CustomAction ConfigDB returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    03/14/2017 15:03:25.780 [3564]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
    03/14/2017 15:03:25.780 [3564]: Detailed info about C:\Windows\assembly\tmp\EZU0IWE9\Microsoft.MetadirectoryServices.Host.dll
    03/14/2017 15:03:25.780 [3564]:  File attributes: 00000080
    03/14/2017 15:03:25.811 [3564]:  Restart Manager Info: 1 entries
    03/14/2017 15:03:25.811 [3564]:   App[0]: (3564) Windows Installer (msiserver), type = 3
    03/14/2017 15:03:25.811 [3564]:  Security info:
    03/14/2017 15:03:25.811 [3564]:   Owner: S-1-5-18
    03/14/2017 15:03:25.811 [3564]:   Group: S-1-5-18
    03/14/2017 15:03:25.811 [3564]:   DACL information: 4 entries:
    03/14/2017 15:03:25.811 [3564]:   ACE[0]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-18
    03/14/2017 15:03:25.811 [3564]:   ACE[1]: Type = 0x00, Flags = 010, Mask = 001f01ff, SID = S-1-5-32-544
    03/14/2017 15:03:25.811 [3564]:   ACE[2]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-5-32-545
    03/14/2017 15:03:25.811 [3564]:   ACE[3]: Type = 0x00, Flags = 010, Mask = 001200a9, SID = S-1-15-2-1
    MSI (s) (EC:94) [15:03:25:827]: Note: 1: 2265 2:  3: -2147287035
    MSI (s) (EC:94) [15:03:25:827]: User policy value 'DisableRollback' is 0
    MSI (s) (EC:94) [15:03:25:827]: Machine policy value 'DisableRollback' is 0
    Action ended 15:03:25: InstallExecute. Return value 3.

    Errors in Event Viewer:

    Error #1

    Exception: Execution failed with errorCode: 1603.

    Details:

    Error #2

    SynchronizationServiceSetupTask:InstallCore - Caught unexpected exception. Details Microsoft.Azure.ActiveDirectory.Synchronization.Framework.ProcessExecutionFailedException: Exception: Execution failed with errorCode: 1603.

    Details:
       at Microsoft.Azure.ActiveDirectory.Synchronization.Framework.ProcessAdapter.StartProcessCore(String fileName, String& processOutput, String arguments, String workingDirectory, NetworkCredential credential, Boolean loadUserProfile, Boolean hideWindow, Boolean waitForExit, Boolean traceArguments)
       at Microsoft.Azure.ActiveDirectory.Synchronization.Framework.ProcessAdapterCallerBase.TypeDependencies.StartBackgroundProcessAndWaitForExit(String fileName, String arguments, String workingDirectory, NetworkCredential credential, Boolean loadUserProfile)
       at Microsoft.Azure.ActiveDirectory.Synchronization.Framework.MsiExecAdapter.InstallMsiPackage(String msiPackageDirectory, String msiPackageFileName, String packageOptions, String installationPath, NetworkCredential credential, String installLogFileName, Boolean extractOnly, Boolean quiet, Boolean suppressReboot)
       at Microsoft.Azure.ActiveDirectory.Synchronization.Setup.SynchronizationServiceSetupTask.InstallSynchronizationService(String pathToMsiFiles, String msiFileName, String installationPath, String sqlServerName, String sqlInstanceName, Boolean useInstallPathForDBFiles, IDictionary`2 syncServiceGroups, NetworkCredential syncServiceAccountCredential, String logFilePath)
       at Microsoft.Azure.ActiveDirectory.Synchronization.Setup.SynchronizationServiceSetupTask.InstallCore(String logFilePath, String logFileSuffix)

    Error #3

    Error installing msi package 'Synchronization Service.msi'. Please look at log 'C:\ProgramData\AADConnect\Synchronization Service_Install-20170314-112715.log' for more details

    Error #4

    Windows Installer installed the product. Product Name: Microsoft Azure AD Connect synchronization services. Product Version: 1.1.443.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

    Error #5

    Product: Microsoft Azure AD Connect synchronization services -- Installation operation failed.

    Error #6

    Faulting application name: MsiExec.exe, version: 5.0.9200.21523, time stamp: 0x557c2cd5
    Faulting module name: RPCRT4.dll, version: 6.2.9200.21826, time stamp: 0x56fd54f0
    Exception code: 0xc0000005
    Fault offset: 0x0000000000016797
    Faulting process id: 0x89c
    Faulting application start time: 0x01d29cd776265eeb
    Faulting application path: C:\Windows\System32\MsiExec.exe
    Faulting module path: C:\Windows\system32\RPCRT4.dll
    Report Id: b9ef0cf7-08ca-11e7-93f9-005056a44d83
    Faulting package full name:
    Faulting package-relative application ID:

    Error #7

    RemoveSqlLocalDbInstance: Error while removing database ADSync. This may be expected. Details: Microsoft.Azure.ActiveDirectory.Synchronization.Framework.ProcessExecutionFailedException: Exception: Execution failed with errorCode: 1.
    Details: Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Named Pipes Provider: Could not open a connection to SQL Server [2]. .
    Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login timeout expired.
    Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

       at Microsoft.Azure.ActiveDirectory.Synchronization.Framework.ProcessAdapter.StartProcessCore(String fileName, String& processOutput, String arguments, String workingDirectory, NetworkCredential credential, Boolean loadUserProfile, Boolean hideWindow, Boolean waitForExit, Boolean traceArguments)
       at Microsoft.Azure.ActiveDirectory.Synchronization.Framework.ProcessAdapterCallerBase.TypeDependencies.StartBackgroundProcessAndWaitForExit(String fileName, String arguments, String workingDirectory, NetworkCredential credential, Boolean loadUserProfile)
       at Microsoft.Azure.ActiveDirectory.Synchronization.Framework.SqlCmdAdapter.ExecuteCommand(String arguments, NetworkCredential credential)
       at Microsoft.Azure.ActiveDirectory.Synchronization.Setup.SynchronizationServiceSetupTask.<>c__DisplayClass16.<RemoveSqlLocalDbInstance>b__15()

    Friday, March 17, 2017 2:55 PM

All replies

  • We need more information to troubleshoot this further. Recommend you to create a technical support ticket to work closely with the support engineers and get a quick resolution to your issue.

    Here is the link https://docs.microsoft.com/en-in/azure/azure-supportability/how-to-create-azure-support-request to create support case.

    Monday, March 20, 2017 5:59 PM
    Moderator
  • Hi Sadiqh Ahmed, Greetings for the day!

    Thanks for quick updates!

    We had created a ticket with MPN support last week(03/16). Few support engineers verified the issue,  but it has not been resolved yet. They are still working on it.

    Meanwhile, I posted the issue here to get some help from other experts who has experience on this kind of issues. 

    Please let me know if you have come across this kind of issue any time and possible reasons.

    Thanks

    -Srini

    Tuesday, March 21, 2017 1:43 PM
  • Could you share the SR # with us?
    Tuesday, March 21, 2017 6:19 PM
    Moderator
  • Here is the SR#117031515459441.

    Tuesday, March 21, 2017 8:59 PM