IT Core Blog

Never stop questioning. Curiosity has its own reason for existing…

Archive for the ‘Troubleshooting’ Category

SCVMM P2V fails with Error 2910 (0x80070005) Access Denied

leave a comment »

Symptom

When using Microsoft System Center Virtual Machine Manager 2008 to perform a Physical-to-Virtual conversion (P2V), the following error message appears during the Scan System phase.
Error (2910)
VMM does not have appropriate permissions to access the resource on the %server.
Access is denied (0x80070005)
Recommended Action
Ensure that Virtual Machine Manager has the appropriate rights to perform this action.
Additional Information: The Source computer is the machine intended to be virtualized in the P2V conversion.

 Cause

This failure is typically caused by either of the following conditions:

•  The credentials provided during the P2V wizard is not a member of the local ‘Administrators’ group on the Source computer.
•  The Source computer does not allow remote WMI calls to the CIMV2 namespace for the credentials entered during the P2V wizard.

Resolution
To resolve the problem, follow these steps:

  1. Make sure that the account used during the P2V wizard is a member of the local ‘Administrators’ group on the Source computer. Note Pay particular attention to this if the SCVMM server and Source computer are in different domains.
  2. During the Scan System phase of the P2V conversion, SCVMM makes WMI calls to the CIMV2 namespace on the Source computer to pull basic system information. If these WMI calls fail, then the P2V conversion will also fail. To verify WMI connectivity to the CIMV2 namespace on the Source computer, perform the following actions from the SCVMM server:
  3. Click Start , point to Run and type ” WBEMtest” (without the quotes) in the Open box and click OK . This will open the WBEMtest window.
  4. Click Connect in the upper right hand corner.
  5. Now, connect to the CIMV2 namespace on the Source computer.

Example: \\Source\ROOT\CIMV2

                Note Be sure to use the name of your Source computer.

  1. Then click Connect to complete the connection. This should connect without any errors displayed.
  2. Just to confirm access to a sample object, select Open Class and type Win32_PhysicalMemory
  3. You should see objects populate in the Object Editor window. The actual content returned is not as important as the fact that a remote connection to the CIMV2 namespace was established.
  4. Open wmimgmt.msc and verify connectivity to the Local computer and also check the ‘Remote Enable’ permissions.
    1. Click Start , point to Run and type wmimgmt.msc and click OK . This will open the WMI Control (Local).
    2. Right click on the WMI Control (Local) node and select Properties .
    3. Select the Security tab, highlight Root and then open security by clicking the Security button in the lower right.
    4. Select “Remote Enable” permission for Everyone or the specific user account that you want to grant this permission to.
    5. This action does not require a reboot.
    6. Open dcomcnfg and verify that DCOM is running and also check the ‘Remote Activation’ permission.
      1. Click Start , point to Run and type dcomcnfg and click OK . This will open the Component Services snap-in.|
      2. Expand Component Service , then Computers , then My Computer . If My Computer has a red down arrow mark, it means that the service is not running. It will need to be started.
      3. Right click on My Computer and select Properties and select the COM Security tab.
      4. Click Edit Limits under the Launch and Activation Permissions section.
      5. For the Everyone user give the “Remote Activation” permission or add the specific user account that you want to grant this permission to.

Note The following error message may occur if the appropriate WMI permission is not granted to the user:
Access Denied” with Error Code: 0x80041003

  1. This problem can also occur if the OLE registry key is missing or has the incorrect value on the Source computer.
    1. Start Registry Editor.
    2. Locate the following path:
      HKLM\SOFTWARE\Microsoft\OLE
    3. This key should have a REG_SZ value EnableDCOM and a value of Y

Written by IT Core

November 23, 2010 at 9:17 PM

KB2465160: Add Host or other action fails with (2916) 0x80338126 in System Center Virtual Machine Manager 2008

leave a comment »

From Microsoft , KB2465160.

