Conference iosg::all-in-1_v30

The error you are getting is coming from the FCS, which requires system file
protection to access the drawer files. Check that the following files have
at lease S:RWED file protection...

ACCESS.DAT
DOCDB.DAT
DAF.DAT
*.DIR (the document directories DOC0 thru DOC9 and MSG)
The document body file (if it got created)

The file protection for newly created document body files is determined by
a default protection ACE on the DOC% directory files, unfortunately these ACEs
get dropped the first time you modify the allowed access to the drawer and the
default file protections reverts back to the user's RMS defaults. Check that
the default protection includes S:RWED.

HTH

Terry

    Terry,
    
    	I've done what you suggested in 166.1, unfortunately I still have
    the problem.
    
    	Steve.

    
    Not being entirely sure what the ordering of FCS calls that A1 makes
    in this case I would guess that you never added the drawer to your
    file cabinet.
    
    You say you created it from the ALL-IN-1 managers account and granted
    access to your account. In order to access it from your account you
    would have to add the drawer to your file cabinet.
    
    >        File Cabinet object does not exist
    >
    >GOLD W only gives : %OAFC-I-CARDIDNF, File Cabinet object does not exist
    
    This means that when the actual create was attempted that the parent
    did not exist (the drawer) in your file cabinet.
    
    --Bob
    

    The drawer was already added to my file cabinet and is listed when I use 
    the IAD option from the Drawer Management menu. The error I get has 
    changed however. Yesterday, before and after changing the file protections
    (suggested in .1) I was able to create a document successfully but always 
    got the error message as described in .0. Today I can not create a 
    document instead I get an error message 'No document was created'. Gold W
    gives the following :
    
     %OAFC-I-CARDIDNF, File Cabinet object does not exist
     %OA-I-LASTLINE, The document could not be reserved (Document not edited)
     %OA-I-LASTLINE, No document was created
    
    		Steve.
    
    
    	

Just because the drawer appears in IAD does not mean that it is in your
file cabinet...  To see which drawers are in your file cabinet, do FC ID.

Scott

    OK, when I do an FC ID the drawer is listed.
    
    	Steve.

    Hi Steve!
    
    	Are you sure you have the latest version of the filecab server
    	in SYS$SYSTEM? No old versions sitting in SYS$SPECIFIC?
    
    Regards,
    Paul

    Hi Paul,
    
    	I have a OAFC$SERVER.EXE dated 27-FEB-1992 in SYS$SYSTEM but
    nothing like that in SYS$SPECIFIC.
    
    Any others that I should look for ?
    
    	Steve.

    
    If you do an anal/image on the oafc$server.exe what is the linker
    ID (hopefully OAFC V1.0) ??
    
    

    The image file identification is "OAFC V1.0"
    
	Steve.

    
    
    Steve,
    
    Here's some more things to check out :
    
    Check for   SYS$SHARE:OAFC$CLIENT_SHR.EXE		(RWED,RWED,RE,RE)
    		SYS$SHARE:OAFC$MTS_PRIV_SHR.EXE         (RWED,RWED,RWED,RE)
    
    Ensure that the latest versions are not superseeded by earlier ones in
    SYS$SYSROOT:[SYSLIB]
    
    
    Both these images should be INSTALLed as follows :
    
    OAFC$CLIENT_SHR.EXE     Open     Shar          Lnkbl
    OAFC$MTS_PRIV_SHR.EXE   Open     Shar     Prot Lnkbl
    
    
    
    If any changes are needed then remember to stop and restart the server
    to pick up what's been done.
    
    NOTE: If you've relinked the server, then OAFC$SERVER.EXE and
          OAFC$MTS_PRIV_SHR.EXE will remain in OA$BUILD_SHARE and
          you'll have to manually copy and INSTALL.
    
    
    
    HTH,
    
    Kevin.
    ~~~~~~
    
    
    

    
    Steve,
    
    I currently don't have much of an idea as to what is causing your 
    problem, but can you do the following:
    
    From the manage servers menu, turn on server tracing for ALL USERS.
    
    Try the document create again, please start from the time you
    enter ALL-IN-1.
    
    Turn server tracing off and run the trace file through the 
    trace formatter (in sys$system:oafc$print_trace_log.exe, assign
    sys$output to a file and run the trace formatter)
    
    Post the trace log here or mail it to me.
    
    This will show what FCS calls are being made and what they are 
    really trying to do.
    
    --Bob
    

    Kevin,
    
        I've made the checks you suggested in .11 and everything is correct.
    
    Bob,
    
            I turned the server tracing on using the EST option (I don't
    know how to do this for all users). I ran the oafc$print_trace_log.exe to
    produce a file containing the following :
    
             Error opening the file OA$DATA_SHARE:OAFC$SERVER_LOG.DAT
    
    This file doesn't exist in OA$DATA_SHARE: I couldn't find this file in
    the kit so I'm not sure if it's supposed to be created at some point.
    
    
                    Steve.

    
    Steve,
    
    The error is nothing to worry about. The trace format utility is a 
    rather dumb utility. It was basically written just as a starting 
    point. Anyone who wants to write another, better utility is welcome
    to, we publish the record layout of the trace file.
    
    What you need to do (this is buried someplace in the users manual
    for the FCS) is:
    
    1) Set the trace formatter as a foreign symbol:
    	
    	$ TRACE_FORMAT :== $SYS$SYSTEM:OAFC$PRINT_TRACE_LOG
    
    2) Pass the trace file as a parameter to the formatter.
    
    	$ TRACE_FORMAT whatever_your_trace_file_is
    
    THe default name for the trace file is:
    OA$DATA_SHARE:OAFC$SERVER_LOG.DAT
    
    By the looks of things thats not what yours is called. 
    to find the trace file name, turn on server tracing and under the
    manage servers menu, ask for the trace file name.  Run this through
    the formatter.
    
    --Bob
    

    I've been able to reproduce this problem on our development systems,
    where we have more than ALL-IN-1 system running. Because we have more
    than one ALL-IN-1 system there are different settings of OA$DATA_SHARE,
    and so more than one PARTITION file. If I run ALL-IN-1 interactively
    using one definition of OA$DATA_SHARE, and run the File Cabinet Server
    using another definition then when I create a drawer an entry gets
    added to a PARTITION file that will never be seen by the server. When I
    try to reserve (say) a document in this drawer, the FCS comes up with
    the File Cabinet object does not exist message.
    
    So are you running more than one ALL-IN-1 system? Do you have more
    than one PARTITION file?
    
    Cheers
    
    Stuart

