Summary

When you click the Print PDF button in WebLink's document viewer and WebLink 8 is installed on a 64-bit operating system, you may receive the following error message:

500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

Cause

There may be an invalid .PDF handler mapping. This issue can occur if WebLink is not running under the default Web site and the 64-bit version of .NET Framework is not installed on the Web server.

When you create a new Web site in IIS on a 64-bit operating system and create a new virtual directory for WebLink, the executable path of the handler mapping for PDF files may point to the default installation path for the 64-bit version of .NET Framework even though the 64-bit version of .NET Framework is not installed.

Workaround 1

Install the 64-bit version of the .NET Framework 2.0 redistributable. You can download the installation package from the Microsoft Web site.

Workaround 2

If you do not wish to install the 64-bit version of .NET Framework 2.0, modify the .PDF handler mapping to point to the valid 32-bit installation path for .NET Framework.

To modify the handler mapping

1. Load the Internet Information Services (IIS) Manager.
2. Expand the tree to the WebLink 8 virtual directory under your custom Web site.
3. In IIS 5 and 6, view the properties of the virtual directory and on the Virtual Directory tab, click the Configuration button. In IIS 7, double-click the Handler Mapping item.
4. Make sure there is only one item for the .pdf extension and that the executable path for the mapping points to "C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll."