July 28, 2013 at 11:27 am
I have a simple SSIS package that uses and odbc connection using a dl4 driver connection. It works fine in Bids but when I try to execute through a job or through the ssis store it fails. I get the following error:
Code: 0xC0047062 Source: Data Flow Task 1 Source - Query [1] Description: Microsoft.SqlServer.Dts.Runtime.DtsCouldNotCreateManagedConnectionException: Could not create a managed connection manager. at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction) at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction) End Error Error: 2013-07-28 09:56:03.77 Code: 0xC0047017 Source: Data Flow Task 1 SSIS.Pipeline Description: component "Source - Query" (1) failed validation and returned error code 0x80131500. End Error Error: 2013-07-28 09:56:03.77 Code: 0xC004700C Source: Data Flow Task 1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2013-07-28 09:56:03.77 Code: 0xC0024107 Source: Data Flow Task 1 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:56:03 AM Finished: 9:56:03 AM Elapsed: 0.235 seconds. The package execution failed. The step failed.
Can anyone help?
July 28, 2013 at 1:20 pm
Are the dL4 drivers installed on the server?
If yes, then is your server 64-bit? If so, are your dL4 drivers 32-bit or 64-bit drivers?
If 32-bit, make sure you're Agent job is using the 32-bit runtime and not the 64-bit runtime?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 28, 2013 at 1:26 pm
The driver is installed on the server. I tried the 32 bit vs the 64 bit. Neither of those seem to be the issue
July 28, 2013 at 2:14 pm
Is the dL4 server reachable from your SQL Server, networking-wise? If your design time server is not and you are using a Package Configuration make sure you have DelayValidation set to true on your Connection Manager or a higher-level container.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 28, 2013 at 9:00 pm
I tried delaying the validation and still getting the same error.
July 28, 2013 at 9:24 pm
Verify network connectivity?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 30, 2013 at 5:37 pm
Its running over vpn to the customers server from our datacenter.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply