Customaction returned actual error code 1603

When installing an Autodesk product, a message like the following appears: CustomAction UnzipZipFiles returned actual error code 1603 This error occurs when an Autodesk product installer tries to unzip a file and host-based antivirus or Windows security settings are preventing zip file extraction

Products and versions covered

Alias AutoStudio 2017, Alias AutoStudio 2018, Alias AutoStudio 2019, Alias Concept 2019, Alias Design 2015, Alias Design 2016, Alias Design 2017, Alias Design 2018, Alias Design 2019, Alias Products 2014, Alias Products 2015, Alias Products 2016, Alias Products 2017, Alias Products 2018, Alias Products 2019, Alias SpeedForm 2016, Alias SpeedForm 2017, Alias SpeedForm 2018, Alias SpeedForm 2019, Alias Surface 2014, Alias Surface 2015, Alias Surface 2016, Alias Surface 2017, Alias Surface 2018, Alias Surface 2019, AutoCAD 2014, AutoCAD 2015, AutoCAD 2016, AutoCAD 2017, AutoCAD 2018, AutoCAD 2019, AutoCAD Architecture 2014, AutoCAD Architecture 2015, AutoCAD Architecture 2016, AutoCAD Architecture 2017, AutoCAD Architecture 2018, AutoCAD Architecture 2019, AutoCAD Electrical 2014, AutoCAD Electrical 2015, AutoCAD Electrical 2016, AutoCAD Electrical 2017, AutoCAD Electrical 2018, AutoCAD Electrical 2019, AutoCAD LT 2014, AutoCAD LT 2015, AutoCAD LT 2016, AutoCAD LT 2017, AutoCAD LT 2018, AutoCAD LT 2019, AutoCAD MEP 2014, AutoCAD MEP 2015, AutoCAD MEP 2016, AutoCAD MEP 2017, AutoCAD MEP 2018, AutoCAD MEP 2019, AutoCAD Map 3D 2014, AutoCAD Map 3D 2015, AutoCAD Map 3D 2016, AutoCAD Map 3D 2017, AutoCAD Map 3D 2018, AutoCAD Map 3D 2019, AutoCAD Mechanical 2014, AutoCAD Mechanical 2015, AutoCAD Mechanical 2016, AutoCAD Mechanical 2017, AutoCAD Mechanical 2018, AutoCAD Mechanical 2019, AutoCAD Plant 3D 2014, AutoCAD Plant 3D 2015, AutoCAD Plant 3D 2016, AutoCAD Plant 3D 2017, AutoCAD Plant 3D 2018, AutoCAD Plant 3D 2019, AutoCAD Raster Design 2014, AutoCAD Raster Design 2015, AutoCAD Raster Design 2016, AutoCAD Raster Design 2017, AutoCAD Raster Design 2018, AutoCAD Raster Design 2019, Civil 3D 2019, Inventor 2014, Inventor 2015, Inventor 2016, Inventor 2017, Inventor 2018, Inventor 2019, Inventor LT 2014, Inventor LT 2015, Inventor LT 2016, Inventor LT 2017, Inventor LT 2018, Inventor LT 2019, Inventor Products 2017, Inventor Products 2018, Inventor Products 2019, Inventor Professional 2015, Inventor Professional 2016, Inventor Professional 2017, Inventor Professional 2018, Inventor Professional 2019, Inventor Tolerance Analysis 2019, Navisworks Freedom 2014, Navisworks Freedom 2015, Navisworks Freedom 2016, Navisworks Freedom 2017, Navisworks Freedom 2018, Navisworks Freedom 2019, Navisworks Manage 2015, Navisworks Manage 2016, Navisworks Manage 2017, Navisworks Manage 2018, Navisworks Manage 2019, Navisworks Simulate 2014, Navisworks Simulate 2015, Navisworks Simulate 2016, Navisworks Simulate 2017, Navisworks Simulate 2018, Navisworks Simulate 2019, Revit 2014, Revit 2015, Revit 2016, Revit 2017, Revit 2018, Revit 2019, Revit LT 2014, Revit LT 2015, Revit LT 2016, Revit LT 2017, Revit LT 2018, Revit LT 2019, VRED Design 2014, VRED Design 2015, VRED Design 2016, VRED Design 2017, VRED Design 2018, VRED Design 2019, VRED Presenter 2014, VRED Presenter 2015, VRED Presenter 2016, VRED Presenter 2017, VRED Presenter 2018, VRED Presenter 2019, VRED Products 2014, VRED Products 2015, VRED Products 2016, VRED Products 2017, VRED Products 2018, VRED Products 2019, VRED Professional 2014, VRED Professional 2015, VRED Professional 2016, VRED Professional 2017, VRED Professional 2018, VRED Professional 2019, Vault Products 2015, Vault Products 2016, Vault Products 2017, Vault Products 2018, Vault Products 2019, Vault Professional 2014, Vault Professional 2015, Vault Professional 2016, Vault Professional 2017, Vault Professional 2018, Vault Professional 2019, Vault Workgroup 2014, Vault Workgroup 2015, Vault Workgroup 2016, Vault Workgroup 2017, Vault Workgroup 2018, & Vault Workgroup 2019

