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

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2511.0. "TLC V2.5 failing" by ATHINA::KARVOUNIS () Fri Feb 07 1997 11:29

    I am trying to install Teamlinks V2.5 on my VAX system running VMS
    V6.0.  I have alread install TLC v2.1 with ALL-IN-1 V3.0a.
    
    When doing the installation it fails after Checking the ALL-IN-1 IOS.
    
    %TLC-I-CHKA1 Checking ALL-IN-1 IOS...
    %TLC-E-NOA1IOS,  No ALL-IN-1 IOS IMAGE can be found,  ALL-IN-1
                     IOS must be installed and started before the 
                     teamlinks connection can be installed.
    
    I have search quite a few stars/notes file but I have not come
    across this error yet.  Can anyone suggest anything on this.
    
    regards
    Olympia

T.RTitleUserPersonal
Name
DateLines
2511.1IOSG::CARLINDick Carlin IOSG, Reading, EnglandFri Feb 07 1997 14:357
    Olympia
    
    Did you include the old abbott::windows_office notesfile in your search?
    
    Do notes 3694 or 2966 help?
    
    Dick
2511.2Things to check...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeFri Feb 07 1997 21:4620
    The code will be looking for the logical OA$IMAGE to find OA$MAIN.EXE.
    You're most likely to get this error because you haven't run A1V30START
    on the node where you are doing your installation.
    
    Try $ SHO LOG OA$IMAGE
        $ DIR OA$IMAGE
    
    The next possibility is that the TLC can't read the image ident, use
    this command to find out what it is:
    
    	$ ANAL/IMAGE/INTER OA$IMAGE {Press CR four times}
    
    it should say something like:
    
    	image file identification: "ALL-IN-1 V3.0"
    
    Graham
    
    PS Please be careful to type 'ALL-IN-1' correctly in your notes, since
    it's a trademark.

2511.3ATHINA::KARVOUNISMon Feb 10 1997 13:069
    Thanks for your reply I just checked the logial and it is
    assigned. Also when I do anal/image/inter the image file
    identification is "ALL-IN-1 V3.0A3"
    
    Is this correct.  Is there something else that I should
    look for because I am still getting a failure.
    
    Thanks for your help
    
2511.4IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeTue Feb 11 1997 14:546
    I'm sorry, I've looked at the code now, and it is actually looking in
    OA$LIB for OA$MAIN.EXE.
    
    The test is:
    
    	if f$search("oa$lib:oa$main.exe") .eqs. "" then ........
2511.5help ....ATHINA::KARVOUNISMon Feb 17 1997 11:0512
    	I am now baffled and lost I cannot seem to find out where my problems
    are coming from.  I read in the installation guide that if you are
    trying to install TLC 2.5 on ALL-IN-1 V3.0-a then you must have all the
    elements of TLC 2.1 installed first.  Can you help me maybe I not
    running the correct version of TLC 2.1 and this is why TLC v2.5.
    is failing?  I really don't know because this is the first time I am
    installing teamlinks.  My colleague that originally installed this is
    not working here anymore.
    
    regards
    Olympia
    
2511.6Install TLC V2.1 again?IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeMon Feb 17 1997 12:0316
    The kit makes the following checks:
    
    1) VMS Version
    2) OA$LIB:OA$MAIN exists
    3) OA$IMAGE has version of V3.0
    4) OA$BUILD:SM.A1$MSG contains the TLC Version Message:
    
    	TeamLinks Connection Package V2.1
    
    5) Various OA$* logicals are defined
    
    I suggest that you also reinstall TLC V2.1 to get your system back into
    a known state. Then try the V2.5 install again.
    
    If it still fails, then post the location of a W:R logfile, or mail me
    details of how to log into the system.
2511.7Closing the loop...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeTue Feb 18 1997 11:4113
    Having logged into the system, the error reported was an invalid UIC:
    
    	%DCL-W-INVUIC, invalid UIC - must be of the form [group,member]
    
    which then bombed the installation. It appears that this was caused by
    the installation using the manager's OpenVMS account name rather than
    its UIC in the SET UIC command. Normally, this works fine, since the
    account name will also be the name of an identifier with the
    corresponding UIC.
    
    However, on this system, the Manager's account name, ALLIN1, was also
    used as a disc name, and so the DCL command parser translated the disc
    name into its physical name, which SET UIC didn't like much!