PRB: "Invalid Line in Setup Information File" Error Message

Last reviewed: April 23, 1997
Article ID: Q159411
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 32-bit only, for Windows, version 4.0

SYMPTOMS

During the installation of a Visual Basic 4.0 application that uses Jet, a message box entitled "APPNAME Setup" appears with the following error message:

   Invalid line in setup information file!

   Section: Files
   1,,DAO3032.DL_,DAO3032.DLL,$(MSDAOPath),$(DLLSelfRegister),$(Shared),
   1/12/1996,456464,3.0.0.2504

NOTE: The date, version number, and size shown in the error message may vary according to the build of Jet being distributed.

CAUSE

The 32-bit Jet components are registered as installed to a network server with a UNC path. The error message appears because this registration occurs before you install your Visual Basic 4.0 application.

STATUS

This behavior is by design.

WORKAROUND

NOTE: Microsoft Developer Support does not support the modification of the setup process or any of the setup files. Support is provided for the Setup Wizard only on an "as is" basis.

Several workarounds are possible. The following three are recommended:

  1. "Trick" setup into thinking DAO is not installed by removing the offending registry reference to the UNC path. Use the Regedit utility to find the DAO key. The DAO key is located in:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\DAO

    There will be a value named "Path" in the following form:

    "\\MyServer\DAO\DAO3032.DLL"

    Rename "Path" to "OldPath," and re-run the application setup.

  2. If the Jet components are already installed on all the workstations, remove them from the application setup routine.

  3. (NOTE: This is the most reliable method.) Modify the code in the Setup1.vbp project as follows:

    a. Open the Setup1.vbp project located in \VB\setupkit\setup1\setup1.vbp

        in 32-bit Visual Basic 4.0.
    

    b. Go to the strGetDAOPath() subroutine in the basSetup1.bas module and

        locate this section of code:
    

          If RegOpenKey(HKEY_LOCAL_MACHINE, strKey, hkey) Then
    
                   RegQueryStringValue(hkey, strValueName, strPath)
                   RegCloseKey(hkey)
          End If
    
          Insert this line of code immediately following the preceding section:
    
          If Left(strPath, 2) = "\\" Then strPath = ""
    
          If the DAO Path is a UNC Path, Setup1 does not consider Jet to be
          installed.
    
       c. Save basSetup1.bas and run the Setup Wizard again to re-create the
        setup process for your project.
    
    

MORE INFORMATION

The Setup1 project routines that check the validity of the installation paths will mark UNC paths as invalid. UNC paths for DAO frequently occur on systems where you install Office95 from a network server that uses UNC paths, and select the option to leave system components on the network.


Keywords : kbinterop kbsetup kbtool TlsSetWiz vb432 vb4win
Version : 4.0
Platform : NT WINDOWS
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.