belle’s sql musings

Connection to target machine could not be made in a timely fashion

Posted in Issues/Troubleshooting by belle on November 6, 2008

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:

  1. Start > Run > type services.msc and press Enter
  2. Scroll down to Windows Management Instrumentation, right click, restart
Tagged with:

7 comments

7 Responses

Subscribe to comments with RSS.

  1. Niall said, on April 20, 2009 at 10:54 pm

    Great, worked for me. Thanks 🙂

    Reply
  2. rviera said, on September 30, 2009 at 9:13 am

    your post worked, great, thanks

    Reply
  3. Nick said, on February 1, 2011 at 4:32 am

    In my case I got an error when I tried to restart the Windows Management Instrumentation Service.

    “Error 1053: The service did not respond to the start or control request in a timely fashion”.

    Reply
  4. Austin said, on February 16, 2011 at 3:27 pm

    Worked for me, too. Thanks!!

    Reply
  5. Suresh said, on June 2, 2011 at 4:53 am

    This is not worked. The error is not fixed even after restarting WMI service.
    ??

    I am using SQL Server 2008 in server 2008 R2 Operating system.

    Regards,
    Suresh.

    Reply
  6. Nitish said, on March 24, 2012 at 6:31 am

    its work! thnx

    Reply
  7. msuworld said, on October 1, 2012 at 12:06 am

    WMI restart doesn’t works, what to do ?

    Reply

Leave a comment