HTTP Error 403 - Forbidden or HTTP Error 404 - File Not Found

Symptoms

"You are not authorized to view this page (HTTP Error 403 - Forbidden)""The page cannot be found (HTTP Error 404 - File not found)"These errors occur when accessing the WebView or WebPort.

Cause

The default document (default.asp) in the WebPort virtual directory within IIS is set incorrectly or is missing from the WebPort directory.

Resolution

On the Web Server, verify the default document setting.
  1. Open the IIS console (Internet Services Manager).
  2. Right-click on the WebPort virtual directory and select Properties.
  3. Click the Documents tab.
  4. Select each document and click the Remove button.
  5. Click the Add button.
  6. Type "Default.asp" and click OK.
  7. Click OK again to return to the main IIS Console screen.
  8. You should now have access to the WebPort site.
Verify that the default.asp document exists in the WebPort directory on the server. If that file is missing, contact your FRx support provider to receive a new copy.
  • If the WebPort installation does not have the latest FRx service pack applied, apply the service pack. Be sure to stop the web service and the FRxPDFSvr process prior to applying the service pack. For information on how to stop the web service, please see Stopping and Restarting the World Wide Web Service.
  • If WebPort is installed on a Windows server 2003, verify that ASP pages are enabled on the server. Unless it is selected manually during the installation of Windows Server 2003, Active Server Pages functionality will not be available on the server. This functionality was enabled by default with Windows 2000 Server.
Refer to the Enable a Pre-Existing Web Service Extension in IIS 6.0 section in the following Microsoft Knowledge Base article. 315122 - HOW TO: Enable and Disable Dynamic Content in IIS 6.0
Verify that the application mappings for the .asp and .asa extensions are mapped to asp.dll.
  1. Open the IIS console (Internet Services Manager).
  2. Right-click on the WebPort virtual directory and select Properties.
  3. Click the Virtual Directory tab.
  4. Click the Configuration button in the Application Settings section.
  5. On the Mappings tab of the Application Configuration window, verify that the .asa and .asp extensions are mapped to asp.dll. If they are not, correct the mapping.
  6. Click OK

References

Eigenschappen

Artikel-id: 965174 - Laatst bijgewerkt: 4 feb. 2009 - Revisie: 1

Feedback