Home - Technologie Wissen

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)

Default Network Setting Lmhosts should always be deactivated

the Microsoft default network setting "using LMHOSTS"

sometimes blocks dns requests,

so that multiple problems can occur.

me and my technicans always deactivate this setting

if we rollout clients and server running microsoft operating systems.

a few weeks ago i got a call, that an adminisrator is not able to change network security permissions on network shares

any more.

the domain field is missing if he tried to add active directory user accounts.

the solution was in deactivating the lmhosts setting, too.

then did "ipconfig /flushdns" and open the security settings of the sahre again.

the add field contained the ad groups directly without rebooting...

on the client side it´s also possible that no internet connection

starts (without proxy server),

cause dns resolving fails.

and a lot of other bugs...

deactivate lmhosts in order to circumvent such problems...

Posted at 15:51 by Administrator | Category: Networking | Permalink | Email this Post | Comments (0)

09.04.2010

Hex Code Fehler - Ursache ausgeben lassen - scheduled task - last result error 0x4f7 - let the system explain the detailed error

So könnt Ihr einen Hex Fehler unter Geplante Tasks

in eine System Fehlermeldung ausgaben lassen...

Beispiel:

Ihr habt unter Server 2008 oder wo auch immer einen geplanten Task,

sagen wir Neustart.

Der Befehl lautet

shutdown -r -t 3 -c "automatischer Neustart"

Läuft aber nicht,

endet bei last result mit 0x4f7

So, wie wisst Ihr, was die Ursache ist?

- cmd öffnen

- calc

-Im Rechner auf Programmier Anzeige und hex auswählen
(vor windows 7 - wissenschaftliche Ansicht...)

-4f7 eingeben

-auf dezimal umstellen

Ergebnis lautet 1271

im cmd net helpmsg 1271 eingeben

Ihr erhalten die Erklärung:

Der Computer ist gesperrt und kann nicht heruntergefahren werden, ohne die Optio
n "force" zu verwenden.

Also, Lösung:

shutdown -r -f -t 3 "Automatischer Neustart"

:-)

Posted at 10:26 by Administrator | Category: Scripte | Permalink | Email this Post | Comments (0)

05.03.2010

System Center 2007 R2 and later- All Domain Controllers / DNS Server listed in critical state - DNS external resolution monitor failure

Error:

In System Center, all of you DNS Servers are listed in critical state.

External Resolution Monitor, from Microsoft DNS Management Pack,

failed to query the ns entries from www.microsoft.com,

or other hosts.

although everything working fine...

Cause:

This is the default setting of the management pack.

www is a host entry, and no domain/subdomain,

so you cannot query for nameserver.

solution:

change the default entry to host type or change the querying "domain"...

As listed here:

http://technet.microsoft.com/en-us/library/dd187144.aspx

Setting the DNS 2003 and DNS 2008 External Resolution Monitor

By default, the external name resolution monitor performs an NSLOOKUP query for a host (NS) record at www.microsoft.com to verify that external resolution is functioning properly. If desired, you can change the Host, Query Type, or disable the monitor entirely.

To override the Host or Query Type

In the Operations console, click the Authoring button.
In the Authoring pane, expand Authoring, expand Management Pack Objects, and then click Monitors.
In the Monitors pane, use Look for: to locate External Resolution Monitor.
Right-click DNS 2003 External Resolution Monitor or DNS 2008 External Resolution Monitor.
Select Overrides, select Override the Monitor, select For all objects of type: DNS 2003 Server or For all objects of type: DNS 2008 Server.
Select Query Type and change the default setting NS, or select Host and change the default setting www.microsoft.com to e.g. you domain...

please check, that you really resolv your domain through external dns server,

and do not have a copy of that zone in you local infrastructure...

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

Extend / Change Partition Size with board tools under Microsoft Server 2003/2008 / Windows XP

Howto extend / change partition size, also on 64 bit systems:

Partition auf Server 2003 / 2008 vergrößern

