Teradata destination ODBC connections failing in SSIS job

Windows Server 2012 R2
SQL Server Integration Services 2012
Teradata 13.10.00.14, Driver 14.10.00.06
We have a situation where ODBC connections to Teradata destination database keep getting errors from time to time, not every night though.
Some nights regular load jobs execute successfully and sometimes they get errors "There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server." -
one or more component failed validation.
The faulty component is usually different, not the same every time. Package may also differ. There are 4 packages starting parallelly at the same time, each having 1 or 2 sequences of dataflows and sql tasks (about 60 dataflows and 40 sql tasks in total in
those packages). Packages have been migrated from DTS to SSIS and this kind of error-situation has never occurred before.
So we checked what happens on the Teradata side - many simultaneous sessions, validation sessions at first then TPT Load and ODBC sessions, but the number of concurrent open sessions never exceeds something like 30-40. And there is a parameter in Teradata indicating
that max allowed sessions is 120.
Two different kinds of connection managers used - Teradata Connection Manager, used in Attunity Teradata Destination component for TPT Loading and ODBC Connection manager to execute SQL Tasks and also for loading to Teradata destination tables in case of low
number of records being transfered.
TPT Loads take 14 sessions each, ODBC destination and validation sessions apparently 1 per validation/component.
What could be the reason for this error? Where to look, what to check?
Thanks for any advice!

Sorry the information given doesnt help much to understand the root cause. Anyways something you could do is to set delay validation to true so that actual error you will get at runtime rather than a validation failed message as above. One more thing you
can try is running packages one at a time and see if error occurs. Also see if multiple packages running in parallel are using same object.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

ODBC connections fails after going from Office 2003 to 2010 on some but not all PCs

ODBC connections fails after going from Office 2003 to 2010 on some but not all PCs. Setting up the connection has been a hit and miss. Have tried both x86 and x64. Any ideas? Use ODBC from the control panel and C:\Windows\SysWOW64 same results. Using
SQLexpress 2008r2
Thanks

Hello,
Please consider to configure Windows Firewall or disable it. Not only Windows Firewall but any security software.
https://msdn.microsoft.com/en-us/library/cc646023(v=sql.120).aspx
Windows Firewall is enabled by default.
Make sure you are using SQL Server Native Client to create the ODBC DSN. Not all Windows versions have it, so you may need to download and install it.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

ODBC connection failed (SQL Server Native Client)

