Microsoft KB Archive/265183

= FP2000: Error Message: Error INI File Section Port 80 Not Found =

Article ID: 265183

Article Last Modified on 8/27/2002

-

APPLIES TO


 * Microsoft FrontPage 2000 Standard Edition

-



This article was previously published under Q265183



SYMPTOMS
When you attempt to open a subweb after upgrading to the Microsoft FrontPage 2000 Server Extensions, you may receive the following error message:

Server error: INI file &quot;&quot; section &quot;Port 80&quot; not found.

The subweb does not open as expected.



CAUSE
This behavior can occur if there is a physical _vti_bin folder in the subweb rather than a virtual _vti_bin directory. To verify this, use Windows Explorer to examine the folders in your Web content area and look for a _vti_bin folder.



RESOLUTION
To resolve this issue, use the appropriate method for your version of IIS:

If you are using IIS 4.0
 Make sure that the FrontPage Server Extensions are not currently loaded into memory. To do this, restart Internet Information Services (IIS). To do this, use either of the following methods:  Restart the WWW, FTP, and IIS Admin Services by using the Services Control Panel.

-or- Restart all of the IIS services by using a batch file. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

194916 Restarting Web Services and Scheduled Tasks with a Batch File

  Open the Internet Services Manager for IIS. On the Windows Start menu, point to Programs, point to Microsoft Windows NT 4 Option Pack, point to Microsoft Internet Information Server, and then click Internet Service Manager. Locate and select the affected Web site in the tree view.</li> Right-click the _vti_bin folder in the affected Web site and then click Delete. If you are prompted to confirm the deletion, click Yes.</li> Create a new virtual _vti_bin folder. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Right-click the affected Web site, point to New, and then click Virtual Directory.</li> Name the new virtual directory _vti_bin.</li> Point to the new virtual directory to the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\40\isapi folder.</li> Give the virtual directory Read access permissions only.</li> Click Finish.</li></ol> </li> Right-click the _vti_bin virtual directory in your Web site and click Properties.</li> Click the Virtual Directory tab.</li> Set the directory to allow programs to be executed. In the Application Settings section, set the Permissions to Execute (including script), and click OK.</li> Right-click the affected Web site, point to Task, and then click Check Server Extensions.</li> If you are prompted to tighten the security of the Server Extensions, click Yes.</li></ol>

If you are using IIS 5.0
<ol> Make sure that the FrontPage Server Extensions are not currently loaded into memory. To do this, restart Internet Information Services (IIS): <ol style="list-style-type: lower-alpha;"> Open a command prompt.</li> Type IISRESET and then press ENTER.</li> Close the command prompt after IIS has restarted.</li></ol> </li> <li>Open the Internet Services Manager for IIS. On the Windows Start menu, point to Programs, point to Administrative Tools, and then click Internet Services Manager.</li> <li>Locate and select the affected Web site in the tree view.</li> <li>Right-click the _vti_bin folder in the affected Web site and then click Delete. If you are prompted to confirm the deletion, click Yes.</li> <li>Create a new virtual _vti_bin folder. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>Right-click the affected Web site, point to New, and then click Virtual Directory.</li> <li>Name the new virtual directory _vti_bin.</li> <li>Point the new virtual directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\40\isapi folder.</li> <li>Give the virtual directory Read access permissions only.</li> <li>Click Finish.</li></ol> </li> <li>Right-click the _vti_bin virtual directory under the Web site and click Properties.</li> <li>Click the Virtual Directory tab.</li> <li>Set the directory to allow programs to be executed. In the Application Settings section, set the Execute Permissions to Scripts and Executables, and click OK.</li> <li>Right-click the affected Web site, point to Task, and then click Check Server Extensions.</li> <li>If you are prompted to tighten the security of the Server Extensions, click Yes.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
In FrontPage 98 and earlier, the FrontPage extensions were physically installed to folders that contained FrontPage Webs. In contrast, in FrontPage 2000, all FrontPage Webs share the same executables by adding a virtual folder to each Web that points to the location of the FrontPage common files. In some situations, the physical folder still exists and prevents the FrontPage extensions from functioning correctly.

<div class="references_section">