Microsoft KB Archive/194296

{|
 * width="100%"|

HOWTO: Debug PDW Internet Deployment Issues

 * }

ID: Q194296

-

The information in this article applies to:


 * Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 6.0

-

SUMMARY
The Visual Basic Package and Deployment Wizard (PDW) deploys Visual Basic Internet applications to a Web server. This article contains a few steps to help you debug problems when deploying your Visual Basic Internet Applications to a Web Server.

Deploy Your Visual Basic Internet Application to a Web Server
 Make sure you are an Administrator on the Web server machine you are deploying to and the client machine you are deploying from. Try deploying to the server using the FTP "Web Publishing Protocol." NOTE: If this does not work, refer to the Knowledge Base article Q192639 (HOWTO: Use PDW to Deploy Using the FTP Web Publishing Method). You do not need Posting Acceptor installed on the server for this to work. Make sure this works before going onto the next step.

NOTE: Without setting FTP write permissions, deployment will not work.

Following are steps to create a new FTP virtual directory and allow write access:

  From the Start menu, open the Internet Service Manager on the server computer. This starts up Microsoft Management Console (MMC). To start the MMC do:

            Start menu Select Programs Windows NT 4.0 Options Pack Microsoft Internet Information Server Internet Service Manager.  Click Console Root, click Internet Information Server, then click the name of your Web server machine. Start up Microsoft Management Console (MMC). Right-click on "Default FTP Site," choose "New," and then choose "Virtual Directory" from its context menu. Type in an alias to be used to access the virtual directory (for example, ftpupload). Enter the physical path of the directory to map the virtual drive (for example, c:\inetpub\ftproot).</li> Select the checkbox "Allow write access."</li> Right-click on Default FTP Site and choose "Stop."</li> Right-click on Default FTP Site and choose "Start."</li></ol> </li> Once FTP works, try deploying to the server using the HTTP POST "Web Publishing Protocol." If this does not work, refer to Knowledge Base articles Q192116 (HOWTO: Configure Posting Acceptor To Work With the PDW) and Q190046 (INFO: VB6 Readme: Part 6 - Wizard Issues).

NOTE: You need Posting Acceptor installed on the server for this to work.

IMPORTANT: Do not have the check box "Unpack and install server-side cab" selected.

Use the following steps to install Posting Acceptor 2.0:

<ol style="list-style-type: lower-alpha;"> Launch Visual Studio 6.0 or Visual Basic 6.0 Enterprise edition setup from your installation CDs.</li> When prompted to choose options to install, click Install Server Applications and Tools, and then click Next.</li> Click Launch the BackOffice Installation Wizard, and then click Install.</li> Now select the button for Custom, and then click Next.</li> You will see the options to install and their sizes. Click Next.</li> Select Microsoft Posting Acceptor 2.0.</li></ol>

If you want to install Posting Acceptor 2.0 on a computer that already has the Windows NT Option Pack, you should first check to see if Posting Acceptor is already installed. If so, remove it before installing Posting Acceptor version 2.0 from the Visual Studio Enterprise edition CD.

NOTE: Make sure the Posting Acceptor (PA) is installed from the Visual Studio 6.0 or Visual Basic 6.0 Enterprise Edition CDs, not from the NT 4.0 option pack. The NT 4.0 Option Pack will not set the registry settings correctly on the SERVER.

Without setting Web write permissions, deployment will not work.

Following are the steps to create a new Web virtual directory and allow write access:

<ol style="list-style-type: lower-alpha;">  From the Start menu, open the Internet Service Manager on the server computer. This starts up Microsoft Management Console (MMC). To start the MMC do:

<pre class="FIXEDTEXT">            Start menu Select Programs Windows NT 4.0 Options Pack Microsoft Internet Information Server Internet Service Manager </li> Click Console Root, click Internet Information Server, then click the name of your Web server machine.</li> Start up Microsoft Management Console (MMC).</li> Right-click on "Default Web Site," choose "New," and then choose "Virtual Directory" from its context menu.</li> Type in an alias to be used to access the virtual directory (for example, wwwupload).</li> <li>Enter the physical path of the directory to map the virtual drive (for example, c:\inetpub\wwwroot).</li> <li>Select the checkbox "Allow write access."</li> <li>Right-click on Default Web Site and choose "Stop."</li> <li>Right-click on Default Web Site and choose "Start."</li></ol> </li> <li>Once HTTP POST works without the check box "Unpack and install server- side cab" selected, try deploying to the server using the HTTP POST with the check box "Unpack and install server-side cab" selected.

IMPORTANT: The PDW will not reboot the server machine you are deploying to. Once you have deployed to a Web server machine you will need to reboot it manually.</li></ol>

Using PDW Standard Setup Package Instead of a PDW Internet Package
The first time you are deploying a Visual Basic Internet application to a Web server, it's recommended that you create a PDW Standard Setup Package instead of a PDW Internet Package for your application. This is because your Visual Basic Internet application requires the Visual Basic 6.0 run- time and some system files on the server be updated, and the standard setup will ensure that these files are present on the server. Reboot the server and try the deployment again.

<pre class="FIXEDTEXT">mswcrun.dll    WebClass run-time version 6.00.8169 msvbvm60.dll   Visual Basic Run-time version 6.00.8176 oleaut32.dll   version 2.30.4261 olepro32.dll   version 5.0.4261 asycfilt.dll   version 2.30.4261 comcat.dll     version 4.71

