Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 26 replies
  • Subscribers 1 subscriber
  • Views 103694 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SEC 5.2 - install error 1603

Ingo

Hello all,

on a fresh installation of SEC 5.2 the following error got displayed:

        Sophos Management Server -- Installation failed

It a new installation with the database located on a different server.

OS is Windows 2008 R2.

Sophos_server64msi:

....

MSI (s) (08:C0) [13:51:58:268]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:268]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:268]: Entering MsiProvideAssembly. AssemblyName: policy.8.0.Microsoft.VC80.MFC,type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:268]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:268]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:284]: Entering MsiProvideAssembly. AssemblyName: Microsoft.VC80.MFC,type="win32",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:284]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:284]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:284]: Entering MsiProvideAssembly. AssemblyName: Microsoft.VC80.MFC,type="win32",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:284]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:284]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:315]: Entering MsiProvideAssembly. AssemblyName: policy.8.0.Microsoft.VC80.CRT,type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:315]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:315]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:315]: Entering MsiProvideAssembly. AssemblyName: policy.8.0.Microsoft.VC80.CRT,type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:315]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:315]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:330]: Entering MsiProvideAssembly. AssemblyName: Microsoft.VC80.CRT,type="win32",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:330]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:330]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:330]: Entering MsiProvideAssembly. AssemblyName: Microsoft.VC80.CRT,type="win32",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:330]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:330]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:346]: Entering MsiProvideAssembly. AssemblyName: policy.8.0.Microsoft.VC80.ATL,type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:346]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:346]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:346]: Entering MsiProvideAssembly. AssemblyName: policy.8.0.Microsoft.VC80.ATL,type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:346]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:362]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:377]: Entering MsiProvideAssembly. AssemblyName: Microsoft.VC80.ATL,type="win32",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:377]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:377]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:377]: Entering MsiProvideAssembly. AssemblyName: Microsoft.VC80.ATL,type="win32",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86", AppContext: , InstallMode: -4
MSI (s) (08:C0) [13:51:58:377]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (08:C0) [13:51:58:377]: MsiProvideAssembly is returning: 1607
MSI (s) (08:C0) [13:51:58:408]: Note: 1: 2318 2:  
MSI (s) (08:C0) [13:51:58:408]: No System Restore sequence number for this installation.
MSI (s) (08:C0) [13:51:58:408]: Unlocking Server
MSI (s) (08:C0) [13:51:58:408]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 13:51:58: INSTALL. Return value 3.

....

MSI (s) (08:C0) [13:51:58:627]: Note: 1: 1708
MSI (s) (08:C0) [13:51:58:627]: Product: Sophos Management Server -- Installation failed.

MSI (s) (08:C0) [13:51:58:642]: Windows Installer installed the product. Product Name: Sophos Management Server. Product Version: 5.2.0. Product Language: 1033. Manufacturer: Sophos Limited. Installation success or error status: 1603.

MSI (s) (08:C0) [13:51:58:658]: Deferring clean up of packages/files, if any exist
MSI (s) (08:C0) [13:51:58:658]: MainEngineThread is returning 1603
MSI (s) (08:9C) [13:51:58:658]: No System Restore sequence number for this installation.
=== Logging stopped: 8/26/2013  13:51:58 ===
MSI (s) (08:9C) [13:51:58:658]: User policy value 'DisableRollback' is 0
MSI (s) (08:9C) [13:51:58:658]: Machine policy value 'DisableRollback' is 0
MSI (s) (08:9C) [13:51:58:658]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (08:9C) [13:51:58:658]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (08:9C) [13:51:58:658]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (08:9C) [13:51:58:658]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (08:9C) [13:51:58:658]: Restoring environment variables
MSI (s) (08:9C) [13:51:58:658]: Destroying RemoteAPI object.
MSI (s) (08:4C) [13:51:58:658]: Custom Action Manager thread ending.
MSI (c) (EC:D8) [13:51:58:674]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (EC:D8) [13:51:58:674]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/26/2013  13:51:58 ===

I appreciate your  help.

Regards,

Ingo

:42884


This thread was automatically locked due to age.
  • 0

    Bootstrapper seems chopped off.

    FYI: I'm hoping the ability to upload files when replying will be switched on shortly.

    :42946

     - - - - - - - - - - - -

    Communities Moderator, SOPHOS
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0

    The sophos_server64 log shows...

    MSI (s) (E4:F4) [11:41:53:149]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI4749.tmp, Entrypoint: CreateScheduledTask
