Visual Basic Q&A

Symptoms
When deploying to a Web server using the Package and Deployment Wizard (PDW), you see the following error:

Unexpected error number 40042119 has occurred: There is no PostInfo file on the server.
This error may occur if you have typed an incorrect URL or if the URL does not refer to a correctly configured Web server. Ensure that the URL is correct and the Web server is properly configured. For proper configuration, you may need to install Microsoft Visual Studio’s server-side setup on the Web server.
Resolution
This error occurs because of the following reasons: The Web service is not running.The PostInfo.asp file is missing or is not located in the InetPub\scripts physical directory.You do not have NTFS Read and Execute (RX) permissions to the InetPub\scripts directory.The <META> tag in default document (typically named Default.htm) in the root directory of the Web is pointing to the incorrect location for PostInfo.asp.

Symptoms
The information below includes the documentation and workarounds for VisualBasic 6.0. This information can also be found in the README.htm file thatships with Visual Basic 6.0 on the Visual Basic 6.0 CD-ROM. Please see theREFERENCES section of this article for a list of the Microsoft KnowledgeBase articles relating to the Visual Basic 6.0 readme.
Following is a list of all parts of the readme file:
Part 1.Important Issues Please Read First!
Part 2.Data Access Issues and DataBinding Tips.
Part 3.Control Issues.
Part 4.Language Issues.
Part 5.Samples Issues.
Part 6.Wizard Issues.
Part 7.Error Message Issues.
Part 8.WebClass Designer Issues.
Part 9.DHTML Page Designer Issues.
Part 10. Extensibility Issues.
Part 11. Miscellaneous Issues.
Part 12. Microsoft Transaction Server (MTS) Issues.
Part 13. Dictionary Object.
Part 14. Visual Component Manager.
Part 15. Application Performance Manager.
Resolution
Package and Deployment Wizard (PDW):Automatically Picks Up Files From Redist DirectoryA new feature of the Package and Deployment Wizard is its ability pick upfiles from the Redist folder. An example of how the feature is used wouldfollow the steps below:You have created an application that is ready for packaging.The application depends on a certain system file “MySysFile.dll” which,until recently, has been a stand-alone file. But now a recent systemupdate has made that file dependent on other files to function properly.However, a stand-alone version of the system file is also supplied.To simplify setups, you place that stand-alone version into the Redistfolder.When creating your deployment package, you navigate to the system fileto instruct the wizard that the system file should be included.Instead of picking up the system file (which is dependent on otherfiles), the Package and Deployment Wizard will pick up the stand-aloneversion that is in the Redist directory.
By default, no files are placed in the redist folder.
Package and Deployment Wizard Has [Do Not Redist] SectionA new section has been added to the Package and Deployment VB6Dep.ini file:[Do Not Redist]
Two kinds of files are listed under the new section:Files that are not needed at run-time. For example, ActiveX designersoften require two file references, one for design-time, and one for run-time. Since the design-time reference is not needed, it is listed in thesection and is not included in the package.Files that cannot be redistributed by the Package and Deployment Wizard.Some dependent files are not installed by Visual Basic, but must beinstalled by another component. For example, the following files areinstalled by Internet Explorer 4.x: Shdocvw.dll and Mshtml.dll.
Package and Deployment Wizard: In Silent Mode the NotificationWindow May Not Be First in the Window Z-orderWith Visual Basic, it is possible to run the Package and Deployment Wizardin silent mode from a command prompt. When doing so, you can also set apath for logging the wizard’s output (/l ). With the path set, the wizardwill create a log of events. If you do not use the argument, the wizardwill instead display a dialog box to notify you of the wizard’s completion.However, the window is not always obvious because it may be underneathother windows. In order to see it, you may need to close or minimize allother windows.
For more information, search online for “running as a stand-alone” inVisual Basic Concepts in the MSDN Library Visual Studio 6.0 documentation.
Package and Deployment Wizard: Command Line Mode Argument Added forSpecifying Executable PathAn argument has been added to the command line mode of the Package andDeployment Wizard. The argument is shown in the table below:

