Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 186
  • Last Modified:

SSMA Error while trying to migrate Access to SQL

I'm trying to use the SQL Server Migration Assistant.

I've got an Access 2010 database (32-bit Access software running).
Computer is running 64-bit version of Windows.
I've tried the 32-bit and 64-bit version of SSMA.

Always get the error:

Retrieving the COM class factory for component with CLSID {CD7791B9-43FD-42C5-AE42-8DD2811F0419} failed due to the following error: 80040154. This error may be a result of running SSMA as 64-bit application while having only 32-bit connectivity components installed or vice versa. You can run 32-bit SSMA application if you have 32-bit connectivity components or 64-bit SSMA application if you have 64-bit connectivity components, shortcut to both 32-bit and 64-bit SSMA can be found under the Programs menu. You can also consider updating your connectivity components from go.microsoft.com/fwlink.

    An error occurred while loading database content.

Most answers on the Nets say to use the 32-bit version of SSMA, but I've tried that and it doesn't help.
0
skbohler
Asked:
skbohler
  • 3
  • 2
1 Solution
 
PatHartmanCommented:
I'm getting the same error.  I haven't tried to run the conversion in a few weeks so sometime between then and Friday, something changed.  I reinstalled SSMA.  I tried it on a different computer.  I even installed SQL Server Express 2012 on the other computer.  So far no luck.  Also, I have another tool that I used for converting FoxPro to SQL Server.  I tried it with Access and it fails.  It says the provider is not found.Conversion errorConversion error for SSMA
0
 
PatHartmanCommented:
Are you using O365?  I just tried the same database with a remote connection (RDP) to a virtual machine and it worked fine.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
skbohler, you still have the issue or it's already solved?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
skbohlerAuthor Commented:
I was able to solve this issue by:

Uninstalling Office 365 32-bit version
Installing Office 365 64-bit version
Installing the Access 2010 64-bit engine/driver

After that, the process worked.
0
 
PatHartmanCommented:
Using the 64-bit version of Office will make your Access apps incompatible with 32-bit office users.

I was able to resolve mine by installing the 32-bit Access 2013 runtime.

Apparently, there is some missing library that the runtime installs.  This is a MS bug that was introduced in the past month.
0
 
skbohlerAuthor Commented:
Was able to solve it myself.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now