SfB Server 2015 (KB4464355) could not be installed. Error code 1603.

While installing the Skype for Business Server 2015 CU8 on the Edge Server we had the following error:

In the Server.msp-SFBEDGE01-[2019-01-24][10-36-34]_log:

MSI (s) (C0:B4) [10:37:04:023]: Executing op: CustomActionSchedule(Action=CA_InstallDBonPatchInstall,ActionType=3073,Source=BinaryData,Target=ExecuteCommand,CustomActionData=powershell -noprofile -command ” & Install-CsDatabase -Update -DatabaseType Registrar -Verbose “|C:\Windows\system32\\WindowsPowerShell\v1.0\powershell.exe|C:\Windows\system32\)
MSI (s) (C0:B4) [10:37:04:027]: Creating MSIHANDLE (10878) of type 790536 for thread 4788
MSI (s) (C0:20) [10:37:04:027]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI665.tmp, Entrypoint: ExecuteCommand
MSI (s) (C0!24) [10:37:10:516]: Creating MSIHANDLE (10879) of type 790531 for thread 3876

MSI (s) (C0!24) [10:37:10:516]: Product: Skype for Business Server 2015, Edge Server — Error 29024. Error 0x80004005 (Unspecified error) occurred while executing command ‘C:\Windows\system32\\WindowsPowerShell\v1.0\powershell.exe’. For more details, check log file ‘C:\Users\ADMINI~1\AppData\Local\Temp\LCSSetup_Commands.log’.

And in the LCSSetup_Commands.log:

Install-CsDatabase : Command execution failed: The network path was not found.

The issue was the Remote Registry Service was Disabled:

We then temporary configured the service to Manual and Start it:

Back to the Cumulative Update Installer to retry the installation:

The update should complete without issues:

If required we can change back the Remote Registry Service back to Disabled after installing the update:

6 thoughts on “SfB Server 2015 (KB4464355) could not be installed. Error code 1603.

  1. Hello,

    I had the same error, but Remote Registy was started.
    I solved the issue extending disk because SQL needs 32Gb of free diskspace.
    After have extended the disk the update was applied successful

    Regards
    Andy L.

  2. Unable to complete the installation of Skype for Business Server 2019

    Error Message from Server.msp—————————-
    RegisterPerfmon: Converting DLL path to short format: C:\Program Files\Skype for Business Server 2019\Server\Core\McuFactoryPerf.ini
    RegisterPerfmon: RegisterPerfmon running command: ‘lodctr “C:\PROGRA~1\SKYPEF~1\Server\Core\MCUFAC~1.INI”‘
    RegisterPerfmon: Entering RegisterPerfmon in C:\Windows\Installer\MSIBAF3.tmp, version 3.10.2516.0
    RegisterPerfmon: Converting DLL path to short format: C:\Program Files\Skype for Business Server 2019\Server\Core\DataCollectionPerf.ini
    RegisterPerfmon: RegisterPerfmon running command: ‘lodctr “C:\PROGRA~1\SKYPEF~1\Server\Core\DATACO~1.INI”‘
    RegisterPerfmon: Entering RegisterPerfmon in C:\Windows\Installer\MSIBBCF.tmp, version 3.10.2516.0
    RegisterPerfmon: Converting DLL path to short format: C:\Program Files\Skype for Business Server 2019\Server\Core\SLAPerf.ini
    RegisterPerfmon: RegisterPerfmon running command: ‘lodctr “C:\PROGRA~1\SKYPEF~1\Server\Core\SLAPerf.ini”‘
    RegisterPerfmon: Entering RegisterPerfmon in C:\Windows\Installer\MSIBC6C.tmp, version 3.10.2516.0
    RegisterPerfmon: Converting DLL path to short format: C:\Program Files\Skype for Business Server 2019\Server\Core\BusyOptionsPerf.ini
    RegisterPerfmon: RegisterPerfmon running command: ‘lodctr “C:\PROGRA~1\SKYPEF~1\Server\Core\BUSYOP~1.INI”‘
    RegisterPerfmon: Entering RegisterPerfmon in C:\Windows\Installer\MSIBD09.tmp, version 3.10.2516.0
    RegisterPerfmon: Converting DLL path to short format: C:\Program Files\Skype for Business Server 2019\Server\Health Agent\RtcHealthAgentPerf.ini
    RegisterPerfmon: RegisterPerfmon running command: ‘lodctr “C:\PROGRA~1\SKYPEF~1\Server\HEALTH~1\RTCHEA~1.INI”‘
    CustomAction CA_ExtendExpirationTimer returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    ——————– End Error Message from Server.msp ———————–
    failure code 1603
    Error returned while installing Server.msi, code 1603. Error Message: A fatal error occurred during installation. For more details please consult log at C:\Users\Administrator.LYNC\AppData\Local\Temp\ApplyPatch-Server.msp-[2018_05_31][12_19_50].log or contact support.

    could you help me to sort out this issue?

    1. The detailed error information will be in the log file: C:\Users\Administrator.LYNC\AppData\Local\Temp\ApplyPatch-Server.msp-[2018_05_31][12_19_50].log
      Look for 1603 then check what actions were executed before the error.

  3. MSI (s) (48:B4) [12:20:12:829]: Windows Installer installed an update. Product Name: Skype for Business Server 2019, Front End Server. Product Version: 7.0.2046.116. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Skype for Business Server 2019 (KB4506173). Installation success or error status: 1603.

    MSI (s) (48:B4) [12:20:12:829]: Note: 1: 1729
    MSI (s) (48:B4) [12:20:12:829]: Product: Skype for Business Server 2019, Front End Server — Configuration failed.

  4. Hi,
    Here the error logs

    C:\Users\Administrator.LYNC> Get-CsAdDomain -Domain Lync.com -GlobalSettingsDomainController feserver.Lync.com
    WARNING: Get-CsAdDomain failed.
    WARNING: Detailed results can be found at
    “C:\Users\Administrator.LYNC\AppData\Local\Temp\Get-CsAdDomain-48ee6a7b-2817-491e-b474-f5eac7318bb8.html”.
    Get-CsAdDomain : Command execution failed: Message-“The LDAP server is unavailable.” LdapError-“ServerDown”
    “Lync-feserver.Lync.com”:”389″
    At line:1 char:1
    + Get-CsAdDomain -Domain Lync.com -GlobalSettingsDomainController Lync- …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [Get-CsAdDomain], SuitabilityDirectoryException
    + FullyQualifiedErrorId : ProcessingFailed,Microsoft.Rtc.Management.Deployment.GetDomainStateCmdlet

    1. That looks like an issue connecting to the domain controller, is there any firewall between front end and the DC?
      I would recommend to open a MS Support ticket to have a look on this issue.

Leave a Reply to Andy L. Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.