Scheduled package problem: Class not registered

Hi,

Attempting to schedule and execute a package. The server is a 64bit clustered sql 2005 server.

The package was developed on my local install of sql 2005 client tools. I can run the package within BIDS, I can export and run the package from MSDB, but I cannot get it to execute without failure when scheduled.

I suspect it is some weirdness caused by the difference between 32 bit and 64 bit type program, but do not know what to do to figure it out.

Job history output below:

Date 14/09/2007 1:07:30 PM
Log Job History (SISS)

Step ID 1
Server servername

Job Name SSIS test job
Step Name Import NE Outpat
Duration 00:00:02
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: HAHS\billsqlserver. ...9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:07:30 PM Progress: 2007-09-14 13:07:31.54 Source: Clinics Validating: 0% complete End Progress Progress: 2007-09-14 13:07:31.54 Source: Clinics Validating: 33% complete End Progress Progress: 2007-09-14 13:07:31.75 Source: Clinics Validating: 66% complete End Progress Error: 2007-09-14 13:07:31.89 Code: 0xC0202009 Source: ImportNewEnglandOutpatientData Connection manager "Clinics" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2007-09-14 13:07:31.89 Code: 0xC020801C Source: Clinics Clinics Access Database [15] Description: SSIS Error Code DTS_E_CANNOTACQ... The package execution fa... The step failed.

Thanks for all suggestions,

Does the package run when executed from SQL Management Studio on the server itself?|||

Hi,

Not sure.....

Been doing some further reading, and found:

"Noted that the Microsoft OLE DB Provider for Jet, used for Access and Excel databases, is not available in a 64-bit version."

on http://msdn2.microsoft.com/en-us/library/ms141766.aspx

The package has 4 MS access as datasources and imports the data into 2005.

Is this possible? is there another way around this?

|||

Well it sounds to me like you are on the right track.

Someone else will ahve to answer the 64bit question. I have no experience with using Access on a 64 bit install (thank god!)

|||

You cannot run this package in 64-bit mode as there is no 64-bit JET provider. Use the 32-bit dtexec when scheduling your jobs.

Thanks,

Bob

sql