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 9 Installation problems on Windows 2003 Server boxes

Looking around for a possible solution, or at least people that have experienced something similar.  I've talked to two different technicians on this, with responses that seem unrelated to the actual problem.

We're having problems with Sophos installations/updates on Windows Server 2003 machines.  There are a number of servers that are stuck in various states.  Policy Compliance is blank, Up to Date might be blank, or there is an error.  On those serves, all three Sophos components are installed.  Most of the time, the Sophos icon on the server is blue, with no errors.  Sometimes, the icon will be in the process of updating and in most cases, msiexec.exe is running anywhere from 25% to 99%.

When I see this type of activity, I have no choice but to kill the msiexec.exe process. If I attempt to update again, I’’’’ll just get the same result (usually gets stuck at Phase 2 of 2 on the installation), with msiexec.exe spinning up around that same range. To be sure, I’’’’ve let this run all night, and it would still be the same the next day. My only choice after that is to uninstall all three components, reboot, and then reinstall…. At the reinstallation though, the same thing will happen. At phase 2 of 2, it’’’’ll just sit there, with the msiexec.exe process kicking up the CPU. Again, I’’’’ve let this sit for awhile, and it never completes. Once I kill the process though, the Sophos icon turns blue, and the console reports that it’’’’s healthy.

While I can’’’’t complain about the healthy status of our clients, this problem seems to come back sometime within that next month.

Hope someone out there can relate and/or help out.

Thanks!

:2030


This thread was automatically locked due to age.
  • I had a very vaguely similar problem once, so you can try my solution to see if it applies.

    Turn off the Indexing Service on a problem server. Reinstall Sophos and try the update again.

    :2088
  • Thanks for the feedback.  the indexing service is already disabled on all of our servers.

    :2291
  • I'd suggest using Sysinternals' Process Monitor which should show what msiexec.exe is doing when it's burning cycles (maybe in conjunction with Process Explorer). I understand that not all of your servers have this problem.

    After you kill the runaway msiexec.exe - what does the updating log say (it should at least tell you which component has been or should have been updated) and what's in ALUpdate....log (in the %ProgramFiles%\Sophos\AutoUpdate\Logs\ folder)?

    Have you tried simply emptying (or deleting) the ...\AutoUpdate\Cache\  folder instead of uninstalling?

    Christian

    :2294
  • Checking the autoupdate log as Christian said will show you which product (SAVXP, RMSNT etc.) it was installing last.  Sounds like it is sticking on one.

    When you know which product it is, you can check the end of the install log to see what it was doing last.

    They will be in c:\windows\temp\   (most recent sophos log file)

    A normal log will end with something general like installation failed/succeeded.  If it sticks you will not see this, but it should tell you what function or customaction it is attempting to do.

    Let us know what you find.

    OD

    :2330