Home » SQL Server

Package Fails When Using 32-bit Teradata Driver

Upfront - I'm not sure if this question belongs with this forum or another more specific to SQL Server Agent.

I have a package running on Windows 2003 (64-bit) attempting to pull data from a Teradata server using its 32-bit driver.  The package runs as expected within BIDS and when called from a BAT file run from the command prompt using the 32-bit version of DTEXEC. 

The package fails with the following error when I attempt to run it using the same *.BAT file (which succeeds from a command prompt) or when specifying the DTEXEC command directly in an operating system job step.  Any insight, suggestions, or workarounds would be helpful.

Executed as user: <<<userName removed>>>. ...\dtexec.exe /SQL \HRD_ODS\TheW_Connection_Test /SERVER CRPRDNMSQR2  /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EMicrosoft (R) SQL Server Execute Package Utility  Version 9.00.4035.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  11:47:59 AM  Error: 2011-01-25 11:48:01.26     Code: 0xC0047062     Source: Data Flow Task DataReader Source [419]     Description: System.Data.Odbc.OdbcException: ERROR [IM003] Specified driver could not be loaded due to system error  126 (Teradata) .     at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)     at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle)     at System.Data.Odbc.OdbcConnectionOpen..ctor(OdbcConnection outerConnection, OdbcConnectionString connectionOptions)     at System.Data.Odbc.OdbcConnectionFactory.CreateConn...  Process Exit Code 1.  The step failed.


10 Answers Found


Answer 2

Hello , please check this


maybe you need Edit your step and then go to Execution options and Check the Box for 32 Bit.

give a try



Answer 3

Arthur, Aamir:


I appreciate the reply guys the option is available.  I should have mentioned in the original post I'm using SQL Server 2005.


Answer 4

You are welcome Orlanzo,

curious if you have resolved the issue by applying this setting.


Answer 5

Hi Arthur,

No, the setting isn't available in SQL Server 2005.  What you're referring to was introduced in SQL Server 2008.


Answer 6

Add the /X86 key to the DTExec

Answer 7

Add the /X86 key to the DTExec
Arthur My Blog
By: TwitterButtons.com
That option is not available with SQL Server 2005.

Answer 8

Follow this article "How to use the 64-bit SQL Server Agent to schedule a SQL Server 2005 Integration Services package":


The post walks you through on how to properly set up the Agent Job to run the 32 Bit version of DTExec.


Answer 9

Hi Arthur,

I'm familiar with how to call the 32 bit version of DTEXEC from SQL Server Agent.  I did review the article you provided and confirmed my end result is identical to what it describes.


Answer 10

Started to think this can be because your environment is clustered.

I can see how this was be fixed here: http://blog.vyvojar.cz/dotnet/archive/2008/04/09/227349.aspx

Short excerpt:

w3wp.exe didnt see path \Program Files\NCR\Common Files\Shared ICU Libraries for Teradata\lib -- in your case it might be different

Fix solution:
Copy files from Teradata\lib to one from directorys where execept w3wp.exe files (System32 dir, ..)

So in your case running the package as SQL Server Agent does not let the file be found. It runs in BIDS because you execute the package locally (on your PC) unless you are running it directly on the server.

Arthur My Blog
By: TwitterButtons.com


<< Previous      Next >>

Microsoft   |   Windows   |   Visual Studio   |   Sharepoint   |   Azure