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

Failed to register patch agent.

I have no idea what has happened or changed, I just know that 3 days agao, my Sophos Console Server started spitting out the following Event Errors

"PID 3268 : TID 16

Failed to register patch agent. Internal exception information supplied. Version:100 Agent Version:1.0.303.0 Agent ID:44bc8259-c827-4a81-ae69-24c20cbaef75 User Agent:SophosAgent/1.0 (type="spa"; mid="44bc8259-c827-4a81-ae69-24c20cbaef75"; host="SMHR02") Internal Exception:System.Exception: Patch agent version is greater than maximum supported value.Agent Version: 1.0.303.0

at Sophos.Patch.EndpointCommunicator.MethodUtil.ValidateAgentVersion(String strAgentVersion, CapabilitiesVersion interfaceVersion)

at Sophos.Patch.EndpointCommunicator.PatchService.PutRegistrationV100(Stream streamRequestBody)

-- System Exception Details --

Message: Patch agent version is greater than maximum supported value.Agent Version: 1.0.303.0

Type: Exception

Source: PatchEndpointCommunicator

Target: Void ValidateAgentVersion(System.String, CapabilitiesVersion)

Stack Trace:

Sophos.Patch.EndpointCommunicator.MethodUtil.ValidateAgentVersion(String strAgentVersion, CapabilitiesVersion interfaceVersion)

Sophos.Patch.EndpointCommunicator.PatchService.PutRegistrationV100(Stream streamRequestBody)"

If anyone has any ideas I would be grateful, as it is not impacting our Encrypted clients

Regards

Andy

This thread was automatically locked due to age.

0 QC over 13 years ago

Hello Andy,
remember I had a similar issue during the 5.1. Beta. But as it was during testing and there were definitely changes involved, whatever resolved it then probably doesn't apply. Nevertheless - if you want to give it a try I used the instructions in article 16385. While it is long and doesn't seem to apply that did it, both clients with the issue registered then.
But it might be prudent to contact Support.
Christian
:28139
Cancel
Vote Up 0 Vote Down

Cancel
0 AndyBolton over 13 years ago

HI QC
Thanks for the info - I have however already tried the solution highlighted within that article - to no avail
Thanks
Andy
:28141
Cancel
Vote Up 0 Vote Down

Cancel
0 QC over 13 years ago

I see, Andy.
Please post a follow up when you've solved it.
Christian
:28145
Cancel
Vote Up 0 Vote Down

Cancel
0 MatthewEllis over 12 years ago

I am seeing this same error.
The linked fix did not work for me.
Still investigating but if anyone has a solution, the information would be appreciated.
Matthew
:44311
Cancel
Vote Up 0 Vote Down

Cancel