[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

1503.0. "Create Drawer Problem with ACES" by JOCKEY::MCCAFFREYJ (If in doubt switch it off.) Thu Sep 24 1992 16:16

    Having just upgraded to V3.0 I've been creating new user accounts.
    
    The accounts are made up of VMSusername - EM101AA1 and ALL-IN-1
    username BLOG��GS,FRED.
    
    The problem occurs when a user is creating a new regular shared drawer
    and adding in a user to access it.  The following message appears on
    the screen
    
    One or more Identifier ACEs have not been recognized.
    
    The log file produces the following -
    
    
    BIND *DOCN_ACCESS TO ACL$:#DIR0
    Function: BIND, Cmd line: *DOCN_ACCESS TO ACL$:#DIR0
    %OA-I-LOGFUN, Function:
    BIND *DOCN_ACCESS TO ACL$:#DIR0
    Symbol: #DIR0, Value: DISK$ALLIN1:[EM101AA2.A1.ZUIKGUZYM]DOC0.DIR
    %OA-I-LOGERROR, %OA-W-ACL_HIDDEN_ACE,
    One or more Identifier ACEs have not been recognized
    %OA-I-LOGERROR, -OA-W-ACL_NO_HOLDERS,
    No VMS accounts hold identifier !AS
    %OA-I-LOGERROR,
    -OA-W-ACL_BAD_ACE, Hidden ACE is:
    (IDENTIFIER=PCFS$READ,OPTIONS=HIDDEN+PROTECTED,ACCESS=READ)
    %OA-I-LOGERROR, %OA-W-ACL_HIDDEN_ACE,
    One or more Identifier ACEs have not been recognized
    %OA-I-LOGERROR, -OA-W-ACL_NO_HOLDERS, No VMS accounts hold identifier
    !AS
    %OA-I-LOGERROR, -OA-W-ACL_BAD_ACE,
    Hidden ACE is: (IDENTIFIER=PCFS$UPDATE,OPTIONS=HIDDEN+PROTECTED
    ACCESS=READ+WRITE+EXECUTE+DELETE+CONTROL)
    
    
    Any ideas of wher��e I'm going wrong would be appreciated!
    
    thanks,
    
    josie

T.R	Title	User	Personal Name	Date	Lines
1503.1	More information please	IOSG::MAURICE	See below	`Thu Sep 24 1992 17:33`	9
	Hi, Does the user's VMS account name (EM101AA1) have an identifier? What is PCFS$UPDATE? Cheers Stuart
1503.2	PCFS = Pathworks	IOSG::TALLETT	Arranging bits for a living...	`Thu Sep 24 1992 18:55`	1

1503.3	UAF entry looks like this...	JOCKEY::MCCAFFREYJ	If in doubt switch it off.	`Fri Sep 25 1992 10:21`	44
	Hi. no the entry in authorize does show any identifiers, but then neither does the account on which it does work. Pathworks is running on this machine. EM101AA1's authorize entry looks like this.... Username: EM101AA1 Owner: Fred Bloggs Account: UIC: [500,33]([EM101AA1]) CLI: DCL Tables: DCLTABLES Default: DISK$ALLIN1:[EM101AA1] LGICMD: SYS$MANAGER:A1_LOGIN.COM Flags: Restricted Primary days: Mon Tue Wed Thu Fri Secondary days: Sat Sun No access restrictions Expiration: (none) Pwdminimum: 6 Login Fails: 0 Pwdlifetime: 90 00:00 Pwdchange: 23-SEP-1992 11:32 Last Login: 25-SEP-1992 09:00 (interactive), (none) (non-interactive) Maxjobs: 0 Fillm: 100 Bytlm: 36000 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 50 JTquota: 1024 Prclm: 10 DIOlm: 50 WSdef: 600 Prio: 4 ASTlm: 100 WSquo: 1000 Queprio: 0 TQElm: 50 WSextent: 3000 CPU: (none) Enqlm: 300 Pgflquo: 20000 Authorized Privileges: TMPMBX NETMBX Default Privileges: TMPMBX NETMBX I can't see anything else unusual about it. It does seem to create the drawer and allows other users to access it but this error message keeps displ�aying itself. help - any pointers? thanks for any help... josie
1503.4		IOSG::MAURICE	See below	`Mon Sep 28 1992 09:32`	13
	My guess is that it's something to do with identifier PCFS$UPDATE. Have you any idea why the ACE with identifier is being added? Another guess is that the error message: %OA-I-LOGERROR, -OA-W-ACL_NO_HOLDERS, No VMS accounts hold identifier !AS is significant. How about giving PCFS$UPDATE to an account and seeing what happens. Cheers Stuart
1503.5	Bug IMHO	IOSG::TALLETT	Arranging bits for a living...	`Mon Sep 28 1992 11:50`	9
	This is a teeny bit serious if you indeed need to give PCFS$UPDATE to an account. Pathworks puts the PCFS$UPDATE identifier onto all directories served up in a file service as far as I can tell. Please submit a bug so that it gets fixed. Regards, Paul
1503.6	Fixed!	JOCKEY::MCCAFFREYJ	If in doubt switch it off.	`Tue Sep 29 1992 11:55`	26
	Well it seems that we have worked out the answer with the help of a Pathworks Specialist... The problem was that a Pathworks file service had been created at the top level of the disk. All Pathworks file services have ACEs associated with them not only on the file service itself but on the directory above which in this case was 000000.DIR. As VMS propogates all ACEs on any new directories created by VMS, regardless of being Pathworks directories or not the EM101AA1 directory had the ACE attached. This ACE was the one causing us the problem. The fix was to move the Pathworks file services to sub directories and then remove the ACE from the top directory and then my EM101AA1 directory. This could cause us a future problem if a user directory is also a Pathworks file service as Pathworks needs the ACE whereas ALL-IN-1 will throw up the error message when it comes across it. thanks for your help josie
1503.7	Me too...	ROMEDU::NEBBIA	Mario Nebbia @RIO - EDU Rome Italy	`Fri Nov 27 1992 11:46`	15
	> The fix was to move the Pathworks file services to sub directories > and then remove the ACE from the top directory and then my EM101AA1 > directory. I fond the same problem, but the PCSA ACE is set over all the ALL-IN-1 directories of the disk where ALL-IN-1 is installed and the user files are created... What is the most simple (and safe) way to remove the PCSA ACEs from all the directories of the disk (PCSA is no more installed on the system) without damaging the ALL-IN-1 ACEs??? Thanks Mario
1503.8	set acl ?	UTRTSC::SCHOLLAERT	AJAX beats Feyenoord again and again	`Fri Nov 27 1992 12:31`	9
	Mario, I didn't test it, but try something like.... $ set acl /object=file /delete /acl=(iden=pcfs$update) [...].. Regards, Jan