Orchestrator Installation failed: SetWindowsAuthentication

Help Orchestrator
, ,
1

Hi everyone,

I tried installing the Orchestrator, unfortunately during the installation I got an error. After checking the log files, the following error occurs:

=== Logging stopped: 27.09.2018 12:00:11 ===
MSI (c) (F0:E8) [12:00:11:430]: Note: 1: 1708
MSI (c) (F0:E8) [12:00:11:430]: Product: UiPath – Installation failed.

MSI (c) (F0:E8) [12:00:11:430]: Windows Installer installed the product. Product Name: UiPath. Product Version: 18.1.2.0. Product Language: 1033. Manufacturer: UiPath. Installation success or error status: 1603.

MSI (c) (F0:E8) [12:00:11:430]: Grabbed execution mutex.
MSI (c) (F0:E8) [12:00:11:430]: Cleaning up uninstalled install packages, if any exist
MSI (c) (F0:E8) [12:00:11:430]: MainEngineThread is returning 1603

Or more detailed, the step “SetWindowsAuthentication” fails:

Action 11:59:58: Orchestrator_SetWindowsAuthentication.
MSI (s) (DC:74) [11:59:58:425]: Executing op: CustomActionSchedule(Action=Orchestrator_SetWindowsAuthentication,ActionType=3073,Source=BinaryData,Target=WixQuietExec,CustomActionData=“C:\WINDOWS\SysWOW64\inetsrv\appcmd” set config “UiPathOrchestrator2018.1” /section:windowsAuthentication /enabled:true)
MSI (s) (DC:74) [11:59:58:425]: Creating MSIHANDLE (2218) of type 790536 for thread 7540
MSI (s) (DC:60) [11:59:58:425]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI5356.tmp, Entrypoint: WixQuietExec
MSI (s) (DC!08) [11:59:58:550]: Creating MSIHANDLE (2219) of type 790531 for thread 9736
WixQuietExec: ERROR ( message:Configuration error
MSI (s) (DC!08) [11:59:58:550]: Closing MSIHANDLE (2219) of type 790531 for thread 9736
MSI (s) (DC!08) [11:59:58:550]: Creating MSIHANDLE (2220) of type 790531 for thread 9736

Does anyone have an idea what might be wrong?

Thanks a lot in advance!

2

On which OS are you running? 2nd were you able to set the domain for the windowsauthentication? Do you have a screenshot on where you fail? Maybe i can try to reproduce the problem, although i dont have any problems on 2012/2016 Windows Systems

Did you check/install all the prerequisites before starting the installation?

3

The Problem was that the user did not have the right to run as a batch job.

2 Likes