Related Topics

HOWTO: Backing Up the ILLiad Database
HOWTO: Breaking the User Link in the ILLiad Database
PROBLEM: Cancellations or OCLC Reasons for No are all updating as Other
HOWTO: Changing the Port for Microsoft SQL Server 2000
HOWTO: Changing the size of a field in the ILLData database
See more

Other Support Options

Contact Atlas Systems
Phone Numbers, Support Options, Online Help, and more.
Listserv
Pose a question to other users.

Page Tools

Print this page Print this page
E-mail this page E-mail this page

Feedback

How helpful was this article?
Suggestions:

Revised:January 5, 2006 (mc)
Version:Version 6.2 and higher
Revision:1
OCLC ILLiad and Windows Server 2003
January 5, 2006

SUMMARY

OCLC ILLiad has been tested with Windows Server 2003, Standard Edition, and is completely compatible. Once ILLiad is setup, the usage of ILLiad is no different when using Windows Server 2003 vs. Windows 2000 Server.

By default, Internet Information Server 6 is more secure than the older versions, and requires specifying which ILLiad files are allowed to be executed. This article covers the differences between the Windows 2000 Server install (which is in the documentation) and Windows 2003.

 

INSTALLING INTERNET INFORMATION SERVER 6 (IIS)

By default, IIS is not installed when you install Windows Server 2003. After installing, you can choose to make the server an Application Server, and choose which Application environments you want to add. Using this Wizard, you can select IIS for installation.

 

INSTALLING SQL SERVER 2000

SQL Server 2000 is only supported on Windows 2003 Server, Standard Edition, with Service Pack 3 or greater installed. The system will not let you run with less than SP3.

 

CONFIGURING INTERNET INFORMATION SERVER 6 (IIS)

After following the current ILLiad installation instructions for the web pages, you must enable the ILLiad.DLL application file in order for it to be allowed.

Under Computer Management, chooise Services and Applications, then Internet Information Server. Choose Web Service Extensions, then choose Add a new Web Service extension.

For Extension Name, you can type ILLiad DLLs.

Click Add, and find the ILLiad.DLL file on your server (usually in the c:\inetpub\wwwroot\illiad\ folder).

Click the check box for "Set extension status to Allowed". Hit OK.

You will also need to add the ILLiadReports.DLL file (usually in the c:\inetpub\wwwroot\illiad\webreports\ folder) and the isapi_redirect.dll file for OpenURL (usually in the c:\illiad\OpenURL\jakarta\bin\ folder).

After adding and setting up those three extensions to be allowed, stop and restart IIS before testing the ILLiad pages.

More Related Topics

PROBLEM: Class Not Registered error when trying to initiate Z39.50 Searching
PROBLEM: Incorrect Queues and E-mail Routing Entries in the ILLiad Client for a Shared Server Site
HOWTO: Enabling Logging on the ILLiad Gateway
HOWTO: Enabling Logging on the ILLiad Web DLL
HOWTO: Increasing the Username field in the ILLiad database
INFO: ILLiad and McAfee VirusScan 8
INFO: ILLiad and the NVTGC Field
HOWTO: Implementing SSL with ILLiad
HOWTO: Importing a Customized List of Addresses to ILLiad
HOWTO: Importing Pre-ILLiad Copyright Information into your ILLiad Database
PROBLEM: Z39.50 Searching Form gives File Not Found error for Yaz.dll
INFO: Z39.50 Profiles in ILLiad
INFO: Z39.50 Compatibility in ILLiad
INFO: What Ports are Required to be Open for General ILLiad Use?
INFO: User Request Limits
HOWTO: Updating Across a Multiple Server ILLiad Installation
PROBLEM: I/O Error 32 or Path not Found when opening the Borrowing Request Form
HOWTO: Migrating an ILLiad Database to a New ILLiad Server
PROBLEM: Error Message "Login failed. Reason: Not associated with a Trusted SQL Server connection"
PROBLEM: SQL Server Agent fails when executing job to run ILLiad Connector
ERROR: SQL ERROR: Unmatched '' near TransactionNumber
PROBLEM: EDBEngine Error: Vendor Initialization Failed
Microsoft SQL Server 2005 Compatibility
HOWTO: Changing the Default Request Type for Manually Entered Transactions
INFO: Required ILLiad Server Permissions
HOWTO: Routing Rules Across Modules
BUG: Routing Rules for Borrowing and Doc Del do not work using the ILLiad Connector