InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 04:19:33 GMT20http://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxWe encountered the same problem in April. I got lucky and found one discussion regarding the issue, which pointed me to the KB article. http://relatedterms.com/ViewThread.aspx?t=1464269We also tried reinstalling the OS prior to finding the fix. Now whenever we encounter any strange problem with our 24 proc servers we start wondering if it's related to the proc bug/feature.Good article. Hope it saves people some time when they encounter the problem.DaveTue, 04 Aug 2009 07:57:50 GMTDBADavehttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxI also asked our MS Technical Account Mangager at the time for a consolidated release but with no joy.Officially (I cannot speak of any done internal builds and special customer arrangements) there is no slipstreaming before SQL Server 2008 SP1. This is due to the architecture that was used before SQL Server 2008 (SP1).Wed, 15 Jul 2009 09:33:21 GMTdouglasmeakinhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxIt is definitely an issue with CPU count not being powers of 2, it was only picked up when the 6-core CPUs started to arrive on the scene and was fixed in higher service packs of SQL 2005 and 2008.I went to a SQLBits conference here in the UK around Easter and a few of the DBAs presenting mentioned this issue, both with Cluster and Standalone installations.Setting the CPU count to a factor of 2 will get round the installation issue. Microsoft seem to be a bit reluctant to issue media with the service packs included.Wed, 15 Jul 2009 09:25:34 GMTpaulrynrhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxGreat 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.Wed, 15 Jul 2009 09:15:20 GMTdouglasmeakinhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxNice article !This is a time saver !Thank you for sharing the experience.Wed, 15 Jul 2009 01:01:50 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxExcellent 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.Tue, 14 Jul 2009 14:56:19 GMTtimothyawisemanhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspx[quote][b]fhooglander (7/14/2009)[/b][hr]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[/quote]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.Tue, 14 Jul 2009 11:24:49 GMTsanderstadhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspx[quote][b]ammo (7/14/2009)[/b][hr]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[/quote]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.Tue, 14 Jul 2009 11:01:29 GMTsanderstadhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxI'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 CPUsTue, 14 Jul 2009 10:17:28 GMTfhooglanderhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxSander,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,AaronTue, 14 Jul 2009 09:41:58 GMTammo-963576http://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxThanks 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.Tue, 14 Jul 2009 08:43:18 GMTSanjayAttrayhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxI 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 PinTue, 14 Jul 2009 07:12:39 GMTeduardo.pinhttp://www.sqlservercentral.com/Forums/Topic752488-1569-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/SQL+2005/67297/">Failing SQL 2005 Cluster Installation because of too many cpu's</A>[/B]Tue, 14 Jul 2009 00:23:15 GMTsanderstad