Solved

Errors when pulling data from MS Access into Sql Server 2005 database using Visual Studio

Posted on 2008-10-03
3
548 Views
Last Modified: 2013-11-30
I'm working on a 64 bit server and have tried setting up a package to pull in data from an access database into sql server 2005.  I set up my source connection as  oledb and the access database file name and path is in the database file name box.  When I test the source connection it works perfectly.  Same with the destination.  The data flow task has the source and the destination - I can see the columns and the mapping works fine.  When I execute the task the package fails with the following error at the source.


Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.

Any ideas?  Thanks as always for your help.

0
Comment
Question by:rsmuckles
  • 2
3 Comments
 
LVL 22

Expert Comment

by:PedroCGD
Comment Utility
in 64 bits machines there is always some strange things happening...
your package is not making the connection to the source... do you have ODBC connections?
Try to execute the SSIS package as 32 bits... and check if the error still ocurr...
Regards!!
0
 
LVL 51

Accepted Solution

by:
Mark Wills earned 500 total points
Comment Utility
In fact, would definitely be running SSIS as 32-bit...

Well, possibly the above opener was a bit strong... It really depends a bit on some of the features, but until the upgrades (and keep a watch), then 32-bit is probably a lot more reliable as a general experience. For a general comment, see : http://msdn.microsoft.com/en-us/library/ms141766(SQL.90).aspx

Now, if what you are doing is via BI studio, then there is a small extra problem in so much as BI studio will not support 32-bit binaries on a 64 bit machine... see: http://ssis.wik.is/64-bit_Story

When testing and running using the Execute Package Utility (dtexecui.exe) it is in fact 32 bit, but dtexec has both the 32bit and 64bit. Either that, or, there is also the difference in privilege / profile and security between SSMS and SQl Server Agent and agentservices - so may need to check thos profiles. see: http://msdn.microsoft.com/en-us/library/ms178142(SQL.90).aspx


0
 
LVL 51

Expert Comment

by:Mark Wills
Comment Utility
And here is a great comment from Brian Nights blog (MVP) - see some of the comments that follow as well...
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Nowadays, some of developer are too much worried about data. Who is using data, who is updating it etc. etc. Because, data is more costlier in term of money and information. So security of data is focusing concern in days. Lets' understand the Au…
Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Via a live example, show how to setup several different housekeeping processes for a SQL Server.
Viewers will learn how the fundamental information of how to create a table.

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

7 Experts available now in Live!

Get 1:1 Help Now