Symptoms
Adding a Host to System Center Virtual Machine Manager 2008 (SCVMM 2008) fails with a variation of Error (2916):

Error (2916)
VMM is unable to complete the request. The connection to the agent ServerA.contoso.com was lost.
(The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. (0x80338126))

Recommended Action:
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTP traffic. If the error persists; reboot ServerA.contoso.com and then try the operation again.

Cause
Specific content is being filtered by a non-Windows firewall. The firewall could be software installed on either the SCVMM 2008 Server or the Host that is being added. More likely, there is a hardware appliance firewall on the network between the two communicating servers.

Resolution
Test multiple communication protocols between the two systems; the SCVMM 2008 Server and Host in this example. Some firewalls can have content filtering enabled despite showing that it is not. Remove all non-Windows software firewalls and bypass all hardware appliance firewalls entirely long enough to perform testing to verify whether or not they are contributing to the problem.

The following tests are examples of protocols that should always succeed. Test both directions always:

Ping by DNS name in both directions (NETBIOS and FQDN). The IP address returned must match.
Access to ‘\\ServerA.contoso.com\admin$’ from the ‘Run’ command in both directions. This must succeed.
From Server B: \\ServerA.contoso.com\admin$
From Server A: \\ServerB.contoso.com\admin$
WinRM basic connectivity in both directions. This must succeed. If it does not, execute ‘winrm qc’ on both servers, accepting all prompts, then test again.
Remote NETBIOS test: winrm id -r:remoteserver
Remote FQDN test: winrm id -r:remoteserver.contoso.com
WinRM successful reply example:

C:\>winrm id -r:ServerA
IdentifyResponse
    ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
    ProductVendor = Microsoft Corporation
    ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0

More Information
Recently a firewall appliance sold by a major vendor showed content filtering disabled and not licensed to be turned on, yet was still filtering specific content. This was discovered through examination of network traces. Do not assume content, protocols or traffic are not being blocked. Perform tests to verify.

Written by IT Core

November 23, 2010 at 9:12 PM

KB2413735: Mouse and screen resolution issues when managing a virtual machine using the Hyper-V

leave a comment »

From KB2413735

Windows Server 2008 or Windows Server 2008 R2, you may experience one of the following symptoms when you connect to a Hyper-V virtual machine using the Hyper-V Manager console or the System Center Virtual Machine Manager Administrator Console:
· The mouse cursor is frozen or has disappeared
· The screen resolution has reverted to the default size
If you connect to the virtual machine using a Remote Desktop Connection (RDP), the symptoms listed above are not exhibited.

This issue can occur after a new Hyper-V VMMS certificate is generated.
Note: The following event will be logged in the Hyper-VMMS event log when a new VMMS certificate is generated:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Event ID: 12520
Level: Warning
Description:
Auto-generating a self-signed certificate for server authentication.

To resolve this issue, perform one of the following steps on the Hyper-V server:
·Place the virtual machines in a saved state and then resume the virtual machines.
or
·Restart the virtual machines.

The self-signed certificate that is generated by the Hyper-V Virtual Machine Management service is valid for one year.

To create a self-signed certificate that doesn’t expire for several years, perform the following steps:
1.
Copy the PowerShell script from the following Microsoft Web site:
http://gallery.technet.microsoft.com/ScriptCenter/en-us/be2da634-978b-48d7-b3ab-01c593c9d177 (http://gallery.technet.microsoft.com/ScriptCenter/en-us/be2da634-978b-48d7-b3ab-01c593c9d177)
2. Paste the script into notepad, and then save the file as Cert.ps1. 
3. Copy Makecert.exe to the same directory as the Cert.ps1 file.
For more information on how to obtain Makecert.exe, please visit the following Microsoft web site: http://msdn.microsoft.com/en-us/library/aa386968(VS.85).aspx (http://msdn.microsoft.com/en-us/library/aa386968(VS.85).aspx)
4. Open an elevated Windows PowerShell command prompt. 
5. Run the Cert.ps1 script.