ArgumentDescription/e pathUse the argument to set the path for the project’sexecutable file if it is different from the project’spath. The argument allows the command line mode to be used in a multi-developerenvironment where a computer is dedicated to compiling the project andcreating the package.
For more information, search online with Package and Deployment Wizardselected, for running as a stand-alone in the MSDN Library Visual Studio6.0 documentation.
Package and Deployment Wizard: Manually Add User Control License FilesWhen creating a package for a user control that requires a license key, thelicense file (.vbl) is not automatically included. Instead, you must addthe file manually.
When you are at the dialog titled “Package and Deployment Wizard IncludedFiles,” click the Add button and search for the appropriate .vbl file.
Package and Deployment Wizard: Steps in the Web Deployment ProcessWhen you post an Internet package to a Web server using the Package andDeployment Wizard, the wizard uses a technology known as WebPost to copyyour package to the server and process it appropriately. These are thesteps that the WebPost process goes through when processing your .cab:It extracts the .cab file into a temporary directory.It locates the .inf file for the .cab file.Based on the contents of the .inf file, the WebPost process installsapplication files (based on the RInstallApplicationFiles section of the.inf file), installs system files (based on the RiinstallSystemFilessection), and installs shared files (based on the RInstallSharedFilessection). In the process, it registers any necessary files.NOTE: The DefaultInstall section of the .inf file is not run, because theinstructions it contains often require user input. The WebPost process alsodoes not create a virtual directory for your application, if one isrequired; directories must be set up in advance.
Package and Deployment Wizard: Web Deployment Tips for HTTP or FTP ProtocolIf the .cab file you are attempting to deploy to a Web server is copiedto the server but is not unpacked, make sure you included the .cab fileon the Items to Deploy screen, and that you used HTTP Post as theprotocol on the Web Publishing Site screen. In addition, you must havechecked the Unpack and Install Server-Side Cab check box on the WebPublishing Site screen. If you did not, try re-deploying your packageagain with this option selected.
NOTE: Cab unpacking is supported by Posting Acceptor 2.0 running on IIS4.0. If you receive an error saying that the Web server you selecteddoes not support the service provider you selected, there are severalthings you can do to try to fix this problem:If you are using the HTTP Post protocol, make sure that PostingAcceptor is installed on your Web server. If you are running IIS4.0, install Posting Acceptor 2.0. If you are running IIS 3.0,install Posting Acceptor 1.0. Cab unpacking is not supported byPosting Acceptor 1.0.Ensure that your URL is correct. If you are using HTTP Post,ensure that your URL begins with “http://”. If you are using FTP,ensure that your URL begins with “ftp://”.If you are uploading to a server location that has PostingAcceptor 1.0 installed, you cannot select the option to unpack andinstall your cabinet files when you deploy your package using thewizard. If you receive an error C0042115 that the query stringINSTALL is invalid, check your server configuration to determinewhat version of posting acceptor is installed. If it is version1.x, deploy your cab again, making sure to deselect the Unpack andInstall Server-Side Cab option.If you need to use the FTP protocol to post to a URL beginningwith “http://”, you may be able to resolve this error by adding thefollowing entry to the end of your Web server’s postinfo.asp file,usually located in the scripts directory on the Web server:[{02B5E1D1-8B7C-11D0-AD45-00AA00A219AA}]ServerName=” <%= Request.ServerVariables(“SERVER_NAME”) %>”MDAC installation requires DCOM95 to be installed. Setup programscreated with the Package and Deployment Wizard install the MicrosoftData Access Components (MDAC), which includes OLE DB, ADO and Jet,via the MDAC installer program: Mdac_typ.exe. This EXE requires thatthe machine being installed to have DCOM95 (or the newer DCOM98)installed on it.
If the MDAC intaller fails with a “DLL registration failed” message,this is because DCOM was not found on the machine. To restorefunctionality of existing data components, install DCOM95 and run theinstaller again.If you use the HTTP Post protocol and receive an error that you do nothave write access for the Web server, open the Internet Service Manageron the server computer, access the node for your Default Web Site(Console Root \ Internet Information Server \ machinename \ Default WebSite), choose Properties, select the Home Directory tab, and check theWrite check box.If your files are read-only when you try to post, you will receive anerror C0042116 announcing that processing has stopped. Change your fileattributes to proceed.Be aware that if you post a file to a directory where the same filealready exists, the file on the server will be overwritten and nowarning message will be displayed.If you use the FTP protocol and receive an error that access is denied,open the Internet Service Manager on the server computer, access thenode for your Default FTP Site (Console Root \ Internet InformationServer \ machinename \ Default FTP Site), choose Properties, select theHome Directory tab, and check the Write check box.If you use the FTP protocol and receive additional errors besides theone described in the previous bullet, make sure that you have properlyconfigured your FTP service on the Web server. To do so, start theMicrosoft Management Console (MMC), then follow these steps:Right-click on Default FTP Site and choose New Virtual Directory.Enter an alias to be used to access the virtual directory, thenclick Next.Enter the physical path of the directory to which to map thevirtual directory (for example, c:\inetpub\ftproot) then clickNext.Select the appropriate access permissions, making sure to allow writeaccess so that your deployments can proceed without errors, thenclick Finish.Right-click on Default FTP Site and choose Stop.Right-click on Default FTP Site and choose Start.
When you deploy to the FTP server using the Package and DeploymentWizard, use the site FTP://servername/alias where alias is the aliasyou assigned in step 2. Use the username “anonymous” and the password”me@somewhere” for anonymous login.
Package and Deployment Wizard: Start Menu Items: Run Option Not SupportedWhen creating a package for deployment, you can also create a Start menuitem. Although it is mentioned in the Help topic for the dialog box, theRun option is not supported.
System Configurations for WebPost’s Posting AcceptorWhen you deploy your packages to a Web server, the Package and DeploymentWizard uses a technology known as WebPost to move your files to the desiredlocation. WebPost consists of two main components:The Package and Deployment Wizard, which sends your content to aqualified site.A Posting Acceptor, located on the Web server, that enables the postingof content to an IIS server.There are multiple versions of Posting Acceptor available. You must makesure you install the correct version on your Web server based on yourmachine configuration. The following table lists the appropriateconfigurations:

