SQL Server - Cluster / Single Server

27.04.2010

SQL 2008 won´t install - message awaiting first complete passive cluster node displayed

You try to install/Upgrade to sql server 2005 enterprise x64 Sp3.

the message "awaiting first complete passive cluster node"

is displayed, but you see no progress.

german message "warten auf den vollständigen passiven Clusterknoten"

possible problems:

- the cluster resources can move and freeze

- cluster service on the node where you started sp3 ist

stopped.

you have to rebbot all the nodes and nothing changed/upgraded.

solution:

- deactivate "DNS Registration must succeed on the cluster

quorum network name

- activate "fallback immediatly" on the cluster quorum group.

- Start the Sp3 Installation/Upgrade on one node
on the "remote auth screen" type the administrator account

who is controlling the sql server ressources

At the promt "awaiting first complete passive cluster node"

go to cluster administrator, into sql group

and manually take offline "sql server service"

by the way dependencies are stopped to (agent and name)

the sp3 routine begins to updates all the nodes,

reboot whole environment.

Posted at 15:53 by Administrator | Category: SQL Server - Cluster / Single Server | Permalink | Email this Post | Comments (0)

03.03.2010

SQL 2008 Setup - Accessing the Filestream Access Option - Setup fails with message "requested resource is in use"

Setup fails with message "requested resource is in use".
Installer crashes.

Cause:

If SQL Server VSS Writer under Services is running,

Setup cannot access Filestream Access Option during setup.

Stop the Service and start Setup again...

Information:
Microsoft (R) SQL Server 2008 Setup 10.00.1600.22
Copyright (c) Microsoft Corporation. All rights reserved.

The following error occurred:
The requested resource is in use. (Exception from HRESULT: 0x800700AA)

Error result: -568706566
Result facility code: 1562
Result error code: 14842

28.02.2010

SQL 2005 / 2008 - Cannot connect to SQL via TCP - using Management Studio or client connection - message: The configuration of the SQL instance MSSQLSERVER is not valid change instance

This Problem can occur in a cluster or standalone.

version sql 2005 / 2008

in one of my environments, one of the nodes

successfully takes the clustered sql instance XY

and accepts pipe connections via management studio

and sql client hosts,

but not via tcp, e.g. named instance.

i find out that sql browser service does not start,

also in clustered infrastructure client based,

not controlled by cluster and set to auto...

by starting i got the error:

The configuration of the SQL instance MSSQLSERVER is not valid change instance

and that´s true.

my instance is not the default one.

also you can see, that under sql network configuration,

there are multiple instances registrated..

Cause:

Sometimes the first installation was not possible

or you removed an instance,

however sql browser service is not bind correctly to the actual used instance(s).

so, look at the registry with regedit on the failed node.

directly under

machine \ software \ microsoft \ Microsoft SQL Server

you find a key called "InstalledInstances".

If there are multiple Entries/Data,

delete the fauled instances.

SQLBrowser Service cannot bring tcp online by failed/missing instances.

i believe that sql browser is always taking tha last instance in the data field,

so cannot provide tcp port 1433 to the first instances...

close registry, start sql browser again and it will function...

also you can see, that under sql network configuration,

the deleted instance is away...

SQL 2008 Setup - Network Interface not displayed vor administrative Communication - Public LAN

In SQL 2008 Setup, based on Server 2008 R2 you cannot select the public Interface in setup.

Maybe no Interface is displayed or only a few, but not this one you need for communication to the sql clients...

Cause:

Only Network Interfaces assigned with a default gateway are listed in the setup of the administrative interface.

solution:

Assign a default gateway on each interface you need to communicate with the clients.

if there is not always a possible gateway to use, walk to this configuration:

Assing for example a dummy gateway, such a domain controller who is not routing...

now, change all gateway entries into a manual metric.

The important gateway gots a metric of 1.

for example the dummy gateways got the lowest metric, in this configuation the 2.

Server cannot understand different gateways with a default metric.

the communication fails!

if you have to assign multiple gateways, you have to work with manuel merics, and this functions very well.

27.02.2010

SQL 2008 Rollup Pack installiert nicht wg Fehlender Registry Berechtigung ? - Rule "Consistency validation for SQL Server registry keys" failed.

Nie davon ausgehen,

dass bei Fehlermeldung während der Prüfung die Meldung der Ursache entspricht !

Ihr versucht ein wichtiges Rollup Pack für SQL 2008 zu installieren.

Fehler, die bei der Rule Prüfung gemeldet werden:

Rule "Consistency validation for SQL Server registry keys" failed.

