SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


ssis 2012 package


ssis 2012 package

Author
Message
Jon Jaroska
Jon Jaroska
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 26
I have successfully deployed my first package to sql 2012. The package runs fine in visual studio but when deployed it gets an error message saying there was an error trying to establish an odbc connection to the database. Anybody encounter this and does anybody have a solution?
robert.gerald.taylor
robert.gerald.taylor
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1808 Visits: 1493
Jon Jaroska (12/26/2012)
I have successfully deployed my first package to sql 2012. The package runs fine in visual studio but when deployed it gets an error message saying there was an error trying to establish an odbc connection to the database. Anybody encounter this and does anybody have a solution?

I've not done much yet with SSIS 2012, but here are questions that immediately come to mind: Are you running Visual Studio on your development machine? Do you have a DSN setup to the DB on your development machine? Is this same DSN setup on the server where you deployed the SSIS package? Does the account that the SSIS package run on the server have permissions to the database?

I hope this helps,
Rob
Jon Jaroska
Jon Jaroska
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 26
Visual studio is installed on the server where sql server resides. The DSN is setup on the machine and running the package in debug mode works. I have to assume that permissions are correct because it runs this way.
robert.gerald.taylor
robert.gerald.taylor
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1808 Visits: 1493
Jon Jaroska (12/27/2012)
Visual studio is installed on the server where sql server resides. The DSN is setup on the machine and running the package in debug mode works. I have to assume that permissions are correct because it runs this way.

Well no luck there. Hmm -- any reason you're using ODBC rather than an OLE DB provider? What is the data source you're connecting to?

Rob
Jon Jaroska
Jon Jaroska
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 26
Its PostgreSQL
robert.gerald.taylor
robert.gerald.taylor
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1808 Visits: 1493
There does appear to be OLEDB providers for PostgreSQL ( http://www.postgresql.org/about/news/1153/ ), but that doesn't answer your immediate question. Sorry I couldn't be more help.

Rob
Phil Parkin
Phil Parkin
SSCoach
SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)

Group: General Forum Members
Points: 18810 Visits: 20459
Jon Jaroska (12/26/2012)
I have successfully deployed my first package to sql 2012. The package runs fine in visual studio but when deployed it gets an error message saying there was an error trying to establish an odbc connection to the database. Anybody encounter this and does anybody have a solution?


Did the package run as a SQL Agent job?

Can you post the full text of the error message?

As you have VS installed on the server, can you confirm that you can run the package using BIDS on the server? If so, I would be looking at possible permissions issues first.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Jon Jaroska
Jon Jaroska
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 26
The package does not run in the sql agent, it fails. Also the package runs perfect in BIDS. Here is the full text of the error:

There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.

The AcquireConnection method call to the connection manager glxy_epace.epace_read failed with error code 0xC0014009.
Phil Parkin
Phil Parkin
SSCoach
SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)

Group: General Forum Members
Points: 18810 Visits: 20459
Jon Jaroska (12/28/2012)
The package does not run in the sql agent, it fails. Also the package runs perfect in BIDS. Here is the full text of the error:

There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.

The AcquireConnection method call to the connection manager glxy_epace.epace_read failed with error code 0xC0014009.


OK - but I asked whether the package ran in BIDS on the server.

Can you try logging in as the user under which the SQL Agent service is running and then executing the package in BIDS again (on the server)?


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
nick.mcdermaid
nick.mcdermaid
Old Hand
Old Hand (398 reputation)Old Hand (398 reputation)Old Hand (398 reputation)Old Hand (398 reputation)Old Hand (398 reputation)Old Hand (398 reputation)Old Hand (398 reputation)Old Hand (398 reputation)

Group: General Forum Members
Points: 398 Visits: 778
The problem could be that you don't have 64 bit drivers installed. Packages run in BIDS as a 32 bit process (last time I used it), which can only 'see' the 32 bit hive of the registry (containing DSN's)

Then if you run the package in 64 bit (which is generally the default under SQL Agent), the process only see the 64 bit hive of thre registry, which does not contain your DSN (or driver).

So try running the package in 32 but mode. Here's a link that may help.

http://sqlblog.com/blogs/john_paul_cook/archive/2010/03/24/running-32-bit-ssis-in-a-64-bit-environment.aspx

None of the clues you have given actually indicate this issue but it's the first thing I thought of when I saw your error message.


If you could post more information about your configuration it would help everyone.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search