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

Client Failed scynchronize with Safeguard Server

Hi Guys,

As per subject above, appreciate if anyone can share on how to solve the issue or root cause of the issue .

Below is the information for Sophos Safaguard deployment at our client site. Thanks

Main Problem / Scenario:
Client failed to synchronize with Safeguard Console

Temporary Solution:

Restart IIS service

Other Issue Found:

1. IIS event viewer ID 5508
2. Database CPU utilization 96-100%
3. Open Safeguard Console took about 20min to open after login username & Password
4. Database integrity test took about 20min to complete (Direct access to database table no issue or problem)


Deployment:

1. Sophos Safeguard 6.0
2. Total Client is 3000 with license DE,DX & CP
3. Safeguard Console & management server install on single server
4. Safeguard database install on single server with other safeguard database (Other Team Project) differenttiate by MSSQL instance and database name
5. Database maintenance is applied including event table shrink script execute daily at 1am

:55694


This thread was automatically locked due to age.
  • There a re a lot of things that could be. Have you tried going through this guide?

    https://www.sophos.com/support/knowledgebase/109662.aspx

    :55704
  • Hi Simon,

    Appreciate the feedback, I have refer the KB provided and support case has been open with Sophos Support and while waiting  Im also open to other suggestion or experience by other customer and partner if they have encounter similiar issue. Thanks :smileywink:

    :55718
  • Glad to have helped.

    Is it just one client that cant synchronise or is it all of them?

    :55719
  • Hi Azwan,

    any idea what causes the heavy load on the server hosting the Database? Which process consumes the majority of the CPU time on this machine (if its the SQL process, can you identify which Database is involved)?

    When starting the Management Center and running DB Integrity check take a long time, its problaby related to the size of a specific table (if not releated to the high CPU load). I would suspect the EVENT or FILE_ACCESS_EVENT table.

    When you run the following query on the tables, what is the result of these?

    SELECT COUNT (*) FROM dbo.EVENT

    SELECT COUNT (*) FROM dbo.FILE_ACCESS_EVENT

    (The Management Center brings up a warning if the Event table exceed the 500.000 limit, so I guess the numbers should be smaller here)

    Regards,

    ChrisD

    :55728