February 18, 2009 at 8:06 am
Issue: importing Access table into SQL
Works on 32 bit server Not on 64 bit server
I have created a job to import information from Access to SQL using the access driver and it works great on a 32 bit system. However, it needs to work on a 64 bit system.
The driver does exist on: C:\Windows\SysWOW64\odbcad32.exe
The driver does NOT exist on: C:\Windows\System32\odbcad32.exe
How do I utilize the 32 bit driver?
Thanks in Advance, this is urgent.
February 18, 2009 at 8:08 am
(C:\Windows\SysWOW64\odbcad32.exe)
That is the driver you need and you will find it in that location because Acess comes only in 32bits.
Kind regards,
Gift Peddie
February 18, 2009 at 8:11 am
Right, I know I need this driver, but how do I specify this driver so the job will work?
February 18, 2009 at 8:26 am
Any ideas? Lets just throw some stuff out there. I have got to figure this out, and who to better ask than the experts. 🙂
February 18, 2009 at 8:35 am
(To setup DSN for 32-bit application you must use:
%WINDIR%\SysWOW64\odbcad32.exe)
The above is how you setup DSN and the thread below shows how to make sure your SSIS package is x86, read my last post in the thread below to make sure your package is x86. And no I don't know how to just run your table as a job.
http://qa.sqlservercentral.com/Forums/Topic652827-391-1.aspx#bm654978
Kind regards,
Gift Peddie
February 18, 2009 at 8:40 am
To use the 32 bit driver, you must run the SSIS package via the 32 bit DTExec. On SQL 2005, this means you have to use a command line job step (not an SSIS job step) and call the 32 bit DTExec with the apporpriate command line parameters.
In SQL 2008, there is a checkbox in the SSIS job step dialog.
February 18, 2009 at 9:03 am
So i imported my task in to BI. I changed the project 64 thing to FALSE.
I clicked to debug and have this error on a perfectly fine package.
The error is attached.
February 18, 2009 at 9:14 am
That error is not related to 32bits or 64bits but rather security, wrong connection string and provider like using JET for Access 2007 database.
Kind regards,
Gift Peddie
February 18, 2009 at 9:19 am
I am using access 2003. The DB is not password protected. The ssis package is password protected, but when i open it in BI it requires a password that I type in and it accepts.
February 18, 2009 at 9:27 am
Password protection and related errors are covered below, the reason is related to the context your debug run was executed.
http://support.microsoft.com/kb/918760
Kind regards,
Gift Peddie
February 18, 2009 at 10:10 am
I don't think it is credentials. It works on 32 but not 64.
February 18, 2009 at 10:23 am
You have a platform problem so you need to start a new project native to the x64 Win2003 and use the WOW64 directory and all the features needed to run a 32bits package and your code will run.
That is don't import existing 32bits package with password to the 64bits box and you will know why you have the error based on the steps taken before your error.
Kind regards,
Gift Peddie
February 18, 2009 at 10:25 am
ok. That makes sense, but how do I create an SSIS package on a 64 bit server and utilize 32 bit.
February 18, 2009 at 10:38 am
I just checked my 2005 BIDs there is place for you to add the x86 DSN I posted and use the steps posted by the other user relevant to 2005.
Kind regards,
Gift Peddie
February 18, 2009 at 10:56 am
Do you know where that location is?
Viewing 15 posts - 1 through 15 (of 33 total)
You must be logged in to reply to this topic. Login to reply