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 Log writer service is installed in our SEC but the log files are not updated or not retrieved from db

Hi All,

 

We have issues in Sophos Log writer service installed in our SEC.  The logs are not getting pulled and is is not updated in C:\Sophoslogs.

Below is the error i could see in event logs, any one can suggest a fix for below issue ?

Log Name: Application
Source: Sophos Reporting Log Writer
Date: 17/12/2018 02:15:19
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXX
Description:
System.Data.SqlClient.SqlException - Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. The DefaultCommonEvents call did not execute correctly.
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
<System>
<Provider Name="Sophos Reporting Log Writer" />
<EventID Qualifiers="0">0</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-12-17T02:15:19.000000000Z" />
<EventRecordID>480373</EventRecordID>
<Channel>Application</Channel>
<Computer>xxx</Computer>
<Security />
</System>
<EventData>
<Data>System.Data.SqlClient.SqlException - Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. The DefaultCommonEvents call did not execute correctly.</Data>
</EventData>
</Event>

Log Name: Application
Source: Sophos Reporting Log Writer
Date: 17/12/2018 02:23:20
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXX
Description:
System.Data.SqlClient.SqlException - Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. The DefaultFirewallEvents call did not execute correctly.
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
<System>
<Provider Name="Sophos Reporting Log Writer" />
<EventID Qualifiers="0">0</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-12-17T02:23:20.000000000Z" />
<EventRecordID>480374</EventRecordID>
<Channel>Application</Channel>
<Computer>XXX</Computer>
<Security />
</System>
<EventData>
<Data>System.Data.SqlClient.SqlException - Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. The DefaultFirewallEvents call did not execute correctly.</Data>
</EventData>
</Event>



This thread was automatically locked due to age.
Parents
  • Hello Arjunan Subramanian,

    when did it start to fail - I assume it worked before? SEC is working fine?
    The error is "just" a timeout, guess the SQL Server's ERRORLOG won't have more details. Did you try to restart the SQL Server instance?

    Christian

Reply
  • Hello Arjunan Subramanian,

    when did it start to fail - I assume it worked before? SEC is working fine?
    The error is "just" a timeout, guess the SQL Server's ERRORLOG won't have more details. Did you try to restart the SQL Server instance?

    Christian

Children
  • Thanks for

    QC said:

    Hello Arjunan Subramanian,

    when did it start to fail - I assume it worked before? SEC is working fine?
    The error is "just" a timeout, guess the SQL Server's ERRORLOG won't have more details. Did you try to restart the SQL Server instance?

    Christian

     

     

    Thanks for your reply Christ ,it was working before the upgrade of sql server.

    We recently upgraded sql server2008r2 to sql server 2014 after that it stopped working.

    We have checked the connection strings in configuration xml file,all looks good, any suggestions would be really helpful to resolve the issue

    we didn't restart the sql instance since it is a new DB server.

    is it any port to be opened in new database server ?

  • Hello Arjunan Subramanian,

    the Report Writer has no special requirements. It seems to be able to connect - otherwise you'd get a different error - but then retrieval of the data times out. Can't say right now if an SP is involved (but anyway additional information, if there is some, can likely only be found on the SQL server).

    Christian