Dear ..
I tried to connect to ODBC with SQL Server Native Client 11.0.
It successfully connected in SQL mgmt studio : (LocalDB)\AAA
but when I tried to connect to ODBC, it's failed like below..
[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'KKIKKI\Jinsu'.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "MAPDB" requested by the login. The login failed.
test failed.
How to initialize all of my SQL Native Client and ODBC configuration?
I tried to remove all SQL application, but it's same situation.. Please help..
jinsu

https://www.connectionstrings.com/sql-server-native-client-11-0-odbc-driver/
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog

SSIS job runs in designer but fails in SQL Agent - timeout error

I have several SSIS packages that have been running without issue for well over a year. These jobs were imported into SQL Server and run on a schedule with SQL Agent.
Over the weekend these jobs failed with the message:
Description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. Source: .Net SqlClient Data Provider Started: 8:13:01 AM
Finished: 8:13:31 AM Elapsed: 30.155 seconds. The package execution failed. The step failed.
When I look at the package history it doesn't even show that the job attempted to run over the weekend. As such I assume that the error is related to SQL Agent attempting to connect to the SSIS job.
As stated in the title, the jobs run without issue in the designer.
I did stop and restart SQL to see if that would have an effect - sadly it did not.
I attempted to reload one of the packages. More specifically I re-imported it and allowed it to overwrite the existing project, This step completed ok and moved to the next step - deploy the project. It fails to deploy the project with the following error
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2218&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
Server Name: XXXXXXX
Error Number: -2
Severity: 11
State: 0
Program Location:
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.IntegrationServices.Common.ObjectModel.SqlHelper.ExecuteSQLCommand(SqlStoreConnection storeConnection, CommandType cmdType, String cmdText, SqlParameter[] parameters, ExecuteType execType, Int32 commandTimeout)
   at Microsoft.SqlServer.Management.IntegrationServices.CatalogFolder.DeployProject(String projectName, Byte[] projectStream)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeployExportProjectHelper.DeployProject(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.Deploy(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.DeployProject()
   at Microsoft.SqlServer.IntegrationServices.Deployment.DeployProjectPage.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
===================================
The wait operation timed out
It would seem to me that there is an environmental error, though I know of nothing that has changed. I don't know where to look. If you have seen this behavior before or have an idea, I welcome your input.
Thanks
Mike

Hi Mike,
Based on the error message, we can infer that the issue is caused by connection or command timeout.
To work around this issue, we can increase the connection timeout and command timeout, buffer size and create two indexes in the SSISDB catalog to improve the performance. For more details, please see:
http://capstonebi.blogspot.com/2012/09/ssis-2012-deployment-frustrations.html
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/804901/ssis-2012-deploying-new-versions-of-large-projects-runs-into-a-timeout-during-deployment-into-ssis-catalog
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Data services on Linux to MS SQL ODBC connection

We have DS 4.1 SP2 running on Linux and trying to connect to MS SQL database via odbc. The admin guide tells you to modify the ds_odbc.ini file with an entry like this:
[test_Microsoft_SQL_SERVER]
Driver = <install_location>/lib/libodbc.so
RebrandedLib = TRUE
where install location is location of datadirect ODBC driver. But the problem is there is no libodbc.so in this library. There is a libodc.a file there instead.
Secondly, it also tells us to modify the file referenced by $ODBCINI with the following entry. In my case, ODBCINI also references to ds_odbc.ini under /dataservices/bin folder !!. Also, below it tells you to enter the /lib/DAmsssxx.so file location. But there is no such file under datadirect/lib folder. There is a DAsql25.so instead.
[test_Microsoft_SQL_SERVER]
Driver=<install_location>/lib/[DA][DD]msssxx.so
Description=DataDirect <current version number> SQL Server Wire Protocol
AlternateServers=
AnsiNPW=Yes
ConnectionRetryCount=0
ConnectionRetryDelay=3
Database=<database_name>
EnableQuotedIdentifiers=1
HostName=<SQL_Server_host>
LoadBalancing=0
LogonID=
Password=
PortNumber=<SQL_Server_server_port>
QuotedId=No
ReportCodePageConversionErrors=0
DriverExpirationBehavior=1
What should I do ? which file do I need to modify exactly and with which library ?? I don't have to modify the odbc.ini file at all ??
Do I need to install the Data direct drivers first ?? if so, how ?
Thanks
BV

Hi,
ODBC connectivity from your machine will not help as the connectivity to SQL Server will be established from the job server.
On the connectivity test, can you please check with your Linux admin. You can also refer to the following link for some details.
Links:
http://www.easysoft.com/developer/interfaces/odbc/linux.html
https://wiki.archlinux.org/index.php/Odbc
Can you please check the following link. this is specific to ODBC connectivity for Linux based job server.
Links:
http://wiki.sdn.sap.com/wiki/display/EIM/ODBC+connections+from+a+Linux+%28or+UNIX%29+jobserver
The below is for SQL server based connectivity from Linux.
Links:
http://wiki.sdn.sap.com/wiki/display/EIM/To+configure+DataDirect+ODBC+on+Linux+and+Unix
Or Please refer below thread
Link:
Data Services 4.0 connectivity to SQL Server 2005
Thanks,
Daya

Odbc-connection with ms-access

hello,
this is my problem
if I migrate an MS Access db to Oracle with the OMW than is the ODBC connection, from MS Access to Oracle, perfect.
Bud I have used the migration script witch is generated by OMW and by made a connection from MS Access to Oracle in some tables the ODBC connection Failed.
What is the problem????
Thanks
Andre

You don't need MS Access installed to use the JDBC-ODBC driver.

Issues while readin SQL server via ODBC connection

Hi Experts,
I havea SQL server db as a source. I have configured the Datastore using ODBC connection. Developed a job which simply reads a table and populates into a flat file. when we run the job, it doesnt show any progress, it just stops after a log message "initializing data store, processing job" . I looked at the job logs file on the Job server, its incomplete as well.
One thing is that, im able to see the data when i go under data store and view data option for that particular table. My other jobs works just fine with oracle data base sources. We restarted the BODS server as well, but it doesnt help. Any idea on what might be going on ?.
Thanks for your time.
Regards,
Narayanan

Hi Narayanan ,
There are two steps:
1) Set up the ODBC connection correctly on your Linux server
http://wiki.sdn.sap.com/wiki/display/EIM/ToconfigureDataDirectODBConLinuxand+Unix
(test with isql command line if connection on that server to the SQL Server is working)
2) Select ODBC connection in the datastore and then put the name of the connection you defined. (do not choose Database - SQL Server)
Norbert

SSIS job fails on connection to target db - works in debug

the ongoing saga...
I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package. The website and the instance of SQL Server with the agent and SSIS package are
on the same windows 2008 r2 server. When the button is operated no exceptions are raised but the SSIS package did not execute. The SQL Server Agent job owner is sa ...that seemed to resolve some issues as originally I had the owner being another
admin on the same box. Now the job seems to be failing on connect to the target database on an IBM iSeries DB2 server. The job runs fine in debug connecting to the db and doing its task successfully.
The log indicates that the user specified in the connection manager is using an invalid password or is otherwise unable to connect, although it works fine in debug mode and save password is specified.  I use BIDS remote desktoped to the server
when developing and debuging.
Can anyone show me whats wrong now? Thanks much in advance for any help, Roscoe
The log shows as follows...
The job failed. The Job was invoked by User DOMAINNAME\myuserid. The last step to run was step 1 (Step1).,00:00:00,0,0,,,,0
06/12/2014 13:34:50,runWebDevSmall,Error,1,NTSVR59,runWebDevSmall,Step1,,Executed as user: WINDOWSSERVRNAME\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights
reserved.    Started: 1:34:50 PM Error: 2014-06-12 13:34:50.31     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "DTS:Password"
with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error:
2014-06-12 13:34:50.84     Code: 0xC0202009     Source: vbTestsmall Connection manager "iSeriesname.DBNAME.iSeriesuserid"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE
DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "IBMDA400 Session" Hresult: 0x80004005 Description: "CWBSY0002 - Password for user iSeriesuser on system iSeriesname is not
correct ". End Error Error: 2014-06-12 13:34:50.86     Code: 0xC00291EC     Source: clear iSeriesname libraryname tablename Execute SQL Task     Description: Failed
to acquire connection "iSeriesname.DBNAME.iSeriesuserid". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1).
Started: 1:34:50 PM Finished: 1:34:50 PM Elapsed: 0.703 seconds. The package execution failed. The step failed.,00:00:00,0,0,,,

