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:All Versions
Revision:1
INFO: Required ILLiad Server Permissions
January 5, 2006

SUMMARY

ILLiad Anonymous User Permissions
ILLiad requires that the Anonymous User Account (generally, but not necessarily ALWAYS IUSR_Servername) and the Launch IIS Process Account (generally, but not necessarily ALWAYS IWAM_Servername) have Read and Execute permissions on the server to the following directories in order to properly run the ILLiad.dll through IIS:

" C:\Program Files\Common Files\Borland Shared\BDE

* C:\WinNT\temp
* C:\WinNT\System32
* C:\Inetpub\wwwroot\ILLiad\ (or whichever directory is your default ILLiad web directory).

In addition, both the Anonymous User Account and the Launch IIS Process Account also need to have Write access to the C:\WinNT\temp folder for the ILLiad.dll to function properly.

ILLiad Share Permissions
All ILL staff/employees who will be using the ILLiad Client will need to have read access to the ILLiad Share in order to run the ILLiad Client.
In the case of locally installed clients, the share referred to here essentially exists as a local directory on each client machine, without having to be shared for other users. In such cases, the server side ILLiad share either doesn't exist or is not used by the client machines. Special share permissions are not generally required.

PDF Share Permissions (If using the Electronic Delivery option.)
All ILL staff/employees who will be using the ILLiad Client to post Electronic Documents will need to have read/write access to the PDF Share in order to post electronic documents to the PDF share on the ILLiad server.

MORE INFORMATION

There is a separate KB article on how to fix the Anonymous User Permissions here.

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
OCLC ILLiad and Windows Server 2003
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
HOWTO: Routing Rules Across Modules
BUG: Routing Rules for Borrowing and Doc Del do not work using the ILLiad Connector