Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Snapshots of VMs with an incorrect date are not deleted by alert management actions

Snapshots of VMs with an incorrect date are not deleted by alert management actions

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 926 Votes: 0 Revisions: 10



The Delete Snapshot alert trigger management action does not delete snapshots of Hyper-V VMs. The issue can occur for more than one Hyper-V VM on the same host.


NPM on Hyper-V


The snapshots of the affected VMs are displayed with an incorrect creation date in the list of snapshots in the Delete Snapshots dialog.


When a virtual machine snapshot is created in a Hyper-V environment, the creation date of the snapshot is saved incorrectly. This is a known issue with Hyper-V.

If a virtual machine contains a snapshot with a creation date that is lower than the minimum SqlDateTime value (January 1, 1753), the date is considered invalid, and the Delete Snapshot action by design does not delete the snapshot.

For more information, see the Hyper-V documentation and the Microsoft Technet forums.

Last modified