[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference rocks::dec_edi

Title:DEC/EDI
Notice:DEC/EDI V2.1 - see note 2002
Moderator:METSYS::BABER
Created:Wed Jun 06 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3150
Total number of notes:13466

3132.0. "CANTGETAUTH ObjectBroker problem" by JOBURG::BERETTA () Mon May 19 1997 17:01

    Hi,
    
    I just upgraded a decedi 2.1c VMS alpha system to 2.1d and upgraded
    objectbroker to 2.7-10.
    
    When I run the decedi$configure_obb.com I get the following error:
    
    Objectbroker error occured in DECEDI_IMC_IMPL_REGISTER
    Objectbroker error: %OBB-E-INV_CANTGETAUTH, could not get an
    authentication key from node '$node$'.
    -OBB-E-INV_CANTGETAUTH, Could not get an authentication key from node
    '<nil>'.
    
    Any help much appreciated.        
    
    Peter.
T.RTitleUserPersonal
Name
DateLines
3132.1METSYS::THOMPSONTue May 20 1997 10:3511
Peter,

It is ObjectBroker that is reporting this error, so they would be the 
logical choice to ask for an explanation.

Did you read all the Release Notes for OBB V2.7?

Also read all of 2978.6, only the last paragraph applies.

Regards
Mark
3132.2Working after a re-installJOBURG::BERETTATue May 20 1997 15:3723
    Hello Mark,
    
    I admit I had  not read the release notes, thanks for reminding me.
    Here is the reply I posted in the Objectbroker conference:
    
    "
        I managed to get it working by re-installing and choosing the
    option 3
        which enables decnet and tcpip. I had selected option 2 previously
    (tcpip
        only). I also installed it from the system account this time, in
    case
        this made a difference.
    
        What put me onto to this was having only read the release notes
    after I
        encountered the problem, I noticed that if you choose the tcpip
    only
        option, AuthrWOAuthn should be set to enabled in trusted
    environments.
        I tried changing this to enabled  and got the message "command
        failure". So then I re-installed as mentioned above.
    "