Use thisif you are runningComments————————————————————————–Posting Acceptor 2.0Windows NT 4.0 with SP3Posting Acceptor 2.0IIS 4.0supports both contentposting and theunpacking of cabinet(.cab) files on theserver.Posting Acceptor1.0 Windows NT 4.0You cannot unpack .cabwith SP3with this versionIIS 3.0files of postingacceptor. Use this forcontent posting only.You can move yourfiles to the serverand then manuallyregister any necessaryfiles that would havebeen registered by the.cab process. NOTE: Posting Acceptor does not work on any platforms that are usingPersonal Web Server or Peer Web Server. You must use IIS. Steps forinstalling Microsoft Posting Acceptor 2.0 if you have Visual Studio orVisual Basic Enterprise Editions.Launch Visual Studio or Visual Basic setup from your installation CDs.When prompted to choose options to install, click Install ServerApplications and Tools, then click Next.Click Launch the BackOffice Installation Wizard, then click Install.Now select the radio button for Custom, then click Next. You will see the options to install and their sizes. Click Next.Select Microsoft Posting Acceptor 2.0.You can install Posting Acceptor 2.0 from the Deploy folder of VisualStudio installation CD number 2. Posting Acceptor 1.0 can be installed fromthe Microsoft Posting Acceptor Information Website. If you want to installPosting Acceptor 2.0 on a computer that already has the Windows NT OptionPack, you should first check to see if version 1.0 of the Posting Acceptoris already installed. If so, remove it before installing version 2.0. Todetermine if 1.0 is installed, select the NT Option Pack on the Add/RemovePrograms mechanism of the Control Panel. Click Add/Remove, then look forPosting Acceptor 1.0 among the components listed. You may find it underMicrosoft Site Server. If it is installed, remove it. You can then installversion 2.0 by running PASetup.exe.
Package and Deployment Wizard: Edit Setup.lst File If YouRebuild Cabs From Batch FileAfter creating a standard setup package using the Package and DeploymentWizard, you can manually recreate the setup files (Setup.exe, Setup.lst,and all .cab files) by running the batch file found in the in the Supportfolder. Doing this allows you to manually customize the package or torecreate a package without running the wizard again. Running the batch filewill copy setup.exe and setup.lst from the Support folder to the Packagefolder and will generate the cab file(s) in the Package folder. However,once the batch file is finished, setup.lst will not know how many .cabfiles were generated. Unless this problem is remedied, the setup programwill fail.
To remedy this situation, do the following:Before running the batch file, delete all .cab files in the Packagefolder.After running the batch file, count the number of cabs produced by thebatch operation.Open the Setup.lst file in the Package folder with a text editor. NOTE: There are two Setup.lst files. One is found in the Support folder. Thesecond is found outside the Support folder, in the Package folder wherethe .cab files are created. Be sure to open the Setup.lst file in thePackage folder.In the text editor, look for the following lines, which are at the topof the file):

[Bootstrap]SetupTitle=InstallSetupText=Copying Files, please stand by.CabFile=Projec1.CABSpawn=Setup1.exeUninstal=st6unst.exeTmpDir=msftqws.pdw After the last line (TmpDir=msftqws.pdw), insert the following linewhere N equals the number of cabs generated:

Cabs=N The Setup.lst should now be up to date, and the setup won’t fail.
Package And Deployment Wizard: Error 80042114If you are creating a package for Internet deployment and you get thefollowing error:

