[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

3075.0. "OAFC-I-DSTNF - controller can't Create in drawer" by KIRKTN::GMURRAY (Have Mercy I Cry City !) Tue Jul 27 1993 17:46

    
    Hi,
    
    One of our users has control access to a shared drawer, but is unable to
    Create a document within it. The drawer was created under the ownership
    of ALLIN1 and placed on a disk with other such drawers files, but was
    set up to be controlled by this and other users. He has Created 
    successfully in the past.
    
    Here is the error on Create:
    
     %OAFC-I-DSTNF, A target was specified that does not exist                    
     %OA-I-LASTLINE, The document could not be reserved (Document not edited)     
     %OA-I-LASTLINE, No document was created                                      
    
    Does this mean anything to anyone ?
    
    Thanks,
    
    	Gil
    
    
    
    
T.RTitleUserPersonal
Name
DateLines
3075.1Mini checklistIOSG::MAURICEDifferently hirsuteTue Jul 27 1993 18:0120
    Re .0
    
    Some things to check:
    
    1. As the ALL-IN-1 Manager type SM MFC MD (manage drawers) and select
       the drawer. Type R to read it and check that there are no errors
       on the listing.
    
    2. Do the other users who have been given CONTROL access to this drawer
       have any problems?
    
    3. Can the user edit documents in the drawer?
    
    4. Can the user read documents in the drawer?
    
    5. Is the drawer an ADVANCED SHARED drawer or REGULAR SHARED?
    
    Cheers
    
    Stuart
3075.2Checklist resultsKIRKTN::GMURRAYHave Mercy I Cry City !Wed Jul 28 1993 14:5551
    
    
Hi Stuart,
    Thanks for the reply. I've checked the 5 points and come up with the
    following answers:
    
    1. SM MFC MD gives no apparent errors:
    
Date: 28-Jul-1993         File Cabinet Drawer Full Report               Page: 1
                          ===============================               
    Drawer              MASALA::"[ESG]MAIN"
    System              MASALA::
    Owner               ESG
    Drawer name         MAIN
    Description         
    Directory           DISK$ALLIN1_SD1:[SHARED_DRAWERS.ESG]
    You have CONTROL access to the drawer
    Drawer is shared with other users
    Drawer is located on this system
    Drawer type is REGULAR SHARED
                       List of users who may access the drawer
                       =======================================
                                 Shared                        Delete/
User or Group                   VMS Acct  Read  Create   Edit  Refile   Control
AMSG                               Y       Y      Y       Y      Y         Y
ROSS.JOHN                                  Y      Y       Y      Y         Y
FOX.RON                                    Y      Y       Y      Y         Y
HARRIS.BRUCE                               Y      Y       Y      Y         Y
HUTCHEON.GRAEME                            Y      Y       Y      Y         Y
CRAWFORD.MARTIN                            Y      Y       Y      Y         Y
    
    2. Other CONTROL users do NOT have any problems Creating/Editing in the
    drawer.
    
    3. The user is unable to Edit - getting:
    
    %OAFC-I-NOACCESS, Insufficient privilege for requested operation             
    
    4. However, he can Read documents in the drawer.
    
    5. It's a REGULAR SHARED drawer.
    
    All this points to a problem with the users' account. Disk quota seems
    OK (approx 6K free blocks).
    
    Could it be something in his profile ?
    
    Cheers,
    
    	Gil
     
3075.3More questionsIOSG::MAURICEDifferently hirsuteWed Jul 28 1993 15:3411
    Hi,
    
>    Could it be something in his profile ?
    
    Yes. The VMSUSR and DIRECT fields have to be correct. Does the user login
    to ALL-IN-1 by just typing $allin1, or does the user specify a /USER or
    /DIRECT parameter? Has the profile been customised?
    
    Cheers
    
    Stuart
3075.4Hmmm...KIRKTN::GMURRAYHave Mercy I Cry City !Thu Jul 29 1993 11:3049
    
    Hi,
    
    He invokes ALL-IN-1 with /USER=fox.ron
    
    DIRECT and VMSUSR look normal:
    
    DIRECT=INFORMATION_SERVICES:[RFOX.ALLIN1]    
    VMSUSR=RFOX
    
    The profile itself hasn't been customised. However, I noticed that he had a
    (now redundant) form library in his FRMLIB, and removed it.
    
    Interestingly, he still can't Edit or Create, but on Create the error
    has changed to:
    
    %OAFC-I-NOACCESS, Insufficient privilege for requested operation             
    %OA-I-LASTLINE, The document cannot be accessed for editing                  
    %OA-I-LASTLINE, No document was created                                      
    
    Privs/protection ?
    
    The protection on the shared drawer files looks OK I think:
    
    DISK$ALLIN1_SD1:[SHARED_DRAWERS]ESG.DIR;1
    
    ESG.DIR;1            [SYSTEM]              (RWE,RWE,E,E)
    
    DISK$ALLIN1_SD1:[SHARED_DRAWERS.ESG]ACCESS.DAT;1
    
    ACCESS.DAT;1         [SYSTEM]              (RWED,RWED,,)
             
    (IDENTIFIER=[ALLIN1],OPTIONS=HIDDEN,ACCESS=READ+WRITE+DELETE+CONTROL)
    (IDENTIFIER=[MANU,JROSS],ACCESS=READ+WRITE+DELETE+CONTROL)
    (IDENTIFIER=[INFORM,RFOX],ACCESS=READ+WRITE+DELETE+CONTROL)         
    (IDENTIFIER=[INFORM,BHARRIS],ACCESS=READ+WRITE+DELETE+CONTROL)
    (IDENTIFIER=[INFORM,GHUTCHEON],ACCESS=READ+WRITE+DELETE+CONTROL)         
    (IDENTIFIER=[INFORM,MCRAWFORD],ACCESS=READ+WRITE+DELETE+CONTROL)
    
    Confused,
    
    	Gil
    
    
    
    
    
    
    
3075.5Next checkIOSG::MAURICEDifferently hirsuteThu Jul 29 1993 12:3414
    Hi,
    
    Everything looks OK there. For some reason ALL-IN-1 and VMS think the
    user has proper access to the drawer, but the File Cabinet Server
    doesn't. 
    
    In the user's own drawer can the user successfully use the RSV
    (reserve) and URV (unreserve) commands on his own documents? This will
    tell us if the user has a general problem using the FCS, or whether it
    is particular to the drawer.
    
    Cheers
    
    Stuart
3075.6Need to know who FCS thinks you are...CHRLIE::HUSTONThu Jul 29 1993 17:2920
    
    Turn on FCS logging and see what the FCS thinks the username is, my 
    guess is that it does not understand something about the /user.
    Remember that all authentication is via VMS username, 
    
    my guess is that the connect to the FCS is not passing something
    to tell it that this guy is not acting as himself, but is acting
    as someone else.
    
    Stuart,
    
    Helmut once told me that when the connect is made to the FCS the
    username and password passed are the local username, if the person
    is doing a /user=x, then if there is a differenet VMS name associated
    with this, it would cause problems with the above, can you find out
    what happens when a connect is done from INDEX$ when the user
    came in via /user=x?
    
    --Bob
    
3075.7Errors show up in OAFC$SERVER.LOG - relevant ?PAKORA::GMURRAYHave Mercy I Cry City !Mon Aug 02 1993 12:0230
    
    Hi Stuart, Bob,
    
    Sorry for the delay....
    
    RE .5  Bang on target ! When the user tries to RSV one of his own MAIN	
    documents, he gets:
    
    %OAFC-I-NOACCESS, Insufficient privilege for requested operation
    %OA-I-LASTLINE, The document could not be reserved
    
    RE .6  I checked OAFC$SERVER.LOG (correct ?) and found these two
    errors:
    
    28-JUL-1993 09:09:35.66  Server: MASALA::"73="  Error:
    %OAFC-E-INTERR, Internal error in File Cabinet Server  Message: CsiOpenDrawer;
    DOCDB file/dev id does not match IUID in partition, continuing
    
    29-JUL-1993 11:44:06.65  Server: MASALA::"73="  Error:
    %OAFC-E-INTERR, Internal error in File Cabinet Server  Message: CsiOpenDrawer;
    DOCDB file/dev id does not match IUID in partition, continuing
    
    Should we assume that these errors belong to the user, and if so, what
    do they mean ?
    
    Cheers,
    
    	Gil
    
                           
3075.8Errors fixed on the flyCHRLIE::HUSTONMon Aug 02 1993 16:367
    
    Nope, those errors will be fixed up on the fly by the FCS.
    
    They should go away.
    
    --Bob
    
3075.9Trace resultsPAKORA::GMURRAYHave Mercy I Cry City !Mon Aug 02 1993 17:5164
    Hi Bob,
    
    The user has reported the same problems on a different drawer now.
    
    I switched tracing on, and attempted to Create in the original drawer,
    from his account. The trace log proved tricky to look at as it was in 
    Stream_LF format, but after conversion I got the following (not too
    revealing I'm afraid):
    
          11 7919856
    
            Task Start           2-AUG-1993 16:17:54.51 OafcOpenCabinetW
    
          11 7919856PAKORA.FOX.RON
    
            Connection Rcv'd     2-AUG-1993 16:17:54.58 OafcOpenCabinetW
               PAKORA
    
          11 7919856PAKORA.FOX.RON
    
            Connection Rejected  2-AUG-1993 16:18:00.22 OafcOpenCabinetW
               RFOX
    
          11 7919856PAKORA.FOX.RON
    
            Task Complete        2-AUG-1993 16:18:00.39 OafcOpenCabinetW
       55804138RFOX
    
             7919856PAKORA.FOX.RON
    
            Disconnect Done      2-AUG-1993 16:18:00.87
    
          11 7936768
    
            Task Start           2-AUG-1993 16:18:00.43 OafcOpenCabinetW
    
          11 7936768THERAJ.FOX.RON
    
            Connection Rcv'd     2-AUG-1993 16:18:01.61 OafcOpenCabinetW
               PAKORA
    
          11 7936768THERAJ.FOX.RON
    
            Connection Rejected  2-AUG-1993 16:18:05.13 OafcOpenCabinetW
               RFOX
    
          11 7936768THERAJ.FOX.RON
    
            Task Complete        2-AUG-1993 16:18:05.18 OafcOpenCabinetW
       55804138RFOX
    
             7936768THERAJ.FOX.RON
    
            Disconnect Done      2-AUG-1993 16:18:05.24
    
    	Am I right in thinking that this doesn't really tell us much ?
    
    	Cheers,
    
    	Gil
    
    	P.S. Am I missing an easy way to look at the Trace log ?
    
    
3075.10Easy to read trace file...CHRLIE::HUSTONMon Aug 02 1993 18:0816
    
    >	P.S. Am I missing an easy way to look at the Trace log ?
    
    Yup, there is a trace formatter, sys$system:oafc$print_trace_file.exe
    (or something close to that), set it as a VMS symbol, then pass
    the trace file in as P1, it will nicely format and dump this to the
    screen for you, or you could re-define sys$output to a file and have
    the output go there.
    
    If one drawer is showing it, chances are mulitple drawers will show it.
    anything that can change the physical location of a drawer (ie the
    file id for instance) like a fc reorg will cause this. As I said the
    FCS fixes it on the fly.
    
    --Bob
    
3075.11How long to self-correct ?KIRKTN::GMURRAYHave Mercy I Cry City !Tue Aug 03 1993 12:3819
    
    Thanks for the pointer to the trace log formatter - that'll make life a
    lot easier !
    
    You're right. Every shared drawer the user tries to Create in is now
    failing - same error. 
    
    You say that errors like this are fixed "on the fly" by the FCS - what 
    worries me is how long it's taking.... the user tells me that he first 
    noticed the problem some 3 weeks ago !
    
    Is there anything I can do to speed up the process - maybe fool the FCS
    into fixing it faster ?
    
    Cheers,
    
    	Gil
    
    
3075.12Fixes as it finds itCHRLIE::HUSTONTue Aug 03 1993 15:0512
    
    the FCS should be fixing it as it discovers it. 
    
    There is also a system management option to fix it (I think), if not,
    I can tell you how to write up a quick and dirty C program to do it, 
    real easy, but I know there is a way to fix it besides the FCS.
    
    Sounds like there may be another problem here as well since this 
    doesn't seem to go away.
    
    --Bob
    
3075.13CASE resolved and closed.WAYOUT::TALBOTTrevor TalbotFri Aug 06 1993 13:0019
Hi,


        There was another problem here!

By doing the following commands the protection problem
can be highlighted easily without wading through yards of
trace etc...

1)set audit/alarm/enable=file=fail
2)reply/enable
3)set term/broad
4)get user to perform tricks..
5)fix file protection from output on screen

In this case the users directory lacked system access for
RWE, once corrected the user had no further problems.

-Trev