INFO: VB6 Readme: Part 6 Wizard Issues

Package and Deployment Wizard (PDW): Automatically Picks Up Files From Redist Directory

1. You have created an application that is ready for packaging.
2. The application depends on a certain system file "MySysFile.dll" which, until recently, has been a stand-alone file. But now a recent system update has made that file dependent on other files to function properly.
3. However, a stand-alone version of the system file is also supplied.
4. To simplify setups, you place that stand-alone version into the Redist folder.
5. When creating your deployment package, you navigate to the system file to instruct the wizard that the system file should be included.
6. Instead of picking up the system file (which is dependent on other files), the Package and Deployment Wizard will pick up the stand-alone version that is in the Redist directory.
   
   By default, no files are placed in the redist folder.

Back to the top

Package and Deployment Wizard Has [Do Not Redist] Section

1. Files that are not needed at run-time. For example, ActiveX designers often 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 the section and is not included in the package.
2. Files that cannot be redistributed by the Package and Deployment Wizard. Some dependent files are not installed by Visual Basic, but must be installed by another component. For example, the following files are installed by Internet Explorer 4.x: Shdocvw.dll and Mshtml.dll.

Back to the top

Package and Deployment Wizard: In Silent Mode the Notification Window May Not Be First in the Window Z-order

Back to the top

Package and Deployment Wizard: Command Line Mode Argument Added for Specifying Executable Path

Argument       Description

/e path        Use the argument to set the path for the project's
               executable file if it is different from the project's
               path.
				

Back to the top

Package and Deployment Wizard: Manually Add User Control License Files

Back to the top

Package and Deployment Wizard: Steps in the Web Deployment Process

1. It extracts the .cab file into a temporary directory.
2. It locates the .inf file for the .cab file.
3. Based on the contents of the .inf file, the WebPost process installs application files (based on the RInstallApplicationFiles section of the .inf file), installs system files (based on the RiinstallSystemFiles section), and installs shared files (based on the RInstallSharedFiles section). In the process, it registers any necessary files.

Back to the top

Package and Deployment Wizard: Web Deployment Tips for HTTP or FTP Protocol

• If the .cab file you are attempting to deploy to a Web server is copied to the server but is not unpacked, make sure you included the .cab file on the Items to Deploy screen, and that you used HTTP Post as the protocol on the Web Publishing Site screen. In addition, you must have checked the Unpack and Install Server-Side Cab check box on the Web Publishing Site screen. If you did not, try re-deploying your package again with this option selected.
  
  NOTE: Cab unpacking is supported by Posting Acceptor 2.0 running on IIS 4.0. If you receive an error saying that the Web server you selected does not support the service provider you selected, there 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. If you are running IIS 4.0, install Posting Acceptor 2.0. If you are running IIS 3.0, install Posting Acceptor 1.0. Cab unpacking is not supported by Posting 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 Posting Acceptor 1.0 installed, you cannot select the option to unpack and install your cabinet files when you deploy your package using the wizard. If you receive an error C0042115 that the query string INSTALL is invalid, check your server configuration to determine what version of posting acceptor is installed. If it is version 1.x, deploy your cab again, making sure to deselect the Unpack and Install Server-Side Cab option.
  • If you need to use the FTP protocol to post to a URL beginning with "http://", you may be able to resolve this error by adding the following 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 programs created with the Package and Deployment Wizard install the Microsoft Data Access Components (MDAC), which includes OLE DB, ADO and Jet, via the MDAC installer program: Mdac_typ.exe. This EXE requires that the 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 restore functionality of existing data components, install DCOM95 and run the installer again.
• If you use the HTTP Post protocol and receive an error that you do not have write access for the Web server, open the Internet Service Manager on the server computer, access the node for your Default Web Site (Console Root \ Internet Information Server \ machinename \ Default Web Site), choose Properties, select the Home Directory tab, and check the Write check box.
• If your files are read-only when you try to post, you will receive an error C0042116 announcing that processing has stopped. Change your file attributes to proceed.
• Be aware that if you post a file to a directory where the same file already exists, the file on the server will be overwritten and no warning 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 the node for your Default FTP Site (Console Root \ Internet Information Server \ machinename \ Default FTP Site), choose Properties, select the Home Directory tab, and check the Write check box.
• If you use the FTP protocol and receive additional errors besides the one 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), then follow these steps:

