In This Topic ▼

LEADTOOLS WCF IIS Setup Tool Troubleshooting Guide

The version of the LEADTOOLS Imaging Development SDK installed on this machine contains the LEADTOOLS WCF (Windows Communication Foundation) components.
The WCF components must be configured and hosted in IIS (Internet Information Services) before they are usable in your application or the LEADTOOLS WCF demos.
The LEADTOOLS WCF IIS Setup Tool creates the items in your IIS 6 or 7. The various LEADTOOLS WCF demos require that you configure this exact setup on your machine.
If you wish to change any of these configuration values, then you must change the WCF end-point configuration in your application to match the machine and virtual directory names.

For example, the file CSImageProcessingClientDemo_Original.exe.config in the WCF image processing client demo contains the following entries:

<endpoint 
address="http://localhost/LEADTOOLSWCFServices/RasterService.svc" 
binding="basicHttpBinding" 
bindingConfiguration="BasicHttpBinding_IRasterService" 
  contract="IRasterService" name="BasicHttpBinding_IRasterService" />

Use the LEADTOOLS RasterService WCF component hosted at localhost in the LEADTOOLSWCFServices virtual directory.

Default Configuration

The LEADTOOLS WCF IIS Setup Tool will create the following configuration on your machine.

Property	Value
Machine	localhost
Name	LEADTOOLSWCFServicesAppPool
.NET Framework Version	v2.0 (or v4.0 if you selected the use .NET 4 version of LEADTOOLS option)
Enable 32-Bit Application	(Valid only for 64-Bit Operation Systems) True if hosting the LEADTOOLS 32-Bit assemblies, False otherwise.
Identity	LocalSystem

Table 1. Application Pool

Property	Value
Machine	localhost
Sites	Default Web Site
Name	LEADTOOLSWCFServices
Physical Path	<LEADTOOLS_ROOT_DIR>\WCFHost
ApplicationPool	LEADTOOLSWCFServicesAppPool

Table 2. Virtual Directory

Other properties are all set to their default values. Once the application pool and virtual directory are created, the LEADTOOLS WCF IIS Setup Tool will copy the required LEADTOOLS for .NET assemblies to the Virtual Directory physical path. The runtime version (x86 or x64) of the LEADTOOLS assemblies copied depend on your selection in the setup tool.

Troubleshooting

LEADTOOLS does not require more than the normal prerequisites for hosting and consuming a .NET 3.5 WCF components in IIS. If you are experiencing difficulties using the LEADTOOLS WCF components (either by the demos or the Test tab in the LEADTOOLS WCF IIS Setup Tool interface), then you might find the following guide on setting up IIS with .NET 3.5 helpful.

OS Prerequisites

Windows XP 32-Bit

Prerequisites:

Add ASP Net as Administrator user on Computer name is a domain (XP 32-Bit)
Register IIS with the .NET Framework 2.0 or 4.0

Steps:

@REM Add ASP Net as Administrator user on current machine 
net localgroup Administrators <computer_name>\ASP net /add 
@REM Register IIS 
SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i 
@REM Use this line if you are going to use .NET 4 runtime 
@REM SYSTEMROOT\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i 
@REM Reset IIS 
isreset

Windows Server 2003 32-Bit

Prerequisites:

Register IIS with the .NET Framework 2.0 or 4.0
Enable ASP.NET Extensions

Steps:

@REM Register IIS 
SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i 
@REM Use this line if you are going to use .NET 4 runtime 
@REM SYSTEMROOT\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i 
@REM Enable ASP.NET extensions 
CScript SYSTEMDRIVE\WINDOWS\system32\iisext.vbs /EnFile "SYSTEMDRIVE\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" 
@REM Reset IIS 
isreset

Windows XP 64-Bit and Windows Server 2003 64-Bit

Prerequisites:

If hosting 32-Bit version of LEADTOOLS WCF Services:

Enable 32-Bit Applications on Win XP 64-Bit Machine (Host 32-Bit Bin on 64-Bit)
Register IIS with the .NET Framework 2.0 or 4.0
Enable ASP.NET Extensions

Steps:

