Hello,
This morning we saw that the three Sophos Patch Endpoint Comm/Endpoint Orch/Serer Comm services were in a 'Starting' state.
All their logs show this common error:
2019-07-23 09:22:44 | PID 5732 | TID 4 | ID: 5000 | Severity: error | Error fetching upgrade status.-- System Exception Details --
Message: Could not find stored procedure 'dbo.usp_UpgradeStatusGet'.
Type: SqlException
Source: .Net SqlClient Data Provider
Target: Void OnError(System.Data.SqlClient.SqlException, Boolean, System.Action`1[System.Action])
Help Link:
-- Evidence At Publish --
The DB is local on the server and the Sophos connection string registry key is correct (SOPHOSPATCH52).
We have another Sophos install on another box which also points to SOPHOSPATCH52, so we exported the stored procedures there and imported them on the problem box.
A new error presents:
2019-07-23 09:23:14 | PID 5732 | TID 4 | ID: 5000 | Severity: error | Error fetching upgrade status.-- System Exception Details --
Message: Input string was not in a correct format.
Type: FormatException
Source: mscorlib
Target: Void StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)
Help Link:
-- Evidence At Publish --
By all counts, the Sophos SEC GUI is working, and we're not sure how long these three services have been stuck in Starting. We installed Sophos back in 2017. The DB backups of SOPHOSPATCH52 are all 430KB, going back to early June so the stored procedures weren't deleted recently. On the working Sophos Patch instance, the DB is 1.6GB.
How should we proceed?
Thanks,
David
This thread was automatically locked due to age.