Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 1 subscriber
  • Views 7969 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

Autoupdate failed and insufficient rights to do anything with Sophos

kiril982

Hi Sophos team,

I had to register as I have annoying problem with Sophos. The most I got from my IT admin (who is in Denmark while I am on a stay in China) is to uninstall it and instal something else. While that's the last option. I will give a last try to ask you.

I neither have the rights to manipulate with Sophos properly (it says "insufficient right"), nor the autoupdate funtion works. This is all from today when I tried to delete a virus or whatever was it from usb, and I noticed the first one. Once I tried to fix using your (increadibly confusing and overloaded) forums, the auto-update stoped working as well. Its a bit annoying and I got a bit frustrated.

1. I have tried to fix the "sufficient rights" issue by following your posted procedure i.e. updating the SID numbers using the SophosLocalGroups.txt file but it didn't work. I also downloaded some file, and than copied it in the indicated lcoation and run it (which was suppose to automatically updade the SIDS) but it was waste of time in both reading and doing it.

2. I have tried to fix the auto-update issue, i even don't remember what I did, but i stoped the Sophos virus protection and did what was written in your post and activated it again. It didn't work.

Is there any solution except spending hours and trying to understand what SID and DSN settings are or?

Thanks a lot,

Kiril

p.s. for the record, when I start up my pc, the notification appears with "Sophos Endpoing Secirity and Control updater has faild to download", and in the update log the following appears (the other updates seem to work properly- as it says in the log):

Time: 23-07-2012 23:37:14
Message: Could not connect to the server. Check that this computer is connected to the network and that Sophos AutoUpdate is configured to update from the correct location with the correct credentials and proxy details (if required)
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:13
Message: Downloading product Sophos AutoUpdate from server \\SOFUS\SophosUpdate\CIDs\S000\SAVSCFXP\
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:11
Message: Could not add a connection to server \\SOFUS\SophosUpdate; user djf\sophos; Windows error 53
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:09
Message: Could not connect to the server. Check that this computer is connected to the network and that Sophos AutoUpdate is configured to update from the correct location with the correct credentials and proxy details (if required)
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:08
Message: Downloading product SAVXP from server \\SOFUS\SophosUpdate\CIDs\S000\SAVSCFXP\
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:06
Message: Could not add a connection to server \\SOFUS\SophosUpdate; user djf\sophos; Windows error 53
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:04
Message: Could not connect to the server. Check that this computer is connected to the network and that Sophos AutoUpdate is configured to update from the correct location with the correct credentials and proxy details (if required)
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:03
Message: Downloading product RMSNT from server \\SOFUS\SophosUpdate\CIDs\S000\SAVSCFXP\
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:37:01
Message: Could not add a connection to server \\SOFUS\SophosUpdate; user djf\sophos; Windows error 53
Module: CIDUpdate
Process ID: 4808
Thread ID: 4412

Time: 23-07-2012 23:36:38
Message: *************** Sophos AutoUpdate started ***************
Module: ALUpdate
Process ID: 4808
Thread ID: 4412

:27249


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

    Hello Kiril,

    thanks. Close, it shows that downloading AutoUpdate from your server failed and in the last lines it starts trying Sophos - which suggests that Sophos is set a secondary update location. As the update cycle is not finished at this point there must be additional lines and one of them should read SDDSUpdate(SyncProduct.Start): SAVXP, Sophos. The following lines should show that it successfully contacted Sophos (might be that at this time there was nothing to download though - if you go back to the log which contains the actions around 15:03 you should see that something has be done).

    If it successfully updates from Sophos this would explain a) that Sophos is indeed current and correctly displayed in WSC as such and b) you nevertheless get the failed message because of Trace(2012-Jul-25 19:03:25): ALUpdate(ProductUnavailable): RMSNT, Sophos. RMS (the management component) can't be updated from Sophos so this is not actually an error (I use to say it's a gentle reminder from Sophos that the clients should update from the site's infrastructure :smileywink:).

    Christian

    :27339
Reply
  • 0

    Hello Kiril,

    thanks. Close, it shows that downloading AutoUpdate from your server failed and in the last lines it starts trying Sophos - which suggests that Sophos is set a secondary update location. As the update cycle is not finished at this point there must be additional lines and one of them should read SDDSUpdate(SyncProduct.Start): SAVXP, Sophos. The following lines should show that it successfully contacted Sophos (might be that at this time there was nothing to download though - if you go back to the log which contains the actions around 15:03 you should see that something has be done).

    If it successfully updates from Sophos this would explain a) that Sophos is indeed current and correctly displayed in WSC as such and b) you nevertheless get the failed message because of Trace(2012-Jul-25 19:03:25): ALUpdate(ProductUnavailable): RMSNT, Sophos. RMS (the management component) can't be updated from Sophos so this is not actually an error (I use to say it's a gentle reminder from Sophos that the clients should update from the site's infrastructure :smileywink:).

    Christian

    :27339
Children
No Data