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 AutoUpdate Failure

Hello,

This is my first post, so please don't pick on me!

My side job at university requires me to look after several computers in class rooms, designed to mainly play back videos and support presentations.

Now while the job itself is usually not that challenging, I am somehow confronted with a more serious problem at the moment: Every computer is equipped with Sophos EndPoint Security System (or whatever it is called) and HDGuard. Two computers specifically have issues with Sophos:

Firstly, the "HiWI-PC", which refuses to update Sophos. It tells me, that Sophos cannot be auto updated. The weird thing is, that this happened exactly after updating Windows, there haven't been any problems right before the Windows updates. Because there's HDGuard on every PC, which resets the computer to a previously saved state after each reboot, it's necessary to have an update round every once in a while. Sophos itself is unaffected by HDGuard though, as I believe.

Secondly, the computer in room 21, which has the same problem, maybe a little bit worse: No auto update and it's impossible to get to the Sophos Endpoint Main Window (I am not sure how to call that window, you get whenever you right click on the icon in the right part of the task bar). Basically, that computer is completely unprotected, which is unacceptable.

I did some research on the error in room 21 and I have read something about problems with rights. After I have given more general rights to every user, the autoupdate lasted longer and actually created some directories, but the outcome was the same: It wasn't able to auto update. I have attached the logs here.

I am grateful for every hint, that might solve the problem.


Best regards!

:52275


This thread was automatically locked due to age.
Parents
  • OK, I tried to gather some new data, but it seems like I have an entirely new problem: I can't start ALMon.exe, which is why I can't see any icon in the tray bar.

    I've attached a screenshot of the error, translation goes like this:

    This application could not be started, because the Side-By-Side-Configuration is invalid. For more information, have a look at the "Anwendungsereignisprotokoll" (Application event log?). You may also use the command line tool sxstrace.exe.

    I actually have no idea, where to find that "application event log", probably a mistranslation anyway on my part.

    ALsvc.exe and ALUpdate.exe are also non-executable, as it tells me to check my Windows version. Some 64-bit/32-bit problem... I've never seen that before, but I'm not sure, if these two executables are necessary. (They should be, right? Why else would they be there?)

    As for the other computer, I'll didn't have a chance to look at it, but I'll come back to that soon.

    :52355
Reply
  • OK, I tried to gather some new data, but it seems like I have an entirely new problem: I can't start ALMon.exe, which is why I can't see any icon in the tray bar.

    I've attached a screenshot of the error, translation goes like this:

    This application could not be started, because the Side-By-Side-Configuration is invalid. For more information, have a look at the "Anwendungsereignisprotokoll" (Application event log?). You may also use the command line tool sxstrace.exe.

    I actually have no idea, where to find that "application event log", probably a mistranslation anyway on my part.

    ALsvc.exe and ALUpdate.exe are also non-executable, as it tells me to check my Windows version. Some 64-bit/32-bit problem... I've never seen that before, but I'm not sure, if these two executables are necessary. (They should be, right? Why else would they be there?)

    As for the other computer, I'll didn't have a chance to look at it, but I'll come back to that soon.

    :52355
Children
No Data