locked
Error 1603 with server.msp while trying to patch Edge-server to 6.0.9319.510 RRS feed

  • Question

  • Hello,

    while patching to the latest CU the Standard FE went fine but on the single Edge Server the CoreComponents are updated from 6.0.9319.281 to .510 but "kb 4036312 Skype for Business Server 2015" is stuck in error 1603.

    Both servers are up and running SfB Server 2015 since early 2015 and were patched since then successfully. This is the first time that something like that happens here. 

    (Of course I did "stop-CsWindowService" before and there is 97GB of 136GB free disk space on C: (the only Volume))

    What I have done so far:

    - reboot many times

    - uninstalled the .510 from windows-Update-list

    - rerun the "Setup or Remove Skype for Business Server Components" in the "Skype for Business Server 2015 – Deployment Wizard"

    No luck so far.

    Folder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
    Property(S): NetHoodFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
    Property(S): OLEAdvtSupport = 1
    Property(S): _97C2FC5BE73C46719B88477974494FC9 = C:\Windows\Installer\a28dd.msp
    Property(S): OutOfDiskSpace = 0
    Property(S): OutOfNoRbDiskSpace = 0
    Property(S): PrimaryVolumeSpaceAvailable = 0
    Property(S): PrimaryVolumeSpaceRequired = 0
    Property(S): PrimaryVolumeSpaceRemaining = 0
    Property(S): REINSTALL = Feature_Server_Edge,Feature_Server_Update,RegistrarStoreUpdate
    Property(S): INSTALLLEVEL = 1
    Property(S): PROPERTY_LOCALGROUPLOCATION = EDGE

    Product: Skype for Business Server 2015, Edgeserver - Update 'Skype for Business Server 2015 (KB4036312)' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\Administrator\AppData\Local\Temp\2\Server.msp-EDGE-[2017-12-16][18-56-34]_log.txt.

    MSI (s) (D0:A0) [18:56:38:832]: Windows Installer installed an update. Product Name: Skype for Business Server 2015, Edgeserver. Product Version: 6.0.9319.510. Product Language: 1031. Manufacturer: Microsoft Corporation. Update Name: Skype for Business Server 2015 (KB4036312). Installation success or error status: 1603.

    MSI (s) (D0:A0) [18:56:38:832]: Note: 1: 1729 
    MSI (s) (D0:A0) [18:56:38:832]: Produkt: Skype for Business Server 2015, Edgeserver -- Fehler beim Konfigurieren.

    MSI (s) (D0:A0) [18:56:38:832]: Windows Installer reconfigured the product. Product Name: Skype for Business Server 2015, Edgeserver. Product Version: 6.0.9319.510. Product Language: 1031. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.

    So I tried to run the "server.msp" alone - but that ends with a message (roughly translated from german):

    "The installed product is not suitable to the installation source. As long as there is no suitable installation source or the the installed product and the installation source are not synchronized this operation can not take effect." (sorry for my translation!)

    This dialogue windows points to "C:\ProgramData\Microsoft\Skype for Business Server\Deployment\cache\6.0.9319.0\setup\" searching for "server.msi" where a server.msi is located, but dated back to April, 2015 which is the same like on the original installation media back to 2015. If I point to that file I get "this is not an allowed installation package for "Skype for Business 2015, Edgeserver"..."

    Any hint is appreciated.

    Thanks - F.One

    Saturday, December 16, 2017 6:34 PM

Answers

  • Finally I was able tp patch the Edgeserver by doing the following:

    - made a HyperV-Snapshot to have an easy rollback option

    - for safety reasons on FrontEnd: "Export-CsConfiguration -FileName "C:\Config.zip" -LocalStore"

    - On EdgeServer: looked in control panel / software which part of SfB server ist patched and which is not: SfB Main Components and UWCA were already .510, SfB Edgeserver still .259 which is from CU5 (May 2017)

    - uninstalled this part, ignoring all warnings and rebooted

    - ran SfB installation wizard Step #2: Install Server and Components

    - rebooted

    - "get-cswindowservice" showed running: REPLICA and RTCCLSAGT, all other were in state "stopped"

    - "stop-cswindowservice", closed SfB shell

    - ran SkypeServerUpdateInstaller.exe successfully

    - now Edgeserver is .510 = CU6 (Dec. 2017)

    I decided to not run "import-CsConfiguration", because the FE and Edge began immediately to talk to each other and so the topolgy changes should be deployed by replicationservice as usual.

    I have no explanation why I could not patch this component from May 6.0.9319.281 directly to .510 and had to go back to .0

    This is odd and nasty and should not happen at all in an otherwise solid running topology.


    • Marked as answer by F.One Monday, December 18, 2017 9:13 PM
    Monday, December 18, 2017 9:13 PM
  • Hi F.One,

    Maybe you can try to reinstall the SfB server and update to the latest CU?


    regards Holger Technical Specialist UC

    • Marked as answer by F.One Monday, December 18, 2017 8:55 PM
    Sunday, December 17, 2017 7:30 PM

