| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3172.1 | | FORTY2::LEAVER | | Thu Apr 17 1997 10:15 | 10 |
| You say that the peer MTA has stopped working so lets look at this first.
What actually happens and do they get any other events in the event file ?
As it used to work has anything changed on their system ?
Are there any events for insufficient memory ?
Karen
-----
|
| 3172.2 | Also preventing connection to Peer MTA | KERNEL::16.182.96.46::houldingj | | Thu Apr 17 1997 10:45 | 27 |
| Hi
The event log shows :
Event: Outbound Failure
RTSE Entity Initiating Failure = This MTA
Abort Reason Code = Local System Problem
Local Diagnostic = Internal Error
Follwed by:
Event: Internal Error from node......
Diagnostic no. = 102
So it looks as if this is why the MTA cannot make an association with the
Peer MTA.
I can find no information about these events. Where can I look? Or should I
log an IPMT?
Regards
Jill
|
| 3172.3 | | FORTY2::LEAVER | | Fri Apr 18 1997 10:07 | 15 |
| It makes more sense now that we know the Internal Error event is associated with
the Outbound Failure.
These events are documented in Tuning and Problem Solving.
However as they are internal software errors it cannot give any actions to
resolve the problem.
I think that 102 is reported because of insufficient receive buffers. So are
they having any memory problems ? Are there any events for insufficient memory?
As it used to work has anything changed on their system ?
Karen
-----
|