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 Management Service Error 0x80004005

Hi

We are using SEC 4 on Windows 2003 R2 x64. Our Sophos management server rebooted for Windows updates last night and the management Service will not start up with the error 0x80004005.

We recently had to rename our domain and had previously encountered error 0x80004005 which was fixed by following step three of http://www.sophos.com/support/knowledgebase/article/16195.html

However, after the updates the service is failing to start again and the above KB no longer fixes the problem.

I have included excerpts of the management services logs below.

sophos-management-data.log

[Begin]
2010-08-13 09:04:31,517 [3] ERROR {Sophos.Management.Data.SPErrorHandler.CheckReturnCode} [(null)]
    |====> Call to SP dbo.ComputerBasedPolicyByTypeAndNameGet returned error code 22
2010-08-13 09:04:31,767 [3] ERROR {Sophos.Management.Data.DAUpdateHandler.da_RowUpdated} [(null)]
    |====> Exception thrown by command dbo.ComputerBasedPolicyAdd (System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object 'dbo.ComputerPolicyMapping' with unique index 'IX_ComputerPolicyMapping_ComputerID_Type_UC'.
The statement has been terminated.
sqlfile(36): Error inserting to ComputerPolicyMapping).
2010-08-13 09:04:31,767 [3] ERROR {Sophos.Management.Data.SPErrorHandler.AnalyseAndConvertException} [(null)]
    |====> Command execution attempted to violate unique index or primary key
[End]

sophos-management-services.log

[Begin]
2010-08-13 09:04:28,923 [3] INFO  {Sophos.Management.Services.Messaging.Handler.AfterPropertiesSet} [(null)]
     |====> Number of receivers registered 4
2010-08-13 09:04:28,923 [3] INFO  {Sophos.Management.Services.Messaging.Handler.AfterPropertiesSet} [(null)]
     |====> Registering for events from: Sophos.Management.Services.MessageReceiverBase to : SCF
2010-08-13 09:04:28,923 [3] INFO  {Sophos.Management.Services.Messaging.Handler.AfterPropertiesSet} [(null)]
     |====> Registering for events from: Sophos.Management.Services.Nac.MessageReceiver to : NAC
2010-08-13 09:04:28,923 [3] INFO  {Sophos.Management.Services.Messaging.Handler.AfterPropertiesSet} [(null)]
     |====> Registering for events from: Sophos.Management.Services.Sddma.MessageReceiver to : SDDM
2010-08-13 09:04:28,923 [3] INFO  {Sophos.Management.Services.Messaging.Handler.AfterPropertiesSet} [(null)]
     |====> Registering for events from: Sophos.Management.Services.MessageReceiverBase to : SAV
2010-08-13 09:04:28,939 [3] INFO  {Sophos.Management.Services.ServicesCore.GetService} [(null)]
     |====> GetService SystemSecretCollector
2010-08-13 09:04:28,939 [3] INFO  {Sophos.Management.Services.ServicesCore.GetService} [(null)]
     |====> Spring is aware of service - delegating
2010-08-13 09:04:28,939 [3] INFO  {Sophos.Management.Services.ServicesCore.GetService} [(null)]
     |====> GetService SddmaService
2010-08-13 09:04:28,939 [3] INFO  {Sophos.Management.Services.ServicesCore.GetService} [(null)]
     |====> Spring is aware of service - delegating
2010-08-13 09:04:31,532 [3] WARN  {Sophos.Management.Services.Sddma.UpstreamPolicyRepository.GetByServer} [(null)]
     |====> GetByName for 3d941439-3149-408d-b98b-bec12f654032 didn't work. Returning default policy.
[End]

Any help would be greatly appreciated,

Regards,

James Beck

:4596


This thread was automatically locked due to age.
Parents
  • I've tried all the solutions regarding the management service that won't start.

    But everything failed.

    Fortunately, I had another EM server (Which has also the database and the management server onboard) and

     I exported a big part of the registry (HKLM\Software\Sophos), edited it with notepad to change the servername from old to new and I imported the keys in the new server, on which the management server failed to start.

    And voila; it works!!!

    The Management service starts and the EM console is accessible!! Ofcourse, you have to edit some configuration settings, but it works. I have a sample of the exported registry parts available for anyone who needs it.

    :6475
Reply
  • I've tried all the solutions regarding the management service that won't start.

    But everything failed.

    Fortunately, I had another EM server (Which has also the database and the management server onboard) and

     I exported a big part of the registry (HKLM\Software\Sophos), edited it with notepad to change the servername from old to new and I imported the keys in the new server, on which the management server failed to start.

    And voila; it works!!!

    The Management service starts and the EM console is accessible!! Ofcourse, you have to edit some configuration settings, but it works. I have a sample of the exported registry parts available for anyone who needs it.

    :6475
Children
No Data