Friday, March 23, 2012

MICROSOFT JET OLEDB 4.0?

hi i have another question.. is this connection provider supported on servers running under 64 bits? if not? which provider should i use instead? is there any service pack or upgrades for this ?

i think this is the problem running my job.. there's no other option left.. it is not permissions.. the path of the connection manager exists, the file destination does exist as well.. the curious thing is that my dts runs fine from SSIS but fails using the job..

do i need to have installed excel in my server to do this or any other component?

There is only 32-bit Jet provider, so you need to run the package using 32-bit DtExec.exe to use it. When scheduling job in Agent, select Operating System (CmdExec) step type, and the command to run is
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DtExec.exe" /f "package-path"|||

thaaaaaaaanks thanks thaaaank youuuuuuuu this was the solution for all my problems... i own you one!!!!!

regards

|||

DTEXEC does not work well with Excel on my system

I am using DTEXEC utility to run the packages on 64-bit system. One of the packages has connection to Excel. The package runs fine from SSMS but return error “Class not registered” OLE DB error has occurred. Error code: 0x80040154.

The package is stored in MSDB. I use following syntax to run the package:

dtexec /sq DTSpkg

Any help?

|||Have you read the discussion above?

There is no 64-bit OLEDB provider, so you need to use 32-bit DTEXEC:
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DtExec.exe" <rest of the arguments>|||

Hi Michael, Thanks for help. Connection to Excel works. Can you take a look on another problem bellow?

I use Flat File Connection manager in different package. The package creates a file on other server on completion. The package runs successfully from SSMS but returns error when run with dtexec /sq DTSpkg

Description: The file name "\\SERVER2\FTProot\PackageOK.RCV" specified in the connection was not valid.

No comments:

Post a Comment