The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.

PatchGlobalRules: SQL Server 2008 Setup configuration checks for rules group 'PatchGlobalRules'

AclPermissionsFacet

Checks if the SQL Server registry keys are consistent.

Failed

Geht in folgenden Pfad:

C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\

aktuelles Datum suchen, Darin findet Ihr die Details.txt und die HTM mit dem Bericht.

Sucht nach failed in der Details.txt.

Zum Beispiel kann es sein,

dass die Cluster Resource nicht online ist, bzw.

auf einem anderen Host.

Da im SQL Data Laufwerk wichtige Dateien für jedes Setup liegen,

erhaltet Ihr die obigen Fehlermeldungen sofort,

wenn das Setup nicht die Cluster Disk findet.

Es kann aber auch sein,

dass wirklich eine fehlende Berechtigung in der Registry vorliegt.

Dann habt Ihr folgende Einträge:

Could not fix registry key

und

System.UnauthorizedAccessException: Attempted to perform an unauthorized operation

Passt in dem Fall die Berechtigung auf den Zweigen an,

eingeloggter Benutzer muss VollZugriff haben.

26.02.2010

SQL 2008 Cluster unter Server 2008 R2 - The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster

man will einen weiteren Knoten im SQL Cluster hinzufügen,

man erhält:

The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster

Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x2841E06E@1204@2
Configuration error description: The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster. To cluster an instance, the language of the instance on each node must be the same.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Datum/Zeit\Detail.txt
Configuration status:          Failed: see details below
Configuration error code:      0x2841E06E@1204@2
Configuration error description: The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster. To cluster an instance, the language of the instance on each node must be the same.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Datum/Zeit\Detail.txt

Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x2841E06E@1204@2
Configuration error description: The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster. To cluster an instance, the language of the instance on each node must be the same.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Datum/Zeit\Detail.txt
Configuration status:          Failed: see details below
Configuration error code:      0x2841E06E@1204@2
Configuration error description: The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster. To cluster an instance, the language of the instance on each node must be the same.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Datum/Zeit\Detail.txt

Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x2841E06E@1204@2
Configuration error description: The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster. To cluster an instance, the language of the instance on each node must be the same.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Datum/Zeit\Detail.txt
Configuration status:          Failed: see details below
Configuration error code:      0x2841E06E@1204@2
Configuration error description: The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster. To cluster an instance, the language of the instance on each node must be the same.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Datum/Zeit\Detail.txt

Folgende Ursache besteht:

- Ihr habt wirklich einen unterschiedlichen Patch Stand auf den Nodes

- Ihr habt vergessen eine Instance zu aktualisieren !
Oder Ihr habt eine Instance, die als Leiche im System liegt !

Hintergrund / Bug bei Prüfungsprozess AddNode

Obwohl Ihr mit dem identischen Patch Stand auf den Nodes

die korrekte Instance auswählt, die denselben PatchStand / Sprache aufweist,

schaut der AddNode Prozess in die Registrierung aller Nodes

und vergleicht (Bug) den Versionsstand aller Instances !

Wenn Ihr eine Leiche im System habt,

entfernt die Instance manuell aus der Registry aller Nodes

\ Local Machine \ Software \ Microsoft SQL Server \ MSSQL.10.InctanceLeichenName

Schaut auch unter \ Software \ MSSQLSERVER

Ihr habt eine saubere Konfig,

wenn Ihr das Setup neu aufruft und die defekte Instance nicht mehr zur Auswahl steht.

SP1 für SQL 2008 auf allen möglichen Knoten hinzufügen.

Dann Rollup für Sp1 SQL 2008 installieren,

wieder auf allen Nodes.

Welches Rollup aktuell ist, seht Ihr hier:

http://support.microsoft.com/kb/956909/en-us

(Lest Ihr den Artikel in einigen Monaten, ist ja klar,

dass Ihr nach Sp2, etc schaut.)

Für Sp1 war das Rollup04 das erste Mal ohne den Fehler.

Aktuell ist es Rollup09 für SP1

http://support.microsoft.com/kb/977444/en-us

Dann Setup neu starten mit:

PfadzuSQLDVD\setup.exe /PCUSource=C:\SP1 /SkipRules=Cluster_Veri
fyForErrors /Action=AddNode

Siehe Blog zu SQL 2008 zum Laufen kriegen...

bezüglich Slipstream Installation des SQL 2008 mit dem Sp1...

Technologie Wissen

Technologie Wissen

27.04.2010

03.03.2010

28.02.2010

27.02.2010

26.02.2010