Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SSIS and Import/Export (2005)
 64 bit SQL Server and Access

Author  Topic 

Van
Constraint Violating Yak Guru

462 Posts

Posted - 2007-10-04 : 15:18:09
I've created an SSIS package that imports data from Access. I've done it connecting to Access as OLEDB and specified the Access db path and name. I've done it using a DSN through ODBC as well. It works fine either way when running on my pc (Windows XP) but as soon as I deploy it to the SQL Server and run it from there, there are problems. The reason I think is because the server is 64 bit and there are no Access ODBC drivers installed. It gives me an error when running from the server that DSN not found or drivers not installed. I had copied the dsn (file system dsn) to the server and put it under ProgramFiles\CommonFiles\ODBC\DataSources and it showed up unter the gui Data Sources in Administrative Tools. But it gives an error if you try to configure it (since there are no Access drivers installed). Even using the OLEDB connection in SSIS and specifying the db path and name doesn't work...I get some error about Class not registered. I also tried ADO.Net ODBC as well.

So how can I set up an SSIS package to import from Access when the SQL Server it will be running from (and has to run from) is 64 bit. As I understand it, there is no 64 bit ODBC Access drivers out there to even install.

Please help.

Thanks,

Van

Van
Constraint Violating Yak Guru

462 Posts

Posted - 2007-10-04 : 16:04:33
Come on y'all, surely some of you have ran into this or know about it. How do I import from Access through SSIS on a 64 bit SQL Server since there are no 64-bit Access drivers available. Install the 32 bit Access drivers and hope it works?
Go to Top of Page

Van
Constraint Violating Yak Guru

462 Posts

Posted - 2007-10-05 : 11:26:19
Found a fix. You can go into the SSIS Project Properties and set the Run64BitRuntime value to false and then use the 32 bit version of dtexec to run the package.
Go to Top of Page
   

- Advertisement -