Bob,
    
            Please find the trace details below :
    
    Stuart,
    
            We only have one ALL-IN-1 system running. We only have the
    following partition files on OA$DATA_SHARE.
    
              
    	Steve.
    
    Trace details . . . 
    
                    PARTITION.DAT;1
                    PARTITION_MASTER.DAT;1

SESSION ID:  3641216
OAFC FUNCTION: OafcSetServer                 
TRACE EVENT: Task Complete       
EVENT TIME:  9-MAR-1992 15:45:58.79 
STATUS: 55803913
STRING1 IS: ALLIN1


SESSION ID:  3641216
OAFC FUNCTION: OafcShowServer                
TRACE EVENT: Task Start          
EVENT TIME:  9-MAR-1992 15:45:59.98 
STRING1 IS: ALLIN1


SESSION ID:  3641216
OAFC FUNCTION: OafcShowServer                
TRACE EVENT: Task Complete       
EVENT TIME:  9-MAR-1992 15:46:00.12 
STATUS: 55803913
STRING1 IS: ALLIN1


SESSION ID:  3641216
OAFC FUNCTION: OafcShowServer                
TRACE EVENT: Task Start          
EVENT TIME:  9-MAR-1992 15:46:30.22 
STRING1 IS: ALLIN1


SESSION ID:  3641216
OAFC FUNCTION: OafcShowServer                
TRACE EVENT: Task Complete       
EVENT TIME:  9-MAR-1992 15:46:30.49 
STATUS: 55803913
STRING1 IS: ALLIN1


SESSION ID:  3641216
OAFC FUNCTION: OafcShowServer                
TRACE EVENT: Task Start          
EVENT TIME:  9-MAR-1992 15:47:00.28 
STRING1 IS: ALLIN1


SESSION ID:  3641216
OAFC FUNCTION: OafcShowServer                
TRACE EVENT: Task Complete       
EVENT TIME:  9-MAR-1992 15:47:00.37 
STATUS: 55803913
STRING1 IS: ALLIN1


SESSION ID:  3641216
OAFC FUNCTION: OafcSetServer                 
TRACE EVENT: Task Start          
EVENT TIME:  9-MAR-1992 15:47:01.31 
STRING1 IS: ALLIN1

    Problem solved! Steve's system started life before BL90 and his update
    to BL90 missed the manual post-installation step to run script
    OAFC_LOCAL_PHASE_IV_NAMES.SCP (well hidden in the small print!).
    
    Now this script has run and all seems to be well again. 
    
    Cheers
    
    Stuart

    
    OUCH !!!
    
    I *KNEW* I'd seen this before !!
    
    The Atlanta people had the same problem on DIMUND over Christmas,
    it took a while for me to suss it out then !
    
    Oh well, I guess I'm just getting too old for this kinda thing...
    
    
    
    Kevin.
    ~~~~~~
    
    

    
    I have a customer who is running ALL-IN-1 V3.0-1 and some of his users
    are getting exactly the same error, but after they file a document (?)
    
    This is happening for all documents in a couple of folders in a shared
    drawer. The documents are straight forward WPS-PLUS documents, which
    when filed after being editing, after the filing complete message they
    see.. (after gold w)
    
    %OA-I-CARDIDNF File cabinet object does not exist
    
    Other folders in the same drawer are unaffected. I have got him to go
    away and check things suggested in .1 but seeing as the original
    problem was seen whilst trying to create a shared drawer, I don't know
    how relevant this is.
    
    Nonetheless, I have got him to check out a few things, will let you
    know what he says.
    
    Thanks,
    
    Emma.