Anyone have any suggestions about how to correct this? This happens on
just a few Max 6000's - others run for months with no fatalhistory entries.
Thanks!
ERROR_UNEXPECTED =
Warning 179 indicates an anomalous event order occurred in terminating a digital call. Normally, a digital
call can terminate in an anomalous event order and not cause harm. Warning 179 provides debug information in
the unlikely event of a fatal error immediately following the warning.
WARNING: Index: 179 Load: tbaxkh.m60 Revision: 6.1.7
Date: 06/20/2001. Time: 05:48:39
Location: b0147580 b0147644 b030ba78 b030bf64 b030d84c b014a870
WARNING: Index: 179 Load: tbaxkh.m60 Revision: 6.1.7
Date: 06/20/2001. Time: 05:48:39
Location: b0147580 b0147644 b030ba78 b030bf64 b030d84c b014a870
WARNING: Index: 179 Load: tbaxkh.m60 Revision: 6.1.7
Date: 06/20/2001. Time: 05:48:39
Location: b0147580 b0147644 b030ba78 b030bf64 b030d84c b014a870
_____________________________________________________________________
Bob Dozier rwdozier at apex2000.net
Apex 2000 Internet Services Corporation Phone: (915) 570-1676
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request at bungi.com
Archives: http://www.nexial.com/mailinglists/