[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

1640.0. "EMDDSNOTAUTH You Could Not Be Authenticated" by GIDDAY::SETHI (Man from Downunder) Wed Oct 21 1992 09:40

    Hi All,
    
    A customer has Version 2.4 of ALL-IN-1 installed and is having the
    following problem when he creates a new user account the logfile shows
    the following
    
    $ allin1/noinit/reenter/user=manager/language=BRITISH
      oa$ini_init
    
      get oa$function="do " cli$script_file
      %OA-I-LASTLINE, <ALL-IN-1 username>
      EMDDSNOAUTH You could not be authenticated in the mail directory
      EMDDSNOAUTH You could not be authenticated in the mail directory
      
    The "EMDDSNOAUTH" message appears twice.  The <username> entry is not
    created in the DDS database.  I have checked the following
    
    1. OA$DDS_PRIME = 1
    2. The various DDS detached DDS$55_i1,DDS$55_lt1,DDS$55_lt2 and 
       DDS$LSTN_55_1 are present
    3. The mail directory has been installed sometime back
    4. The MDFLAG="Y"
    5. The details for the User Agent OA$<node>$ALLIN1 appear to be fine
    
    I followed the page in the Mail Management Guide (2.4) 6-10 and carried
    out the procedure requested.  But before I did I made sure the the
    MDFLAG for the user was "Y" and that PROFIL.DDSID[$ACCOUNT] was blank.
    
    <get #dds_account=$account
    <do subscriber_add <--- at this point I got the "EMDDSNOTAUTH" message
    again.
    
    I would be grateful for any other suggestions.  Thanks in advance.
    
    Sunil
T.RTitleUserPersonal
Name
DateLines
1640.1MANAGER problem ?UTRTSC::SCHOLLAERTServices, Services, ServicesWed Oct 21 1992 10:418
    Hello Sunil,
    
    Looks like the MANAGER is not authenticated. See page 3-10
    for the steps to check. 
    
    Regards,
    
    Jan
1640.2May have been caused by INQUE.DAtGIDDAY::SETHIMan from DownunderMon Oct 26 1992 03:5913
    Hi All,
    
    Investigated the problem further.  What we did was create the DDS entry
    using 
    $MC MBMAN create dds subscriber/surname=<surname> etc.
    
    Than deleted the entry went into ALL-IN-1 and followed the steps and
    the user entry was created successfully.  It appears as if a partial
    entry was created in DDS I suspect that the cache INQUE.DAT may have
    been the cause of the problem.  At the moment I am unable to prove
    anything it's just a hunch.
         
    Sunil