Archive for the ‘Troubleshooting’ Category
KB2397370: A System Center Virtual Machine Manager 2008 R2 virtual machine migrated between Failover Clusters fails with Error 12711
Migration of a virtual machine from one Microsoft Windows 2008 R2 Failover Cluster to another fails. Both Failover Clusters are managed by System Center Virtual Machine Manager 2008 R2 (SCVMM).
VMM cannot complete the WMI operation on server Contoso.LOCAL because of error: [MSCluster_ResourceGroup.Name=”2068e895-4930-42be-a4c8-152ab15a28b8″] The cluster group could not be found.
(The cluster group could not be found (0x1395))
Resolve the issue and then try the operation again.
SCVMM 2008 R2 attempts to execute an operation on the source host (of the source cluster) using the resources names and GUIDS of the destination cluster. Migration will always fail right after the BITS migration when the virtual machine is placed in a saved state.
This issue can only be reproduced under these conditions:
VM is created using Hyper-V
VM is made into an HA VM using the Failover Cluster GUI (resource name will be called something like “Virtual Machine <vmname>”)
VM is in a running state
VM is migrated to a different cluster. VMM will chose Quick Storage Migration with network migration in this case
There are two different workarounds for this issue.
1. Perform the migration when the virtual machine is in a saved state or powered down.
2. Use the Failover Cluster Manager User Interface to locate the virtual machine in “Services and Applications”. Right click the top resource group for this virtual machine and change the Resource Name from “Virtual Machine <vmname>” to “SCVMM <vmname>”. Then refresh the virtual machine in SCVMM PowerShell using the “refresh-vm -force ‘<vmname>'” cmdlet. The virtual machine can now be migrated while in a running state.
This article describes an update rollup package that resolves some issues for the Hyper-V role on a computer that is running Windows Server 2008 R2 and that is dated August 24, 2010.
When a computer has one or more Intel CPUs code-named Nehalem installed, you receive the following Stop error message:
0x00000101 ( parameter1 , 0000000000000000, parameter3 , 000000000000000c) CLOCK_WATCHDOG_TIMEOUT
Note The Nehalem CPU for a server is from the Intel Xeon processor 5500 series and for a client computer is from the Intel Core-i processor series.
Consider the following scenario:
You run a virtual machine (VM) on the computer.
You use a network adapter on the VM to access a network.
You establish many concurrent network connections. Or, there is heavy outgoing network traffic.
In this scenario, the network connection on the VM may be lost. Additionally, the network adapter is disabled.
Note You have to restart the VM to recover from this issue.
When a computer has an Intel Westmere processor, you receive an error message that resembles the following:
STOP: 0x0000001a ( Parameter1 , Parameter2 , Parameter3 , Parameter4 ) MEMORY_MANAGEMENT
How to recover from the error 10207 when performing the Administrator setup console stage:
Setup was not able to retrieve the service account from the specified Virtual Machine Manager server.
Specify a different VMM server and then try the operation again.
Check if the SPN for the SCVMM service account is OK. Use the SETSPN -L, or check the account properties using ADSIEDIT or any other tool that allows you to confirm the SPN. If everything is ok you may need to recreate the SCP container that is under the SCVMM server account (In the picture bellow you can check that using the tool ADSIEDIT.msc).
To manually create this container, use the SCVMM CD and browse to the \Setup folder using command prompt. Run CONFIGURESCPTOOL.EXE –INSTALL from that folder. This should create the SCP, after running the cmd confirm the SCP creation using ADSIEdit. Now rerun the integration setup and all steps should complete without errors.
Note: If you do uninstall/reinstall SCVMM then make sure you patch it to the level it was at before. Up-to-date SCVMM agents cannot communicate with out-of-date SCVMM servers.
The full story Aida-s blog.
From Virtual PC Guy’s Blog, here’s a documentation list for Dynamic Memory included in in the Windows Server 2008 R2 SP1 beta release:
Dynamic Memory Technical Overview whitepaper
This paper talks about what dynamic memory is, what it does and how it does it. It is a good read for those curious to understand what is happening under the covers.
Hyper-V Dynamic Memory Evaluation Guide
This article steps you through the process of setting up SP1 and enabling dynamic memory. It also gives you some good tips on configuration and troubleshooting.
Windows Server 2008 R2 Service Pack 1 – TechNet Center
For all things “Windows Server 2008 R2 Service Pack 1” related – the TechNet Center has you covered.
Hyper-V: Dynamic Memory Survival Guide
The TechNet Wiki also has a “Dynamic Memory Survival Guide” article with some extra links.
Thanks Ben 🙂
Here’s one that I already saw a couple of times. You try to run Service Pack 3 in Windows XP and, almost, immediately you get the error:
The System cannot find the file specified.
From my experience this error is caused by the “Wintrust.dll” and/or ‘atl.dll’. This error can be solved by running regsvr32 from command prompt to register the “Wintrust.dll”:
After searching for similar behavior in the web I also discover that, in some scenarios, you may need to re-register some additional dlls. Here’s a nice list that you can copy to a batch file to run in the computer that is having that error:
# Batch start
# Batch End
Hopefully after that you should be able to run the Service Pack 3 without problems.
Here’s an Interesting one that I ran into recently…
You are running Windows 2003 Server and you have IIS 6 installed and hosting your web-sites. The operating system prompts you to install Microsoft update MS10-040 (KB 982666). After completing the install you note the following errors:
- IIS application pools or websites will no longer start
- IIS web-sites may not be able to start.
- Rapid Fail Protection will shut down your application pools
- An inspection of the event logs show that the IIS worker processes are terminating unexpectedly, showing event messages similar to the following:
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Time: 10:55:01 AM
Description: A process serving application pool ‘DefaultAppPool’ terminated unexpectedly. The process id was ‘1234’.
The process exit code was ‘0xffffffff‘.
Ensure that you are seeing the above process exit code ‘0xffffffff‘ for which this post applies.
So what really happens?
NOT ALL IIS installs running on Windows 2003 will be impacted by this patch. YOU CAN INSTALL the patch and continue running IIS normally. The only case when the error occurs is the following:
You installed Windows 2003 and you did not install IIS 6 when you did this. You then installed Service Pack 1 or Service Pack 2 directly and afterwards you decided to install IIS. When installing IIS you were prompted to insert the original installation disk (not the Service Pack 1 disk or the Service Pack 2 disk).
If you followed the scenario above, you will most likely end up with what is called a binary mismatch between the operating system dlls and the dlls that belong to IIS. In plain English: your Windows 2003 files are those of Service Pack 2 and your IIS files are those of Service Pack 1 or RTM.
How can you verify that you are in this scenario?
In a Windows 2003 command prompt, type the following command:
This will show you the Windows 2003 version that you are running and the patch level. You should see that the operating system is patched to Service Pack 2. If you are not, you should seriously consider upgrading since Service Pack 1 of Windows 2003 is no longer supported.
If you are running service pack 2, then go ahead and check the version of an IIS 6 files in the following folder: %windir%\system32\inetsrv. The minimum version of the file(s) is the following if you are running SP2.
Solution to this:
Should you find yourself in this situation, and only after you confirm the symptoms, you should go ahead and re-install the Service Pack 2 from Windows 2003. To download the Service Pack you can go to:
You do not need to un-install and re-install Service Pack 2, just re-install it. Upon install, the Service Pack installer will make a list of all Windows components that are installed on your system (including IIS) and will update their binaries.
This issue is specific to Windows Server 2003. We won’t run into this issue on a Windows 2008 server.
The Credits for this solution goes for the excellent WebTopics Blog.