Conference pamsrc::objectbroker_development

2477.0. "object '$Register$' not found " by LEMAN::NAUFFRAY () Wed May 28 1997 11:42

    Hi,
    
    Under the following configuration :
    
          ALPHA VMS CLUSTER with 2 DEC 4000/620 nodes :  NODE1, NODE2
          Homogeneous VMS cluster
          OpenVms v6.2
          DECnet v6.3 ECO6
          UCX v4.1
    
    I tried to installed from scratch OBB v2.7-11 on NODE2, using the
    SYSTEM account. The first installations failed due to a bad DECnet
    setting. Finally when everything fixed from a network point of view.
    I did delete all the OBB references/images/files/logicals/Identifiers on 
    the system via the DELOBB.com/DELTREE.com procedures that Dick passed on 
    to me (I took care also to delete any OBB logical defined on NODE1).
    Reinstalling OBB v2.7-11, I got the following message, leading the IVP
    to fail afterwards :
    
    ...
    
    %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target
    directories...
    Starting registry setup
    Connect to Security registry partition
    %OBB-E-REG_REGNOTFND, Registry `$RegistryName$' not found. 
    Registry `REG_KEY_SECURITY' not found. 
    %OBB-E-REG_REGNOTFND, Registry `$RegistryName$' not found.
    Starting ObjectBroker Agent
    %RUN-S-PROC_ID, identification of created process is 20C00188
    
    ***************************************************************************
    
           Beginning Installation Verification Procedure for
                ObjectBroker for OpenVMS 
    
    ***************************************************************************
    
    Showing the ObjectBroker agent attributes...
    %OBB-E-INV_NOCTRLSRV, No agent is running on node `MTNA05'. 
    -OBB-E-INV_TRANSSRVNTF, The requested server was not found or is not
    accessible 
                    on the network. 
    -OBB-E-INV_TRANSERR, Transport error `Error Code: 61'. 
    -OBB-E-INV_TRANSSRVNTF, The requested server was not found or is not
    accessible 
                    on the network. 
    -OBB-E-INV_TRANSERR, Transport error 
                    `%SYSTEM-F-INVLOGIN, login information invalid at
    remote node'. 
    
    ***************************************************************************
    
              Installation Verification Procedure failed for
                  ObjectBroker for OpenVMS 
    
    ***************************************************************************
    
    %VMSINSTAL-E-IVPFAIL, The IVP for OBBDEV V2.7 has failed.
    
        Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
    
        Creating installation data file:
    VMI$ROOT:[SYSUPD]OBBDEV027.VMI_DATA
    
    
    
    This kind of error is normally due to some OBB files remaining from a 
    previous installation, or logicals remaining defined; but I know that
    the delete procedure I normally use to clean everything is working OK
    and that nothing is remaining. What could be the origin of this
    problem. The .REG files are created under OBB$LIBRARY, and the
    configuration is the following :
    
    
     Configuration  "DECnet and TCP/IP Configuration"  (Current) 
     -------------------------------------------------------
      Authentication
        AuthrWOAuthn: Enabled
        Package:      Trusted
         Description: Trusted authentication package
      Network
        Package:      DECnet
         Description: DECnet transport package
        Package:      TCP
         Description: TCP/IP transport package
      Logging Level                  None
      Keep database files            0
      Object Hash Table Size         0
    
    Moreover, looking to the agent log file, the following message appears:
    
    "%OBB-E-AGN-INITFAIL, Agent Service Initialisation failed
      OBB-E-DB-OBJALREXIST, Specified Object 'ROOT' already exists"
    
    
    Maybe someone could help me on this issue which start to drive me
    nervous.
    
    Thanks a lot for the hand so far.
    
    James NAUFFRAY
 
 European Expertise Center for Enterprise Client-Server Softwares
 Digital Multivendor Customer Services
 Geneva, Switzerland
 Tel : (++41) 22-709-4782
 fax : (++41) 22-709-4451
    nauffray@mail.dec.com 
 or nauffray@leman.enet.dec.com

    

James,

The early errors about registry not found are causing the agent
to fail. I suggest re-installing once more. Make sure that you

1. Run the obb removal script. Make sure that sys$library:obb$shr.exe
   is gone.

2. Make sure that the logical names, reg_key*, are not defined.


Make sure that the DECnet nodename is defined as the sysgen
parameter SCSNODE. If not, you've got to define it.

Then do a full reinstall.



   Dick

    
    Dick,
    
    Thanks for your quick answer.
    I was sure that sys$library:obb$shr.exe was gone, but I'll (at least)
    triplecheck again. I must admit I didn't pay attention to the reg*
    logicals, I'll have a look. The same for the SCS node in SYSGEN. I'll
    make a new try and I come back to you for the status.
    
    Thanks for your kind help.
    James

    Dick,
    
    I did exactly the same as you proposed, but I had the same failure.
    I succeed installing at least 10 times OBB v2.7 on a VMS v6.2 Aplha
    platform. So, in this context, the only thing I saw is that the node
    is part of a cluster, where DECnet has been installed, but there's 
    apparently a problem in the way the cluster has been configured
    (the other cluster member is not reachable from the first one !).
    2 solutions appear, to exclude the node from the cluster, or to 
    find a way to workaround the fact that OBB cannot create and 
    access its SECURITY REGISTRY as mentioned in the initial entry.
    Have you some clue on that ? 
    What is the way to really avoid OBB to take care of the cluster
    setting from a DECnet point of view.
    
    For information, I'm really sure that all the files/logicals and
    shareable images are removed before a new OBB installation.
    
    Thanks for your help so far
    James

James,

Sounds like that one node in the cluster is not configured
properly. You need to check that:

	DECnet nodename = SCSNODE     these must be identical.

Check the logical name SYS$NODE -- is it the DECnet nodename
and does it match SCSNODE?

Once you get your VMS node configured properly (ie DECnet works
cleanly), then you can reinstall OBB.




     Dick

    Dick,
    
    Thanks for the answer.
    I asked the guys to reinstall properly the cluster in terms of 
    network point of view, or to remove the node from the cluster
    with or without DECnet. When done, I'll check again the 
    SCSNODE and SYS$NODE values before a new test.
    
    James

    Dick,
    
      No surprise, good result !
      Reinstalling on a standalone node properly configured from a 
    network point of view worked fully OK.
    
      Thanks for your help.
      James