[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

2539.0. "Cannot create user in ALL-IN-1 3.0 when Identifier nes VMSusername" by VNOAPP::TIMA_204410 (Plus en plus seule...) Tue Apr 06 1993 16:51

In ALL-IN-1 V3.0, If a System Manager modifies the VMS identifier of a user for
example TEST to TESTTESTTEST, the ALL-IN-1 create user logfile shows the
following message, and the user is not created.

A fatal error has occurred in the SM_CR_USER_DETAILS.SCP
OA-W-RGT_NOSUCHID, Kennung oder Inhaber ist nicht in der
Berechtigungsdatenbank,

Which means roughly:

%OA-W-RGT_NOSUCHID, Identifier or holder identifier does not exist in the
  rights database.

Marianne Schnabel
T.RTitleUserPersonal
Name		DateLines
2539.1not really liked ;-)IOSG::TYLDESLEYTue Apr 06 1993 15:2538
    Hi! this is a difficult one. My assessment of what's happening is as
    follows:
    . ALL-IN-1 has no knowledge of the changed identifier in Rightslist.
      It only knows the VMS username.
    . just as if you did: 
      DISKQ>add TEST /perm=10000
      %SYSTEM-E-NOSUCHID, unknown rights identifier
      - you will get failure because you do not have the correct rights 
      identifier (TESTTEST).
    . ALL-IN-1 fails in Create User in SM_CR_USER_DETAILS, when it calls 
      oa$lib:sm_add_diskquota.com; this returns value = 3   and the log
      will show:
        Adding disk quota for the new or existing account ...
        Finished adding disk quota with status = -3
    
        A fatal error has occurred in SM_CR_USER_DETAILS.SCP
        %OA-W-RGT_NOSUCHID, Identifier or holder identifier does not exist 
        in the rights database
    . I cannot be certain of the exact point in sm_add_diskquota that the
      procedure will fail, without setting verify. But, it will certainly
      fail.
    
    We strongly recommend that ALL-IN-1 should not be used with accounts 
    that are set up to use VMS identifiers that are different from the 
    VMS account names. The V3.0 Release Notes contain the following
    statement under section 1.4, Rightslist Entries:
    
          "VMS usernames used with ALL-IN-1 must have corresponding
          rightslist entries with the same name, so that shared filing and
          system management can operate correctly. After upgrading to
          ALL-IN-1 Version 3.0 you can run the script
          OA$LIB:SM_CHECK_PROFILE, which generates a report indicating
          those accounts which may not conform to this requirement."
    
    Even if you got the account all set up, I suspect that you would have
    trouble with shared filing under this arrangement.
    Hope this helps.
    DaveT
2539.2Note stream reposted from 2530.*IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Apr 07 1993 18:021