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 E-mail this page

Feedback How helpful was this article? 5 Best 4 3 2 1Worst 0 N/A Suggestions:

SYMPTOMS

When the SQL Server Agent attempts to run the ILLiad Connector batch files, it immediately returns a status of "Failed".

ERROR MESSAGES

If you right-click on the job and choose Job History, you will see an error like this:

The job failed. The Job was invoked by User MACHINENAME\ACCOUNT. The last step to run was step 1 (Run ILLiad Connector).

If you click the checkbox to view details, then you will see this or a similar additional error:

Executed as user: MACHINENAME\ACCOUNT. ...nformation ************************ C:\WINNT\system32>REM C:\WINNT\system32>REM This batch file is what the SQL Agent runs when it is scheduled to run. C:\WINNT\system32>REM C:\WINNT\system32>REM There are 4 possible commands you can send the Connector. They are: C:\WINNT\system32>REM C:\WINNT\system32>REM BorrowingDownloads - downloads statuses like Shipped, Conditional, etc. C:\WINNT\system32>REM LendingDownloads - imports new requests as well as conditionals and renewals C:\WINNT\system32>REM BorrowingUpdates - updates items to received or returned and requests renewals C:\WINNT\system32>REM LendingUpdates - updates as conditional, cancelled, shipped, etc. C:\WINNT\system32>REM C:\WINNT\system32>REM Each of these can be done individually or at the same time, by adding C:\WINNT\system32>REM them to the same command line. C:\WINNT\system32>REM C:\WINN... Process Exit Code -1073741787. The step failed.

CAUSE

The SQL Server Agent, in order to run a CmdExec type job (system commands, external applications, etc.), must have permissions. Only Administrator (local/domain) level accounts on the NT/2000 machine have permissions to run this type of job by default.

Another cause could be that the ILLiadVersion6Update.exe was not run on the server where the ILLiad Connector is running.

RESOLUTION

IF the ILLiadVersion6Update.exe has not been run (it would show under Add/Remove Programs if it had been installed), you can run the executable from the Setup .. ClientUpdates .. 6.0.0.1 folder. It is the same file that was run on the client machines.

There are 3 possible solutions to the permissions issue: Changing the account that the SQL Server Agent uses to run (recommended), overriding the setting that resticts the CmdExec jobs being only run by Admin accounts, or using a different scheduling software to run the ILLiad Connector batch files.

To change the account that the SQL Server Agent uses to run, open the Services dialog, find SQLSERVERAGENT, right-click and choose properties, click the LogOn tab and put an Administrator level account and password into the fields provided. Stop and restart the service.

To allow all users the ability to run the SQL Server Agent CmdExec jobs, right click the SQL Server Agent under Management using the SQL Server Enterprise Manager. Select the Job System tab. Under "Non-SysAdmin job step proxy account", uncheck the "Only users with SysAdmin privileges can execute CmdExe and ActiveScripting job steps. The system will prompt you for an Administrator username, password, and domain. Fill in these 3 items and hit OK.

If you elect to use a third-party scheduling software, just run the batch files as needed. The default schedule is:

• ILLiadConnector1.bat (7:00AM)
• ILLiadConnector2.bat (10:00AM)
• ILLiadConnector3.bat (1:00PM)
• ILLiadConnector4.bat (4:00PM)
• ILLiadConnector5.bat (7:00PM)

USING THE WINDOWS TASK SCHEDULER

The Windows Task Scheduler is another way to run the ILLiad Connector. It is part of Windows 2000 Server, as well as Windows NT 4.0 Server machines that have had the installation of the Offline Browsing Pack, a component of Internet Explorer 5. This method is recommended if the SQL Server database is not on the ILLiad server machine.

To access the Windows Task Scheduler, follow these steps:

1. Start the Task Scheduler Wizard (go to Start, Settings, Control Panel, Scheduled Tasks, Add Scheduled Tasks).
2. Click Next to begin the wizard and display a list of programs installed on your machine. Click Browse, and locate the c:\illiad\connector folder. In this folder are the 5 default batch files installed by ILLiad. Select the one you are scheduling and click next.
3. Select a display name for your task, select when you want the task to run (daily), and click Next.
4. Put in the start time, using the suggested times above, or your own schedule. You most likely want to schedule this to run on Weekdays, with a start date of today's date (the default). Click Next.
5. Enter a username and password for an account to run the ILLiad Connector. It needs sufficient permissions to run the Connector and access the database. Click Next.
6. Review the information displayed, and if it is corrent, hit the Finish button. You task is now scheduled. Repeat for each of the ILLiad Connector Batch Files.

The new task will appear in the Scheduled Tasks applet in Control Panel. If you want to modify a task, right-click the process and select Properties to display an advanced dialog box where you can change the task parameters.