Insufficient privileges

Hi Nick,

You can assign users to the local groups of Sophos, however if you're using the same account now as when you were able to open Sophos it seems unlikely you are no longer of the local SophosAdministrators group.  It is worth checking though.  If you right click on my computer and choose manage, you should be able to find the users and groups,  from there, check who is a member of the above Sophos group.  Hopefully the account you are logged in as is.  If you do find yourself missing add yourself back in.  You will not need to log off and on before the permissions are granted.

If the group membership looks good, and you also mention problems with other applications.  I would suggest permissions, either at a file or registry level are the most likely.  How much memory is the savservice.exe process consuming on the machine.  It should be in the order of ~60 to ~90 MB.  If it is significantly less, i.e. in the range of 10 MB, it would suggest the failure to load a significant portion of the components.

You may wish to rule out a virus by running a command line scan of the machine, ideally this would be run from files taken from a known clean machine but you'll probably be safe running sav32cli from the local machine, to do so. launch a command prompt as administrator, navigate to "C:\Program Files\Sophos\Sophos Anti-Virus" or the relevant directory and run SAV32CLI.  It would be interesting to see, a) if this works, proving that the virus data is in good order and b) there doesn't appear to be any obvious piece of malware on the machine.

Failing all this, I would suggest:

1. Stop the SAVService (from using the service control manager SCM. Start->Run and type "services.msc"

2. Get a copy of ProcessMonitor from http://live.sysinternals.com/Procmon.exe

3. Start Process Monitor running.

4. Start the SAVService using the SCM.

5, After SAVService seems to have started stop Process Monitor from capturing

6. Search for "Access Denied" this is usually a good place to start.

7. Fix any permission problems on either the registry or files that are incorrect.  Ideally using a reference system to compare ACLs.

8. Start SAVService.

9. Start the GUI of SAV, hopefully all is in order.

I hope this helps and gives you a few things to try.

Thanks

JAK

Hi Nick,

You can assign users to the local groups of Sophos, however if you're using the same account now as when you were able to open Sophos it seems unlikely you are no longer of the local SophosAdministrators group.  It is worth checking though.  If you right click on my computer and choose manage, you should be able to find the users and groups,  from there, check who is a member of the above Sophos group.  Hopefully the account you are logged in as is.  If you do find yourself missing add yourself back in.  You will not need to log off and on before the permissions are granted.

If the group membership looks good, and you also mention problems with other applications.  I would suggest permissions, either at a file or registry level are the most likely.  How much memory is the savservice.exe process consuming on the machine.  It should be in the order of ~60 to ~90 MB.  If it is significantly less, i.e. in the range of 10 MB, it would suggest the failure to load a significant portion of the components.

You may wish to rule out a virus by running a command line scan of the machine, ideally this would be run from files taken from a known clean machine but you'll probably be safe running sav32cli from the local machine, to do so. launch a command prompt as administrator, navigate to "C:\Program Files\Sophos\Sophos Anti-Virus" or the relevant directory and run SAV32CLI.  It would be interesting to see, a) if this works, proving that the virus data is in good order and b) there doesn't appear to be any obvious piece of malware on the machine.

Failing all this, I would suggest:

1. Stop the SAVService (from using the service control manager SCM. Start->Run and type "services.msc"

2. Get a copy of ProcessMonitor from http://live.sysinternals.com/Procmon.exe

3. Start Process Monitor running.

4. Start the SAVService using the SCM.

5, After SAVService seems to have started stop Process Monitor from capturing

6. Search for "Access Denied" this is usually a good place to start.

7. Fix any permission problems on either the registry or files that are incorrect.  Ideally using a reference system to compare ACLs.

8. Start SAVService.

9. Start the GUI of SAV, hopefully all is in order.

I hope this helps and gives you a few things to try.

Thanks

JAK