Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 11967 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.1 to 5.2 Upgrade Failed

bhx90

Hi,

I sucessfully upgraded from SEC 4.5 to 5.1 without issue and now I'm trying to go to 5.2.

The DB is on a separate server and the DB upgrade ran successfully.

I'm now trying to run the upgrade on the SEC server and the install fails at the server32.msi.

This is the end of the server32.msi log file

Property(S): DATABASE = C:\WINDOWS\Installer\1868f6.msi
Property(S): OriginalDatabase = C:\sec_52\ServerInstaller\Server32.msi
Property(S): UILevel = 2
Property(S): Preselected = 1
Property(S): ACTION = INSTALL
Property(S): DB_UPGRADE_VERSION.E96667BC_B851_472E_B9EA_5E2B142E3BFA = 51
Property(S): HASIIS4 = 1
Property(S): HASWEBSERVER = 1
Property(S): IEVERSION = 800
Property(S): OSSupportSxS = 1
Property(S): ASPNET = 4.0.30319.0
Property(S): AspNetVersionRequirementMet = 1
Property(S): DotNetFrameworkVersionRequirementMet = 1
Property(S): ROOTDRIVE = C:Property(S): CostingComplete = 1
Property(S): CRYSTALREDIRECTIONNUMBER = 2
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): INSTALLLEVEL = 1
MSI (s) (9C:D0) [19:30:09:490]: Note: 1: 1708 
MSI (s) (9C:D0) [19:30:09:490]: Product: Sophos Management Server -- Installation failed.

MSI (s) (9C:D0) [19:30:09:490]: Windows Installer installed the product. Product Name: Sophos Management Server. Product Version: 5.2.0. Product Language: 1033. Installation success or error status: 1603.

MSI (s) (9C:D0) [19:30:09:490]: Cleaning up uninstalled install packages, if any exist
MSI (s) (9C:D0) [19:30:09:490]: MainEngineThread is returning 1603
MSI (s) (9C:04) [19:30:09:599]: No System Restore sequence number for this installation.
=== Logging stopped: 31/01/2013  19:30:09 ===

And this is the end of the bootstrapper log file

31/01/2013 19:22:00, INFO : Start state: Idle
31/01/2013 19:22:00, INFO : Deactivate state: Idle
31/01/2013 19:22:00, INFO : Activate state: Installing
31/01/2013 19:22:00, INFO : Verifying files in folder
31/01/2013 19:22:00, INFO : Target folder verification completed successfully
31/01/2013 19:22:00, INFO : Copied SmAgentAPI.dll from C:\sec_52\ServerInstaller\pre-reqs\SmAgent\SmAgentAPI.dll into C:\Program Files\Business Objects\BusinessObjects Enterprise 11\win32_x86\plugins\auth\secLDAP\SmAgentAPI.dll
31/01/2013 19:22:00, INFO : Verifying files in folder
31/01/2013 19:22:03, INFO : Target folder verification completed successfully
31/01/2013 19:22:03, INFO : About to install Server32.msi
31/01/2013 19:30:01, INFO : Processing INSTALLMESSAGE_ERROR or INSTALLMESSAGE_FATALEXIT message from MSI
31/01/2013 19:30:01, INFO : Deactivate state: Installing
31/01/2013 19:30:01, INFO : Activate state: Failing
31/01/2013 19:30:09, INFO : Installation of Server32.msi failed with error code: 1603
31/01/2013 19:30:09, INFO : Ended installing Server32.msi
31/01/2013 19:30:11, INFO : Installation failed with error code: 1603
31/01/2013 19:30:11, INFO : Deactivate state: Failing
31/01/2013 19:30:11, INFO : Activate state: Failed
31/01/2013 19:30:11, INFO : Entered Installation failed page.
31/01/2013 19:31:45, INFO : Opening logs folder: C:\Documents and Settings\All Users\Application Data\Sophos\Management Installer

Can anyone suggest away to resolve this?

Thanks

Phil

:37303


This thread was automatically locked due to age.
Parents
  • 0

    The endpoints are probably still getting updates if SUM is still working.  You could check the last time an .ide file was created in the distribution point (\\127.0.0.1\sophosupdate\CIDS\...etc..) or even at a test endpoint in program files directory of Sophos.

    I can only think that there must be an open handle to the servie that is preventing the service being removed.  You could try taking a look at the handles with Process Explorer.

    At the risk of breaking it, you could even try using the SC command line tool to delete the service before attempting an upgrade but you may want to check with Support.   As the installer is unable to delete the service, there is a good chance sc will not be able to either but at least you have a quick check to know when the upgrade is likely to work.

    It might b easier to log a support call so they can examine the logs in full.  They may even request a remote access to take a look.

    Regards,

    Jak

    :37349
Reply
  • 0

    The endpoints are probably still getting updates if SUM is still working.  You could check the last time an .ide file was created in the distribution point (\\127.0.0.1\sophosupdate\CIDS\...etc..) or even at a test endpoint in program files directory of Sophos.

    I can only think that there must be an open handle to the servie that is preventing the service being removed.  You could try taking a look at the handles with Process Explorer.

    At the risk of breaking it, you could even try using the SC command line tool to delete the service before attempting an upgrade but you may want to check with Support.   As the installer is unable to delete the service, there is a good chance sc will not be able to either but at least you have a quick check to know when the upgrade is likely to work.

    It might b easier to log a support call so they can examine the logs in full.  They may even request a remote access to take a look.

    Regards,

    Jak

    :37349
Children
No Data