Windows Event Log Errors & Warnings

Discussions specific to Microsoft Hyper-V hypervisor

Windows Event Log Errors & Warnings

Veeam Logoby Nick-SAC » Sun May 13, 2018 6:29 pm

Note: I haven’t opened a support ticket on this yet because I don’t think it’s actually a problem, i.e., I suspect it’s just Windows reacting to the appearance & disappearance of the “Hard Disks” and “Volumes” temporarily created in the normal course of the VB&R backup processes.


Infrastructure:

Backup Server
Physical : Server 2012-R2 SP1 with Hyper-V Host Roll
Primary Backup Repository = Internal HDDs
VB&R 9.5.0.1536 (all-in-one configuration)

Production Servers
Host: Physical : Server 2008-R2 SP1 : Hyper-V Host
VMs : Server 2008-R2 SP1 : Hyper-V Guests


Issue:
When running the backups from the Backup Server I’m getting a slew of Errors & Warnings in the Logs on the Production Server Host, specifically as shown below (in an actual chronological order and with the approximate number of instances per backup session):

================================================================

1x
Log Name: System
Source: Virtual Disk Service
Date: 5/12/2018 11:04:50 PM
Event ID: 9
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
Unexpected provider failure. Restarting the service may fix the problem. Error code: 80004005@02000014

-------------------------------------------------------------------------------------------------------

1x
Log Name: System
Source: VDS Basic Provider
Date: 5/12/2018 11:08:02 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
Unexpected failure. Error code: D@01010004

-------------------------------------------------------------------------------------------------------

2x
Log Name: System
Source: volsnap
Date: 5/12/2018 11:10:40 PM
Event ID: 27
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
The shadow copies of volume \\?\Volume{4c937bnn-bd4e-11e5-8c66-ac220b8b292a} were aborted during detection because a critical control file could not be opened.

nn These 2 digits vary from instance to instance.

-------------------------------------------------------------------------------------------------------

10x
Log Name: System
Source: Microsoft-Windows-FilterManager
Date: 5/12/2018 11:10:45 PM
Event ID: 3
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: <ComputerName>
Description:
Filter Manager failed to attach to volume '\Device\Harddisk<#>\DR<##>'. This volume will be unavailable for filtering until a reboot. The final status was 0xc03a001c.

# These numbers vary but they are always numerically higher than the number of physical HDDs in the system.

-------------------------------------------------------------------------------------------------------

10x
Log Name: System
Source: Disk
Date: 5/12/2018 11:10:55 PM
Event ID: 51
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
An error was detected on device \Device\Harddisk<#>\DR<##> during a paging operation.

# These numbers vary but they are always numerically higher than the number of physical HDDs in the system.

-------------------------------------------------------------------------------------------------------

4x
Log Name: System
Source: volsnap
Date: 5/12/2018 11:10:58 PM
Event ID: 16
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
The shadow copies of volume \\?...nn-nnnn-nnnn-ac220b8b292a} were aborted because volume \\?... nn-nnnn-nnnn-ac220b8b292a}, which contains shadow copy storage for this shadow copy, was force dismounted.

nn These digits vary from instance to instance.

-------------------------------------------------------------------------------------------------------

20x
Log Name: System
Source: Microsoft-Windows-FilterManager
Date: 5/12/2018 11:11:19 PM
Event ID: 3
Task Category: None
Level: Error
Keywords:
User: <ComputerName\UserName>
Computer: <ComputerName>
Description:
Filter Manager failed to attach to volume '\Device\HarddiskVolume<##>'. This volume will be unavailable for filtering until a reboot. The final status was 0xc03a001c.

## This number varies but it is always numerically higher than the number of actual Volumes in the system.

================================================================

So, is it okay to simply ignore these... or might it be cause for concern?

Thanks,
Nick
Nick-SAC
Influencer
 
Posts: 17
Liked: 1 time
Joined: Fri Oct 27, 2017 5:42 pm
Full Name: Nick

Re: Windows Event Log Errors & Warnings

Veeam Logoby foggy » Fri May 18, 2018 4:45 pm

Hi Nick, I'd let our engineers take a look, just to be sure.
foggy
Veeam Software
 
Posts: 16178
Liked: 1290 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Windows Event Log Errors & Warnings

Veeam Logoby Nick-SAC » Fri May 18, 2018 7:08 pm

Thanks Foggy, I've got a support ticket opened with them now

Case # 03011866

Nick
Nick-SAC
Influencer
 
Posts: 17
Liked: 1 time
Joined: Fri Oct 27, 2017 5:42 pm
Full Name: Nick

Re: Windows Event Log Errors & Warnings

Veeam Logoby Nick-SAC » Sat May 19, 2018 12:48 pm

In the interest of making this Topic thread useful to others, here’s one more thing I probably should have noted in my initial report...

During the VB&R Backups; in the VM Guest Event Logs, I will get anywhere from none to several dozen instances of the below Error which I also see outside of VB&R systems, e.g., when using MS Windows Server Backup and/or attaching/detaching a Pass-Thru HDD to the virtual SCSI Controller of a Windows 2008-R2 VM.

I didn’t mention it because it’s documented to be a non-issue (as seen here http://support.microsoft.com/kb/979391 ) which can be safely ignored... but perhaps it’s playing a part in triggering the aforementioned Errors & Warnings on the Hyper-V Host?

------------------------------------------------------------------
Log Name: System
Source: VDS Basic Provider
Date: 5/12/2018 11:03:48 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <ComputerName>
Description:
Unexpected failure. Error code: 490@01010004
------------------------------------------------------------------
Nick-SAC
Influencer
 
Posts: 17
Liked: 1 time
Joined: Fri Oct 27, 2017 5:42 pm
Full Name: Nick

Re: Windows Event Log Errors & Warnings

Veeam Logoby foggy » Sun May 20, 2018 8:57 pm

Looks relevant to me. I'd appreciate if you share the results of support findings here. Thanks.
foggy
Veeam Software
 
Posts: 16178
Liked: 1290 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 7 guests