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

    this maybe useful for anyone picking up the thread, after seeing a similar issue on several machines the clue was in the sys/app event logs with errors relating to DCOM registration for an Autoupdate related GUID. These errors appeared after each time the autoupdate install completed. After browsing the com+ Applications under DCOMCNFG a catalog related error was generated. 

    In this particular instance COM+ failure was down to oleaut32.dll being unregistered. Registering the file fixed the problem.

    Certainly a good place to start would be to look for errors in the sys\app eventlogs after the install completes.

    SA

    :1396
Reply
  • 0

    hi,

    this maybe useful for anyone picking up the thread, after seeing a similar issue on several machines the clue was in the sys/app event logs with errors relating to DCOM registration for an Autoupdate related GUID. These errors appeared after each time the autoupdate install completed. After browsing the com+ Applications under DCOMCNFG a catalog related error was generated. 

    In this particular instance COM+ failure was down to oleaut32.dll being unregistered. Registering the file fixed the problem.

    Certainly a good place to start would be to look for errors in the sys\app eventlogs after the install completes.

    SA

    :1396
Children
No Data
Unfiltered HTML