I’m using using Basic MSI to install my application.

I’m getting Error 1001 during installation and roll back action takes place. I’ve noticed in the installation log that I get this error:

«CustomAction returned actual error code 1603. Action ended InstallFinalize. Return value 3.

Custom Action dll is a .NET Installer Class and the property is set to True.

Does anyone have an idea what could be the problem?

gideon's user avatar

gideon

19.2k11 gold badges73 silver badges113 bronze badges

asked Aug 3, 2011 at 16:22

Vimal's user avatar

0

Your installation project includes a component with .NET Installer Class set to Yes. Using this option is an anti-pattern, as it can result in modal UI even in silent installations, and often tells you only «Error 1001». You can either look for the component with this setting, or take a verbose log and look for information shortly before the first or only return value 3.

answered Aug 2, 2011 at 13:25

Michael Urman's user avatar

Michael UrmanMichael Urman

15.7k2 gold badges27 silver badges44 bronze badges

1

Error code 1603 is a Windows installer’s generic error code when custom action throws any error/exception. Windows installer does not show actual error/exception in installer logs. To verify actual error/exception we have to debug the custom action.

Please verify if custom action is throwing any error/exception.

answered Sep 22, 2011 at 19:53

Bhalchandra K's user avatar

Bhalchandra KBhalchandra K

2,6113 gold badges29 silver badges42 bronze badges

4

A verified solution:

Error 1001 is due to a .Net framework mismatch. InstallShield uses RegAsm.exe and InstallUtilLib.dll to compile the installer, and these must match your application’s target framework, and the target computer must also have it:

Error 1001 reason and solution discussed here

enter image description here

Open Installshield IDE -> Go to Tools menu -> Options and check the following settings as shown in the above screenshot:

Community's user avatar

answered Jan 2, 2013 at 14:15

Munawar's user avatar

MunawarMunawar

2,5682 gold badges25 silver badges28 bronze badges

In my case, I was installing an x86 windows service to an x64 machine. I had to change both paths in my options to my local x86 .net installation folder for my executable’s target framework. ie.

32-bit location
C:WindowsMicrosoft.NETFrameworkv4.0.30319

64-bit location
C:WindowsMicrosoft.NETFrameworkv4.0.30319

answered Jan 20, 2014 at 13:29

Kaido's user avatar

KaidoKaido

3,31124 silver badges34 bronze badges

2

Error: CustomAction _ConfigureAnalysisServer returned actual error code 1603

My Scenario: SCSM — Comp 1; SCDW — Comp 2; SCSMDatabase for both SCSM and SCWD — Comp -3, Self Service and other — Comp — 4.