🙂

Written by IT Core

September 23, 2010 at 12:14 PM

Hyper-V R2 Cluster CSV stops working when NTLM is disabled in cluster with Hyper-V Enabled

leave a comment »


Hyper-V R2 Cluster CSV stops working when NTLM is disabled in cluster with Hyper-V Enabled

ID: 5121
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: DCM_VOLUME_NO_DIRECT_IO_DUE_TO_FAILURE
Message: Cluster Shared Volume ‘%1′ (’%2′) is no longer directly accessible from this cluster node

This error may be caused because the NTLM was disabled in your Hyper-Host. Enabling a policy to disable NTLM may break CSV and cause the alert described before.

If the NTLM was disabled using GPO in your Active Directory Domain, identify the GPO with this setting and create an exception to this policy for all clustered Hyper-V computer objects. Alternatively you can create and link another GPO (GPO with “enable NTLM” setting) that applies just to the clustered hosts. 

 🙂

Written by IT Core

September 21, 2010 at 10:07 PM

Hyper-V Host may stop when VM’s Dynamic Memory use all available RAM

leave a comment »

When setting up VMs with dynamic memory remember that your hyper-v host may stop if those VMs consume (or try to) use all existing memory on the host leaving nothing for the parent partition. 

To prevent that Crete the following Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ Virtualization
RED_DWORD value
Name = MemoryReserve
Setting = amount of MB to reserve for the parent partition.
After setting up the desired value you must reboot the host to the setting become active.

Note: if you set this value too low; VMs will be able to use too much memory and cause performance issues for you. Equally – the higher you set this the fewer VMs you can run.
For more information about memory reserve with dynamic memory check the Virtual PC Guy’s Blog

Written by IT Core

September 21, 2010 at 9:52 PM

How to manually remove a missing host from SCVMM

leave a comment »

You may see the following error when trying to remove a “dead” host from your SCVMM console.

Error (406)
Access has been denied while contacting the server <servername>. 

Recommended Action
1. Verify that the specified user account has administrative privileges on <servername>.
2. Verify that DCOM access, launch, and activation permissions are enabled on <servername> for the Administrators group. Use dcomcnfg.exe to modify permissions, and then try the operation again.

If that server is no longer online you need a way to remove it from your SCVMM. To do that you may use the PowerShell that come with the SCVMM console:

get-vmmserver <Vmm_Server_Name>
Than forcibly remove the missing host server by running:
remove-vmhost <Host_Server_Name> –force
Wait a few seconds and the host should be removed from the console.

🙂

Written by IT Core

September 21, 2010 at 8:49 PM

KB:980054 Recommended hotfixes and updates for Windows Server 2008 R2-based server clusters

leave a comment »

From KB:980054
This article describes the hotfixes and updates that we recommend that you install on each node of a Windows Server 2008 R2-based failover cluster. When you update your Windows Server 2008 R2-based failover cluster, you help reduce downtime. You also help decrease the number of errors, failed print jobs, and other support issues that you experience.

We recommend that you install the following hotfixes if you plan to install the failover clustering feature on Windows Server 2008 R2 Core:
KB978309: IPv6 transition technologies, such as ISATAP, 6to4 and Teredo do not work on a computer that is running Windows Server 2008 R2 Server Core
KB976571: Stability update for Windows Server 2008 R2 Failover Print Clusters

For additional information about Network related issues and Hyper-V check my previous post at:
Hyper-V Fixes for Network Connectivity related issues

🙂

Written by IT Core

September 11, 2010 at 10:59 AM

KB2397370: A System Center Virtual Machine Manager 2008 R2 virtual machine migrated between Failover Clusters fails with Error 12711

leave a comment »

 

From KB2397370

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

Error (12711)
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))
Recommended Action
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.

Written by IT Core

September 2, 2010 at 12:02 PM

KB2264080: Update rollup package for the Hyper-V role in Windows Server 2008 R2

