RESOLUTION:
1. Make sure your SQL server name is correct, e.g. no typo in the name.
2. Make sure the Migration server is reachable, e.g. DNS can be resolved correctly
3. Make sure SQL Browser service is running on the Migration server.
4. Disable the firewall on the Migration server.
Otherwise, create an inbound rule with service exception
for the service sqlbrowser.exe and UDP port 1434
5. Check the SQL connection using the portqry tool
- Get it from http://support.microsoft.com/kb/832919
and run:
portqry.exe -n your-Migration-servername -p UDP -e 1434
Note: This tool is more/less similar to >netstat -nao