_____________________________________________________________________________

SCSM — Comp 1 — Successfully Installed 

No Issues faced

_____________________________________________________________________________

SCDW — Comp 2 — Fails with the error «CustomAction _ConfigureAnalysisServer returned actual error code 1603″ from setup logs and from the SCWArehouse Installer GUI «An error
occurred while executing a custom action:_ConfigureAnalysisServer 
This upgrade attempt has failed before permanent modifications were made. Upgrade has successfully rolled back to the original state of the system.
Once the correction
<g class=»gr_ gr_244 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace» data-gr-id=»244″ id=»244″ style=»font-size:0.75em;»>are</g>
made, you can retry upgrade for this role.» 

Analysis Service and Reporting Server both are installed on the same server where data warehouse hosted.

_____________________________________________________________________________

Please suggest any possible solution or workaround for this issue

Try to install «XDCC-9.1.12_nl_NL_WIN_64» getting the following error:

MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])

MSI (s) (D8:E8) [15:29:51:453]: Executing op: IconCreate(Icon=ARPPRODUCTICON.exe,Data=BinaryData)

MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CADeploy,,)

MSI (s) (D8:E8) [15:29:51:469]: Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeploymentManagerCA,CustomActionData=mode=install;sourceDir=C:installXDCC-9.1.12-defBuild;installDir=;origDB=C:installXDCC-9.1.12-defBuildXDCC-9.1.12-def.msi;installLang=)

MSI (s) (D8:2C) [15:29:51:469]: Invoking remote custom action. DLL: C:windowsInstallerMSI1C78.tmp, Entrypoint: runDeploymentManagerCA

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

After that a rolling back will take place and the installation failed. Zie log part below this line.

MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])

MSI (s) (D8:E8) [15:29:51:453]: Executing op: IconCreate(Icon=ARPPRODUCTICON.exe,Data=BinaryData)

MSI (s) (D8:E8) [15:29:51:453]: Executing op: ActionStart(Name=CADeploy,,)

MSI (s) (D8:E8) [15:29:51:469]: Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeploymentManagerCA,CustomActionData=mode=install;sourceDir=C:installXDCC-9.1.12-defBuild;installDir=;origDB=C:installXDCC-9.1.12-defBuildXDCC-9.1.12-def.msi;installLang=)

MSI (s) (D8:2C) [15:29:51:469]: Invoking remote custom action. DLL: C:windowsInstallerMSI1C78.tmp, Entrypoint: runDeploymentManagerCA

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

Any idea how to solve this? I cannot install the update on any windows 10 computer.

Up to version XDCC5.0.12_nl_NL_WIN_64 never had such porblem.

  • Remove From My Forums

 locked

