Conference iosg::all-in-1_v30

1923.0. "CO-EX install fails, A1CONFIG does not exist" by AIMTEC::MORABITO_P () Tue Dec 08 1992 22:35

I have a customer that is having problems installing a Co-Existent system.
When the installation is setting global buffers on the A1CONFIG.DAT,
an error is returned saying the file does not exist.  I also has
problems finding A1.CLD.  This is when the files are still in the 
SYS$UPDATE A1030 directory.  

	Environment:
			ALL-IN-1 2.3  Installing Co-Existent 3.0
			VMS A5.5
			VAX 6420

Any ideas?

Paul


%A1-I-RNEPROF, Running command procedure EPROFIL.CA1
%OA-I-LASTLINE, "ALL-IN-1 running -- opening form libraries"
%OA-I-LASTLINE, "ALL-IN-1 running -- creating BASE data files"
%OA-I-LASTLINE, Adding records to CM$APP...
%OA-I-LASTLINE, Adding ENGLISH records to CM$AUTH$LOCATIONS...
%OA-I-LASTLINE, Adding reserved records to CM$APP...
%OA-I-LASTLINE, Adding SHARE records to CM$AUTH$LOCATIONS...
%OA-I-LASTLINE, Adding records to CM$SDC$LOCATIONS...
%OA-I-LASTLINE, Adding ENGLISH records to CM$FORM$LIBS...
%OA-I-LASTLINE, Adding SHARE records to CM$FORM$LIBS...
%OA-I-LASTLINE, "ALL-IN-1 running -- creating PROFILE.DAT"
%OA-I-LASTLINE, "ALL-IN-1 running -- populating BASE data files"
%OA-I-LASTLINE, "ALL-IN-1 running -- creating LANGUAGE data files"
%OA-I-LASTLINE, "ALL-IN-1 running -- creating CBI data files"
%OA-I-LASTLINE, "ALL-IN-1 running -- updating A1CONFIG data file"
%OA-I-LASTLINE, "ALL-IN-1 running -- data file creation complete"
\<)0*<}(B>
\<)0*<}(B>
%A1-I-SETACL, Setting ACLs

          $SET ACL /DEFAULT 'FILENAME'

%A1-I-SETGBL, Setting global buffers
%VMSINSTAL-W-NOFILE, New file A1CONFIG.DAT  does not exist.
%A1-I-CREMBX, Creating mailbox entry A2
        This is MRMAN V3.2 (BL9.07)
%Added A2,                       Owner=ALLIN1_1 Complete_Messages Ignore_Sender Grant_Id Service_Messages
%VMSINSTAL-W-NOFILE, New file A1.CLD  does not exist.

%A1-E-RETRY1, Please correct any reported problems before attempting
%A1-E-RETRY2, to install ALL-IN-1.

%VMSINSTAL-E-INSFAIL, The installation of A1 V3.0 has failed.
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_COPY_SDC_HLP.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_COPY_SDC_TEXT.SCP;1 not changed
-RMS-E-FNF, file not found
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_CREATE.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_CREATE_FILE.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_CREATE_HLP.BLP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_DELETE_APP_AREA.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_DELETE_DEVELOP_FRM.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_DELETE_DEVELOP_HLP.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_DELETE_HLP.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_DELETE_OACODE.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file
%SET-E-PRONOTCHG, protection on $1$DUA21:[SYS2.SYSUPD.A1030]CM_DELETE_TEXT.SCP;1 not changed
-SYSTEM-W-NOSUCHFILE, no such file

	VMSINSTAL procedure done at 11:51

    Looking at the log a little closer, the following error appears when
    adding the new accounts to the rights data base:
    
    UAF-I-RDBADDMSGU, identifier ALLIN1_1 value: [000001,000034] added to
    rights data base
    
    UAF-E-RDBADDERRU, unable to add 243100 value: [000001,177777] to rights
    data base -SYSTEM-F-IVIDENT, invalid identifier format
    
    .
    .
    .
    .
    It does this for each of the new accounts created, no matter what the
    member number is it changes to 177777.
    
    
    Any ideas????
    
    Jean

    Jean,
    
>    UAF-I-RDBADDMSGU, identifier ALLIN1_1 value: [000001,000034] added to
>    rights data base
>    
>    UAF-E-RDBADDERRU, unable to add 243100 value: [000001,177777] to rights
>    data base -SYSTEM-F-IVIDENT, invalid identifier format
    
    VMS is trying to add a group identifier to the rights list.
    243100 is not a valid value. All numbers.
    
    Have a look at de ACCOUNT field of user DEFAULT and the first
    user in group 1 .... I think this field is used when the group
    identifier does not exist yet.
    
    Regards,
    
    Jan
    

    I worte this up in some detail elsewhere in this notesfile somewhere,
    but Jan is right.
    
    The first time you add an account to a UIC group that hasn't been used
    before, VMS adds an identifier of member number 177777 to be the name
    translation of the group number. However it fails if the account name
    in the newly created SYSUAF record is numeric, since it gets confused
    about whether the idnetifier is name or number.
    
    Or something like that... :-)
    
    Graham