Microsoft KB Archive/234972

= PRB: Unexpected Error 40042119 with PDW: There Is No PostInfo File on the Server =

Article ID: 234972

Article Last Modified on 9/5/2006

-

APPLIES TO


 * Microsoft Visual Basic 6.0 Learning Edition
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition
 * Microsoft Internet Information Server 4.0
 * Microsoft Internet Information Services 5.0

-



This article was previously published under Q234972



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.



CAUSE
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  tag in default document (typically named Default.htm) in the root directory of the Web is pointing to the incorrect location for PostInfo.asp.



RESOLUTION
Use the following steps to work around this problem:

 Make sure the Web service is running. Make sure PostInfo.asp is loated in the InetPub\scripts directory. By default, the Microsoft Posting Acceptor 2.0 installs the PostInfo.asp and Cpshost.dll files to the InetPub\scripts directory. Make sure the user has NTFS Read and Execute (RX) permissions to the InetPub\scripts directory.  Make sure your default document has the following  tag on the first line and the "content" parameter points to a valid location for the PostInfo.asp file as shown below:  </ul>

<div class="status_section">

STATUS
This behavior is by design.

<div class="references_section">