February CTP: SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I was happy to see that February CTP for SQL Server 2008 was ready to download for use, in coinciding with my presentation in SQLBits I wanted to work my demos on this CTP release, nothing worked out successfully!!
It is fair that new release will help developers and DBAs to test their solutions and get familiar with the next CTP of SQL Server as compared to the last ones, I feel not many of the bugs are fixed and they have released stating they will get fixed. IN specific to this Februar 2008 CTP it worked for first time after installation, when I'm trying to check the Policies within SSMS- Object Explorer ----> Policy Management an exception error was thrown that added more fuel to the problems I was having, my machine was completely hung, not an easy situation when you have got a public presentation to give in next couple of days and wanted to a glimpse of newest features from available CTP to the public.
Thought a reboot of machine would fix this issue, no it even made it worse whenever I started to open up Management Studio to connect to that SQL 2008 instance (10.0.1300) and unable to start SQL Server services. Due to the time constraint in order to get my session demos up and running I haven't had a chance to look around the Connect site or web resources for a fix, the actual error it throws out is:
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
On the day (01st March 2008) after my presentation at SQLBits Tom Pullen (one of the speaker) referred this was a bug reported to connect site and after I get time checked that relevant bug report here.