Hi Arthur, Thanks for the reply,
BIDS would not let me save the package with ProtectionLevel of ServerStorage giving error...
Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.". This error occurs when saving
to Xml.
(vbTestsmall)
...but it would let me change the ProtectionLevel to EncryptSensitiveWithPassword so I did that and provided the jobstep in the agent with the password and the agent was able to run successfully.
Thanks for all the help...I will follow your blog, Roscoe

Sql server agent job failing to connect excel connection manager of SSIS package by 32-bit mode run time

I am unable to succeed with sql agent job, I am trying to execute the SSIS package through sql agent job by ticking 32 bit runtime check box in 64 bit machine , even it does not worked..
could any one helpme on this?
Source: Excel Load Connection manager "Excel Connection Manager"
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 TS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error
messages posted before this with more information on why the AcquireConnection method call failed. End... The package execution fa... The step failed.

Hello Keerthi,
Can you please modify settings and set delay validation for Excel connection manager? I think its validating connection and failing because it might be picking that from some variable.
Alternatively, please run package using below and see what happens.
EXEC master..xp_cmdshell 'DTEXEC.exe /SQL "Folder\Package" /SERVER Servername'
I will recommend you to follow steps in below link.
http://www.sqlhammer.com/blog/running-ssis-packages-in-32-bit/
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