leave a comment »

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.

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

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

Issue 3
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

Source: KB2264080

Written by IT Core

August 25, 2010 at 12:00 AM

SCVMM integration with Opsmgr fails with the error ID:10207

leave a comment »

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.

ID: 10207

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.

Written by IT Core

July 18, 2010 at 12:00 AM

Documentation for Dynamic Memory Resources

leave a comment »

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.
http://download.microsoft.com/download/E/0/5/E05DF049-8220-4AEE-818B-786ADD9B434E/Implementing_and_Configuring_Dynamic_Memory.docx

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.
http://technet.microsoft.com/en-us/library/ff817651(WS.10).aspx

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.
http://technet.microsoft.com/en-us/library/ff817647(WS.10).aspx

Hyper-V: Dynamic Memory Survival Guide
The TechNet Wiki also has a “Dynamic Memory Survival Guide” article with some extra links.
http://social.technet.microsoft.com/wiki/contents/articles/hyper-v-dynamic-memory-survival-guide.aspx

Thanks Ben 🙂

Written by IT Core

July 15, 2010 at 12:53 AM

Microsoft Network Monitor 3.4 available for download

leave a comment »

Microsoft Network Monitor 3.4 available for download

Check out the new features at the Network Monitor Team Blog Beta announcement.

Additionally check the related Network Monitor Resources:

  1. Network Monitor Experts
  2. Network Monitor Parsers
  3. Network Monitor Blog
  4. Network Monitor Forums

Written by IT Core

July 1, 2010 at 9:12 PM

Windows XP Service Pack 3 setup error: The System cannot find the file specified

with 3 comments

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:
Setup 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”:
regsvr32 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
regsvr32 wuapi.dll
regsvr32 wuaueng.dll
regsvr32 wucltui.dll
regsvr32 wups.dll
regsvr32 wuweb.dll
regsvr32 atl.dll
regsvr32 Softpub.dll
regsvr32 Wintrust.dll
regsvr32 Initpki.dll
regsvr32 Mssip32.dll
# Batch End

Hopefully after that you should be able to run the Service Pack 3 without problems.

🙂

Written by IT Core

June 25, 2010 at 12:48 AM

Posted in MS Hotfixes, Troubleshooting

Tagged with

IIS 6 applications may stop responding after you install Microsoft update KB 982666

with 2 comments

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
Date:  12/9/2009
Time:  10:55:01 AM
User:  N/A
Computer: WEBSERVER01
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:

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

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:
http://www.microsoft.com/downloads/details.aspx?FamilyId=95AC1610-C232-4644-B828-C55EEC605D55&displaylang=en
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.

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

Written by IT Core

June 15, 2010 at 9:12 PM

Posted in MS Hotfixes, Troubleshooting

Tagged with

Hyper-V Backups Cause Large Registry Files and may slow system boot

leave a comment »

Acording with Ben Armstrong and KB982210 – The startup time increases every time after you back up the data on all the disks of the computer in Windows Server 2008 R2 if the computer runs some virtual machines.

Note: the KB982210 applies to Windows Server 2008 R2 (not Windows Server 2008).

 

 

Additional Errors:

Log Name: System
Source: PlugPlayManager
Date: date time
Event ID: 12
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: computer name
Description:
The device ‘MSFT Virtual HD SCSI Disk Device’ (SCSI\Disk&Ven_MSFT&Prod_Virtual_HD\ GUID ) disappeared from the system without first being prepared for removal.

Short description by Ben Armstrong:
Whenever we backup a virtual machine using VSS, we momentarily connect the backup copy of the virtual machines virtual hard disks to the parent partition in order to clean them up after backup.  Unfortunately with Windows Server 2008 R2 a new plug-and-play entry would get created in the Windows registry each time that we did this.  Over time this would cause the registry to get larger and larger, which would in turn slow down the Windows boot process.

Written by IT Core

June 15, 2010 at 9:01 PM