Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 3331 views
  • Users 0 members are here
Options
Suggested
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

Error Message Suppression in Enterprise Console.

Primax

Hi all, I am trying to suppress some messages in the enterprise console as they are not relevant and just taking up room.

This is the error that is annoying me :-) http://www.sophos.com/support/knowledgebase/article/14383.html

I have exported my savconf.xml file and adjusted with adding the following to the end of the file as instructed !

http://www.sophos.com/support/knowledgebase/article/54229.html

Placed before </config> tag in exported savconf.xml

<inst:install xmlns:inst="http://www.sophos.com/SAVXP/SavInstallConfiguration" xmlns="http://www.sophos.com/SAVXP/SavInstallConfiguration">
 <onAccess>
  <suppressErrors>
   <item>53</item>
  </suppressErrors>
 </onAccess>
</inst:install>

I have then imported my savconf.xml file
by placing the xml file in my \\servername\interchk\esxp\ area
the output displayed in the dos windows does show that the file has been read but the messages still appear in my console.
just as a side note i did try this method but also had no joy http://www.sophos.com/support/knowledgebase/article/13872.html
Any help is appreciated on this
Kind regards
paul

:3070


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    The savconf.xml should work and prevent the client sending the message up to Enterprise Console.  I would check that machine.xml is being updated with this new code.  However, a simpler solution, if you don't mind the message being sent (if there aren't that many being sent and therefore bandwidth a concern) and you just don't want it to be stored when it arrives at the management server, you could try the following:

    In the SOPHOS3 and SOPHOS4 database (depending on the version you are running), there is a table called: "ErrorAlertFilters".  Can you guess what it does :)

    So you could add to this table by running:

    osql -E -S .\sophos -d SOPHOS4 -Q "insert into dbo.ErrorAlertFilters ([Source], [Number]) VALUES ('SAV', '-235130933')"

    where:

    .\sophos represents the local sophos sql instance, you may need to adjust this if you have a different instance name.

    SOPHOS4 is the database name, if you are using SEC 3, change this to SOPHOS3.

    as:

    e03d035 hex = 235130933 dec

    To check it has been inserted correctly run:

    osql -E -S .\sophos -d SOPHOS4 -Q "select * FROM dbo.ErrorAlertFilters" -o C:\ErrorAlertFilters.txt -w 1000

    Then check:
    C:\ErrorAlertFilters.txt.

    If you acknowledge all your existing ones I think this should prevent them coming back.  You can always remove this filter at any time.

    I hope this still works.

    Thanks,

    Jak

    :3086
Reply
  • 0

    Hi,

    The savconf.xml should work and prevent the client sending the message up to Enterprise Console.  I would check that machine.xml is being updated with this new code.  However, a simpler solution, if you don't mind the message being sent (if there aren't that many being sent and therefore bandwidth a concern) and you just don't want it to be stored when it arrives at the management server, you could try the following:

    In the SOPHOS3 and SOPHOS4 database (depending on the version you are running), there is a table called: "ErrorAlertFilters".  Can you guess what it does :)

    So you could add to this table by running:

    osql -E -S .\sophos -d SOPHOS4 -Q "insert into dbo.ErrorAlertFilters ([Source], [Number]) VALUES ('SAV', '-235130933')"

    where:

    .\sophos represents the local sophos sql instance, you may need to adjust this if you have a different instance name.

    SOPHOS4 is the database name, if you are using SEC 3, change this to SOPHOS3.

    as:

    e03d035 hex = 235130933 dec

    To check it has been inserted correctly run:

    osql -E -S .\sophos -d SOPHOS4 -Q "select * FROM dbo.ErrorAlertFilters" -o C:\ErrorAlertFilters.txt -w 1000

    Then check:
    C:\ErrorAlertFilters.txt.

    If you acknowledge all your existing ones I think this should prevent them coming back.  You can always remove this filter at any time.

    I hope this still works.

    Thanks,

    Jak

    :3086
Children
No Data
Unfiltered HTML