[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

3033.0. "%OA-W-EMDDSNOTAUTH, You could not be authenticated in the mail directory" by SWAM2::RHODEWALT_BR (I am a talking parrot.) Wed Jul 21 1993 01:07

    What does this message mean? What are the ramifications? How do I fix
    it? It happens on a V2.4 system, whenever the user attempts to
    initialize mail or update the profile. The user has a valid DDS entry,
    and OA$DDS_PRIME = 1.
    
    Thanks for any help.
    
    Bruce
T.RTitleUserPersonal
Name		DateLines
3033.1RTFN?SWAM2::RHODEWALT_BRI am a talking parrot.Wed Jul 21 1993 01:144
    BTW, the notes in 1640.* did not help me to understand or fix the
    problem.
    
    Bruce
3033.2Recreate the entry in ddsGIDDAY::SETHIAhhhh (-: an upside down smile from OZWed Jul 21 1993 02:5816
    Hi Bruce,
    
    Sorry I did not make it too clear in my wrapping up of the topic, you
    should have replied to the topic and said so :-).
    
    Basically I found that the DDS entry for that one user was
    incomplete/corrupted and I removed it from DDS, than recreated it.  I
    used MBMAN to do this.
    
    I hope that I have made myself clear or am I still speaking Punjabi
    :-).  If you have more problems let me know and I will do what I can to
    help you.
    
    Regards,
    
    Sunil
3033.4Okay! Okay!SWAM2::RHODEWALT_BRI am a talking parrot.Wed Jul 21 1993 21:1217
    The code is cleverer than I? Hmph! (Andrew, please post the Mail
    Management Guide citation, including version and page number. Of course
    I RTFMed before posting.)
    
    The consensus of -.2 and -.1 (from ALL-IN-1 users with concrete
    experience and cleverness, respectively _and_ respectfully) is that the
    entry is corrupt, and that I should delete it and recreate it -- right?
    
    I'll try this today.
    
    BTW, Sunil, I didn't intend to offend. I just assumed that no one would
    look in that old note, so I wrote a new one. Please check here later so
    you can read my questions or resolution report.
    
    Thanks to all.
    
    Bruce
3033.5Another questionSWAM2::RHODEWALT_BRI am a talking parrot.Wed Jul 21 1993 21:158
    Sunil,
    
    Did you create the good DDS entry using MC MBMAN? I can't tell by
    reading your replies in this topic and 1640.
    
    Sorry for the confusion.
    
    Bruce
3033.8Solved!SWAM2::RHODEWALT_BRI am a talking parrot.Thu Jul 22 1993 02:1511
    Thanks to both of you. The problem appears to have been a missing field
    in the DDS SUBSCRIBER record. 
    
    As you both suggested, I deleted the record in DDS, and then recreated
    it (using DDS_ADD.SCP).
    
    I hope this discussion contributes to someone else's understanding of
    the relationship between DDS and ALL-IN-1. The documentation is a
    little skimpy.
    
    Bruce
3033.9GIDDAY::SETHIAhhhh (-: an upside down smile from OZThu Jul 22 1993 02:5120
    Hi Bruce,
    
    By the way you did not offend me at all, I was just having a laugh.  I
    enjoy being in this conference, it's the best one.  Makes me feel less
    cynical about life and the universe :-).
    
    Sometimes the problem is caused by a mismatch of the DDSID as I
    discovered.  An in the worse case if the User Agent ie 
    OA$<node_name>$ALLIN1, has an incorrect DDSID ALL users will get the
    above error message and DDS searches will not work. I thought that I
    would mention this as I have come across a problem concerning the
    mismatch of the DDSID.
    
    I think that Andrew has had a little bit to do with the EM/DDS
    coding/design etc, in the past, hence he is the "Guru" on the subject
    :-).
    
    Regards,
                         
    Sunil