Connecting Execute SQL Task with Firebird Connection Manager

Hi,

I'm using Integration Service between Firebird and MS SQL 2005. I can able to move data from Firebird db tables to MS SQL db tables using DataReader source (Firebird Connection Manager) and SQL Server Destination (SQL Server Connection Manager) component.

Now I want to execute parametrized SQL statement to fetch data from Firebird DB using Execute SQL Task Component. In this process while trying to set Connection property to this component I can able to view only MS SQL Connection Manager and it is not listing Firebird Connection Manager.

Now I need a help to get connect this Execute SQL Task component with Firebird connection Manager. Help me to find out where I'm making mistake.

FYI. I'm using Firebird .Net Provieder 2.0.1
Thanks in advance.

Suku

More clarification on my query

Here, the mentioned Firebird Connection Manager is a custom created connection manager and we created using Firebird .Net Provider 2.0.1

I tried with Lookup component too, it shows only the destination connection Manager (MS SQL) but not the Source one (Firebird Custom Connection Manager).

Suku

|||

Could you try to set the connection type to Ado .NET in the Execute SQL Task UI?

Lookup can only use OLE DB connections not Ado .NET.

Thanks.

|||

Hi,

Were you able to resolve this issue? I also have a custom connection manager that I am trying to use from Execute SQL Task. Unfortunatelly I don't see my connection object in Execute SQL Task Editor, though it gets added as a new connection successfully. My custom connection manager is basically a very simplified version of the Microsoft's SqlConnectionManager Sample. I am trying to make a custom connection manager which will hide the login info.

Thanks!

Connecting Execute SQL Task with Custom Connection Manager

Hi,

I'm using Integration Service between Firebird and MS SQL 2005. I can able to move data from Firebird db tables to MS SQL db tables using DataReader source (Firebird Connection Manager) and SQL Server Destination (SQL Server Connection Manager) component.

Now I want to execute parametrized SQL statement to fetch data from Firebird DB using Execute SQL Task Component. In this process while trying to set Connection property to this component I can able to view only MS SQL Connection Manager and it is not listing Firebird Connection Manager.

Now I need a help to get connect this Execute SQL Task component with Firebird connection Manager. Help me to find out where I'm making mistake.

FYI. I'm using Firebird .Net Provieder 2.0.1
Thanks in advance.

Suku

More clarification on my query

Here, the mentioned Firebird Connection Manager is a custom created connection manager and we created using Firebird .Net Provider 2.0.1

I tried with Lookup component too, it shows only the destination connection Manager (MS SQL) but not the Source one (Firebird Custom Connection Manager).

Suku

|||

Could you try to set the connection type to Ado .NET in the Execute SQL Task UI?

Lookup can only use OLE DB connections not Ado .NET.

Thanks.

|||

Hi,

Were you able to resolve this issue? I also have a custom connection manager that I am trying to use from Execute SQL Task. Unfortunatelly I don't see my connection object in Execute SQL Task Editor, though it gets added as a new connection successfully. My custom connection manager is basically a very simplified version of the Microsoft's SqlConnectionManager Sample. I am trying to make a custom connection manager which will hide the login info.

Thanks!

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem