Failing SQL 2005 Cluster Installation because of too many cpu's

Question

Post reply

Failing SQL 2005 Cluster Installation because of too many cpu's

sqlstad

SSCrazy

Points: 2484
More actions
July 14, 2009 at 12:23 am

#206969

Comments posted to this topic are about the item Failing SQL 2005 Cluster Installation because of too many cpu's

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply

eduardo.pin SSC Eights! Points: 996 More actions · Answer 1

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

SanjayAttray SSChampion Points: 13157 More actions · Answer 2

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.

ammo-963576 Ten Centuries Points: 1177 More actions · Answer 3

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

fhooglander SSC-Addicted Points: 459 More actions · Answer 4

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

sqlstad SSCrazy Points: 2484 More actions · Answer 5

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.

sqlstad SSCrazy Points: 2484 More actions · Answer 6

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.

TimothyAWiseman SSCrazy Eights Points: 8819 More actions · Answer 7

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/

Johan Bijnens SSC Guru Points: 135376 More actions · Answer 8

Nice article !

This is a time saver !

Thank you for sharing the experience.

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

douglasmeakin SSC Enthusiast Points: 138 More actions · Answer 9

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.

paulrynr Newbie Points: 5 More actions · Answer 10

It 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.

douglasmeakin SSC Enthusiast Points: 138 More actions · Answer 11

I 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).

DBADave SSChampion Points: 10962 More actions · Answer 12

We 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=1464269

We 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.

Dave