All replies

  • Hi F.One,

    Maybe you can try to reinstall the SfB server and update to the latest CU?


    regards Holger Technical Specialist UC

    • Marked as answer by F.One Monday, December 18, 2017 8:55 PM
    Sunday, December 17, 2017 7:30 PM
  • Hello Holger,

    you mean to uninstall "skype for business main components" via control panel and re-running the sfb installation wizard again? 

    I have to republish the topology after that procedure, don´t I?

    Thanks - F.One 

    Sunday, December 17, 2017 7:59 PM
  • Hi F.one,

    If you want to try the resolution provided by Holger, yes, you need to republish the topology, then run Skype for Business deployment wizard again.

    Moreover, based on my research, error 1603 may be caused by the following reason:
    Cause

    1. AccessEdge Service was unable to stop in a timely manner
    2. WebComponents were not configured correctly and the service was not started.
    3. Insufficient database back-end permissions caused errors while installing Database patch

    You can try the method below
    Resolution

    1. Force stop the Access-Edge Services by killing RtcSrv from the TaskManager.
    2. Replaced applicationHost.config file from a working server to the problematic server.
    3. Provided elevated privileges on the Back-End to complete database patch installation.


    Regards,

    Alice Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, December 18, 2017 6:15 AM
  • Finally I was able tp patch the Edgeserver by doing the following:

    - made a HyperV-Snapshot to have an easy rollback option

    - for safety reasons on FrontEnd: "Export-CsConfiguration -FileName "C:\Config.zip" -LocalStore"

    - On EdgeServer: looked in control panel / software which part of SfB server ist patched and which is not: SfB Main Components and UWCA were already .510, SfB Edgeserver still .259 which is from CU5 (May 2017)

    - uninstalled this part, ignoring all warnings and rebooted

    - ran SfB installation wizard Step #2: Install Server and Components

    - rebooted

    - "get-cswindowservice" showed running: REPLICA and RTCCLSAGT, all other were in state "stopped"

    - "stop-cswindowservice", closed SfB shell

    - ran SkypeServerUpdateInstaller.exe successfully

    - now Edgeserver is .510 = CU6 (Dec. 2017)

    I decided to not run "import-CsConfiguration", because the FE and Edge began immediately to talk to each other and so the topolgy changes should be deployed by replicationservice as usual.

    I have no explanation why I could not patch this component from May 6.0.9319.281 directly to .510 and had to go back to .0

    This is odd and nasty and should not happen at all in an otherwise solid running topology.


    • Marked as answer by F.One Monday, December 18, 2017 9:13 PM
    Monday, December 18, 2017 9:13 PM
  • Thanks for your sharing

    Regards,

    Alice Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, December 19, 2017 1:39 AM
  • Finally I was able tp patch the Edgeserver by doing the following:

    - made a HyperV-Snapshot to have an easy rollback option

    - for safety reasons on FrontEnd: "Export-CsConfiguration -FileName "C:\Config.zip" -LocalStore"

    - On EdgeServer: looked in control panel / software which part of SfB server ist patched and which is not: SfB Main Components and UWCA were already .510, SfB Edgeserver still .259 which is from CU5 (May 2017)

    - uninstalled this part, ignoring all warnings and rebooted

    - ran SfB installation wizard Step #2: Install Server and Components

    - rebooted

    - "get-cswindowservice" showed running: REPLICA and RTCCLSAGT, all other were in state "stopped"

    - "stop-cswindowservice", closed SfB shell

    - ran SkypeServerUpdateInstaller.exe successfully

    - now Edgeserver is .510 = CU6 (Dec. 2017)

    I decided to not run "import-CsConfiguration", because the FE and Edge began immediately to talk to each other and so the topolgy changes should be deployed by replicationservice as usual.

    I have no explanation why I could not patch this component from May 6.0.9319.281 directly to .510 and had to go back to .0

    This is odd and nasty and should not happen at all in an otherwise solid running topology.


    This worked for me as well--saw this in our dev environment. I hope we won't see this in our QA and prod environments, but at least we have a workaround. Thanks for sharing.
    Tuesday, January 9, 2018 11:52 PM
  • I've found an easier fix for this issue.

    My edge server had .281 installed and required an upgrade to .510.

    I copied the Server.msi file from the original S4B 2015 installation media to path:

    C:\ProgramData\Microsoft\Skype for Business Server\Deployment\cache\6.0.9319.0\setup

    on the edge server, then re-ran the SkypeUpdateInstaller.

    That fixed it for me.

    I hope you'll find this useful.

    • Proposed as answer by Kadere Tuesday, March 27, 2018 4:00 AM
    Monday, February 19, 2018 3:51 PM
  • AlexN14!

    You are genius! Worked like a charm!

    Saturday, February 24, 2018 9:49 AM
  • Had the same issue, this workaround worked perfectly. Hopefully we won't have much of those in the future.
    Friday, March 9, 2018 12:33 PM
  • Had the same issue. All I had to do is to check free disk space on server ( I had 14 gigs), resized it to at leat 35 GB free space and it patched successfully.

    Thursday, May 10, 2018 8:59 AM
  • This solved the issue in my scenario , AV services were down and was getting error event id 19005 but didn't thought that this might the reason of less disk space on the edge server.
    Saturday, March 2, 2019 4:21 PM
  • I solved this problem by enlarging the C drive of my LYNCEDGE server.  I had 10GB free and the upgrade was failing.  I increased the free space to 35GB and the upgrade was successful.
    Tuesday, October 29, 2019 11:04 PM