Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 4139 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

Clear reboot message from console without rebooting machines

Tech03

Does anyone know if there is a way of clearing the error '0000006d - alert does not clear following reboot' without having to edit the registry on the problem machine.  Can it be done via Enterprise Console?

Thanks,


Sean

:11515


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

    Well I guess in the worst case you could go after the database using PurgeDB.exe.  0000006d  hex = 109 dec, so the following command:

    PurgeDB.exe -action=delete -category=errors -HistoryLengthInDays=0 -type=AutoUpdate -code=109

    should clear the alerts. PurgeDB.exe is in the Enterprise Console directory from SEC version 4 onwards.   This would run in effect the same command as:

    sqlcmd -E -S .\SOPHOS -d sophos50 -Q "UPDATE dbo.Errors SET Outstanding=0 WHERE Source='ALC' AND Number=109"

    Where:
    .\SOPHOS represents a local SOPHPOS named SQL instance.

    SOPHOS50 would be for SEC 5, for SEC 4.7: SOPHOS47, SEC 4.5: SOPHOS45, SEC 4.0: SOPHOS4.

    This would set the reboot alert for all machiens to not outstanding.  The ComputersAndDeletedComputers table does have a pointer however to the Errors table so the above command will not clear the warning triangle against the machine.  The purge task the management service performs will fix that up but it may take up to 24 hours to run.  If you can't wait for that, you could run:

    SQLCMD -E -S .\SOPHOS -d SOPHOS50 -Q "EXEC ErrorUpdateLatestPointerInAllComputers N'ALC'"

    This is the same command the purge task runs to clean things up, note this is for SEC 5, adjust the SOPHOS50 as mentioned above for other versions of SEC.

    The only downside being that for machines that haven't rebooted yet you wouldn't centrally know.  Possibly not so much of an issue.

    Regards,

    Jak

    :20555
Reply
  • 0

    Well I guess in the worst case you could go after the database using PurgeDB.exe.  0000006d  hex = 109 dec, so the following command:

    PurgeDB.exe -action=delete -category=errors -HistoryLengthInDays=0 -type=AutoUpdate -code=109

    should clear the alerts. PurgeDB.exe is in the Enterprise Console directory from SEC version 4 onwards.   This would run in effect the same command as:

    sqlcmd -E -S .\SOPHOS -d sophos50 -Q "UPDATE dbo.Errors SET Outstanding=0 WHERE Source='ALC' AND Number=109"

    Where:
    .\SOPHOS represents a local SOPHPOS named SQL instance.

    SOPHOS50 would be for SEC 5, for SEC 4.7: SOPHOS47, SEC 4.5: SOPHOS45, SEC 4.0: SOPHOS4.

    This would set the reboot alert for all machiens to not outstanding.  The ComputersAndDeletedComputers table does have a pointer however to the Errors table so the above command will not clear the warning triangle against the machine.  The purge task the management service performs will fix that up but it may take up to 24 hours to run.  If you can't wait for that, you could run:

    SQLCMD -E -S .\SOPHOS -d SOPHOS50 -Q "EXEC ErrorUpdateLatestPointerInAllComputers N'ALC'"

    This is the same command the purge task runs to clean things up, note this is for SEC 5, adjust the SOPHOS50 as mentioned above for other versions of SEC.

    The only downside being that for machines that haven't rebooted yet you wouldn't centrally know.  Possibly not so much of an issue.

    Regards,

    Jak

    :20555
Children
No Data