Conference abbott::mailworks-vms

1556.0. "System error 652 (in V13C:[BUILD]CTIDN_V.C;1 at line 956)" by VMSNET::J_COLBURN () Fri Mar 14 1997 02:20

    I have a customer that has installed Mailworks V1.3 onto a single node
    VAX running V5.5-4.  When doing the install, he said no to Message
    Router and DDS and should actually have said yes to remote Message
    Router and DDS.  After the install, he could not get the MUAS$SERVER
    process to stay up.  I dialed iand and found that the MRAPPSHAR.EXE
    file was missing from SYS$LIBRARY and moved it from MUAS$TOOLS.  Now
    the server is staying up but we still have problems.
    
    When trying to run DMW, the following error occurs:
    
    BK>dmw                                                                          
    System error 652 (in V13C:[BUILD]CTIDN_V.C;1 at line 956)                       
    System error 652 (in V13C:[BUILD]CTIDN_V.C;1 at line 956)                       
    %A1MAIL-I-NOSERVERS, No DEC MAILworks servers currently available.              
    
    When trying to add users from the system account, the following error
    occurs:
    
    BK>x4man                                                                        
    V1.3A                                                                           
                                                                                    
    X4MAN.MAIL> manage user                                                         
                                                                                    
    X4MAN.USER> add field                                                           
    System error 652 (in V13C:[BUILD]CTIDN_V.C;1 at line 956)                       
    System error 652 (in V13C:[BUILD]CTIDN_V.C;1 at line 956)                       
    %A1MAIL-E-NOSRVAVA, No DEC MAILworks servers currently available, retry
    operatio
    n later.                                                                        
    %A1MAIL-E-SM_ERRADDUSE, Error occurred while adding a user or profile
    template. 
    -MUAS-E-INVSESS, Invalid session id                                             
                                                                                    
    BK>exit 652                                                                     
    %SYSTEM-F-NOSUCHNODE, remote node is unknown                                    
    
    
    After finding references in the notes file that indicated there could
    possibly be a problem with SYS$NODE, we checked and it was defined
    correctly.
    
    I thought I remembered something in the past about there being a
    problem with a two digit node name and checked the notes files.  Found
    nothing there and after talking with a DECNET support person, it
    appears there are no probelms with two digit node names.
    
    I am going to ask the customer to re-install and use V1.3-A instead of
    V1.3.  Does anyone have any suggestions as to what to check next? 
    There seems to be nothing else in the log files to point us in the
    right direction.

    Had that error/problem two weeks ago at a customer side.
    
    Some application defined there DECnet node name to some
    mailbox device.
    
    Check $show log <node name> and $DIR <node name>:: ....
    
    Cheers,
    
    Jan

    Thanks Jan.... That was the problem....
    
    (LNM$SYSTEM_TABLE)
    
      "BK" = "MBA37:"
    
    Jan Colburn