1. Right-click on Default FTP Site and choose New Virtual Directory.
2. Enter an alias to be used to access the virtual directory, then click Next.
3. Enter the physical path of the directory to which to map the virtual directory (for example, c:\inetpub\ftproot) then click Next.
4. Select the appropriate access permissions, making sure to allow write access so that your deployments can proceed without errors, then click Finish.
5. Right-click on Default FTP Site and choose Stop.
6. Right-click on Default FTP Site and choose Start.
   
   When you deploy to the FTP server using the Package and Deployment Wizard, use the site FTP://servername/alias where alias is the alias you assigned in step 2. Use the username "anonymous" and the password "me@somewhere" for anonymous login.

Back to the top

Package and Deployment Wizard: Start Menu Items: Run Option Not Supported

Back to the top

System Configurations for WebPost's Posting Acceptor

• The Package and Deployment Wizard, which sends your content to a qualified site.
• A Posting Acceptor, located on the Web server, that enables the posting of content to an IIS server.

Use this                  if you are running        Comments
--------------------------------------------------------------------------
Posting Acceptor 2.0     Windows NT 4.0 with SP3   Posting Acceptor 2.0
IIS 4.0                                            supports both content

                                                   posting and the
                                                   unpacking of cabinet
                                                   (.cab) files on the
                                                   server.

Posting Acceptor         1.0 Windows NT 4.0        You cannot unpack .cab
                         with SP3                  with this version
                         IIS 3.0                   files of posting
                                                   acceptor. Use this for
                                                   content posting only.
                                                   You can move your
                                                   files to the server
                                                   and then manually
                                                   register any necessary
                                                   files that would have
                                                   been registered by the
                                                   .cab process.
				

1. Launch Visual Studio or Visual Basic setup from your installation CDs.
2. When prompted to choose options to install, click Install Server Applications and Tools, then click Next.
3. Click Launch the BackOffice Installation Wizard, then click Install.
4. Now select the radio button for Custom, then click Next. You will see the options to install and their sizes. Click Next.
5. Select Microsoft Posting Acceptor 2.0.

Back to the top

Package and Deployment Wizard: Edit Setup.lst File If You Rebuild Cabs From Batch File

1. Before running the batch file, delete all .cab files in the Package folder.
2. After running the batch file, count the number of cabs produced by the batch operation.
3. 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. The second is found outside the Support folder, in the Package folder where the .cab files are created. Be sure to open the Setup.lst file in the Package folder.
4. In the text editor, look for the following lines, which are at the top of the file):

      [Bootstrap]
      SetupTitle=Install
      SetupText=Copying Files, please stand by.
      CabFile=Projec1.CAB
      Spawn=Setup1.exe
      Uninstal=st6unst.exe
      TmpDir=msftqws.pdw
   					

5. After the last line (TmpDir=msftqws.pdw), insert the following line where N equals the number of cabs generated:

   Cabs=N
   					

   The Setup.lst should now be up to date, and the setup won't fail.

Back to the top

Package And Deployment Wizard: Error 80042114

Back to the top

Package and Deployment Wizard: Use Mdac_typ.Cab and Mdac20.Cab to Distribute Data Access Components

Back to the top

Package and Deployment Wizard: Manually Include .ASP and .HTM Files For IIS Applications When Using Standard Setup

Back to the top

Package and Deployment Wizard: Bad Date and Time Formats

• A computer using the German version of Windows (NOTE: the German version of Visual Basic will work correctly.)
• Any computer where the date separator isn't either a forward slash ("/") or a dash ("-").

1. From the Start menu, open Control Panel.
2. Click the Regional Settings icon.
3. On the Date tab, change the Date separator to "/".
4. On the Time tab, change the Time separator to ":".
5. Run the Package and Deployment Wizard.
6. Restore the date and time settings.

Back to the top

Package and Deployment Wizard: Unable to Run Setup.exe on First Windows 95 Version

Back to the top

Package and Deployment Wizard: Packaging ActiveX Documents

• Internet Explorer 3.x. 4.0, and 4.01 cannot read the embedded information 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 is commented out. After removing the comments and an extra <A> tag (<a href=xxxx.VBD>xxxxx.VBD</a>) from the top, from the top, the file will only be an OBJECT tag with the CLSID of your User document and some script code for Window_OnLoad event.
• Internet Explorer 4.01 with Service Pack 1 and later will read this information correctly from the .vbd file.

Back to the top