We saw the following error for about one hour this morning (6:30AM - 7:20AM EST). Assume it was a bad update, and once a new update arrived all corrected itself.
Could this be a local issue, something that we may have been able to prevent, or something beyond our control. Sat 2009-07-18 07:10:19: SNF MessageScan: c:\mdaemon\queues\local\md50144568162.msg, Bad Matrix! Sat 2009-07-18 07:10:19: SNF Debug: EvaluationMatrix::OutOfRange Sat 2009-07-18 07:10:19: SNF MessageScan: c:\mdaemon\queues\local\md50144568163.msg, Bad Matrix! Sat 2009-07-18 07:10:19: SNF Debug: EvaluationMatrix::OutOfRange Sat 2009-07-18 07:10:19: SNF MessageScan: c:\mdaemon\queues\local\md50144568164.msg, Bad Matrix! Sat 2009-07-18 07:10:19: SNF Debug: EvaluationMatrix::OutOfRange Sat 2009-07-18 07:10:20: SNF MessageScan: c:\mdaemon\queues\local\md50144568165.msg, Bad Matrix! Sat 2009-07-18 07:10:20: SNF Debug: EvaluationMatrix::OutOfRange Sat 2009-07-18 07:10:20: SNF MessageScan: c:\mdaemon\queues\local\md50144568166.msg, Bad Matrix! Sat 2009-07-18 07:10:20: SNF Debug: EvaluationMatrix::OutOfRange Thanks! --PR ############################################################# This message is sent to you because you are subscribed to the mailing list <sniffer@sortmonster.com>. To unsubscribe, E-mail to: <sniffer-...@sortmonster.com> To switch to the DIGEST mode, E-mail to <sniffer-dig...@sortmonster.com> To switch to the INDEX mode, E-mail to <sniffer-in...@sortmonster.com> Send administrative queries to <sniffer-requ...@sortmonster.com>
