Forum Discussion
ChuckDonner11
Jul 08, 2021Copper Contributor
SQL Server Migration Assistant for Access - Hangs when selecting Access DB
I downloaded Microsoft SQL Server Migration Assistant for Access last week and successfully converted my local Access database to an online MS SQL database. After testing it for a week I decided to do it again with the current (updated with most recent data) version of the Access database. When I opened SMAA it asked to update. In addition, a Windows 10 update was installed on my PC a few days ago. Now the SMAA software hangs when I try to select my local Access Database. It shows "Connecting to database 'mydata'... but just hangs forever. This worked fine last week and this step did not delay at all. the migration took a while but not this step. Any help would be appreciated.
- rene_hugCopper Contributor
This thread is not the newest anymore. However, I had the same issue after upgrading to SSMAA 8.25. Everything worked the day before and after the upgrade the same symptoms appeared.
My configuration WIN 10 64-bit; Office 365 64-bit. I work in an enterprise environment, so any rollback of O365 is out of discussion.
The final solution for me was to
1. uninstall SSMAA 64-bit version
2. uninstall Microsoft Access Database Engine 2016 Redistributable 64-bit version
3. reboot my machine
4. install SSMAA again 64-bit version
5. Install Microsoft Access Database Engine 2016 Redistributable 64-bit version
All was back to normal after this! Only removing/reinstallation of SSMAA didn't worked for me. Also other solutions with 32-bit and 64-bit that are mentioned here didn't worked.
Hope someone might find this helpful. - tgearyCopper Contributor
I also had no issue with the tool prior to 7/9--I'm now getting the same behavior of hanging at 'Connecting to database'. I rolled back the SSMA update from 8.21 to 8.20, but the issue persists. I noticed Office 365 received an update on 7/9 (Access 16.0.14131.20278), so I believe that's the culprit. . Very frustrating.
- Easy to test whether the Office update is the cause. Rollback to an earlier version of 365
For detailed instructions on how to rollback to an earlier version of 365, see https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841