| 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 |
A customer has described the following problem: The ALLIN1 manager account receives the following message when attempting to create/edit a document: "Referrence to the proper DAF.DAT file could not be established" Neither the DOCDB.DAT and DAF.DAT show any RMS errors. Reorganization of the FC seemed to complete successfully, but it did NOT solve the problem. The [.doc0] directory contains PERSONAL.LGP and GLOBAL.LGP. Thanks, Cb.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 753.1 | More info please | IOSG::MAURICE | A few follicles short | Tue May 26 1992 12:53 | 14 |
Hi,
Which version of ALL-IN-1 and to what patch level?
Are there any more error messages if the users types GOLD W?
How many SDAFs are there? Are all the OASHARx logicals defined
/sys/exec? Do all the SDAFs actually exist?
Do other accounts work correctly?
Cheers
Stuart
| |||||
| 753.2 | V2.3 - any create/edit fails | TAV02::CHAIM | Semper ubi Sub ubi ..... | Wed May 27 1992 07:42 | 7 |
It is V2.3 without any patches. This occurs in ONLY one account and trying to create/edit any file. Thanks, Cb. | |||||
| 753.3 | Corrupt DOCDB record? | IOSG::MAURICE | A few follicles short | Wed May 27 1992 12:05 | 15 |
In V2.4 the message text changed to
CAB_NO_DAF <Invalid DAF POINTER in document: !AS!AS>
which gives a much better clue as to what the problem is and which
document is causing the problem. What you have is one or more corrupt
DOCDB records. In particular the DAPOINTER field will be invalid (i.e.
not "A", "S" or "P"). Try running housekeeping procedure TRU for that
user. If that doesn't cure the problem then try indexing the File
Cabinet and it's likely to end at the document before the corrupt one.
This will then give you the chance to repair the file at DCL.
Cheers
Stuart
| |||||