December 26, 2012 at 10:25 am
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?
December 26, 2012 at 10:45 pm
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
December 27, 2012 at 7:48 am
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.
December 27, 2012 at 7:55 am
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
December 27, 2012 at 8:32 am
Its PostgreSQL
December 27, 2012 at 11:50 am
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
December 28, 2012 at 2:13 am
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.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
December 28, 2012 at 8:33 am
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.
December 28, 2012 at 9:12 am
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)?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
December 31, 2012 at 6:01 pm
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.
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.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply