Problems with SQL 2005 cluster on Server 2008

#31

Josh.

Thanks for the answer. I will definitely documenet this, especially since I
will be pitting a cluster together shortly on Server 2008.

If you send me your full name via email I will give you credit when I post
this solution.

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

"scorpiuss" <yehoshua.gavant (AT) gmail (DOT) com> wrote

On Jun 11, 7:03 pm, "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote:

Quote:

Have you created firewall rules for SQL and clustering?

Try running the security wizard and see if it create the rules for
clustering. Once SQL is installed you may need to rerun the wizard to
create rules for SQL, or you can create them manually.

See my blog post for
details:http://weblogs.sqlteam.com/geoffh/ar...cure--Unusable...

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

"scorpiuss" <yehoshua.gav... (AT) gmail (DOT) com> wrote in message

news:b951d7be-0174-4416-922a-3feb0a98b47a (AT) 27g2000hsf (DOT) googlegroups.com...

Hi all,

I'm testing the installation of SQL Server 2005 clustering on a
Windows Server 2008 Failover Cluster. The Server 2008 cluster setup
went smoothly and I set up a cluster service for the SQL disks. The
installation options for a SQL cluster are all accepted and everything
looks good till I get to the actual installation.

There, the setup begins, but immediately the status for all products
is a red X and states "The installation was cancelled by the user." I
checked permissions for all accounts and groups used in setup and made
sure nothing is happening on either server at the time of setup. There
are no other databases or SQL instances running on either server.

Any help would be much appreciated. We're getting close to giving up
on this.

Thanks,
Josh- Hide quoted text -

- Show quoted text -

Hi Geoff,

Thanks for your prompt response. After digging through the logs, I was
able to determine what was causing the problem. The way SQL installs
itself on the non-local machine is via a scheduled task, which depends
on saved credentials to run. There's a group policy setting on our
domain here which prevents saving credentials.

The setting is [[Security Settings >> Local Policies >> Security
Options >> Network access: Do not allow storage of credentials or .NET
Passports for network authentication]]

Since I couldn't modify the policy itself, I modified the registry key
prior to running the SQL install:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l
\Lsa:"disabledomaincreds"=dword:00000000

Once I did this, the install completed successfully.

Tricky issue - took a long time to find exactly the problem. You might
want to document this somewhere.

Thanks again,
Josh

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Problems with SQL 2005 cluster on Server 2008

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: Problems with SQL 2005 cluster on Server 2008 - 06-13-2008 , 11:00 AM