[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

1414.0. "Can't open filecab, No privilege for attempted operation" by COPCLU::COPRUG::RUNE (Rune Gottschalk @DMO) Tue Sep 15 1992 11:44

Hi, 

My customer is running a new ALL-IN-1 V3.0 installation ( <VERSION gives 
"ALL-IN-1 IOS Server for VMS V3.0 PBL123A  (US) ENGLISH 21-MAR-1992" ).

When they try to access the file cabinet from an unpriviledged user, e.g. 
by calling the WP or EM menues, they get the following error:

          no privilege for attempted operation

When tracing what happens I get the following:

![SCRIPT] IF Operation starting
![SCRIPT] .IF condition $WP_DRAWER EQS ""    is TRUE
![SCRIPT] THEN Operation starting
![SCRIPT] Form: WP, Statement: CAB SET_DRAWER\GET $WP_DRAWER = OA$CURDWR
![FUNC]   Function: CAB, Cmd line: SET_DRAWER
![A1LOG]  Entry: %OA-I-LOGFUN, Function: CAB             SET_DRAWER
![SYMBOL] Symbol: , Value:
![IO]     Getting record from FILECAB, Key: 1, Key-of-ref: INDICATOR/1
![A1LOG]  Entry: %OA-I-LOGERROR, %RMS-W-NOPRIV, no privilege for attempted 
operation
![IO]     Getting field NAME from FILECAB, Value: MAIN
![IO]     FILECAB Server Request: LIST
![IO]     Getting field CODE from OA$FOLDERS, Value: ENUS
![A1LOG]  Entry: %OA-I-LOGERROR, %RMS-W-NOPRIV, no privilege for attempted 
operation
![IO]     Deaccessing FILECAB, File: FILECAB.DAT
![IO]     Closing CAB$PENDING, File:
![A1LOG]  Entry: %OA-I-LOGERROR, %OA-W-CAB_CANT_OPEN, Your File Cabinet 
cannot be accessed

I have compared their installation with DEC's and they seems to be equal 
(file protection etc.).

What could be wrong ?

Rune

T.R	Title	User	Personal Name	Date	Lines
1414.1	Images not $INSTALLED??	IOSG::PYE	Graham - ALL-IN-1 Sorcerer's Apprentice	`Tue Sep 15 1992 12:07`	9
	The error would seem to be occurring when reading the folder names file OA$DATA:SYSTEM_FOLDERS.DAT. Perhaps the protection on this is wrong. Ours doesn't have W:R, so the FCS must be using privs to read it. Perhaps the FCS or ALL-IN-1 images aren't $INSTALLED with the right privileges. Use $ INSTALL LIST/FULL to check. Graham
1414.2	FCS Client sharable image	IOSG::MAURICE	Ceci n'est pas une note	`Tue Sep 15 1992 12:58`	8
	I agree with Graham. I think the most likely one is the File Cabinet Server client sharable image, which needs W:RE on the file OAFC$CLIENT_SHR.EXE Cheers Stuart
1414.3	It isn't the client image	CHRLIE::HUSTON		`Tue Sep 15 1992 16:39`	13
	I hate to disagree with you guys, but... the client image does not have any knowledge of the system_folders.dat and the server only uses the file during startup, it reads the contents in and closes it. I doubt it is that. I can't tell from the log in .0 if it is an FCS problem with protection or the IOS FC code. Can the author of .0 turn on server tracing for all users, then try the operation again. --Bob
1414.5	Protection problem on OAFC$CLIENT_SHR	COPCLU::COPRUG::RUNE	Rune Gottschalk @DMO	`Wed Sep 16 1992 12:33`	10
	Hi again, I just talked to my customer and he confirmed that the problem was wrong protection on the OAFC$CLIENT_SHR image. He is running a standard V3.0 system without customizations etc. so I guess we can expect this problem at other sites as well ! Thanks again for you help, Rune
1414.6	Client sharable image problem.	IOSG::STANDAGE	Oink...Oink...Mooooooooooooooooooooooooooooooooo	`Wed Sep 16 1992 16:01`	14
	Rune, During a V3.0 installation, the protection of OAFC$CLIENT_SHR.EXE is set to (RWED,RWED,RE,RE). Why the protection was wrong on your system I don't know. Was it an update from a previous base level prior to SSB ? Just curious, I certainly haven't seen this one before... Kevin.