TimeTraveler
IS-IT--Management
Situation:
If like me, and just D/L and installed SQL Server 2008 R2 and in a rush to get it connected to your app server just went down the protocol list in the Configuration Manager and flipped everything on, you'll probably have issues starting the following services:
[ul]
[li]SQL Server[/li]
[li]SQL Server Agent[/li]
[li]SQL Server Browser[/li]
[/ul]
... and maybe some of the remaining services.
Try:
Disable VIA protocol in Configuration Manager and that should do allow restarting the above SQL Server services. Try this before attempting to dive through permission-related fixes. This fix solved an error related to time-outs, and to [purple]SQL Server could not spawn FRunCM thread[/purple].
Hope this helps,
S
If like me, and just D/L and installed SQL Server 2008 R2 and in a rush to get it connected to your app server just went down the protocol list in the Configuration Manager and flipped everything on, you'll probably have issues starting the following services:
[ul]
[li]SQL Server[/li]
[li]SQL Server Agent[/li]
[li]SQL Server Browser[/li]
[/ul]
... and maybe some of the remaining services.
Try:
Disable VIA protocol in Configuration Manager and that should do allow restarting the above SQL Server services. Try this before attempting to dive through permission-related fixes. This fix solved an error related to time-outs, and to [purple]SQL Server could not spawn FRunCM thread[/purple].
Hope this helps,
S
