November 14, 2017 at 10:15 am
Hi,
I am trying to connect to excel source but its throwing connection error. After googling it suggested my system might not have ACE driver installed. I checked it and it is.
W hen I try to run the Microsoft Access Database Engine (2012) 64 bit, all it does is to take me to repair mode .
Please suggest me what options can I try.
Thanks,
Bulbul
November 14, 2017 at 10:37 am
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
November 14, 2017 at 11:05 am
Ahh, the bane in our side that is the "ACE" drivers.
What version of SSIS are you using? When you're executing the package, how are you doing so, and are you running it in 32 bit compatibility or not?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 15, 2017 at 5:46 am
November 15, 2017 at 10:07 am
Hi Phil
Microsoft SQL Server Integration Services Designer
Version 14.0.600.250.
November 15, 2017 at 10:08 am
Hi SQL Surfer '66 ,
Would that mean uninstallation of 64 bit.
Thanks,
SQLSniffer
November 17, 2017 at 2:54 am
Phil Parkin - Tuesday, November 14, 2017 10:37 AMComment deleted
Hi Phil
Microsoft SQL Server Integration Services Designer
Version 14.0.600.250.
November 17, 2017 at 2:56 am
SQL Surfer '66 - Wednesday, November 15, 2017 5:46 AMIf you're running into to the connection error in Data Tools (SSDT) you also need to install Access Database Engine 32-bit.
Hi,
I checked out, and I have 32 bit ACE installed and my windows is 64 bit.
Thanks,
SQLSniffer
November 17, 2017 at 3:02 am
sqlsniffer - Friday, November 17, 2017 2:54 AMPhil Parkin - Tuesday, November 14, 2017 10:37 AMComment deletedHi Phil
Microsoft SQL Server Integration Services Designer
Version 14.0.600.250.
That's not SSIS, That's the version of SSDT you have installed (SSDT 2015). I'm not running SQL Server 2017 because I have SSMS 2017 installed (I'm running SQL Server 2012).
Can I thus assume that you're running this locally, and not on your Server? Also, you can,safely have both the 32 bit and 64 bit ACE drivers installed. You'll also then need to run your package/project in 32 bit mode.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 17, 2017 at 3:03 am
sqlsniffer - Friday, November 17, 2017 2:56 AMHi,
I checked out, and I have 32 bit ACE installed and my windows is 64 bit.Thanks,
SQLSniffer
This was posted after i loaded the page. Are you, therefore, running your package/project in 32bit mode if you have the 32 bit ACE drivers installed?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 17, 2017 at 3:26 am
sqlsniffer - Wednesday, November 15, 2017 10:08 AM
No, it does not mean uninstallation of 64-bit but 32-bit is also required because your development environment (SSDT) is 32 bit.
November 17, 2017 at 3:47 am
Just want to share few comments might help the OP
If you are running in your ssis package in the Designer mode i.e. in SSDT then you need to make sure you have 32 bit ACE driver. Doesn't matter if you are using a 64 bit OS.
If you want to run your ssis package using DTEXE Utility and your OS is 64 bit, then you have two option whether to run in 32 bit or you want to run it in 64 bit.
For more detail you can refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Hope it helps.
November 17, 2017 at 4:26 am
twin.devil - Friday, November 17, 2017 3:47 AMJust want to share few comments might help the OPIf you are running in your ssis package in the Designer mode i.e. in SSDT then you need to make sure you have 32 bit ACE driver. Doesn't matter if you are using a 64 bit OS.
If you want to run your ssis package using DTEXE Utility and your OS is 64 bit, then you have two option whether to run in 32 bit or you want to run it in 64 bit.For more detail you can refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Hope it helps.
Running on designer environment, checked that I have 32 bit ACE driver installed.(but office is not installed), I am not using the DTEXE utility. Still it throws the same error.
November 17, 2017 at 4:33 am
sqlsniffer - Friday, November 17, 2017 4:26 AMtwin.devil - Friday, November 17, 2017 3:47 AMJust want to share few comments might help the OPIf you are running in your ssis package in the Designer mode i.e. in SSDT then you need to make sure you have 32 bit ACE driver. Doesn't matter if you are using a 64 bit OS.
If you want to run your ssis package using DTEXE Utility and your OS is 64 bit, then you have two option whether to run in 32 bit or you want to run it in 64 bit.For more detail you can refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Hope it helps.
Running on designer environment, checked that I have 32 bit ACE driver installed.(but office is not installed), I am not using the DTEXE utility. Still it throws the same error.
But are you running the package in 32bit mode...? If you only have the 32 drivers install, and just using DTExec then you'll likely trying to run it as a 64 bit package.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 17, 2017 at 4:37 am
Thom A - Friday, November 17, 2017 4:33 AMsqlsniffer - Friday, November 17, 2017 4:26 AMtwin.devil - Friday, November 17, 2017 3:47 AMJust want to share few comments might help the OPIf you are running in your ssis package in the Designer mode i.e. in SSDT then you need to make sure you have 32 bit ACE driver. Doesn't matter if you are using a 64 bit OS.
If you want to run your ssis package using DTEXE Utility and your OS is 64 bit, then you have two option whether to run in 32 bit or you want to run it in 64 bit.For more detail you can refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Hope it helps.
Running on designer environment, checked that I have 32 bit ACE driver installed.(but office is not installed), I am not using the DTEXE utility. Still it throws the same error.
But are you running the package in 32bit mode...? If you only have the 32 drivers install, and just using DTExec then you'll likely trying to run it as a 64 bit package.
I have set my Run64BitRuntime to False
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply