Windows Server 2019 – Hyper-V VMMS Errors Event ID 19100

March 25, 2020

On the internet I found this nice visual that helps understanding the Hyper-V and Backup Infrastructure.

image

After we installed a Hyper-V on a new Window Server 2019, everything seemed to be running OK.

But apparently after the 1st backup there where a lot of errors in the Event viewer ID 19100.

Error 0x8007052F

image

After that point no backups would run anymore, until the Hyper-V host was restarted.

Next backup cycle the same story Sad smile

So I checked the VSS writer to see if all was OK. But I saw that there was an error reported?

Microsoft Hyper-V VSS writer : Unexpected Error ?

image

So that did not help a lot ?

Next I ran some VSS diagnostics apps, but no errors found ?

VSSDoctor :

image

VssDiag :

image

Everything pointed out to be OK, but it was not … Sad smile

Solution :

Conclusion was that this could be nothing else then a Permission issue.

So I ran the Resultant Set of Policy – rsop.msc

image

I noticed that some policies where overruled by a Domain Policy so I started cleaning up.

But still no success until I noticed that the Local Log on As a Service Policy again I clean this one up.

And check the local Policy settings for this policy using SecPol.msc

image

I noticed that the ‘NT VIRTUAL MACHINE\Virtual Machines’ was not in there ?

After adding the NT VIRTUAL MACHINE\Virtual Machines to the LOCAL Policy ‘Allow run as a Service’

All Backup problems were solved. Smile

TIPS :

Make sure the Hyper-V Guest Integration Services and the Backup (Volums Shadow Copy) are active as well

image

And the CheckPoints are set like this

image

Enjoy !


Windows Server 2019 – Hyper-V VMMS Errors Event ID 15300 – 19600 – 15010 – 16010

March 13, 2020

After restarting the Hyper-V manager or creating a new VM you can get these errors

Event ID 15300 & 19600 & 15010 & 16010 Errors

image

It took me some time to figure out what was causing this …

SOLUTION :

Open the Hyper-V Settings

The reason was an incorrect path in the Hyper-V settings

image

After correcting the PATH to the new destination, all was OK again Smile

Enjoy!


Write cache enabled Event ID 32 Error

March 11, 2019

After physical to Virtual conversion, we get this event ID 32 Error on a regular basis..

image

The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled. Data corruption may occur.

Solution :

See here : https://support.microsoft.com/en-ca/help/324805/how-to-manually-turn-disk-write-caching-on-or-off
Turn Disk Write Caching On or Off
  1. Right-click My Computer, and then click Properties.
  2. Click the Hardware tab, and then click Device Manager.
  3. Expand Disk Drives.
  4. Right-click the drive on which you want to turn disk write caching on or off, and then click Properties.
  5. Click the Policies tab.
  6. Click to select or clear the Enable write caching on the disk check box as appropriate.
  7. Click OK.
For Windows Server 2008
  1. Right-click Computer, and then click Properties.
  2. Click the Device Manager link under Tasks.
  3. Expand Disk Drives.
  4. Right-click the drive on which you want to turn disk write caching on or off, and then click Properties.
  5. Click the Policies tab.
  6. Click to select or clear the Enable write caching on the disk check box as appropriate.
  7. Click OK.

To find out the DISK number relation use this SysInternal tool, diskext.exe :

image

\Device\Harddisk0\DR0 = C drive

If you see the yellow exclamation mark saying you are not allowed to change the caching …

image

See here for more Information :

http://techgenix.com/hyper-v-optimization-tips-part1/

Enjoy!


Windows Server 2016 – Hyper-V CheckPoints Disk Space

December 4, 2018

Once you create VM checkpoints in Hyper-V it might start consuming a lot a disk space afterwards.

image

Because it will write data to the AVHDX files.

You can use PowerShell to investigate the current disk size.

Get-VM YourVM | Select-Object VMId | Get-VHD | Select-Object –Property path,computername,vhdtype,
@{label=’Size(GB)’;expression={$_.filesize/1gb –as [int]}}

image

As you can see the VHD Type is saying DIFFERENCING.

That is because you have a checkpoint pending. And this is NOT recommended in a production environment.

There are some tricky scenario’s where deleting checkpoints can corrupt your VM.

See here for more info

Enjoy !


Windows Server 2016 – Application Errors after a P2V conversion Event ID 1000 Error

October 30, 2018

After converting a Physical server to a VM, I got a lot of Application Errors 1000.

Looking at the details it was relating to, amongst others, HP related drivers and software

Example : This error shows it is trying to reach a Tape device which is not present in a VM…

image

SOLUTION :

First uninstall all hardware drivers that are not needed in the new VM.

1. Open CMD with admin privileges and run this command

set devmgr_show_nonpresent_devices=1

2. Next run this command

devmgmt.msc

And go to VIEW, select SHOW HIDDEN DEVICES

image


3. Make backup of your VM

Before going to next step MAKE SURE you have a good backup of the current SYSTEM STATE

4. Expanded list

Look at all the GREYED out devices and UNINSTALL these Software and Drives

image

5. Uninstall COM Objects

From the Event Viewer Error I could see we where dealing with a COM related DLL

Use WBEMTest.exe to investigate if the COM Object is still in use.

image

In my case I was sure it would not be needed since the HW was not available anymore

Look for the COM DLL : HPWMITape.dll


image

Run the uninstall command :

regsvr32 /u HPWMITape.dll

Enjoy !


Windows Server – Hyper-V migration VM’s

June 25, 2018

Working with Hyper-V and migrating VM’s between VM Hosts can give some surprises now and than.

The IP xxx.xxx.xxx.xxx address you have entered for this network adapter is already assigned to another adapter Microsoft Virtual Machine Bus Network Adapter #2. Microsoft Virtual Machine Bus Network Adapter #2 is hidden from the Network and Dial-up Connections Folder because it is not physically in the computer or is a legacy adapter that is not working If the same address is assigned to both adapters and they both become active, only one of them will use this address. This may result in incorrect system configuration.

Recently I had to migrate a VM running on old Windows OS to a new Hyper-V host.

You would expect to just copy the VM disk for one host to the other. And start it up.

Indeed so far so good. But when the VM had a FIXED IP Address before. You will now see that new copy of the VM has assigned a DHCP IP address ?

The reason is that the the Network Adapter has changed when copying over the VM from one host to the other.

When you try to put back in the same fixed IP ADDRESS you will see this message appear.

image

Whatever you try it will not accept the same IP Address as before Sad smile

Which can be problematic for certain applications running on the VM.

SOLUTION :

  1. Start a CMD prompt as an admin
  2. Type: set devmgr_show_nonpresent_devices=1 and press ENTER
  3. Type DEVMGMT.MSC and press ENTER
  4. In Device Manager, click VIEW then SHOW HIDDEN DEVICES

image

  1. Expand NETWORK ADAPTORS
  2. Right click on each greyed out NIC and select UNINSTALL

image

  1. Close all of the Windows (including your IP, Network and Sharing Center…)
  2. Now can assign the again the same fixed IP ADDRESS to the new Adapter that was added to you VM.

Enjoy!