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

Conference utrop1::linkworks_v3

Title:LinkWorks V3.0 Notes Conference
Notice:LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:tacklr.apd.dec.com::TACK_Lm::TACK_L
Created:Tue Jun 28 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:8338

2126.0. "NTISQL 3.0.8 Dec '96 installation enigmas" by KETJE::HAENTJENS (Beware of Counterfeit) Mon Feb 17 1997 16:19

    We did an LNX 3.0.8 Dec '96 installation on a brand new NT 4 with SQL
    6.5 and found out the following:
    
    1) The installation guide (chapter 2 Installing SQL and chapter 3 LNX)
    states that the installation can be done on a PDC, BDC or server. If the
    installation is done on a server which is not PDB or BDC, this server
    must be in an NT domain with a PDC or the installation will fail.
    
    2) Testing the SQL Server installation (end of chapter 2) on our server
    gave NULL instead of the real servername. We do not know why, but this
    did not have any impact on the LNX installation, which went OK.
    
    3) For a reason unknown to us, %oproot% is undefined in a command box,
    whereas it does exist in the System Variables. No further impact.
    
    4) The section explaining how to grant LogOnAsAService to LinkWorks
    (either just before or at the start of the section "Installing the
    Management Component" depending on the version of the Installation
    Guide confused us. The section made us look for a check box "Grant Log
    On As a Service" which isn't there in NT 4 (of course we are dummies),
    and the installation guide did not explain whether we had to select
    "Log on as System Account" or "Log on as This Account ... omuser"
    (which we fortunately selected).
    
    Also, we were so foolish as to try and start the LinkWorks service,
    which is not yet possible at that point in time. This puzzled us a bit,
    because the event viewer and the logfile told us that the file
    CLTDF.CFG was missing, and indeed it wasn't there...
    
    We suggest that for us, ignorant plebeians, an addendum would be made
    to the Installation Guide, telling us a little bit more about what is
    happening at each installation step, and, while we're asking, also what
    is happening at each startup step.
    
    Rene.
T.RTitleUserPersonal
Name
DateLines
2126.1suppdc.uto.dec.com::PETERS_MMon Mar 03 1997 12:385
For V3.2, the installation procedure for the LinkWorks server on
Windows NT has been rewritten. It will be very easy to install
LinkWorks.

Martin