hck — client installation fail — error 1603

  • Question

  • Hi,

    I’m trying to install HCKSetup.exe on Windows 8 Pro, Build 9200,

    The installation ends prematurely because of an error — 16303: Fatal error during installation.

    attached a log file i find on the system, hope it’s informative —

    WDK Setup Bootstrap Executable
    Start Time: Sunday, September 09, 2012. 06:07:40 PM
    Command line:
    Processor Architecture: x86
    Beginning to process Globals section
    Adding placeholder «%SetupDirectory%=\IL-WHCKHCKInstallClient»
    Finished processing Globals section
    «»@SetupExeLocation@Windows Hardware Certification Kit
    Client-@INSTALL_ARCHITECTURE@_en-us.msi»» updated to «»\il-whckHCKInstallClientWindows Hardware Certification Kit Client-x86_en-us.msi»»
    «»@SetupExeLocation@WindowsXP-KB942288-v3-x86.exe» /quiet» updated to «»\il-whckHCKInstallClientWindowsXP-KB942288-v3-x86.exe» /quiet»
    «»@SetupExeLocation@WindowsServer2003-KB942288-v4-x86.exe» /quiet» updated to «»\il-whckHCKInstallClientWindowsServer2003-KB942288-v4-x86.exe» /quiet»
    «»@SetupExeLocation@WindowsServer2003-KB942288-v4-x64.exe» /quiet» updated to «»\il-whckHCKInstallClientWindowsServer2003-KB942288-v4-x64.exe» /quiet»
    «»@SetupExeLocation@dotNetFx40_Full_x86_x64.exe» /passive» updated to «»\il-whckHCKInstallClientdotNetFx40_Full_x86_x64.exe» /passive»
    «»@SetupExeLocation@WPTx86-x86_en-us.msi»» updated to «»\il-whckHCKInstallClientWPTx86-x86_en-us.msi»»
    «»@SetupExeLocation@WPTx64-x64_en-us.msi»» updated to «»\il-whckHCKInstallClientWPTx64-x64_en-us.msi»»
    «»@SetupExeLocation@Application Verifier x86 External Package-x86_en-us.msi»» updated to «»\il-whckHCKInstallClientApplication Verifier x86 External Package-x86_en-us.msi»»
    «»@SetupExeLocation@Application Verifier x64 External Package-x64_en-us.msi»» updated to «»\il-whckHCKInstallClientApplication Verifier x64 External Package-x64_en-us.msi»»
    «»@SetupExeLocation@Windows Driver Testing Framework (WDTF) Runtime
    Libraries-@INSTALL_ARCHITECTURE@_en-us.msi»» updated to «»\il-whckHCKInstallClientWindows Driver Testing Framework (WDTF) Runtime Libraries-x86_en-us.msi»»
    «Install or Uninstall of Client failed, please see logfile(s) in @temp@» updated to «Install or Uninstall of Client failed, please see logfile(s) in C:UsersAavaAppDataLocalTemp»
    Beginning to process Blocking section
    Beginning to process RunningOnXpOrGreater section
    Finished processing RunningOnXpOrGreater section
    Beginning to process NotRunningOnIa64 section
    Finished processing NotRunningOnIa64 section
    Beginning to process ControllerAlreadyInstalled section
    Finished processing ControllerAlreadyInstalled section
    Beginning to process StudioAlreadyInstalled section
    Finished processing StudioAlreadyInstalled section
    Beginning to process WindowsImagingComponentsMissing section
    Finished processing WindowsImagingComponentsMissing section
    Finished processing Blocking section
    Beginning to process Preconditions section
    Beginning to process XPx86Msi45 section
    Finished processing XPx86Msi45 section
    Beginning to process Server2003x86Msi45 section
    Finished processing Server2003x86Msi45 section
    Beginning to process XPServer2003x64Msi45 section
    Finished processing XPServer2003x64Msi45 section
    Beginning to process DotNet4 section
    Finished processing DotNet4 section
    Beginning to process XPerfX86 section
    Finished processing XPerfX86 section
    Beginning to process XPerfX64 section
    Finished processing XPerfX64 section
    Beginning to process AppVerifierX86 section
    Finished processing AppVerifierX86 section
    Beginning to process AppVerifierX64 section
    Finished processing AppVerifierX64 section
    Beginning to process WDTF section
    Finished processing WDTF section
    Finished processing Preconditions section
    Beginning to process Install section
    Beginning to process TestClient section
    Finished processing TestClient section
    Finished processing Install section
    Beginning to process Postconditions section
    Finished processing Postconditions section
    Evaluating conditions in RunningOnXpOrGreater group
    Evaluating condition «GreaterThanOrEqualOsVersion=5.1.3.0»
    Condition evaluated to TRUE
    Evaluating conditions in RunningOnXpOrGreater group  returning TRUE, continuing…
    Evaluating conditions in NotRunningOnIa64 group
    Evaluating condition «SupportedArchitectures=X86|X64|ARM»
    Condition evaluated to TRUE
    Evaluating conditions in NotRunningOnIa64 group  returning TRUE, continuing…
    Evaluating conditions in ControllerAlreadyInstalled group
    Evaluating condition «Reg64=HKLMSOFTWAREMicrosoftWindowsCurrentVersionInstallerUpgradeCodesA29FF3092508BE3635AC11C976975905»
    Condition evaluated to TRUE
    Evaluating conditions in ControllerAlreadyInstalled group  returning TRUE, continuing…
    Evaluating conditions in StudioAlreadyInstalled group
    Evaluating condition «Reg64=HKLMSOFTWAREMicrosoftWindowsCurrentVersionInstallerUpgradeCodes6749B683276E86E7C78FBDF66467ED87»
    Condition evaluated to TRUE
    Evaluating conditions in StudioAlreadyInstalled group  returning TRUE, continuing…
    Evaluating conditions in WindowsImagingComponentsMissing group
    Evaluating condition «NoReg64=HKLMSOFTWAREClassesCLSID{CACAF262-9370-4615-A13B-9F5539DA4C0A}»
    Condition evaluated to TRUE
    Evaluating conditions in WindowsImagingComponentsMissing group  returning TRUE, continuing…
    Evaluating condition «SupportedArchitectures=X86»
    Condition evaluated to TRUE
    Evaluating condition «LessThanOsVersion=5.2.0.0»
    Condition evaluated to FALSE
    Skipping product XPx86Msi45
    Evaluating condition «SupportedArchitectures=X86»
    Condition evaluated to TRUE
    Evaluating condition «LessThanOsVersion=5.3.0.0»
    Condition evaluated to FALSE
    Skipping product Server2003x86Msi45
    Evaluating condition «SupportedArchitectures=X64»
    Condition evaluated to FALSE
    Skipping product XPServer2003x64Msi45
    Evaluating condition «Reg=HKLMSOFTWAREMicrosoftNET Framework SetupNDPv4.0»
    Condition evaluated to FALSE
    Skipping product DotNet4
    Evaluating condition «SupportedArchitectures=X86»
    Condition evaluated to TRUE
    Installing product XPerfX86
    {ADAABA50-D3AA-D123-147C-6664F3ABDA73} product Installed, no need to remove
    Evaluating condition «SupportedArchitectures=X64»
    Condition evaluated to FALSE
    Skipping product XPerfX64
    Evaluating condition «SupportedArchitectures=X86»
    Condition evaluated to TRUE
    Installing product AppVerifierX86
    {9A537F9C-746D-656A-0592-E82DFABDC599} product Installed, no need to remove
    Evaluating condition «SupportedArchitectures=X64»
    Condition evaluated to FALSE
    Skipping product AppVerifierX64
    Installing product WDTF
    {BBFB8D8C-EEA2-BD32-13C8-B937EA5D99D3} product Installed, no need to remove
    Installing product TestClient
    Installing product {87F916A5-CFED-C28A-8425-DD78E38B333A}
    Logging to C:UsersAavaAppDataLocalTempWindows Hardware Certification Kit Client_Install.log
    Installed product {87F916A5-CFED-C28A-8425-DD78E38B333A}
    Install or Uninstall of Client failed, please see logfile(s) in C:UsersAavaAppDataLocalTemp  System Error 1603: Fatal error during installation.

    Thanks,

    Inbar.

    • Moved by

      Wednesday, October 3, 2012 7:18 PM
      WLK/WHCK related (From:Windows Hardware WDK and Driver Development)

