I've found a few postings on Event ID 157 for Windows 2012 R2, but no answers
We've upgraded from Server 2012 to 2012 R2. Hyper-V Role. Event ID 157 occurs when Windows Backup is running to backup Hyper-V machines. People have reported the same issue I am having. They have ID 157 occurring only during the Windows Backup
process or if they use VSS Snapshots to backup hyper-v virtual machines.
I've found event ID 157 was designed for 2012 R2 Storage Groups when a disk is removed, so it seems like it is a bug showing up during Windows Backup.
One time (out of about 10 now - once each day) that this event was logged, a software RESET was sent to the LSI Mega Raid controller for half of the array and consistency checks were immediately done. I hope this does not happen again.
Everything worked fine before we moved from 2012 to 2012 R2. I've done a clean install and it still happens.
I've looked through the event logs on the virtual machines and we have one Windows 2008 Server running SQL 2008 R2 and it chokes through the entire backup process with hundreds of errors, starting with the SQL VSS Writer receiving a command that it does
not understand. From then onward it says tables and data are corrupt, but the normal SQL maintenance job we have running for SQL Server backs up the databases and performs consistenacy checks without issues.
I've just remove the SQL Server from the Windows Backup and will see how it goes tonight.
In case this is related to the SQL Server, here's the error that is 1st logged as soon as the Windows Backup on the host begins:
Event ID 513, CAPI2, Error, Cruptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Details: AddCoreCsiFiles: BeginFileEnumeratrion() failed.
System Error: Access is denied.
After that it freezes the databases, gives dozens of errors for each table, and then restores each table to normal operation.
The Guest SQL server appears to always be the 1st VM to get backed up, so I doubt this has anything to do with it, but thought I should provide as many details as possible, especially when everyone else has discovered it is VSS related and this guest is
reporting VSS errors.
What do you think?
thanks
John
P.S. there are no hard drive errors, so running check disk will not help.