Hello all,

Iam receiving a message while installing the SQL Server 2008 in a cluster
environment.

Error : "Microsoft Cluster Service (MSCS) cluster verification errors"
failed. The cluster either has not been verified or there are errors or
failures in the verification report. Refer to KB953748 or SQL server books
online for more information"

to resolve this I ran the "validate the cluster" tests under failover
cluster management. The validation was successful without any warnings or
errors. Even then I still get the same error.

Could someone please help me out. I have been spending 2 days on this and
just can't find a solution to this.

Thanks,
rl

Are you using WIndows 2003 or 2008 clustering?

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"rl" <rl (AT) discussions (DOT) microsoft.com> wrote

Windows 2008.

"Geoff N. Hiten" wrote:

I dont even see that KB number (KB953748) on the Microsoft support site.
Can you check the Cluster Events under Failover Cluster Management and see
if there is anything related? Try re-running the Validate a Configuration
wizard once more on your existing cluster nodes and see if it will generate
related errors

"rl" <rl (AT) discussions (DOT) microsoft.com> wrote

Hi
it took us almost 1 month to get an SQL Server 2008 version running in a
Windows 2008 x64 Cluster environment ! So if you are on your second day, ...

We had first a cluster of 4 servers. The installation of SQL Server 2008
went fine on the first 3 servers, then there was some problem on the last
one, and it was impossible to go on with the installation. After one week of
searching with Microsoft, we found that the master table was corrupted. At
this point, we decided to split our cluster in two clusters, one for the
file system and one for SQL Server. We completely reinstalled the cluster
and this time we could install SQL Server. But moving an instance from one
node to the other did not work, which is quite annoying in a cluster
environment: either the database engine failed to start, or the agent, or
both ! There was some kind of Kerberos problem. After many trials, Microsoft
told me to change two keys in the registry:
HKLM\System\CurrentControlSet\Control\Lsa\DisableL oopbackCheck --> 1
HKLM\System\CurrentControlSet\ServicesLanmanServer \Parameters\DisableStrictNameChecking
--> 1

After this change, our instances seem to work properly. Of course, there are
security issues when disabling these checks, so use them at your own risks.

Note that we still have other open cases at Microsoft's, but at least our
users can work.
Good luck
pher




"rl" <rl (AT) discussions (DOT) microsoft.com> wrote

I found at least one potential workaround for this. It does appear to be a
bug with the SQL installer.

In my case it was failing consistently no matter what the results of running
the validation test. Finally I deleted all files out of
C:\Windows\Cluster\Reports on both nodes and ran it again. I verified there
was just one report in the above directory. But running the check again
failed saying there were errors or no verification report.

I then ran Process Monitor and filtered to only capture setup100.exe. I
reran the checks and it failed as expected. In the Process Monitor output I
did a search for Validation and found where it was trying to access the
validation report. It had the path right, but the name it was using was
differenct than the name of my report. Instead of "Validation Data For Node
Set C1DE6...xml" it was looking for "Validation Data For Node Set
D1A1B...xml". I couldn't find any references to this other ID anywhere.

I then copied the real Validation Data report on both nodes and renamed them
to be what the setup was expecting to fine. I reran the install checks and
this time it made it all the way through without error.

"bass_player" wrote:

This is a known issue for multi-site clusters. There is also an issue if
you do some authenticaiton changes.

The best fix is to run any SQL CU before installing SQL 2008. The CU
"pre-patches" the installer and fixes the cluster install bugs. You still
need to run the CU post-install to patch everything else.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"SeanM" <SeanM (AT) discussions (DOT) microsoft.com> wrote