Alex Fenech
Alex Fenech

Reputation: 35

SQL Server Import Wizard, Access Database Engine

There have been questions asked similar to this but I've tried every solution I've come across in 3 straight days of chasing this issue and I can't figure it out.

This started with me not being able to import .xlsx files in the import wizard; I got the error noted here, "The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine." I tried uninstalling all Microsoft Development, Microsoft SQL, Microsoft Server, and MS Office products from my machine then re-installing only those that I use (I was initially getting some errors because I had both 32 and 64 bit applications on my machine).

When I continued getting the Microsoft.ACE.OLEDB.12.0 error, I tried installing every Access Database Engine I could find including:

All of them still produced the same error except the oldest ones. However, all the ones that work then lead to this type of behavior. When I get to the point where I can upload a spreadsheet, it starts normal:

enter image description here

But as soon as I click the Next button, it doesn't render correctly. This only happens when doing an Excel file.

enter image description here

Any assistance or guidance would be greatly appreciated. Running:

SQL Server Management Studio 17.5

Access Database Engine 2010 Redistribute (the others still resulted in the Microsoft.ACE.OLEDB.12.0 error)

Surface Book

Windows 10 Pro, 64 bit

Upvotes: 0

Views: 780

Answers (2)

Alex Fenech
Alex Fenech

Reputation: 35

In case anyone stumbles upon this, I found the issue. The rendering dpi issue only occurs when running 64 bit office applications with the Access Database Engine. If you have 32 bit applications (and the Access Database Engine), it will render the dpi correctly and flow with no issues.

Upvotes: 0

Sandy Winarko-MSFT
Sandy Winarko-MSFT

Reputation: 81

Sorry about this, we're aware of this issue, but unfortunately SSIS product (including I/E wizard) in general doesn’t currently support high DPI mode, so we’ll plan to fix this in the future with ETA still TBD. As a workaround, you could try to adjust your screen resolution lower for now.

Upvotes: 1

Related Questions