At a command prompt, type diskpart.exe.
Type list volume to display the existing volumes on the computer.
Type Select volume volume number where volume number is number of the volume that you want to extend.
Type extend [size=n] [disk=n] [noerr]. The following describes the parameters:
size=n
The space, in megabytes (MB), to add to the current partition. If you do not specify a size, the disk is extended to use all the next contiguous unallocated space.

disk=n
The dynamic disk on which to extend the volume. Space equal to size=n is allocated on the disk. If no disk is specified, the volume is extended on the current disk.

noerr
For scripting only. When an error is thrown, this parameter specifies that Diskpart continue to process commands as if the error did not occur. Without the noerr parameter, an error causes Diskpart to exit with an error code.
Type exit to exit Diskpart.exe.

When the extend command is complete, you should receive a message that states that Diskpart successfully extended the volume. The new space should be added to the existing drive while maintaining the data on the volume.

No Communication caused by multiple Gateways

Server cannot understand different gateways with a default metric.

the communication fails!

The important gateway gots a metric of 1.

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

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

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.

Exchange Mobile Activesync Error DupeAppt Lösung / Solution- Kalender Einträge werden nicht mehr synchronisiert

Problem Beschreibung:

Einzelne Kalender Einträge werden nicht ans mobile Gerät, dem Handy,

übermittelt.

Hier ist es vollkommen egal welche Konstellationen man durchläuft.

Windows Mobile in allen Versionen, Activesync, IPhone, Sprachen...

In Outlook und über dem Outlook Web Portal

sind die Einträge jedoch sichtbar.

Ursache nach System Analyse:

Das Exchange System kann einem Benutzer

bestimmte Kalender Einträge nicht übermitteln,

da diese als Dubletten identifiziert werden.

Auf dem Gerät unter Windows Mobile findet man in den Logs "DupeAppt" als Ursache.

Im Internet gibt es dazu aber keine Lösung /Solution.

Das diese Einträge als Dubletten erkannt werden,

bedeutet das die Objekt ID der Einträge bereits im System vorhanden sind,
bzw. das ein Windows Mobile Gerät beim Unternehmen diese IDs bereits verwendet.

(Denn das Problem existiert lediglich bei der mobilen Synchronisation)

Mögliche Ursachen:

- Einträge wurden aus anderen Kalendern übernommen (durch Kopie, Verschieben, etc)

(Eine Sektretärin hat die Einträge wohl manuell erstellt)

- eine Datenrücksicherung des Postfachs hat diese Einträge nicht korrekt neu erstellen können.

- Da die Einträge im alten Exchange System erstellt wurden, kommt es auf den Mobilen Sync-Server
nun aus Versehen zu doppelt vergebenen Objekt IDs.
(unwahrscheinlich)

In Google gibt es eine Person mit demselben Problem,

der Eintrag ist 3 Jahre alt und es war eine Synchronisation ohne Exchange Server, nur über Kabel.

Aber selbst dort gab es keine Lösung zum Problem.

Betrifft folgende Endgeräte:

- Windows Mobile Endgeräte, Hersteller-unabhängig

- Andere mobilen Business Betriebssysteme wie das Apple IPhone

unabhängig von der Sprache

Betrifft folgende Exchange Benutzer:

- Alle Benutzer, die über diese Einträge verfügen. (etwa durch Kopie, Wiederherstellung aus Sicherung)

Neben dem Benutzer, ist auch direkt ein neu erstellter Test Account betroffen,

dem die Kalender Daten importiert wurden.

Lösung:

Sogar eine Sicherung des Postfachs,

das Entfernen sämtlicher Benutzer bezogener Daten

und die Neueinrichtung des Benutzers führt nicht zu einer fehlerfreien Synchronisation.

Die Einträge (ausser bereits neu erstellte) müssen gelöscht und manuell neu erstellt werden.

Tags:

DupeAppt, Logging, Exchange Client Access Server, 2007, 2003, 2010, Iphone, Calendar Entries, Appointments

RSS Feed

1 - 10

Technologie Wissen

Technologie Wissen

Content Editor Web Part

27.04.2010

09.04.2010

05.03.2010

Setting the DNS 2003 and DNS 2008 External Resolution Monitor

03.03.2010

28.02.2010

‭(Hidden)‬ Admin Links