Network Management

Error 1603 when trying to update the SolarWinds Platform

This article describes the issue when you upgrade some SolarWinds Platform based products, you see Fatal error in installer and the corresponding installer logs has ERROR 1603

First published date

10/18/2018 6:36 PM

Last published date

12/10/2025 12:43 AM

Overview

This article describes the issue where receive the following errors when you are upgrading SolarWinds Platform products.

image.png

On the OrionInstaller log:

<Timestamp> DEBUG OrionInstallerLib.MsiExecutor - Skipped Processing for User.  Record: The setup must update files or services that cannot be updated while the system is running. If you choose to continue, a reboot will be required to complete the setup.
<Timestamp> [24] DEBUG OrionInstallerLib.MsiExecutor -     0 : The setup must update files or services that cannot be updated while the system is running. If you choose to continue, a reboot will be required to complete the setup.
<Timestamp> [24] DEBUG OrionInstallerLib.MsiExecutor -     1 : 1610
<Timestamp> [24] ERROR OrionInstallerLib.MsiExecutor - Installer Exception.  Error Record:   - Error Code: 1603
<Timestamp> [24] ERROR OrionInstallerLib.InstallChain - Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
   at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
   at OrionInstallerLib.MsiExecutor.Execute(String commandLine)
   at OrionInstallerLib.InstallChain.ExecuteInstaller(InstallerInfo info, Int32 startingTick, Int32 totalTickCount)
   at OrionInstallerLib.InstallChain.ThreadProc()

On CoreInstaller log:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: The 'system.net' start tag on line 191 does not match the end tag of 'configuration'. Line 192, position 3. (C:\Windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 192) ---> System.Xml.XmlException: The 'system.net' start tag on line 191 does not match the end tag of 'configuration'. Line 192, position 3.

CustomAction StoreInstallSettings returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)


Administration Service.Client log:

<Timestamp> [42] ERROR (null) SolarWinds.Administration.InstallExecutor.Executors.MsiExecutor - Installer Exception. Error Record:  - Error Code: 1603
<Timestamp> [42] ERROR (null) SolarWinds.Administration.InstallExecutor.InstallationManager - Exception occured during Executor operation: 


TransactionRecorder.msi:

=== Logging stopped: <Timestamp> ===
MSI (s) (F8:B4) [<Timestamp>]: Product: SolarWinds Web Performance Monitor Recorder v2022.3 -- Installation failed.

MSI (s) (F8:B4) [<Timestamp>]: Windows Installer installed the product. Product Name: SolarWinds Web Performance Monitor Recorder v2022.3. Product Version: 122.3.50051.0. Product Language: 1033. Manufacturer: SolarWinds Worldwide, LLC.. Installation success or error status: 1603.

Product section

Orion Platform

Cause

File may be in use and windows installer is unable to update.

Resolution

Resolution 1


1. Please use this MS tool to Uninstall the application that is failing to be upgraded or installed.
https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d
2. Reboot and attempt to re-install

If the above method does not help, then continue to the next section.

Resolution 2

  1. Remove the corrupted machine.config file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\Config\.
  2. Copy the same file from an old server backup.
  3. Save the old backup where you deleted the corrupted file. 
  4. If you continue to get ERROR 1603, Restart the Server.

In most cases the Error 1603 refers to MSI installation - and is mostly caused by a process still running that cannot be stopped by the installer and hence cannot update the files related to that process.

So, make sure to check at what stage you are getting the error i.e. which module or dependencies installer was trying to update and check for the corresponding processes or dependency apps that module may be using or updating.