“Unexpected error 80042114 has occurred: The Web server you selecteddoes not indicate support for the service provider you selected. Do youwant to proceed anyway?”This error occurs because you have specified that your package should beposted to an FTP site using an HTTP URL. If you are certain that you haveaccess privileges to the web server, you can click “Yes” and the deploymentwill proceed.
To avoid this error in the future, when creating a package for deploymenton the same server, specify the site and its protocol. When you do so, thefollowing dialog box will appear:
“The specified URL and publishing method can be saved in the registry asa Web publishing site. This ensures that the URL and publishing methodare valid and saves you time in future deployments to this site. Do youwant to store this information as a Web publishing site?”
If you select “yes,” this saves the site information and you will no longerreceive the 80042114 error.
Package and Deployment Wizard: Use Mdac_typ.Cab and Mdac20.Cab toDistribute Data Access ComponentsWhen your Internet Package includes any of the following four files, thewizard will by default set these files to be downloaded from:
http://activex.microsoft.com/controls/vb6/mdac_typ.cab(http://activex.microsoft.com/controls/vb6/mdac_typ.cab)
MSDAOSP.dll
MSADO15.dll
MSADCF.dll
ODBC32.dll
Similarly, the wizard will, by default, set the following files to bedownloaded from:
http://activex.microsoft.com/controls/vb6/mdac20.cab(http://activex.microsoft.com/controls/vb6/mdac20.cab)
MSADOR15.dll
MSADCO.dll
In both cases, these defaults are indicated as the “Download from MicrosoftWeb site” option on the File Source screen. These cab files (mdac_typ.caband mdac20.cab) perform special handling that should not be attemptedmanually. In order to ensure that the proper handling takes place, yourInternet cab should not include these files but rather should reference thecabs. Therefore, you should never choose the “Include in this cab” optionfor any of these files. In addition, if you choose the “Download fromalternate Web site” option, you should be careful to specify cabs that arecopies of these cabs to ensure that the proper handling takes place.
Do not change the default settings for these files.
Package and Deployment Wizard: Manually Include .ASP and .HTM FilesFor IIS Applications When Using Standard SetupIf you use the Package and Deployment Wizard’s standard setup to deploy anIIS application, you must manually include any .asp or .htm files with thepackage. Add the files using the Include Files dialog box.
Package and Deployment Wizard: Bad Date and Time FormatsIn certain situations, the Package and Deployment Wizard will incorrectlywrite time and date information to the Setup.lst file. When this occurs,the setup will fail because the dates will be written in a form that thesetup.exe can’t read. The problem occurs when you create a deploymentpackage using the US version of Visual Basic on:A computer using the German version of Windows (NOTE: the German versionof Visual Basic will work correctly.)Any computer where the date separator isn’t either a forward slash (“/”)or a dash (“-”).To fix the bad formats:From the Start menu, open Control Panel.Click the Regional Settings icon.On the Date tab, change the Date separator to “/”.On the Time tab, change the Time separator to “:”.Run the Package and Deployment Wizard.Restore the date and time settings.
Package and Deployment Wizard: Unable to Run Setup.exe onFirst Windows 95 VersionAny setup package built with the wizard will not launch on certaininstallations of Windows 95 due to lack of support for an API in theoriginal version of the Oleaut32.dll. This failure will not occur on OSrelease 2 of Windows 95 or any versions of Windows NT 4.0 and later, andwill not occur if Microsoft Office 97 or Internet Explorer 3.0 or 4.0 hasbeen installed. Any installation of a Visual Basic 5.0 application willalso remedy the situation. You can also work around this failure by firstoverwriting the older version of Oleaut32.dll with the latest version. Besure to shut down all applications before attempting to manually updateOleaut32.dll.
Package and Deployment Wizard: Packaging ActiveX DocumentsThe Visual Basic 6.0 Package and Deployment Wizard can insert CODEBASE= andVERSION= information directly embedded into the .vbd file for your ActiveXDocument project. This eliminates the need for having the extra .htm filepreviously used to launch ActiveX Documents. The embedded informationallows Internet Explorer to read the .cab file name for your ActiveXDocument code and version information from the .vbd file and carry out theinstallation. You can now navigate directly to the .VBD file and your Userdocument code will download if necessary.
The same functionality was available for Visual Basic 5.0 setup using theSetCodeBase utility found on the Visual Basic Owners Area.
The following are some issues with Visual Basic 6.0 Package and DeploymentWizard generated setups for User documents:Internet Explorer 3.x. 4.0, and 4.01 cannot read the embeddedinformation in the VBD file. The wizard also generates an old (VB5)style .htm file. This .htm file can be used to launch ActiveX Documents.You must first modify the .htm file, however, since most of the code iscommented out. After removing the comments and an extra <A> tag (<ahref=xxxx.VBD>xxxxx.VBD</a>) from the top,from the top, the file will only be anOBJECT tag with the CLSID of your User document and some script code forWindow_OnLoad event.Internet Explorer 4.01 with Service Pack 1 and later will read thisinformation correctly from the .vbd file.

