Readme IIS4.html

Before you begin

• Install IIS 4 using the Microsoft installation instructions.  Refer to "IIS 4.0 Recommended Installation Procedure" available on the Microsoft support web site (www.microsoft.com/support/iis). 
• You should install MDAC 2.1 or later (available at www.microsoft.com/data).   If you are using Windows Terminal server be careful to follow the instructions outlined in Microsoft support document Q216149 - How to Install ODBC or MDAC on Terminal Server.
• You must have Client Access Express R440 Service pack SF63638 or later or Client Access Express R450 SF62213 or later installed on the IIS server.
• You must install the necessary Client Access Components.  Client Access ODBC and OLEDB are installed as optional subcomponents of the "data access" component. These components are included with a "typical" Client Access install.  Client Access APIs and ActiveX objects are installed as part of the base install.

Setting up the sample web site

1) Create a folder named X3TierSamp
The folder can be located anywhere on the IIS PC.

2) Unzip the files into this folder.

3) Use the Internet Service manager (IIS snapin to MMC) to configure a new application.  Note that the sample MUST be configured as an application.  Only IIS applications support sessions.

3a) Under the target web site (Default Web Site) select new, virtual directory

3b) "Alias to be used to access virtual directory" is the name that will be used to access the application. For example X3TierSamp would result in a URL of http://mypcname/X3TierSamp

3c) "Physical path of the directory containing the content you want to
publish" is the path you specified in step 1.

3d) Accept the default permissions of Read Access and Script Access.  Click finish.

3e) The application will now be displayed under the specified web site.  Select the application, right click, and select properties. We recommend that you check "Run in a separate memory space" while debugging and testing the application.  

3f) On the same application Properties dialog click the "Configuration Button".

3g) Select the App Debugging tab, and then verify that "Script Error Messages" is set to "Send detailed ASP error messages to client".  Note:  You can enable ASP server-side script debugging however any script errors will cause the script debugger to "pop" on the server rather then allowing the error message text to be returned to the browser.

4) Start the web site specified in step 3a

5) Configure a ODBC system DSN.
The ODBC data source MUST BE A SYSTEM DSN. See the Client Access help for assistance configuring an ODBC datasource.

6) Access the sample from any browser.   Use the "alias" specified in 3b. http://<my_iis_pc_name>/X3TierSamp

7)  Fill out the form (enter information and hit submit) and run "Report Versions".  This will verify the proper components are installed, verify the Client Access PTF level, and verify that the ODBC datasource is configured and of the correct type.

Common problems

Problem: The connect string displayed on browse pages is not correct
Resolution:

• You must configure the sample as an IIS application. Only IIS applications support ASP sessions and use global.ASA files.
• The asp file must be opened through IIS and not directly. Verify that the URL used to open the sample is http://<my_iis_pc_name>/X3TierSamp/default.asp. Do not attempt to open the asp file by double-clicking in explorer or by using a file url (file://...)

Problem: Error involving a closed or invalid connection object
Resolution:

• Verify that the ODBC data source is a system DSN (listed on the System DSN tab).
• Verify that the ODBC data source was created on the same server that IIS is running on.
• Verify that you have the correct Client Access service pack.
• Verify that cwbping works against the system name configured in the data source.
• Verify that the system name entered on the DSN is typed correctly. If the name is a system name verify that you are using DNS and not a local hosts table for the IP address lookup. NT services cannot use the local hosts table. If DNS is not available then use the AS/400 IP address in place of the system name (this has slightly better performance since it skips DNS lookups). 
• Verify that the userid/pwd and DSN names on the browse web pages show are valid.
• Check for policies (both Client Access and Windows) that might prevent the connection as well as any security changes that might have been applied to the windows registry (HKLM, software, ODBC).