Monitoring of the Windows Application event channel identified application-level errors affecting two different server contexts.
One group of events occurred on a SQL Server during a Veeam Backup operation, while another occurred on an SH server during catalog database initialization.
Event Location
Location: EventChannel
Channel: Application
The detected events originated from the Windows Application event channel and reflected errors generated by applications and database-related operations running on the monitored servers.
SQL Server Error During Veeam Backup
On the SQL Server, the application error was observed during a Veeam Backup operation.
The identified cause was that the transaction log for the database was full.
This database condition generated Application error events during the backup activity.
Catalog Database Initialization on the SH Server
A separate application error was also observed on an SH server.
In this case, the event occurred during catalog database initialization.
The catalog database initialization process therefore represented a second and separate source of Application events.
Understanding the Anomaly
The detected event activity was not generated by one common problem affecting both servers.
Instead, two different operational situations were identified:
a full database transaction log during Veeam Backup on a SQL Server;
an issue during catalog database initialization on an SH server.
Separating the events by server and application context makes it possible to understand the cause of each event group.
Conclusion
The Windows Application event anomaly was associated with two server-side application conditions.
On the SQL Server, Veeam Backup activity encountered a full database transaction log. On the SH server, Application events were generated during catalog database initialization.