Symptoms
The Microsoft Data Object Libraries may be referenced in your Visual Basic project. When the Package and Deployment Wizard (PDW) is used to build the installation, the PDW scans the project files and determines which dependency files need to be distributed.
This article provides the general information you need to distribute any of the following Data Object Libraries with your Visual Basic project: Microsoft Data Access Objects (DAO) 3.51 Object LibraryMicrosoft Data Access Objects (DAO) 3.6 Object LibraryMicrosoft Remote Data Object (RDO) 2.0Microsoft ActiveX Data Objects (ADO) 2.0, 2.1, 2.5, or 2.6 Library
Resolution
The files are listed in the Setup’s file that is created by the PDW for distribution.
For additional information on how each section in the Setup.lst file is used, click the following article number to view the article in the Microsoft Knowledge Base:
189743?(http://support.microsoft.com/kb/189743/) Description of Setup.lst sections The following sections describe points to be aware of when you distribute any of the Data Object Libraries.
Microsoft Data Access Objects (DAO) 3.51 Object LibraryIntrinsic data control incompatibility with Microsoft Access 2000 (Jet 4.0) If you use the intrinsic data control in your project and you attempt to connect to a Microsoft Access 2000 database, you may receive the following error message:

Unrecognized Database Format This error message occurs because the DAO generic data control is based on Jet 3.51 and does not recognize Jet 4.0 database formats. Access 2000 is a Jet 4.0 format database. Prior to Microsoft Visual Studio 6.0 Service Pack 4 (SP4), the workaround for this problem was to open a recordset with DAO code, and then assign it to the recordset property of a data control. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
238401?(http://support.microsoft.com/kb/238401/) PRB: Unrecognized database format error message when upgrading to Access 2000 This problem does not exist with the data control that ships with Microsoft Visual Studio 6.0 Service Pack 6.
Visual Studio 6.0 Service Pack 6 can be obtained at the Visual Studio 6.0 Service Pack Web site:
http://msdn2.microsoft.com/en-us/vstudio/aa718364.aspx(http://msdn2.microsoft.com/en-us/vstudio/aa718364.aspx)Jet 3.51 OLE DB Provider is not included in MDAC 2.1 or later The Jet OLE DB Provider requires the version number of the provider in order to connect to an Access database. If your application specifies Version 3.51 of the Jet OLE DB provider in a connection string or a UDL, and you install ADO by redistributing MDAC 2.1, you are likely to receive the following error message:

3706: ADO could not find the specified provider This error message occurs because MDAC 2.0 installs version 3.51 of the Jet OLE DB provider while MDAC 2.1 installs version 4.0 of the Jet OLE DB Provider, but does not install version 3.51. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
197902?(http://support.microsoft.com/kb/197902/) PRB: Jet 3.51 OLE DB Provider is not installed with MDAC 2.1 or later
Microsoft Data Access Objects (DAO) 3.6 Object Library DAO version 3.6 is required for applications that use DAO to read and write to Access 2000 databases. If Access 2000 (or DAO 3.6) is already installed on the destination computer, then no additional steps are required. If it is not, it is necessary to distribute DAO 3.6. However, there is currently no redistributable for DAO 3.6. In order to redistribute DAO 3.6, it is necessary to install DCOM, redistribute MDAC 2.1(GA) or later, and ensure that the DAO DLL is also distributed and registered on the destination computer.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
233002?(http://support.microsoft.com/kb/233002/) How to redistribute DAO 3.6
Microsoft Remote Data Object (RDO) 2.0 In order for RDO to be properly distributed and installed, ODBC must already be installed on the destination computer. ODBC can be installed through the odbcst32.exe file, which is located in the ODBC Folder under the SQL/i386 directory on Visual Basic 6.0 Disk 2. ODBC can also be installed by including the MDAC redistributable in the distribution that is outlined in the “References” section covering distributing ADO/MDAC. To determine all of the files needed to distribute for RDO to work successfully on a computer that does not have Visual Basic installed, you can generate a dependency (.dep) file with the Package and Deployment Wizard. To generate a dependency file that shows the files needed for RDO when running the PDW, complete the following steps: Create a Standard EXE project in Visual Basic. Form1 is created by default.Add a reference to Microsoft Remote Data Object 2.0.Save this project and run the Package and Deployment Wizard on it.Select the Package option.On the Package Type, choose Dependency File, and then proceed through the wizard to completion. When you are finished, you have a file with a .dep extension that can be opened with Microsoft Notepad. MSRDO20.dll and its dependencies are shown in this file.
You want to ensure that these files are included with the distribution. If these files are not listed on the Included Files dialog box when you run the Package and Deployment Wizard, include them by clicking Add in the dialog box.
Microsoft ActiveX Data Objects (ADO) 2.0, 2.1 or 2.5 Library The PDW does not distribute mdac_typ unless there is a specific reference to an ADO Library (any version) in the project.
You can also add mdac_typ.exe manually by clicking Add in the Included Files dialog box when you run the Package and Deployment Wizard. The wizard uses the MDAC_Typ.exe file in the …\Wizards\PDWizard\Redist folder. Obtain the MDAC Components at the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/data/aa937695.aspx(http://msdn2.microsoft.com/en-us/data/aa937695.aspx) For additional information how the PDW distributes MDAC, click the following article number to view the article in the Microsoft Knowledge Base:
217754?(http://support.microsoft.com/kb/217754/) How to control which MDAC version the Package and Deployment Wizard (PDW) distributes The installation of Microsoft Data Access Components (MDAC) requires that DCOM be already installed on the destination computer: For Windows 95 computers, install DCOM95.For Windows 98 computers, install DCOM98.Download the latest version of DCOM from the following Microsoft Web page:
http://www.microsoft.com/downloads/details.aspx?familyid=08B1AC1B-7A11-43E8-B59D-0867F9BDDA66&displaylang=en(http://www.microsoft.com/downloads/details.aspx?familyid=08B1AC1B-7A11-43E8-B59D-0867F9BDDA66&displaylang=en) If DCOM is not already installed on the destination computer, you may receive one of the following error messages:

Unable to load file ‘msdadc.dll’ to register it
-or-

DLL registration failed For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191704?(http://support.microsoft.com/kb/191704/) PRB: Unable to load file to register it during setup

Symptoms
The Visual Basic Package and Deployment Wizard (PDW) uses a technologynamed the Posting Acceptor to manage the transfer of your Visual Basicapplications to a Web server. Posting Acceptor is a component that is located on the Microsoft Internet Information Server (IIS) Web server. You can use Posting Acceptor to post the content to the server.Before you can successfully post your applications, you must installPosting Acceptor and configure the Web server correctly.
This article walks you through the basic configuration and presentstroubleshooting information for some of the more common problems that you may experience when you post Visual Basic applications to the Web.
Resolution
Steps in the Web Deployment ProcessWhen you post a Visual Basic application to a Web server by using the Package and Deployment Wizard, you first use the packaging portion of the wizard to package your applications into one or more .cab files. Then, you use the deployment portion of the wizard to transfer your files to the appropriate location.
IMPORTANT: Make sure that you have administrator-level rights to the Web server to which you are posting content.
The Web server goes through these steps during deployment:It extracts the .cab file into a temporary directory.It locates the .inf file for the .cab file.Based on the contents of the .inf file, it installs application files (based on the RInstallApplicationFiles section of the .inf file), system files (based on the RIinstallSystemFiles section), and shared files (based on the RInstallSharedFiles section). In the process, the server registers any necessary files.NOTE: The DefaultInstall section of the .inf file is not run because the instructions it contains often require user input. Additionally, the posting process does not create a virtual directory for your application if one is required; directories must be set up in advance.
Installing Posting AcceptorYou must install Posting Acceptor on any server to which you want to postapplications by using the Visual Basic Package and Deployment Wizard. There are multiple versions of Posting Acceptor. You must make sure you install the correct version based on your server’s configuration:Posting Acceptor 2.0 Windows NT 4.0 with Service Pack 3 (SP3)IIS 4.0 Posting Acceptor 2.0 supports both content posting and the unpacking of cabinet (.cab) files on the server.Posting Acceptor 1.1 Windows NT 4.0 with SP3 IIS 3.0 You cannot unpack .cab files with this version of Posting Acceptor. Use this version to post content only. You can move your files to the server and then manually register any necessary files that the .cab process would have registered.NOTE: Posting Acceptor does not work on any platforms that are usingPersonal Web Server or Peer Web Server. You must use IIS.
Posting Acceptor is no longer available as a separate download. To obtain Posting Acceptor, you can install the Microsoft Windows NT 4.0 Option Pack, which is available from the following Microsoft Web site:
Windows NT 4.0 Option Pack
http://technet.microsoft.com/en-us/library/cc767904.aspx(http://technet.microsoft.com/en-us/library/cc767904.aspx)Installing Posting Acceptor 2.0Start Microsoft Visual Studio or Visual Basic setup from your installation CDs.When you are prompted to choose options to install, click Install Server Applications and Tools, and then click Next.Click Launch the BackOffice Installation Wizard, and then click Install.Click Custom, and then click Next.You will see the options to install and their sizes. Click Next.Click Microsoft Posting Acceptor 2.0.NOTE: If you want to install Posting Acceptor 2.0 on a computer thatalready has the Windows NT Option Pack, you should first check to see ifversion 1.0 of the Posting Acceptor is already installed. If so, remove this version before you install version 2.0.Determine If Posting Acceptor 1.0 Is InstalledIn Control Panel, click Add/Remove Programs.In the Install\Uninstall pane, click NT Option Pack.Click Add/Remove, and then look for Posting Acceptor 1.0 in the component list. You may find Posting Acceptor 1.0 under Microsoft Site Server. If Posting Acceptor 1.0 is installed, remove it.
Configuring the ServerYou must perform the following steps on the Web server to which you want todeploy your packaged Visual Basic applications. To configure your IIS server, follow these steps:Install Microsoft Internet Information Server (IIS) from the NT Option Pack.Follow the steps in the previous procedure to install Posting Acceptor 2.0.Click Start, point to Programs, point to Windows NT 4.0 Options Pack, point to Microsoft Internet Information Server, and then click Internet Service Manager.In the left panel of the manager, make sure that the Console Root node is expanded, and then expand the Internet Information Server node. Your IIS server or servers are listed under this folder.Expand the IIS server that you want to configure. You will see a number of nodes, including a node named Default Web Site.Right-click the Default Web Site node, and then click Properties.In the Default Web Site Properties dialog box, click the Home Directory tab, and then make sure that the Write option is selected.Click Apply. The Inheritance Overrides dialog box may appear, which contains a list of folders to which the setting you just made should apply. Select only those folders to which you want users to be able to deploy packages, and then click OK until you return to the manager.NOTE: Granting write access to a virtual directory is a security RISK. Make sure that you only grant write access to virtual directories that you know are secure.In the left panel, right-click the SCRIPTS node that appears under the Default Web Site node, and then click Properties.Click the Virtual Directory tab, make sure that the Execute (including script) button is selected, and then click OK.
Configuring the Client ComputerVisual Studio installs and configures all the components that you need to deploy applications from your development computer. However, if you are running Visual Studio on a computer that is on an intranet and you connect through a proxy server, you must configure Microsoft Internet Explorer 4.0 to bypass the proxy server for local addresses.
To configure your development computer, follow these steps:On your Windows desktop, right-click the Internet Explorer icon, and then click Properties.In the Properties dialog box, click the Connection tab.In the Proxy Server area, make sure that the Bypass proxy server for local (Intranet) addresses check box is selected if the Access the Internet using a proxyserver check box is selected. Click OK.
Troubleshooting Web Deployment from Visual BasicThe following sections list some of the more common problems that you mayencounter when you try to post applications to the server by using the Package and Deployment Wizard.General TipsYou should have administrator-level rights to the Web server to which you are posting content.If you receive an error that files are busy during the posting process, you should reboot your server rather than just stopping and restarting the service. After you reboot, you can try to post again. In general, it is a good idea to reboot the server as part of your troubleshooting process.Problem: Your Server Does Not Have Visual Basic InstalledIf your Web server does not have a copy of the Visual Basic 6.0 runtimeDLL installed and other system files such as:Msvbvm60.dllOleaut32.dllOlepro32.dllAsycfilt.dllStdole2.tlbComcat.dllMswcrun.dll is needed for IIS Applications (WebClass Designer runtime)Mshtmpgr.dll is needed for DHTML Applications (DHTML Page Designer run-time)You may encounter problems when you try to post an application toit the first time. In this case, the server may not be able to correctly install the necessary system files.
There are several things that you can do about this:
Install a copy of Visual Basic on the server, and then use the wizard to post your application again.Create a standard setup package with the Package and Deployment Wizard instead of an Internet package. You can then move the Setup.exe file to the server and install the program on the server. This installs the necessary system files. After the installation process, reboot your server.You can download the .cab files for the above-needed system files from the Microsoft site. You must install and register these files on the server. You may need to reboot the server after this process.NOTE: This procedure only applies to the first installation of a Visual Basic application on such a server; all subsequent installations can be posted with the Web deployment feature of the wizard.Problem: Cab File Is Copied to Web Server But Is Not UnpackedIf the .cab file that you are deploying is copied to the server but is notunpacked, make sure that:You included the .cab file on the Items to Deploy page of the wizard.You used HTTP Post as the protocol on the Web Publishing Site page of the wizard.You selected the Unpack and Install Server-Side Cab check box on the Web Publishing Site page of the wizard. If you did not, try to redeploy your package with this option selected.NOTE: Only Posting Acceptor 2.0 running on IIS 4.0 supports .cab file unpacking. If you are running Posting Acceptor 1.0, you cannot unpack the file during deployment.Problem: Web Server Does Not Support the Selected Service ProviderThere are several things you can do to try to fix this problem:If you are using the HTTP Post protocol, make sure that Posting Acceptor is installed on your Web server.Make sure that your URL is correct. If you are using HTTP Post, make sure that your URL begins with http://. If you are using FTP, make sure that your URL begins with ftp://.If you are uploading to a server that has Posting Acceptor 1.0 installed, you cannot select the option to unpack and install your cabinet files when you use the wizard to deploy your package. In this case, deploy your .cab file again, and make sure that you click to clear the Unpack and Install Server-Side Cab check box.Problem: Need Write Access to the Web ServerIf you use the HTTP Post protocol and receive an error that you do not havewrite access for the Web server, you must change the access permissions foryour Web server.
To set Write access, follow these steps:On the server computer, click Start, point to Programs, point to Windows NT 4.0 Options Pack, point to Microsoft Internet Information Server, and then click Internet Service Manager.Expand the Console Root and the Internet Information Server nodes, and then expand the node for your Web server computer.Right-click the Default Web Site node, and then click Properties.Click the Home Directory tab, and then click to select the Write check box.NOTE: Granting write access to a virtual directory is a security risk. Make sure that you only grant write access to the virtual directories that you know are secure.Problem: Error c0042116, or Processing Has StoppedIf your files are read-only when you try to post, you receive an errorC0042116, which states that processing has stopped. Use File Explorer tochange your file attributes, and then continue with your posting process.Problem: FTP Protocol ProblemsWith the Package and Deployment Wizard, you can post content by using the HTTP or the FTP protocol. If you use FTP, you may encounter thefollowing issues:
If you receive an error that access is denied, follow these steps:On the server computer, click Start, point to Programs, point to Windows NT 4.0 Options Pack, point to Microsoft Internet Information Server, and then click Internet Service Manager.Expand the Console Root and the Internet Information Server nodes, and then expand the node for your Web server computer.Right-click the Default Web Site node, and then click Properties.Click the Home Directory tab, and then click to select the Write check box.NOTE: Granting write access to a virtual directory is a security risk. Make sure that you only grant write access to the virtual directories that you know are secure.
If you use the FTP protocol and receive additional errors besides the one that is described in the previous bullet, make sure that you have properly configured your FTP service on the Web server. To do so, start the Microsoft Management Console (MMC), and then follow these steps:Right-click Default FTP Site, and then click New Virtual Directory.Type an alias to be used to access the virtual directory, and then click Next.Type the physical path of the directory to which to map the virtual directory. For example, C:\Inetpub\Ftproot, and then click Next.Select the appropriate access permissions, making sure to grant writeaccess so that your deployments can proceed without errors, and thenclick Finish.Right-click Default FTP Site, and then click Stop.Right-click Default FTP Site and then click Start.When you deploy to the FTP server by using the Package and Deployment Wizard, use the site FTP://servername/alias format, where alias is the alias that you assigned in step 2. Use the username “anonymous” and the password “me@somewhere” for anonymous login.Problem: Incorrect ParameterIf you receive an error that states that a parameter is incorrect, you may need to take one of the following actions:Make sure that you have typed a valid URL to the Web server that you have chosen to use.On the Web server, search for files named Default.asp and Default.htm in the \Inetpub\wwwroot directory. Open both files, and make sure that they have the following code at the top of the file:

<META name=”postinfo” content=”/scripts/postinfo.asp”>

Symptoms
When you run a Setup that was created using the Package and Deployment Wizard (PDW), you receive one of the following error messages:

Cannot start main setup program! (CreateProcess() returned error code 0×000000C1H)

VB6stkit.dll is not a valid Windows NT image

The system could not locate the file ‘<Temp Folder>\Msftqws.pdw\Vb6stkit.dll’. Would you like to browse for the file yourself?

The system could not locate the file ‘<Temp Folder>\Windows\Temp\Msftqws.pdw\St6unst.exe’. Would you like to browse for the file yourself? where <Temp Folder> is the Windows\Temp folder on Windows 95, Windows 98, or Windows Me or the folder specified by the TEMP environment variable on Windows NT.
Resolution
If the symptom occurs on all target computers where you run Setup, the cause of the problem is most likely one of the following: A damaged diskette.A damaged setup file. If the symptom only occurs on some target computers, the cause may be one of the following: Left-over files from a previous installation attempt.A machine-specific issue.

Symptoms
When you use a package that you created with the Package and Deployment Wizard (PDW) to install a Visual Basic application, you may receive the following error message (or similar) during the installation:

Unable to register MSADO15.TLBThis error message may reference any of the following files:MSADO15.TLBMSADO20.TLBMSADO21.TLBMSADO25.TLB
Resolution
The Package and Deployment Wizard adds the type library (.tlb) file to the package because the type library is referenced in your project. The PDW also erroneously assigns the $(DLLSelfRegister) registration macro to the type library in the Setup.lst file that is created for your installation package.
Most commonly, this problem occurs when your Visual Basic project contains a reference to a version of ActiveX Data Objects (ADO) that is earlier than the latest installed version. The reference for the latest installed version of ADO points to MSADO15.DLL. Earlier version references point to the above-mentioned ADO type library files.