CreateScheduledTask:  Initialized.
CreateScheduledTask:  Error 0x80070520: Error encountered while creating scheduled task.
CreateScheduledTask:  Error 0x80070520: Failed to create scheduled task.
CustomAction CreateCDLTask returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (E4:A8) [11:41:53:211]: User policy value 'DisableRollback' is 0
MSI (s) (E4:A8) [11:41:53:211]: Machine policy value 'DisableRollback' is 0
Action ended 11:41:53: InstallFinalize. Return value 3.

    Hence: Unable to install Management Server - failure to create scheduled tasks

    :42948

     - - - - - - - - - - - -

    Communities Moderator, SOPHOS
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0

    Made some progress now. Don't see the 0x80070520 any more. A new logfile is attached now.

    Regards,

    Ingo

    :42950
  • 0

    Is there still a problem?  The log file ends with... 

    MSI (s) (A8:94) [16:04:09:043]: Product: Sophos Management Server -- Installation completed successfully.
    :42954

     - - - - - - - - - - - -

    Communities Moderator, SOPHOS
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0

    The setup ended with an error again.

    By re-run the setup I noticed that the Management Server is installed now. Not the Console.

    Here are some parts of the logs:

    ....

    MSI (s) (E0:E0) [19:47:21:507]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'IS_ParseUsernameToTokens'
    MSI (s) (E0:3C) [19:47:21:507]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBE3E.tmp, Entrypoint: ParseUserNameToTokens
    MSI (s) (E0!C4) [19:47:21:522]: PROPERTY CHANGE: Adding IS_NET_API_LOGON_USERNAME_TOKEN property. Its value is 'sophos-upd-srv'.
    MSI (s) (E0!C4) [19:47:21:522]: PROPERTY CHANGE: Adding IS_NET_API_LOGON_DOMAIN_TOKEN property. Its value is 'XXXX'.
    Action start 19:47:21: IS_ParseUsernameToTokens.
    MSI (s) (E0:E0) [19:47:21:522]: Skipping action: SetIS_NET_API_LOGON_DOMAIN_TOKEN (condition is false)
    MSI (s) (E0:E0) [19:47:21:522]: Skipping action: SetIS_NET_API_LOGON_USERNAME_TOKEN (condition is false)
    MSI (s) (E0:E0) [19:47:21:522]: Doing action: IS_ValidateDomainToken
    Action ended 19:47:21: IS_ParseUsernameToTokens. Return value 1.
    MSI (s) (E0:E0) [19:47:21:522]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'IS_ValidateDomainToken'
    MSI (s) (E0:E8) [19:47:21:522]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBE4F.tmp, Entrypoint: ValidateDomainToken
    MSI (s) (E0!30) [19:47:21:538]: PROPERTY CHANGE: Adding IS_NET_API_TOKEN_VALID property. Its value is '0'.
    Action start 19:47:21: IS_ValidateDomainToken.
    MSI (s) (E0:E0) [19:47:39:478]: Doing action: IS_ErrorActionForDomainValidationFailure
    Action ended 19:47:39: IS_ValidateDomainToken. Return value 1.
    MSI (s) (E0:E0) [19:47:39:478]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'IS_ErrorActionForDomainValidationFailure'
    Action start 19:47:39: IS_ErrorActionForDomainValidationFailure.
    MSI (s) (E0:E0) [19:47:39:478]: Product: Sophos Update Manager -- Installation cannot continue. XXXX is not a valid domain name.

    To be valid, the domain part of the username must be either a domain or a physical server or workstation. Check the name and try again.

    Action ended 19:47:39: IS_ErrorActionForDomainValidationFailure. Return value 3.
    Action ended 19:47:39: INSTALL. Return value 3.

    ....

    Why is the domain name not valid? (name got replaced) The Netbios name got used here.

    Regards,

    Ingo

    :42974
  • 0

    Same error on this post.

    :42976

     - - - - - - - - - - - -

    Communities Moderator, SOPHOS
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0

    I need to use a domain account instead of a local account.

    Regards,

    Ingo

    :42986
  • 0

    Do you have any idea how to run this using a domain account?

    Regards,

    Ingo

    :42996
  • 0

    I've found some internal information suggesting a registry string may have the old name and hence could be causing the problem...

    Issue

     

    When performing either of the following two actions:

    1. Removing Sophos Update Manager (SUM) from Add/Remove Programs or Programs and Features.
    2. Sophos Update Manager (SUM) is performing a self-update to a newer version....

    ...the following error messages are shown:

    • On screen during the manual removal of SUM:

      Installation cannot continue [OldServerName] is not a valid domain name.

      To be valid, the domain part of the username must be either a domain or a physical server or workstation. Check the name and try again.

    First seen in
    Sophos Update Manager 1.0.1.111

     

    Cause

    Normally associated with a server name or domain change but can also be caused by corruption that results in an incorrectly configured SUM registry key.

    What To Do

    To do this follow these steps:

    1. Open the registry editor (Start | Run | Type: regedit.exe | Press return).
    2. Browse to:
      • 32-bit computer: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2C7A82DB-69BC-4198-AC26-BB862F1BE4D0}
      • 64-bit computer: HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{2C7A82DB-69BC-4198-AC26-BB862F1BE4D0}
    3. Locate the registry string UserData and its value.
    4. The value format should be: <hostname>;<domainname>;<username>;<integer>;
      Example: myServerName;myDomainName;SophosUpdateMgr;0;
    5. Ensure the values are correct or update as required.

    Once the registry values are correct SUM can be manually removed from Add/Remove Programs or will be able to automatically update itself.

    :42998

     - - - - - - - - - - - -

    Communities Moderator, SOPHOS
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

Unfiltered HTML