Problem
Actually the error is (note spelling mistake on fashion):
"Connection to target machine could not be made in a timely fasion"
Scenario
One of our DBAs was testing the SQL cluster failover. After he failed over from Node 1 to Node 2, he can no longer bring up SQL Server Configuration Manager (SSCM). Whenever he tried, he will wait for about 30-40 seconds before he gets an error message : Connection to target machine could not be made in a timely fasion
Resolution
This could have been caused by a whole host of things.
In our case, all we had to do was to restart WMI service:
- Start > Run > type services.msc and press Enter
- Scroll down to Windows Management Instrumentation, right click, restart
- Tweet
Related posts:
- Connection Error 233 : No process at the other end of the pipe …
- Resolving “A network-related or instance-specific error occurred while establishing a connection to SQL Server…” …
- WMIProviderException when installing SSRS 2005 on Windows 2008 …
- How to Reset Root Password in Linux with a GRUB Menu …
- Drop and Re-Add Server Registration When Renaming Computer …
Filed under:
Issues/Troubleshooting