@REM Enable hosting 32-Bit applications on 64-Bit IIS 
SYSTEMDRIVE\WINDOWS\system32\cscript SYSTEMDRIVE\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 
@REM Register IIS 
SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i 
@REM Use this line if you are going to use .NET 4 runtime 
@REM SYSTEMROOT\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i 
@REM Enable ASP.NET extensions 
CScript SYSTEMDRIVE\WINDOWS\system32\iisext.vbs /EnFile "SYSTEMDRIVE\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" 
@REM Use this line if you are going to use .NET 4 runtime 
@REM CScript SYSTEMDRIVE\WINDOWS\system32\iisext.vbs /EnFile "SYSTEMDRIVE\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" 
@REM Reset IIS 
isreset

If hosting 64-Bit version of LEADTOOLS WCF Services:

Enable 64-Bit Applications on Win XP 64-Bit Machine (Host 64-Bit Bin on 64-Bit)
Register IIS with the .NET Framework 2.0 or 4.0
Enable ASP.NET Extensions

Steps:

@REM Register IIS 
SYSTEMROOT\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i 
@REM Enable ASP.NET extensions 
CScript SYSTEMDRIVE\WINDOWS\system32\iisext.vbs /ENFile "SYSTEMDRIVE\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" 
@REM Reset IIS 
isreset

Note: If hosting 64-Bit version on XP 64-Bit that has 32-Bit hosted before, you need to do the following steps first:

Disable ASP.NET 32-bit Extensions
Unregister IIS with the .NET Framework 2.0 or 4.0 32-Bit
Disable hosting 32-Bit applications on 64-Bit IIS

Steps:

@REM Disable ASP.NET 32-bit Extensions 
CScript SYSTEMDRIVE\WINDOWS\system32\iisext.vbs /disFile "SYSTEMDRIVE\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" 
@REM Use this line if you are going to use .NET 4 runtime 
@REM CScript SYSTEMDRIVE\WINDOWS\system32\iisext.vbs /disFile "SYSTEMDRIVE\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" 
@REM Unregister IIS with the .NET Framework 2.0 32-Bit 
SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -u 
@REM Use this line if you are going to use .NET 4 runtime 
@REM SYSTEMROOT\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -u 
@REM Disable hosting 32-Bit applications on 64-Bit IIS 
cscript SYSTEMDRIVE\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

Windows Vista and Windows 7 32-Bit

Prerequisites:

Register IIS with the .NET Framework 2.0 or 4.0
Enable Microsoft Windows Communication Foundation Activation
Set the Application Pool identity to "Local System". You need to set this step manually

Steps:

@REM Register IIS 
SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i 
@REM Use this line if you are going to use .NET 4 runtime 
@REM SYSTEMROOT\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i 
@REM Enable Microsoft Windows Communication Foundation Activation 
SYSTEMROOT\Microsoft.NET\Framework\v3.0\"Windows Communication Foundation"\ServiceModelReg -i 
@REM Reset IIS 
isreset 
@REM Set the Application Pool identity 
@ECHO Set the application pool identity to LocalSystem

Windows Vista and Windows 7 64-Bit

Prerequisites:

Register IIS with the .NET Framework 2.0 or 4.0
Enable Microsoft Windows Communication Foundation Activation
Set the Application Pool identity to "Local System". You need to set this step manually
Set up the Application Pool to host 32-Bit components (if required)

Steps:

@REM Register IIS 
SYSTEMROOT\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i 
@REM Use this line if you are going to use .NET 4 runtime 
@REM SYSTEMROOT\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i 
@REM Enable Microsoft Windows Communication Foundation Activation 
SYSTEMROOT\Microsoft.NET\Framework\v3.0\"Windows Communication Foundation"\ServiceModelReg -i 
@REM Reset IIS 
isreset 
@REM Set the Application Pool identity 
@ECHO Set the application pool identity to LocalSystem 
@REM Set up the Application Pool to host 32-Bit components (if required) 
@ECHO For hosting 32-Bit applications in 64-Bit Operating System, you must 
@ECHO the [Enable32BitAppOnWin64] property in the application pool to TRUE