Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 14 replies
  • Subscribers 1 subscriber
  • Views 12255 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

Sophos Anti-Vrus installation fails at AutoUpdate install

Sergey

Hello All,

I am attempting to install Sophos AntiVirus v7.6.6 on Windows 2003 Server Standard in an enterprise environment. AutoUpdate installation is failing following policies application. I have tried manually cleaning up previous Sophos installation, installing in Normal Mode, as well as Safe Mode with Networking, and resetting the Local Security Policy. Other servers on the same subnet, targeting the same Sophos enterprise server are having no issues.

In Sophos ES setup.log, I get the following:

12/4/2009,9:28:38 AM,Information,Beginning installation of C:\DOCUME~1\SergeyG\LOCALS~1\Temp\sophosa\Sophos AutoUpdate.msi with command line BOOTSTRAP=noupdate REBOOT=ReallySuppress TRANSFORMS=1033.mst UPDATELOCATION="C:\WINDOWS\Packages\Sophos" RMSACTION=7,
12/4/2009,9:28:38 AM,ERROR,Installation of C:\DOCUME~1\SergeyG\LOCALS~1\Temp\sophosa\Sophos AutoUpdate.msi failed with error code 1601,

Does anyone know what the problem might be?

Thank you,

Sergey

:350


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

    Hi,

    using the autoupdate.msi will just lead to an updating issue but it might help to find out what the root cause for this problem is.

    In this case i assume that there is a problem with the Microsoft Installer.

    As Elmo recommendet you can have a look into the sau install logs - should be lots of information in there and if thats the case best thing is to look out for "value 3" in the log.

    If there is no autoupdate log available or if it is quite short giving no obvious error or some error according the Microsoft installer you can try the following things (you won't break anything if you perform those commands anyway):

    1. Re-register the Microsoft installer using

    msiexec /unregister

    and 

    msiexec /regserver

    2. Update your Microsoft installer to the latest version (if it is not already the latest one).

    You might also want to check if the Microsoft installer service has been disabled or msi execution has been forbidden by the group policy.

    Hope this helps :-)

    Cheers

    :363
Reply
  • 0

    Hi,

    using the autoupdate.msi will just lead to an updating issue but it might help to find out what the root cause for this problem is.

    In this case i assume that there is a problem with the Microsoft Installer.

    As Elmo recommendet you can have a look into the sau install logs - should be lots of information in there and if thats the case best thing is to look out for "value 3" in the log.

    If there is no autoupdate log available or if it is quite short giving no obvious error or some error according the Microsoft installer you can try the following things (you won't break anything if you perform those commands anyway):

    1. Re-register the Microsoft installer using

    msiexec /unregister

    and 

    msiexec /regserver

    2. Update your Microsoft installer to the latest version (if it is not already the latest one).

    You might also want to check if the Microsoft installer service has been disabled or msi execution has been forbidden by the group policy.

    Hope this helps :-)

    Cheers

    :363
Children
No Data