This looks like a known regression issue in SSMA 10.4 rather than a problem with your setup.
A practical workaround is to roll back to SSMA 10.3 (Access → SQL Server). Many users have reported that 10.3 works correctly, while 10.4 throws the “Bad parameters for connection” error in certain environments, especially with SQL Server Express.
What you can do:
Uninstall SSMA 10.4 completely.
Install SSMA 10.3 along with the matching SSMA Extension Pack.
Retry the migration—this usually resolves the issue.
Also, just to be safe, double-check:
Your SQL Server instance name (e.g., .\SQLEXPRESS)
TCP/IP is enabled in SQL Server Configuration Manager
SQL Server service is restarted after any changes
SSMA is run as Administrator
If downgrading is not an option, an alternative approach is to export the Access tables (CSV/Excel) and import them into SQL Server using the Import and Export Wizard, but reverting to SSMA 10.3 is the simplest and most reliable fix right now.
Hope this helps.This looks like a known regression issue in SSMA 10.4 rather than a problem with your setup.
A practical workaround is to roll back to SSMA 10.3 (Access → SQL Server). Many users have reported that 10.3 works correctly, while 10.4 throws the “Bad parameters for connection” error in certain environments, especially with SQL Server Express.
What you can do:
Uninstall SSMA 10.4 completely.
Install SSMA 10.3 along with the matching SSMA Extension Pack.
Retry the migration—this usually resolves the issue.
Also, just to be safe, double-check:
Your SQL Server instance name (e.g., .\SQLEXPRESS)
TCP/IP is enabled in SQL Server Configuration Manager
SQL Server service is restarted after any changes
SSMA is run as Administrator
If downgrading is not an option, an alternative approach is to export the Access tables (CSV/Excel) and import them into SQL Server using the Import and Export Wizard, but reverting to SSMA 10.3 is the simplest and most reliable fix right now.
Hope this helps.