Answers

  • This is a documented issue with secure boot that can be found at

    http://msdn.microsoft.com/en-us/library/windows/hardware/hh998740.aspx

    In some cases, having Secure Boot enabled on a test computer can cause the HCK Client installation to fail. Follow these steps to ensure proper installation:

    For system tests and non-class driver device tests

    1. Disable Secure Boot protections.
      • For x86/x64, enter your BIOS configuration and disable Secure Boot.
      • For Windows RT, install the
        Windows Debug Policy; you don’t need to disable Secure Boot.

    This can only be done by OEMs and Microsoft.


    John — This posting is provided «AS IS» with no warranties, and confers no rights.

    • Proposed as answer by
      John Garcia (HCK)
      Monday, September 10, 2012 4:19 PM
    • Marked as answer by
      Doron Holan [MSFT]
      Monday, September 10, 2012 4:20 PM

Problem

Upgrading a DB2 Server installation may fail with 1603 if the IBM Data Server Driver Package is also installed.

Symptom

An upgrade of DB2 will fail, reporting that ‘A major error occurred while installing DB2 on this computer.’ and a log file will be generated. This end of this log file will contain:
Action 10:17:44: VerifyPrereqsCA.
Action start 10:17:44: VerifyPrereqsCA.
CustomAction VerifyPrereqsCA returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 10:17:44: VerifyPrereqsCA. Return value 3.
Action 10:17:44: SetupCompleteError.
Action start 10:17:44: SetupCompleteError.

