| Title: | VAX MAILGATE for MEMO |
| Moderator: | STKHLM::OLSSON |
| Created: | Sat Feb 25 1989 |
| Last Modified: | Tue May 14 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 216 |
| Total number of notes: | 933 |
Anyone seen FORMERROR with feedback code 1: %x'07', 2: %x'08'?
Time: 1991-06-25 08:45:38.80; message from server MRMEMO2:
%MRMEMO-W-FORMERROR, format error detected by MEMO Gateway
-MRMEMO-I-FEEDBACK, feedback code 1: %x'07', 2: %x'08'
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, receiving from MEMO after data received from MEMO
-MRMEMO-I-RING, ring: '1A 19 1A 19 18 2A 27 1B 13 36.', substates: 00000130
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3943 000001C9 001E379D
----- above condition handler called with exception 08938118:
%MRMEMO-W-FORMERROR, format error detected by MEMO Gateway
-MRMEMO-I-FEEDBACK, feedback code 1: %x'07', 2: %x'08'
----- end of exception message
ALLUNP ALL$UNP_GIU_TO_MSGITMLST 3884 00000119 001F3BC6
SRVACT SRV$ACT_R 5172 000000A2 001EB591
SRVDSP SRV$DSP_FSM 3423 000002A6 001E342A
SRVMMO SRV$MMO_ONE_LIFE 4376 000001EF 001E03BF
SRVMMO SRV$MMO_MAIN 4208 00000017 001E01C3
00239BAE 00239BAE
KOTERM KOTERM 804 00000039 002375A2
00239B89 00239B89
KODOC KODOC 1768 00000097 002347E4
00239B89 00239B89
00264DB2 00264DB2
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 001C0C0E
00239B89 00239B89
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 91.1 | Corrupt service message from MRMEMO | STKOFF::SPERSSON | Pas de probleme | Thu Aug 08 1991 12:30 | 27 |
Hi,
This error has occurred because MRMEMO sends a status message (service
message) to MEMO with erroneous format. The feedback codes mean:
feedback code 1: %x'07' -> invalid format
2: %x'08' -> status list
This might not mean a lot to you :-)
As far as I remember this does not cause the MRMEMO server to crash and
restart, it just throws out this error message once. Correct?
To track the problem, it might help if you could catch the related NBS
files:
MRMEMO$DIR:MRMEMO1-ENVELOPE.NBS
CONTENTS
NOTENV
NOTCNT
This is one of those elusive problems that it's impossible to recreate.
Cheers,
Stefan
| |||||
| 91.2 | Invalid format in status list | STKHLM::OLSSON | Anders Olsson, SIP Sweden | Fri Sep 13 1991 16:44 | 32 |
> Anyone seen FORMERROR with feedback code 1: %x'07', 2: %x'08'?
>
> Time: 1991-06-25 08:45:38.80; message from server MRMEMO2:
> %MRMEMO-W-FORMERROR, format error detected by MEMO Gateway
> -MRMEMO-I-FEEDBACK, feedback code 1: %x'07', 2: %x'08'
> %MRMEMO-W-TRACE, traceback forced from the Server Handler
> -MRMEMO-I-FSM, receiving from MEMO after data received from MEMO
> -MRMEMO-I-RING, ring: '1A 19 1A 19 18 2A 27 1B 13 36.', substates: 00000130
> %TRACE-W-TRACEBACK, symbolic stack dump follows
.
.
.
Maybe it's a little late to answer this now. Seems like I've missed this
note before or forgot about it. Sorry about that but here is the answer
at last:
Feedback codes %x'07', %x'08' means that Memo thinks that a status list
received from MRMEMO has an invalid format. The Memo term "status list"
refers to the part a of message that contains delivery/nondelivery/
receipt information.
The reason for this happening is probably that a service message (or
receipt notification) from Message Router has been transformed by MRMEMO
into something that is not correct according to the Memo/Gateway protocol.
I am trying to guess what part of the status list that is badly formatted
to be able to reproduce the problem but no success yet.
But there is still hope. I'll be back when I have figured out what's going
on.
Anders
| |||||