When a remote console for Quest Migration Manager for Exchange (QMM) was opened, after running for a considerable time with no issues, the popup message: "Login failed for user 'sa'. Please check whether the server is available, and username and password are correct." was received.
The local console connects to the SQL instance with no issues. The SQL instance is installed on the same system as the QMM software.
Resetting the SA password via Open Project, does not allow the connection to be made. When netstat is run on the remote console it reports connections on Microsoft-DS (see Additional Information below) in a "time wait" state to the SQL server. No changes have been made to router ACLs, local firewalls or anything of that nature.
Testing revealed that Microsoft SQL Server Enterprise Manager installed on the remote console can't connect to the SQL server. Over all it appears that the problem is network related but ICMP and most TCP connections seem fine - but there is a "time wait" on Microsoft-DS as noted above.
The SQL instance on the local system had Named Pipes and TCP/IP protocols disabled and therefore the remote console could not make a connection.
Use the SQL tools utility called SQL Server Network Utility (svrnetcn.exe) to re-enable the protocols Named Pipes and TCP/IP.
Please see solution SOL34443 - How to specify SQL server port number when running QMM (Quest Migration Manager) Open Project Wizard? - https://support.quest.com/SUPPORT/index?page=solution&id=SOL34443
Microsoft-DS (Microsoft Directory Services) is a port used for file sharing. It was introduced with Windows 2000 and gives you the possibility to use SMB protocol (stands for Server Message Block, but is also known as Samba) directly over TCP-IP on port 445.