Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 29 replies
  • Subscribers 1 subscriber
  • Views 30411 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 4.7 upgrade to SEC 5.0 fail

xm51

Hi,

When i try upgarde sec 5.0 fail to install show error code : 1603 ,then i try follow http://www.sophos.com/support/knowledgebase/article/116231.html , still got same error, please see below error infrom, please help check what is issue

2/21/2012 1:26:52 AM, INFO : About to install Server32.msi
2/21/2012 1:26:53 AM, INFO : Processing INSTALLMESSAGE_TERMINATE message from MSI
2/21/2012 1:26:53 AM, INFO : Installation of Server32.msi failed with error code: 1603
2/21/2012 1:26:53 AM, INFO : Ended installing Server32.msi
2/21/2012 1:26:53 AM, INFO : Processing INSTALLMESSAGE_INSTALLEND message from MSI
2/21/2012 1:26:53 AM, INFO : Installation of Management Server failed with error code: 1603
2/21/2012 1:26:53 AM, INFO : Deactivate state: Installing
2/21/2012 1:26:53 AM, INFO : Activate state: Failed
2/21/2012 1:26:53 AM, INFO : Entered Installation failed page.

Thanks & Regards

XM

:22257


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

    Hello,

    a completely different approach: 1603 is well known to all who need to install updates for Office or .Net Framework.

    1603-failures at the installation of a msi or msp are mostly caused by a missing msi-file for the original product. When you install application2.msi which replaces application1.msi, the Windows Installer needs access to application1.msi to uninstall the old software package.

    Translated to Sophos EC 5: In order to install server32.msi from EC 5.0, the installer will need to access server32.msi (if that is the old name) from EC 4.7 to gather uninstall information.

    During installation of EC 4.7, all the installation ressources together with all the required msi-files were stored in c:\sec47. Is this folder still stored on c:? If it was removed before the upgrade, the Windows Installer will fail to uninstall 4.7-components during the installation of 5.0.

    It may sound strange, but starting the 4.7-installer will recreate c:\sec47 and it's contents. Just start the installer, wait for the decompression of all files, and abort the installer for EC 4.7. The installation ressources for 4.7 will be recreated, so it is possible to do an upgrade to 5.0.

    Best regards

    Detlev

    :22627
Reply
  • 0

    Hello,

    a completely different approach: 1603 is well known to all who need to install updates for Office or .Net Framework.

    1603-failures at the installation of a msi or msp are mostly caused by a missing msi-file for the original product. When you install application2.msi which replaces application1.msi, the Windows Installer needs access to application1.msi to uninstall the old software package.

    Translated to Sophos EC 5: In order to install server32.msi from EC 5.0, the installer will need to access server32.msi (if that is the old name) from EC 4.7 to gather uninstall information.

    During installation of EC 4.7, all the installation ressources together with all the required msi-files were stored in c:\sec47. Is this folder still stored on c:? If it was removed before the upgrade, the Windows Installer will fail to uninstall 4.7-components during the installation of 5.0.

    It may sound strange, but starting the 4.7-installer will recreate c:\sec47 and it's contents. Just start the installer, wait for the decompression of all files, and abort the installer for EC 4.7. The installation ressources for 4.7 will be recreated, so it is possible to do an upgrade to 5.0.

    Best regards

    Detlev

    :22627
Children
No Data