Errors You Could Encounter During Deployment Process
<ol> <li> Unexpected error number C0042116 has occurred: The server returned the following message:

<pre class="FIXEDTEXT">      200 Type set to I.       200 PORT command successful. 550 WP.CAB:Access is denied. SUGGESTION: Allow write access to the FTP Server Site as described above. </li> <li>Unexpected error number C0042116 has occurred: The Web server returned the following error: The signature on cabinet file xxxx.CAB could not be verified.

SUGGESTION: Reinstall PA 2.0 on the server as described in Knowledge Base article Q192116.</li> <li>Unexpected error number C0042116 has occurred: The Web server returned the following error: The query string "INSTALL" is invalid..

SUGGESTION: If you selected the checkbox "Unpack and install server-side cab" and are uploading to PA 1.0, this error will be displayed.</li> <li>Unexpected error number C0042116 has occurred: The Web server returned the following error: You do not have write access to the destination URL "http://...."

SUGGESTION: Allow write access to the Web Server Site as described above or, if the files you are trying to deploy from the CLIENT machine are read-only, use the File Explorer to change these file attributes on the CLIENT machine to write, then continue with your posting process.</li> <li>Unexpected error C0042116 has occurred: The Web server returned the following error: Cannot move file "Systray.HTM" to its final destination. Further processing is stopped.

RESOLUTION: Allow write access to the Web Server Site as described above or, if the files you are trying to deploy from the CLIENT machine are read-only, use the File Explorer to change these file attributes on the CLIENT machine to write, then continue with your posting process.</li> <li>Unexpected error number 80042114 has occurred: The Web server you selected does not indicate support for the service provider you selected.

SUGGESTION: Make sure the "Destination URL" and the "Web Publishing Protocol" fields are both HTTP or FTP. This error occurs because you have specified FTP for the "Web Publishing Protocol" and HTTP URL as the "Destination URL". Select "Yes" and the deployment process will continue. This is noted to reinforce that both the "Destination URL" and the "Web Publishing Protocol" fields should both either HTTP or FTP.</li> <li>Unexpected error number C0042116 has occurred: Access denied.

SUGGESTION:

<ol style="list-style-type: lower-alpha;"> <li>Use the File Explorer to make sure you have write access to that share.</li> <li> Right-click on Network Neighborhood icon on the DeskTop

<pre class="FIXEDTEXT">      Select Properties Select Protocols Select TCP/IP Protocol and click Properties button Select WINS Address Deselect the check box "Enable LMHOSTS Lookup and click           the OK button.   </li></ol> </li> <li>Unexpected error number 40042119 has occurred: There is not a 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.

SUGGESTION: Install PA 2.0 on the server you are trying to deploy to as described in Knowledge Base article Q192116.</li> <li>Unexpected error C0042116 has occurred: The parameter is incorrect.

SUGGESTION:

<ol style="list-style-type: lower-alpha;"> <li>Check to make sure that you have typed a valid URL to the Web server you have chosen to use.</li> <li> On the Web server, search for default Web server page. Open the default Web server page and make sure that the following code is at the top of the file:

<pre class="CODESAMP">        <META name="postinfo" content="/scripts/postinfo.asp"> Make sure there is a scripts directory in your wwwroot directory with the files called PostInfo.asp and cpshost.dll. </li> <li> Right-click on Network Neighborhood icon on the DeskTop

<pre class="FIXEDTEXT">      Select Properties Select Protocols Select TCP/IP Protocol and click Properties button Select WINS Address Deselect the check box "Enable LMHOSTS Lookup" and click the OK button. </li></ol> </li> <li>Unexpected error number C0042116 has occurred: The Web server returned the following error: There is a problem installing CAB xxxxx.CAB. Please check it and the INF file xxxxx.INF for validity.

SUGGESTION: Use the PDW Standard Setup Package instead of a PDW Internet Package, described above in step 4 of "Deploying your VB Internet Application to a Web server." You will need to do this because your package is trying to update some system files on the Web server.</li> <li>Unexpected error number C0042116 has occurred: The Web server returned the following error: Files specified in section RInstallApplicationFiles of the INF file xxxx.INF are busy. Cannot install the unless allowed to do a REBOOT..

SUGGESTION: Use the PDW Standard Setup Package instead of a PDW Internet Package, described above in step 4 of "Deploying your VB Internet Application to a Web Server. "You will need to do this because your package is trying to update some system files on the Web server.</li> <li>Unexpected error number C0042116 has occurred: The Web server returned the following error: File xxxxx.htm is not a valid cabinet file.

SUGGESTION: Check the value of the key in "HKEY_CURRENT_USER\Software\Microsoft\WebPost\Sites\Site X\postingurl". This can happen if "?INSTALL" is at the end of the postingurl instead of "?PUBLISH". Change "?INSTALL" to "?PUBLISH".This may indicate that the Package and Deployment wizard did NOT get installed correctly on your machine.</li> <li>Problem: Error C0042116, or Processing Has Stopped.

SUGGESTION: If the files you are trying to deploy from the CLIENT machine are read-only, use the File Explorer to change these file attributes on the CLIENT machine to write, then continue with your posting process.</li></ol>