Groups | Blog | Home
all groups > sql server dts > february 2006 >

sql server dts : running as job raises JET error from paradox db?


Allan Mitchell
2/6/2006 7:19:56 AM
Hello Andrew,

Usually when something works interactively and not as a job then the answer
lies within here

http://support.microsoft.com/?kbid=269074

Also have a look here for the Paradox and jet thing

http://support.microsoft.com/kb/230126/EN-US/


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

[quoted text, click to view]

Andrew Brill
2/6/2006 1:48:37 PM
We have a very simple DTS package to import data from a Paradox 4.x database
into SQL server. When the package is executed directly it works fine.
When it is run as an sql server agent job it errors with "Microsoft JET
Database Engine" reporting "External table is not in the expected format."

As an Access developer I'm slightly confused to see the Access JET engine
complaining about a paradox database?

The package has one connection set to Paradox 4.X and one connection as the
SQL server with a simple copy data transformation in between.


Full error text is:
Executed as user: SILVERSTONE\Administrator. DTSRun: Loading... DTSRun:
Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun
OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: Copy Data from
PART to [Parts].[dbo].[PartsFiles] Step DTSRun OnError: Copy Data from
PART to [Parts].[dbo].[PartsFiles] Step, Error = -2147467259 (80004005)
Error string: External table is not in the expected format. Error
source: Microsoft JET Database Engine Help file: Help context:
5003274 Error Detail Records: Error: -2147467259 (80004005);
Provider Error: -328602519 (EC69EC69) Error string: External table is
not in the expected format. Error source: Microsoft JET Database
Engine Help file: Help context: 5003274 DTSRun OnFinish:
Copy Data from PART to [Parts].[dbo].[PartsFiles] Step DTSRun: Package
execution complete. Process Exit Code 1. The step failed.

Andrew Brill
2/6/2006 3:46:26 PM
Sorry false alarm! I didn't take into account that running a package
executes it on the local machine whereas running a job executes it on the
server. It appears the server does not have a paradox filter and so I guess
it is falling back on the jet filter for some reason.



[quoted text, click to view]

AddThis Social Bookmark Button