SQL 2005: SQL Server Configuration Manager Error: Connection to target machine could not be made in a timely fasion.
Published Jan 15 2019 11:29 AM 126 Views
First published on MSDN on Mar 31, 2009

There is a bug with the message spelling (fasion instead of fashion) but that is not the focus of this post.

When launching the SQL Server Configuration Manager you may receive this message if the WMI connections and queries do not complete within 30 seconds.   For the customer case I just worked the queries returned in 42 seconds but at the 30 second mark the SQL server components had deemed this a timeout, displayed the dialog and posted a WM_CLOSE to the main MMC.exe window.

The timeout is applied anytime you use the SQL Server Configuration Manager snap-in for MMC.   (Launching with the Program Files icon or Adding the Snap-in from the MMC console.)

Workaround: There is a way to launch the SQL Server Configuration Manager and avoid the 30 second timeout.   Use Control Panel | Administrative Tools | Computer Management | Services | SQL Server Configuration Manager as it does not honor the 30 second timeout.

Troubleshooting: I used Process Monitor (ProcMon) from http://www.technet.com/SysInternals to watch the activity of the wmiprvse.exe against the sqlmgm*.* paths and descriptions.   I could see the accesses to the sqlmgmprovider.dll, sqlmgm*.mof, .mfl and associated files but it was just taking longer than 30 seconds to complete the full set of queries.  Shown below is the expected and repeated pattern.  This pattern repeats dozens of times for a successful startup of the SQL Server Configuration Manager.

Bob Dorr - Principal SQL Server Escalation Engineer

Version history
Last update:
‎Jan 15 2019 11:29 AM
Updated by: