Intermittent ole db error

I have this problem occuring intermittently:

When I try to add a package to the project, and click on the Package path button. I get a oledb error x080004005 (client unable to establish connection)...

After I click ok, and click on the Package path again 2 or 3 times, the error goes away and I get the list of packages displayed. Some time I get an empty list box.

Similar to this happens when I execute a package also. When I execute it 2nd or 3 rd time it works fine. The error happens only when I am trying to connect to the server\database. Once it is in the database I do not get any error message.

This is what I have:

I have sql 2005 installed.

Microsoft SQL Server Management Studio 9.00.1399.00

Microsoft Analysis Services Client Tools2005.090.1399.00

Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)

Thank you in advance!!!

Well, what database are you connecting to in your OLE DB connector?|||It should be the msdb database since the ssis packages reside there, right?|||No. What source database are you getting your data from in the data flow?|||

Let me clarify:

I have a project. From the solution explorer window, I right click on "SSIS Packages" and choose "Add Existing Package".

In the window that pops I choose "SQL server" for the "Package Location" and I choose my server name for the "server" and when I click on the button next to the "Package path" I get intermittent ole db errors.

Some times I do not get errors and the list of packages get displayed. Some times it takes one, two or three tries and then I get the list.

Again Thanks for your help.

|||Yes, but what the data flow looks like...what Databases is the apckage using as Source and destination. Also provide the full errror message.|||

There are many packages(about 20) in the server and each package uses different databases in that server. In the problem I explained before I have not yet connected to any package. I am just trying to add a package to my project.

For Example, some package is used to bulk insert a file to a table and for that package source is the "flat file" and the destination is a "Native ole db\sql native client". Again, my problem is not executing the package. The intermittent problem is adding the package to my project.

Thank you.

intermittent OLE DB error

I have this problem occuring intermittently:

When I try to add a package to the project, and click on the Package
path button. I get a oledb error x080004005 (client unable to
establish connection)...

After I click ok, and click on the Package path again 2 or 3 times,
the error goes away and I get the list of packages displayed. Some
time I get an empty list box.

Similar to this happens when I execute a package also. When I execute
it 2nd or 3 rd time it works fine. The error happens only when I am
trying to connect to the server\database. Once it is in the database
I do not get any error message.

This is what I have:

I have sql 2005 installed.

Microsoft SQL Server Management
Studio
9.00.1399.00

Microsoft Analysis Services Client
Tools
2005.090.1399.00

Microsoft Data Access Components
(MDAC)
2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)

Thank you in advance!!!(gelangov@.hotmail.com) writes:

Quote:

Originally Posted by

After I click ok, and click on the Package path again 2 or 3 times,
the error goes away and I get the list of packages displayed. Some
time I get an empty list box.
>
Similar to this happens when I execute a package also. When I execute
it 2nd or 3 rd time it works fine. The error happens only when I am
trying to connect to the server\database. Once it is in the database
I do not get any error message.

I have no idea what this may be. However, I noted one thing:

Quote:

Originally Posted by

I have sql 2005 installed.
>
Microsoft SQL Server Management
Studio
9.00.1399.00
>
Microsoft Analysis Services Client
Tools
2005.090.1399.00

This is the RTM version of SQL 2005. There is an SP1 out. There is also an
SP2 in progress, currently a preview of SP2 is available. I would recommend
that you download an install SP1, and that you keep an eye open for the
release of SP2. No promises that it will resolve your problem, though.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thank you, Erland...I will try that!

On Jan 29, 6:07 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:

Quote:

Originally Posted by

(gelan...@.hotmail.com) writes:

Quote:

Originally Posted by

After I click ok, and click on the Package path again 2 or 3 times,
the error goes away and I get the list of packages displayed. Some
time I get an empty list box.

>

Quote:

Originally Posted by

Similar to this happens when I execute a package also. When I execute
it 2nd or 3 rd time it works fine. The error happens only when I am
trying to connect to the server\database. Once it is in the database
I do not get any error message.I have no idea what this may be. However, I noted one thing:

>

Quote:

Originally Posted by

I have sql 2005 installed.

>

Quote:

Originally Posted by

Microsoft SQL Server Management
Studio
9.00.1399.00

>

Quote:

Originally Posted by

Microsoft Analysis Services Client
Tools
2005.090.1399.00This is the RTM version of SQL 2005. There is an SP1 out. There is also an

SP2 in progress, currently a preview of SP2 is available. I would recommend
that you download an install SP1, and that you keep an eye open for the
release of SP2. No promises that it will resolve your problem, though.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Integration Services and Teradata as source

Hi All,

Please let me know whether we can use Teradata as Source in SSIS (Target is SQL Server 2005). ie. Do we have oledb driver for NCR Teradata to connect to it. Our SSIS will be hosted in 64 bit SQL, but for development we use 32 bit.

Any inputs is really appreciated.

Regards, kart

NCR provide an OLE-DB provider, so I would guess that would be your first option. Saying that I do not know if it supported within SSIS, not all providers are, you need a minimum set of features to be implemented in the provider, and implemented correctly according to the specification. Give it a try.

ETI also produce a SSIS connector for Teradata which may be worth a look-

ETI - High Performance Data Integration
(http://www.eti.com/microsoft/)

|||

There are various ways to conneto to Teradata. Their OleDB provider supports both 32 and 64 bit. They also have a new .NET provider, though I'm not sure how good it works with SSIS.

iWay has also Teradata providers (OleDB, ODBC) which could be used.

One thing to note here is that Teradata providers do not support Commands, though they support tables and views. As a workaround, some of our users use linked server in SQL 2005 and got the Commands working that way.

You can also check our young but improving connectivity portal for Teradata and other data sources : http://ssis.wiki.com/Data_Sources

|||

HI Deniz and Daren,

Thanks for the info.

It would be helpful to me if you could provide some inputs on Cost Factor w.r.t ETI and iWay and any other implementation details. I assume, using ETI/iWay connectors is a better approach than using OLEDB Driver provided by NCR - as these improve the access performance.

Regards

Kart

|||

Kart, I think it would be better if you did the research. I don’t know your business requirements, technical constraints, your budget, or quantities you would require, all of which may effect the cost and eventual product selection process. Talk to the suppliers and find out what they can do for you.

|||

We am trying to use the OLEDB provider from Teradata for SSIS and running into the following issues

We are able to connect to the Teradata database using the drivers. When we use the import wizard, the authentication screen into Teradata takes about 5 minutes to return. The screen that brings back the list of tables in Teradata to select from takes about half an hour to come back. The screen after that for mappings also takes a very long time to come back.

So, as you can see, every action on the wizard is taking way too long to come back and we are unable to complete the most basic package creation. We tried to manually create the package as well without using the wizard. Even that takes a long time to come back with the list of tables to select from.

Are there any such known issues with using the Teradata drivers with SSIS. This is making development impossible with Teradata OLEDB Drivers.