|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 11:49 PM
Points: 382,
Visits: 486
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Sunday, April 28, 2013 7:30 PM
Points: 24,
Visits: 313
|
|
I had this trouble about 1 mounth ago and fixed exactly as you said... I spent more than 13 hours to figure out what was happening...
I'm sure that you article is going to be very usefull to many people!
Thanks...
Eduardo Pin Pin
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, March 15, 2013 2:43 PM
Points: 3,924,
Visits: 1,554
|
|
Thanks for the article and bringing the possible show stopper in before I start installing my new cluster next month for a new project.
I added your article in briefcase, to be on safe side.
SQL DBA.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: 2 days ago @ 7:22 PM
Points: 577,
Visits: 168
|
|
Sander,
I'm curious...Were there any suspicious-looking error messages in your installation logs?
Also, what did the Windows Event logs hold (both Application and System) for the failed service start that corresponds to the error message you displayed via screenshot?
I've never run into this error, but we maintain a few clusters and I'd love to have some errors to cross-ref if I run into something that looks very similar.
thanks, Aaron
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, September 17, 2010 3:04 PM
Points: 157,
Visits: 82
|
|
| I've had this same issue. This isn't really related to just clusters. It's the same on a stand-alone SQL Server 2005 that does not have a power of 2 number of CPUs
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 11:49 PM
Points: 382,
Visits: 486
|
|
ammo (7/14/2009) Sander,
I'm curious...Were there any suspicious-looking error messages in your installation logs?
Also, what did the Windows Event logs hold (both Application and System) for the failed service start that corresponds to the error message you displayed via screenshot?
I've never run into this error, but we maintain a few clusters and I'd love to have some errors to cross-ref if I run into something that looks very similar.
thanks, Aaron
There was no significant error that pointed out that is was CPU related. The thing was that I googled the error and and in the results I found a post by someone that was already removed that showed a little info that showed me the way.
But I'll post the errorlogs tomorrow.
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 11:49 PM
Points: 382,
Visits: 486
|
|
fhooglander (7/14/2009) I've had this same issue. This isn't really related to just clusters. It's the same on a stand-alone SQL Server 2005 that does not have a power of 2 number of CPUs
You could be right. I haven't got the chance do test it with a standalone server. But the same article could help out with standalone servers.
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Thursday, February 14, 2013 12:01 PM
Points: 743,
Visits: 900
|
|
Excellent Article. I ran into a very similar problem a while ago, and my final answer after struggling with it for quite some time and even taking the unusual step of contact MS tech support was to migrate that server to 2008.
If this article had been out then it would have saved a lot of time.
--- Timothy A Wiseman SQL Blog: http://timothyawiseman.wordpress.com/
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 6:25 AM
Points: 6,861,
Visits: 8,045
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, April 24, 2012 2:25 AM
Points: 120,
Visits: 167
|
|
Great article, I had this a few months ago and used that method.
Hopefully this will save some people the time on google should they experience it.
|
|
|
|