Groups | Blog | Home
all groups > sql server clustering > march 2007 >

sql server clustering : New fresh 2005 cluster and SCC error


SalamElias
3/31/2007 7:56:01 AM
I am trying to setup an active/passive cluster (everything on 32bit
plateforme) on a virtualized environment. I followed several docs provided by
microsoft especially the one on /prodtechnol/virtualserver/deploy/cvs2005.mpx.
Regarding the w2k3 itself it seems everything is correct, I did all
necesary tests for testing the failover from one node to another and
evrything works correctly.

When I launch SQL 2005 setup on node1 (node 2 of course is on), Setup stops
indicating that some requirements are not met, an SCC Error.

I have an AMD Athlon 64 proc 3000 2.00GHz with and each VM was granted 512 G
of Ram.

I understand that min req is 600Htz for Procs and 512. When I open the
summary.txt file I have the following :

********************************************
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition
Service Pack 1 (Build 3790)
Time : Sat Mar 31 15:55:30 2007

SQLCLUST11 : The current system does not meet minimum hardware requirements
for this SQL Server release. For detailed hardware requirements, see the
readme file or SQL Server Books Online.
SQLCLUST11 : There was an unexpected failure during the setup wizard. You
may review the setup logs and/or click the help button for more information.


SQL Server Setup failed. For more information, review the Setup log file in
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.


Time : Sat Mar 31 15:55:59 2007


List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows
Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows Installer
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_SCC.log
SalamElias
4/1/2007 1:26:00 AM
In fact I remember that I had an alert (! inside Yellow triangle) in the
final step of adding the second node. So the alert indicated the following :
**************************
Reanalyzing cluster
sqlclust12: c omparing cluster and node configurations...
sqlclust12: Collecting managed resources...
Triangle yellow : Status 0x00138f: The cluster resource could not be found
*****************************

As said, the cluster works like a charm (several failover tests)

Thank you for your help
[quoted text, click to view]
AddThis Social Bookmark Button