FP: "HTTP Code 500" Creating Web, Browsing Page w/Image, WebBot

• Microsoft FrontPage 98 for Windows
• Microsoft FrontPage 97 for Windows with Bonus Pack ------------------------------------------------------------------------

SYMPTOMS

In Microsoft FrontPage, you may receive the following error message:

   In FrontPage 98:

      Server Error This server has encountered an internal error which
      prevents it from fulfilling your request. The most likely cause is a
      misconfiguration. Please ask the administrator to look for messages
      in the server's error log.

   In FrontPage 97:

      An HTTP server error has occurred. An error has occurred in the HTTP
      server which made it impossible for the FrontPage Server Extensions
      to process this request (HTTP Error 500).

   Case 1: You browse a page that contains an image map or a WebBot.

   -or-

   Case 2: You create a new Web.

CAUSE

This problem may occur for either of the following reasons:

• If you are using Microsoft Personal Web Server, FrontPage is not able to execute Shtml.dll (Case 1).

  -or-

• If you are using FrontPage Personal Web Server, FrontPage is not able to execute Shtml.exe (Case 1).

  -or-

• FrontPage cannot access the server through the extensions (Case 2).

RESOLUTION

To work around this problem, use the appropriate method for your situation.

Method 1: Check Error Logs and Memory (Case 1)

Check the error logs for any out of memory errors and then verify the amount of physical and virtual memory installed on your computer.

If you are using the FrontPage Personal Web Server, the error logs will be located in the \Server\Logs folder (FrontPage 1.1) or the \Httpd\Logs folder (FrontPage 1.0).

If you are using Microsoft Personal Web Server, the error logs will be located in the \Windows folder.

You should have 16 megabytes (MB) of RAM in order to run the FrontPage Personal Web Server or Microsoft Personal Web Server. You should also set a permanent swap file that is at least 20 MB in size.

Method 2: Check Configuration Settings (Case 1)

If you have changed the default content folder for the FrontPage Personal Web Server, check the following:

• The definition of the DocumentRoot in the Srm.cnf file.
• The following settings in the Srm.cnf:

  FrontPage 1.0:

        WinScriptAlias  _vti_bin/ c:\content\_vti_bin
  

  FrontPage 1.1:

        WinScriptAlias  _vti_bin/ c:\FrontPage/Webs\content\_vti_bin
  

• The Document Root is defined in the Directories tab of the Internet Services Administrator. To access the Internet Services Administrator, follow these steps:

  1. Click the Start button, point to Settings, and then click Control

        Panel.
  

  2. Double-click the Personal Web Server icon.

  3. Click the Administration tab.

  4. Click Administration.

Method 3: Check the Shtml.exe or Shtml.dll File and File Size (Case 1)

If you have not changed the default content folder, check the following:

• If you are using FrontPage Personal Web Server, verify that the \_vti_bin\shtml.exe file exists and that its file size is greater than 0. This file is located in the DocumentRoot folder.
• If you are using Microsoft Personal Web Server, verify that the \_vti_bin\shtml.dll file exists and that its file size is greater than 0. This file is located in the DocumentRoot folder.

Method 4: Check Whether the Server is Running (Case 2)

Verify that the server is running. If it is not running, start it. Confirm it is started by browsing to the URL for the HTTP server.

Method 5: Verify the Server Extensions Are Installed (Case 2)

Verify that the server extensions have been installed on the server. To do this, start the FrontPage Server Administrator and click Check. Confirm that the server information is correct.

Method 6: Install the FrontPage Server Extensions (Case 2)

Install the FrontPage Server Extensions. You can download the FrontPage 98 Server Extensions from the following Microsoft World Wide Web site:

   http://www.microsoft.com/frontpage/softlib/current.htm.

   http://www.microsoft.com

 ~ Fp11ext.exe (size: 511200 bytes)