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

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.

rsmucklesAsked:
Who is Participating?
 
Mark WillsConnect With a Mentor Topic AdvisorCommented:
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
 
PedroCGDCommented:
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
 
Mark WillsTopic AdvisorCommented:
And here is a great comment from Brian Nights blog (MVP) - see some of the comments that follow as well...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.