Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

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: 1,153 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