Archive for the ‘Windows 2008 R2 SP1 Issuses’ Category

A hotfix is available to let you configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2

http://support.microsoft.com/kb/2494036

Windows Server Failover Clustering (WSFC) uses a majority of votes to establish a quorum for determining cluster membership. Votes are assigned to nodes in the cluster or to a witness that is either a disk or a file share witness. You can use the Configure Cluster Quorum Wizard to configure the clusters quorum model. When you configure a Node Majority, Node and Disk Majority, or Node and File Share Majority quorum model, all nodes in the cluster are each assigned one vote. WSFC does not let you select the cluster nodes that vote for determining quorum.
After you apply this hotfix, you can configure a cluster node that does not have quorum votes.

  • The NodeWeight common property for nodes
    This property can be configured by using either the Get-ClusterNode Windows PowerShell cmdlet or the Cluster.exe command. For example, you run the following command at a command prompt:

    Cluster.exe . node <NodeName> /prop NodeWeight=0

    To query the NodeWeight common property, you can use the following PowerShell cmdlet command:

    Get-ClusterNode “NodeName” | fl *

    To modify the NodeWeight property, you can use the following PowerShell cmdlet command:

    (Get-ClusterNode “NodeName”).NodeWeight = 0

    A new NodeWeight property is added to the MSCluster_Node WMI class to let you manage node weights by using WMI.

  • The PreventQuorum (PQ) switch
    This switch starts the Cluster service (ClusSvc) and prevents a node from reaching quorum. The Cluster service can be started by using the PQ switch. For example, you can run the following command at a command prompt:

    NET START ClusSvc /PQ

    The PQ switch can be used to enforce the cluster owner and to maintain consistency in the Cluster database.

6.0.600 2 . 22xxx Windows Server 2008 SP2

 

Get the Hotfix http://support.microsoft.com/kb/2494036

Installing Windows 2008R2 Service Pack 1 Ends with 0x800705b4 or 0x80070643

Well It sounds nice install SP1 and you get new features and it is SP1 greats new stuff for your Hyper-V server. But It can be a disaster for your server. Make sure you always got a backup of your server.!

these are the errors and the errors are not fixable ! there is a work around with a *

image image

Faulting Application Path: C:\Windows\servicing\TrustedInstaller.exe

Problem signature

Problem Event Name: APPCRASH

Application Name: TrustedInstaller.exe

Application Version: 6.1.7600.16385

Application Timestamp: 4a5bc4b0

Fault Module Name: cbscore.dll

Fault Module Version: 6.1.7601.17514

Fault Module Timestamp: 4ce7c541

Exception Code: c0000005

Exception Offset: 000000000005bc2e

Problem signature

Problem Event Name: CbsPackageServicingFailure2

Stack Version: 6.1.7601.17514

Package: Package_for_KB976932

Version: 6.1.1.17514

Architecture: amd64

Culture: unknown

Status: 800705b4

Failure Source: CBS Other

Start State: Partially Installed

Target State: Installed

Client Id: SP Coordinater Engine

If you have the errors above and you are trying to logon to your server it is pending for uninstalling the Service pack and stays there forever. What can you do ?

Well you can boot in safe mode or get the ownership of the pending.xml and rename it.

mm sounds easy connect to your server  \\servername\windows\winsxs\pending.xml

take ownership if you need and rename this file.  Poweroff your server and you can logon again.

Easy but your server is fucked up beyond any repair

Now you think you can start the setup again and yes you can but the next error is “ Wait for the Windows Modules Installer  “ ?

yes see where the pending.xml file is ? well it is not there anymore. Just poweroff the server start in safe mode and reboot.

But what now ? This server is fried I have not found a solution to fix this or to recreate this issue. Next week I’m in redmond and will ask the Team how to solve this.

The problem is the HKLM\components hive is still loaded in the register. and you can’t do a unload. So therefor any update will fail. I has not finished the update the machine thinks it is still pending

image well I tired another setup with out the auto reboot I do this manual image

 

Service Pack installation failed with error code 0x80070bc9. and Initiating changes for package KB976932. Current state is Partially Installed. Target state is Absent. Client id: SP Coordinater Engine.

Well this means I need to reboot the server.

So there is direct fix but you can use your server everything works but there is still a problem with this server.

hope this helps if I find a solution I will let you know.

Technorati Tags: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
WordPress Tags: Service,Pack,Ends,features,Hyper,server,disaster,Make,backup,Application,Path,TrustedInstaller,Problem,signature,Event,Name,APPCRASH,Version,Timestamp,Fault,Module,Exception,Code,Offset,Stack,Package,Architecture,Culture,Status,Failure,Source,Start,State,Target,Client,Coordinater,Engine,boot,mode,ownership,Poweroff,Easy,setup,error,Wait,Installer,Just,solution,Team,HKLM,components,machine,auto,installation,Current,Absent,errors,Modules,rename,reboot

  • Tag