This is a known issue. As a workaround, do the following:
- Stop the Deep Security Manager service.
- Back up the database.
- Execute the following SQL command on the database where the Deep Security Manager is located. You can verify the database name from the DSM console under Administration > System information.
update hosts set virtualpowerstate=0 where virtualpowerstate=1
If the said error message appeared when accessing the Alerts section of Deep Security Manager, run the following SQL commands:
update alert2hosts set TimeResolved = getdate() where TimeResolved is NULL
update alert2s set TimeResolved = getdate() where TimeResolved is NULL