Conference iosg::all-in-1_v30

2524.0. "NETWORK.DAT unable to select a user" by BUSHIE::SETHI (Man from Downunder) Mon Apr 05 1993 03:06

    G'day All,
    
    I have been working on problem reported at a customer site and I am
    pulling my hair out, seeing that I am going bold I need some help ;-).
    The site has Version 3.0 installed and tested with /nocustom.
    
    The customer has the following entry in NETWORK.DAT:
    
                                    Network Profile
    
     Username:   GIBBS STUART                          Node: AUTC01
     Full Name:  Gibbs Stuart  (Lorimer St)
     Network Address: mrgate::"sgibbs@kgfaus01@kgfaus02"@wins
     Last update: 15-Mar-1993 11:53             Mnode: N     Deleted: N
    
    The first problem was that the above user could not be selected by
    pressing return or find.  I put debug on and managed to find the user
    when I pressed return, before the debug I couldn't, I can consistently
    find the user (RETURN) !!!!
    
    Problem two:
    
    Putting on trace you can see that it's actually finding the record here
    is the sample:
    
    ![IO]     Rewinding NETW
    ![IO]     Locating next record to read from NETWORK, Key: , Key-of-ref:
    USER/2
    ![IO]     Getting next record from NETWORK
    ![IO]     Getting field NETWORK from NETWORK, Value:
    "sgibbs@kgfaus01@kgfasu02@w
    !               ins"
    
    I enter the users name and enter FIND or GOLD L and the list does not
    contain the ALL-IN-1 username.  Turning on debug I did the following:
    
    <get @OA$FIELD_NAME, gave me "gibbs"
    <get OA$MAIL_ADDRESS.%WHOLE[@OA$FIELD_NAME] gave the addresses not
    found message.                
    
    I than did a <get OA$MAIL_ADDRESS.%WHOLE["GIBBS"] and this gave me the
    address in UPPERCASE, there is only one GIBBS record in NETWORK.DAT.
    
    I copied the record to my NETWORK.DAT and have had no problems
    selecting Gibbs, so I am a bit stumped for an answer.  The customer has
    setup replacement strings in Message Router for the above address so
    that's why it looks a bit odd.
    
    One final thing the customer has checked his NETWORK.DAT using
    analyze/rms/check no errors reported and has done a reorganisation of
    system files without a problem.
    
    Any help would be appriciated saves me going bold ;0), maybe I have
    been looking at the trace for too long.  The logfile can be found on
    RIPPER::USER$TSC:[SETHI]Q31331_5493.LOG_3, with the protection set to
    w:r.
    
    Regards,
    
    Sunil
    
                                   

    Hi Sunil,
    
    I think this is the known problem where the parentheses in the Full
    Name confuse things. Can you try replacing them with {} and
    see if that fixes the problem.
    
    Cheers
    
    Stuart

    Hi Stuart,
    
    Sorry I made a mistake the entry of the Network profile record I have
    put in .0 was the original entry.  The "()" was the first thing I
    corrected and it still does not work, we have tried "[]" and "{}" with
    no success at all.
    
    I have to add that WordPerfect is integrated and on my system it isn't
    and I can select the record without a problem.  I have come across a
    number of problems where options have stopped working when
    Word/defective/(im)Perfect has been integrated on an ALL-IN-1 IOS 3.0
    system at other sites.  I will be chasing this up with WordPerfect but
    as usual I need something that will standup because they deny all
    knowledge of the problem.
    
    So any help would be appriciated especially your views as to the cause
    of the problem.  As stated in .0 we have done an analyze/rms/check etc.
    no errors found.
    
    Thanks in advance,
    
    Sunil

    Hi Sunil,
    
    Mail addressing is not my strong point, so I hope someone who knows it
    better can take over. I tried to copy the log file in .0 but got file
    not found. Were the values of oa$dds_prime the same on both your system
    and the customers?
    
    Cheers
    
    Stuart

    Hi Stuart,
    
    We managed to solve the problem at last and the reason why this problem
    occured was due to the following:
    
    1. The customers node is called AUTC01 and the address is a non-standard 
       ALL-IN-1 address format.
    
    2. The NETWORK PROFILE had AUTC01 as the node.
    
    Because the address format was "invalid" in terms of ALL-IN-1
    addressing the user address was not displayed.  When we changed the
    node name to something else it started working.
    
    I am collecting the lost hair off the floor and gluing them back :-). 
    
    Thanks for your help and I hope this weiderness will be of some use to
    others.
    
    Regards,
    
    Sunil