Connection failed: SQLState:'01000' SQL Server Error:67 [Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState:'08001' SQL Server Error:17 [Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist o

Help,
setup a new sql server 2012 on a windows 2012r2 server to replace old sql server 2005 on an old windows server 2003 machine. When i test the ODBC connection locally on the server it works fine, however when i try to connect via windows 7 client machine
i get the following error:
Connection failed:
SQLState:'01000'
SQL Server Error:67
[Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState:'08001'
SQL Server Error:17
[Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied
I think it must be a permissions thing, I've turned off the firewall for now and still no difference, 've also made sure remote connection is enabled. I can connect to the other sql server in studio manager on the new machine however, i can't go do
the same in the old server, says:
cannot connect to hbfsqlpro1\hbfsqlpro1
Additonal information a network related or instance specifc error occured while establising a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL server is configured to
allow remote connections. (provider:SQL Network Interfaces, error 26 - error locationg server/instance specified) (Microsoft SQL server)
the instance is def correct, as that is what i use to connect locally on the new machine and what it comes up on the studio manager on the new machine. STarting to pull my hair out somewhat, i'm sure it's something really simple!

Hello,
You are trying to connect to a named instance. Make sure the SQL Server Browser service is started on the SQL Server computer.
Make sure TCP/IP is enabled.
http://msdn.microsoft.com/en-us/library/ms191294(v=sql.110).aspx
Try to disable Windows Firewall or security software on both, SQL Server instance and client computer.
Test basic connectivity too. Try to ping from the client computer to the SQL Server computer.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

ODBC--connection to 'SQL Serverservername' failed for one user but not another

In Win7, we're linking tables in an MS Access 2010 db to tables in a SQL Server 2008 R2 db. The driver user by the File dsn is SQL Server version 6.01.7601.17514 & we're using SQL Server Authentication.
For some reason, one user gets the msg "ODBC--connection to 'SQL Serverservername' failed" before they're even asked for a password, but for other users, the prompt comes up and when they uncheck the Windows Auth box, they enter their password
and connect successfully to the SQL Server db. Both users have db_datareader access to the SQL Server db.
I had the user that gets the error msg log onto my PC and they get the same error (yet it works for me.)
This user was, however, able to successfully relink the tables, but then when we closed the access db and opened it again, the user got the "ODBC--connection..." error agin.
I'm stumped as to why this is happening for one user.

Hello Knellen,
Please help to collect more log information regarding this issue, such as windows event log, SQL Sever log information. They are helpful for us to troubleshoot it.
Regards,
Elvis Long
TechNet Community Support

OWB connection to teradata through ODBC driver

Hi:
I am seeking answers to my OWB connection settings. I have installed OWB 10.2.0.4 on Windows 2003 server. The Oracle 10g database is on the same server. Right now, I want to configure ODBC connection for OWB to source database (all on teradata) on my windows 2003 server. However, I found from control panel
/Adminstrative tool/Data source (ODBC), there is no teradata driver in ODBC administrator. (It is available on windows XP). How can I solve this problem?
OWB perform ETL workflow through OWB server and source database. The connection between OWB server and source database must be set up. If no teradata ODBC driver, is there any other way to work around. Or should I update windows 2003 server to patch teradata ODBC driver to it? Please give me your idea and your thoughts. Thanks in advance.

Hi,
look at this thread
SQLServer access from AIX Warehouse builder
What is the problem with installing Teradata ODBC driver to your Windows2003 server?
Regards,
Oleg

Connecting to Teradata with ODBC

Hi,
Has anyone work with Teradata with Oracle ODBC?
Thanks,
Mustafa

Oracle's ODBC driver is only appropriate for connecting to an Oracle database. If you need to establish and ODBC connection to a Teradata database, you would need to get a Teradata ODBC driver.
Justin

Visio Database Wizard fails - ODBC connection to MS SQL

When I try to create an ODBC connection in Visio's 2010's Database wizard I get the error: "Cannot set the database context information. Additional error information:ODBC Error: s1009. Database cxweba does not exist."
Note that the database name is cxwebapp_bkk. I get the same error if I connect to any database on that server, and it always truncates the name in the error message (if that is a hint to the error).
Using Visio 2013, after connecting to the database: when I select the database object I get the error message: "The selected table has only one field or contains no definition information. The Database Wizard requires a minimum of one key field
and one additional data field."
I have this problem using both SQL Server driver (6.02.9200.116384 and SQL Server Native Client 11.0 (2011.1102.2100.60).
I do not have this problem connecting to a MYSQL database with either version of Visio, nor do I have this problem when I link link to the same SQL database in a drawing and link shapes in that drawing using the "Link Data to Shapes" under the
Data tab.

Hello,
What's the version of the SQL Server instance you connect to? It seems that the Database Wizard in Visio 2010 not work well with the Microsoft SQL Server ODBC driver. Did you try to use the Generic OLEDB Provider for SQL Server?
Since the issue is more related to office Visio, please post the question in the following forum. More experts there will assist you:
Visio General Questions and Answers for IT Professionals
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

[Flat File Destination [220]] Error: Failed to write out column name for column "Column 2"

I am using SSIS to extract fixed width data into a flat file destination and I keep getting below error. I have tried almost everything in this forum but still no solution. can anyone help me out to solve this problem.
[Flat File Destination [220]] Error: Failed to write out column name for column "Column 2".
[SSIS.Pipeline] Error: component "Flat File Destination" (220) failed the pre-execute phase and returned error code 0xC0202095
Thanks

Hi Giss68,
Could you check the Advanced tab of the Flat File Connection Manager to see whether the InputColumnWidth and the OutputColumnWidth properties of the Column2 has the same value? Please refer to the following link about the same topic:
http://stackoverflow.com/questions/10292091/how-do-i-fix-failed-to-write-error-while-exporting-data-to-ragged-right-flat-fil
If it doesn’t work, please post the sample data and the advanced settings of Column2 for further analysis.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

Teradata destination ODBC connections failing in SSIS job

Similar Messages

Maybe you are looking for