Cause

The IBM Data Server Driver Package is also installed.

Diagnosing The Problem

Executing ‘setup.exe’ from the command line and capturing a log and trace file will not provide any additional diagnostic information. This log file will be larger, but will contain similar output.

The problem is occurring because the DS Driver is also installed. To confirm this, check

Control Panel -> Programs -> Uninstall a program

Along with ‘DB2 Server Edition’ you should also see the ‘IBM Data Server Driver Package’ listed.

Resolving The Problem

Uninstall the IBM Data Server Driver Package. It is not required because the DB2 Server Edition provides all the functionality.

Please be aware that uninstalling the DS Driver will ‘break’ any ODBC DSNs that rely upon that driver. These DSNs must be recreated using the ODBC Driver provided by the DB2 Server Edition. You can do this either from the Windows ODBC Data Source Administrator, or with the ‘catalog odbc data source’ command.

Related Information

[{«Product»:{«code»:»SSEPGG»,»label»:»Db2 for Linux, UNIX and Windows»},»Business Unit»:{«code»:»BU058″,»label»:»IBM Infrastructure w/TPS»},»Component»:»Install/Migrate/Upgrade — Install/Setup — GUI»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»10.1;10.5;11.1″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

The Qlik Sense installation fails when attempting to install the Centralizedin Logging Service.

In the installation log, the following error is printed:

Action 12:12:11 95 Failed to execute database setup.
CustomAction CA_SetupLocalLoggingDb returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Environments:

  • Qlik Sense Enerprise June 2017 and higher.

Resolution:

The recommendation is to install Sense without the Centralized logging service and set it up afterwards. See  How to set up the Qlik Sense Logging Service to set it up manually.

However, if the installation is required, verify that the correct hostname is being used during the installation process. If the hostname is incorrect, the installation will error out.

Example:

Qlik Sense will prompt for a hostname during install as seen in Fig 1.

Fig 1Fig 1

This name may be incorrect. Verify your machine’s hostname in the Windows Control Panel as seen in Fig 2.

Fig 2Fig 2

use Google Translate

Last update: 14-02-2013

During installation of True Image 2013 by Acronis you receive this error. The issue is the service TImounter, that could not be uninstalled. Uninstall the Service manually in order to install True Image 2013 by Acronis.

This article applies to:

  • True Image 2013 by Acronis

Symptoms

  1. Running the installation of True Image 2013 by Acronis leads to the message «Uninstall previous version and install current»;
  2. You attempt to uninstall the previous version Acronis True Image Home 2012 (or another old version of Acronis True Image Home) from the machine. The uninstallation fails with a rollback and following error:

CustomAction_USRCUSTACT_MsiTimounterUninstall_TrueImageWinMounter returned actual error code 1603

Cause

The Timounter Service from previous version Acronis True Image Home 2012 could not be uninstalled.

Solution

In order to solve this issue, please follow these steps:

  1. Manually uninstallation of Timounter service:
    1. Start command line as administrator:
      1. For Windows 7 (Vista, 8): Go to Start -> Accessories -> Command prompt -> right click -> run as administrator;
      2. For win XP: Log in under Administrator account -> Start -> Run -> cmd.exe;
    2. Type: sc query timounter -> Enter;
    3. You will see the service parameters: STATE : RUNNING;
    4. Type: sc config timounter start= disabled error= ignore and press Enter;
  2. Clean registry:
    1. Go to Start -> Run -> regedit.exe -> press Enter;
    2. In Registry Editor navigate to this key:

        HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{71A27CDD-812A-11D0-BEC7-08002BE2092F}UpperFilters

    3. Change the «UpperFilters» value data by removing the «timounter» string. DO NOT CHANGE OTHER STRINGS.

      (!) Only delete the string ‘timounter‘ (green box). Do not delete the complete key or registry path (red box)!

  3. Reboot machine.
  4. Control if the service is removed successfully:
    1. Start command line as administrator:
      1. For Windows 7 (Vista, 8): Go to Start -> Accessories -> Command prompt -> right click -> run as administrator;
      2. For win XP: Log in under Administrator account -> Start -> Run -> cmd.exe;
        1. Type: sc query timounter -> Enter;
        2. You will see the service parameters: STATE : STOPPED;
  5. If the service is stopped, you can uninstall the Acronis True Image Home 2012 via Windows.

More information

See also:

  • True Image 2013 by Acronis
  • Acronis True Image Home 2011, 2012 and True Image 2013 by Acronis: Cleanup Utility

Tags: 

  • Error
  • Timounter

Hello…

I recently inherited a physical SBS2011 server with Exchange 2010 SP1 RU8 installed.  SP1 RU7v2 is the only other RU installed.  When attempting to upgrade to SP3 the pre-install checks all pass but when it gets to the removal of Exchange part of the install the following error is thrown and the install fails.

Unable to remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘Service » () could not be stopped.  Verify that you have the correct permissions to stop system services.’.

After fixing the services and rebooting the server EmailExchange connectivity is restored.  I get the same error if I try and install SP2 or SP3, and if I try and uninstall the currently installed SP1 RU’s.  My account is a member of the Domain Admins, Enterprise Admins, Schema Admins, and Organization Management groups.  I can fully interact with all MS Exchange services as well as IIS Admin Service, Remote Registry, WMI, and WWW services.  I’ve stopped the Windows SBS Manager service as well as disabled UAC and my AV prior to install and the issue persists. 

I verified the RangeUpper value on my Schema is correct (14734), but attempted to run Setup.com /PrepareAD anyway (from an admin CMD).  The command output shows the first two lines («Welcome to Microsoft Exchange blah blah blah», and then «Preparing Exchange Setup») but then just goes back to the cursor waiting for the next command and no error or changes made.  Same happens when I tried to run ServiceControl.ps1, first 2 or so lines of the command output are shown then back to the cursor with no actual error or changes made.  Powershell Execution Policy is set to Unrestricted.

As near as I can tell what ever 4934d1ea-be46-48b1-8847-f1af20e892c1 represents iswas installed at some point and then removed, I can find that same GUID in the registry (HKLMSOFTWAREMicrosoftWindowsCurrentVersionInstallerFolders) and the WindowsInstaller folder.  I suspect it is gone though because the error references that GUID, then the installer fails because it is unable to stop service (), which isn’t anything.  Mail is currently flowing to Outlook 2010 and below with no issues.  I don’t want to start ripping things out and mess up mailflow but I’m about out of ideas.  Any help you can provide would be great, let me know if I can provide any more info. 

Понравилась статья? Поделить с друзьями:
  • Cydia error dpkg locked
  • Cyclic redundancy check как исправить hdd
  • Cyclic redundancy check crc error in data message frame
  • Cyberpunk 2077 прекратила работу ошибка при запуске на пиратке
  • Cyberpunk 2077 ошибка установки