Conference iosg::all-in-1_v30

2589.0. "Shared drawer is no longer shared. " by MASALA::GMURRAY (Have Mercy I Cry City !) Mon Apr 19 1993 14:39

    
    Hi,
    
    I have a strange problem with a regular shared drawer. 
    
    Since the end of last week, none of the users on the access list have
    been able to select the drawer. The error they get looks familiar
    enough :
    
     %OA-W-CAB_DWRFAIL, Error opening drawer file "DOCDB"                         
     -RMS-E-PRV, insufficient privilege or file protection violation              
     %OA-W-CAB_DWRFAIL, Error opening drawer file "!AS"                           
    
    However, I've checked all the relevant directory/file protections and
    they seem fine. I had a look in PARTITION.DAT and the drawer points at
    the right place.
    
    Finally, I  used MFC MD to have a look at the drawer. It came up as
    NOT shared. Strange, I thought, perhaps one of the "maintainers" has
    done a MDT to modify the drawer type - so I reset it to a regular
    shared drawer. The old access list came up on the screen so I hit
    Return and it went off to do it's thing. That's bound to cure it, I
    thought....
    
    No such luck. Still a privilege/protection violation. When I looked at
    the drawer again, it has reverted back to a "not shared" state !!!
    
    Help !
    
    		Gil
     
    
    

    Gil,
    	
    	this sounds like the same one of my customers had. Please
    check for any entries in the FCS logfile on sys$manageR:oafc$server.log
    if there are some errors like in 2563.
    
    But first try to stop the FCS and then try to restart the FCS. You'll
    find the Cabinet having the right ACE+ACL and working alright.
    
    Just an idea, maybe it will help you.
    
    Best Regards
    
    Charly_from_CSC_Vienna
    

    
    Hi Charly,
    
    Thanks for the reply - you were right - there are "fatal framework
    condition" errors in the server log file, as per your note 2563.
    
    This morning we upgraded and patched VMS, and the cluster reboot seems
    to have inadvertently cured the problem, presumably by restarting all
    the servers !
    
    Thanks for your pointer - I'll know what to do if there should be a 
    "next time".
    
    Cheers,
    
    	Gil
    
    
    

    
    Gil,
    
    I'd be interested to know how often (if at all) you see this problem
    again. Two people having the same problem warrants some investigation
    probably.
    
    Thanks,
    Kevin.