Error trying to use latest SQL Server Migration Assistant for Access

Question

Error trying to use latest SQL Server Migration Assistant for Access

Kevin Seerup 0

I have the latest SSMA for Access installed but can't get past a "New Workspace Error" either via the start wizard or trying to open a solution I created about 9 months ago.

The error states "The type initializer for 'Microsoft.SSMA.framework.SQLServer.collector.SQLServerObjectCollector' threw an error."

Lakshmi Narayana Garikapati 1,335 Reputation points Microsoft External Staff Moderator

2026-06-03T06:07:26.5933333+00:00

Hi Kevin Seerup,

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we'll assist further

Thanks,

Lakshmi

Answer recommended by moderator

0 additional answers

Your answer

Lakshmi Narayana Garikapati 1,335 Reputation points Microsoft External Staff Moderator

2026-06-03T06:07:26.5933333+00:00

Hi Kevin Seerup,

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we'll assist further

Thanks,

Lakshmi

Answer 1

That error is a .NET type-initializer failure, which means SSMA is hitting a problem loading one of its dependencies before it can do anything else. Since it happens both with new workspaces and existing solutions, the trigger is at startup rather than tied to your specific project.

The most efficient way to resolve it is to look at the inner exception, which names the actual failing dependency. The SSMA log file under %LOCALAPPDATA%\Microsoft SQL Server Migration Assistant for Access\ usually contains it, if that exact path isn't there, searching for "SSMA" under your user profile will find it. Sharing that entry would help narrow things down quickly.

In the meantime, a few things worth trying:

A common cause is a mismatched or damaged SQL Server client library, so reinstalling the Microsoft OLE DB Driver for SQL Server is a reasonable first step. If that doesn't help, fully uninstall SSMA for Access, reboot, and reinstall the latest version. Repairing the .NET Framework is a sensible follow-up if the issue still persists.