Frequently asked questions about the Package and Deployment Wizard in Visual Basic 6.0 (885484)


The information in this article applies to:

  • Microsoft Visual Basic Professional Edition for Windows 6.0
  • Microsoft Visual Basic Enterprise Edition for Windows, Version 6.0

INTRODUCTION

This article contains answers to the most frequently asked questions about the Microsoft Visual Studio Package and Deployment Wizard (PDW).

For frequently asked questions about Microsoft Visual Basic 6.0, visit the following Microsoft Web site:

http://support.microsoft.com/support/vbasic/faq

MORE INFORMATION

  • Does the latest Visual Studio 6.0 service pack update the PDW? Have there been any updates to the PDW?

    Yes, the latest Visual Studio 6.0 service pack fixes the following bugs in the PDW:
    • 198052 FIX: "Out-of-date dependency" warning in Setup Wizard and PDW
    • 190493 FIX: "Locate file" message when running a PDW Setup app
    • 257572 FIX: Error message "Missing dependency information" for Mshtml.tlb when using PDW
    • 221604 Known issues with Internet Explorer 5 and Visual Basic 6.0
    • 224185 FIX: User Defined Type in Public function of a user control fails to run
    The latest Visual Studio 6.0 service pack fixes many other Visual Basic bugs. To obtain the latest Visual Studio 6.0 service pack, visit the following Microsoft Web site:

    http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp6/default.aspx

  • How can I force the Setup program to install my application to a specified location?

    You can force the Setup program to install your application to a specified location by adding the following line to the [Setup] section of the Setup.lst file, immediately following the DefaultDir line. 
    ForceUseDefDir=1
    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    190150 How to force application Setup to use the default directory

  • How can I make the Setup program install files into subfolders of the application's folder?

    You can modify the Install Location setting for the files that are listed in the Install Locations window of the PDW. For example, if you want a file to be installed in the Test subfolder of the application's folder, you can set Install Location to $(AppPath)\Test.

    Note If you change the Install Location setting of the application (.exe) file, you must also change the location that is specified for the application's shortcut in the Start Menu Item Properties window of the PDW.

    The $(AppPath) macro is one of many macros that you can use in the PDW.

    For additional information about the installation macros, click the following article number to view the article in the Microsoft Knowledge Base:

    189739 How to use Package and Deployment Wizard installation macros

  • What do I have to install on a Web server to deploy my Visual Basic Internet applications?

    The Visual Basic 6.0 Package and Deployment Wizard (PDW) uses the HTTP POST method to transfer files to a Web server. To configure your Web server to receive files from the PDW, you must install the Microsoft Posting Acceptor.

    For additional information about how to install and how to configure Microsoft Posting Acceptor, click the following article number to view the article in the Microsoft Knowledge Base:

    192116 How to configure Posting Acceptor to work with the Package and Deployment Wizard

    If you are deploying a DHTML application, you can transfer the files that the Package option of the PDW creates to any folder on the Web server. However, if you are deploying an IIS application, the files must be in a virtual directory on the server. If you do not have an existing virtual directory on the server to store the file, you must create a virtual directory by using IIS Internet Server Manager.

    For additional information about how to create virtual directories, click the following article number to view the article in the Microsoft Knowledge Base:

    172138 How to create a virtual directory in Internet Information Services (IIS)

  • How do I resolve the following error message?
    Unexpected error number C0042116 has occurred: The Web server returned the following error: The signature on cabinet file xxxx.CAB could not be verified.
    Before you can successfully post your applications, you must install the Posting Acceptor and then configure the Web server correctly.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    192116 How to configure Posting Acceptor to work with the Package and Deployment Wizard

  • What do I do when I receive a "Missing dependency information" warning message in the PDW?

    Your project contains a component that does not have an associated dependency (.dep) file and that has no pertinent information in the Visual Basic 6.0 master dependency file (Vb6dep.ini).

    If the component does not require any other files to run correctly, you can ignore this warning message. However, if the component depends upon other files, you must either add those files manually on the Included Files screen of the PDW or obtain a .dep file for the component and then run the PDW again.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    190978 Missing dependency information dialog in PDW

  • What do I do when I receive an "Out-of-date dependency information" warning message in the PDW?

    Each component that appears in the list under the warning message has a dependency (.dep) file. The dependency file lists all the files that the component depends on. However, the .dep file was created for a different version of the component. Therefore, the PDW cannot determine the files that the component depends on.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    198052 FIX: "Out-of-date dependency" warning in Setup Wizard and PDW

  • What causes the following error message to appear when I install my Visual Basic application on a destination computer?
    Unable to load file 'msdadc.dll' to register it.
    You have to install DCOM on the destination computer before you can install Microsoft Data Access Components (MDAC). The Setup program that the PDW created uses the MDAC installer program (Mdac_typ.exe) to install MDAC. MDAC includes OLE DB, ADO, and Jet.

    To install DCOM on a computer that is running Microsoft Windows 95 or Windows 98, run the DCOM98.exe file. The Dcom98.exe file is located in the Dcom98 folder of the Visual Basic distribution disks. Computers that are running Microsoft Windows NT 4.0 already have DCOM installed.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    191704 Unable to load file to register it during setup

  • What causes the following error message?
    The Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) failed to initialize when called. Try reinstalling the applications that returned the error.
    The Jet files or the DAO files are mismatched, or one or more of the files are missing.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    192934 Error "The Jet VBA file...failed to initialize when called"

  • What does the following message mean?
    The SETUP.EXE file is linked to missing export OLEAUT32.DLL:185.
    You are running the Setup program on a client computer that has version 2.1 of the Oleaut32.dll file. This earlier version of the file was included with the original version (4.00.950) of Windows 95. Setup packages that the PDW builds do not run on the original version of Windows 95 because the original version does not support an API function in version 2.1 of the Oleaut32.dll file.

    This problem does not occur on client computers that are running later versions of Windows 95, on client computers that are running Windows 98, or on client computers that are running Windows NT version 4.0 or a later version of Windows NT. Also, this error does not occur if another installation program, such as the installation program for Microsoft Office 97, for Internet Explorer 3.0, or for Internet Explorer 4.0, has updated the Oleaut32.dll file to a newer version of the file.

    Note All Visual Basic 6.0 applications require a newer version of the Oleaut32.dll file.

    To resolve this problem, install the latest versions of the Visual Basic 6.0 run-time files on the client computer before you run your Setup program. You can install the latest versions of the Visual Basic 6.0 run-time files by running the self-extracting file Vbrun60.exe. This file installs the latest Visual Basic 6.0 run-time files.

    The following file is available for download from the Microsoft Download Center:

    DownloadDownload the Vbrun60.exe package now.

    For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

    119591 How to obtain Microsoft support files from online services

    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

    For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    194754 Setup.exe file linked to missing export Oleaut32.dll:185

    192461 VBRun60.exe installs Visual Basic 6.0 run-time files

  • What causes the following error message to appear after I run a Setup program that the Visual Basic 6.0 PDW created?
    The file c:\windows\temp\msftqws.pdw\$(DllSelfRegisterEx) could not be registered because it was not found.
    This problem occurs when the Setup program tries to register the MSCal.ocx file. This problem occurs because the registration macro for the MSCal.ocx file in the Setup.lst file is incorrect. The registration macro should be $(DllSelfRegister) instead of $(DllSelfRegisterEx).

    For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    197123 Out-of-date dependency information for MSCal.ocx

    236529 Deploying package with MSCal.ocx causes error: "The file ...\$(DllSelfRegisterEx) could not be registered..."

  • What causes the following error message to appear when I save a Setup package to disks by using the Package option in the PDW? Why is there insufficient space for the Setup files on my disk?
    An unknown error occurred while building the cabinet file '<Project Name>.CAB'. Please verify that you have proper access to the destination and that there is sufficient space there to create the file.
    The Package option in the PDW creates a Support folder that contains the uncompressed versions of the files that you are distributing. It packages this folder together with the Setup files for your application. There is insufficient space on a disk for both the Setup files and the Support folder.

    When you create the distribution package, save the Setup files to the hard disk instead. Then, use the Deploy option of the PDW to copy the Setup files to your disk.

    For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    196583 An unknown error occurred while building the cabinet file

Modification Type:MinorLast Reviewed:8/19/2005
Keywords:kbDeployment kbsetup kberrmsg kbtshoot kbFAQ kbinfo KB885484 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.