| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
This problem is similar to note 1475 by T Talbot but is reproducible using standard ALL-IN-1 V3.0 options. What is happening on the customer site is that whenever the user reads a new mail message which has a read receipt using RN he gets the following error; 'Invalid DAF Pointer in Document 000000' The read receipt is sent and the mail is ok if read again. The current item block on the EM menu is not updated with the read message as it should be. If a new message with Read Receipt is read by selecting (SEL or II) and then read using R no error occurs. This behaviour is consistantly reproducible using ALLI/NOCUST and has occured since their V3 upgrade. No errors are logged in OA$MTI_ERR, they all use WPS-PLUS local first class mail only. I have checked the named data for RN which is identical to our system where I cannot reproduce this problem. BTW the customer is Yellow Pages, I believe engineering are aware of their difficulties since upgrade. Any ideas Aston
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1502.1 | Invalid DAF Pointer in Document - Error | WAYOUT::CLARKE | The Cat in the Hat comes back. | Wed Oct 28 1992 17:07 | 27 |
If I can just get a word in on this topic! I have further refined the problem for your interest. The problem seems to be using the MAIL READ function causing the error above when reading messages with read receipt. If have a form with named data; ;;.TYPE;; MENU ;;RN;; MAIL READ/NEXT/UNREAD/METER=RECEIVE_MEMO Using RN on a message with Read Receipt causes the above error. If I put a .FX before the MAIL READ on this form (or infact on EMC) the error does not occur. Strange thing is the error only occurs using MAIL READ from named data a; <MAIL READ/NEXT/UNREAD/METER=RECEIVE_MEMO works ok when reading a new mail with read receipt. I think that the /NEXT/UNREAD is relevant as the problem doesnt occur using the Read option from EMC. Any ideas on this ? Aston | |||||