Issue

After installing Windows Updates on a Windows Server 2008R2 server, Veritas Backup Exec Administrative Console crashes on launch.

BackupExec has stopped working
Details:
Problem signature:
  Problem Event Name:    CLR20r3
  Problem Signature 01:    BackupExec.exe
  Problem Signature 02:    20.0.1188.1650
  Problem Signature 03:    5b5b3903
  Problem Signature 04:    mscorlib
  Problem Signature 05:    4.8.4110.0
  Problem Signature 06:    5de6dafa
  Problem Signature 07:    113a
  Problem Signature 08:    61
  Problem Signature 09:    System.Reflection.AmbiguousMatch
  OS Version:    6.1.7601.2.1.0.272.7
  Locale ID:    2057
  Additional Information 1:    a10f
  Additional Information 2:    a10f1727f0cb04d1a53f76cc240325be
  Additional Information 3:    990c
  Additional Information 4:    990c6bf0f28663f36ab65b91a91027fd

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Read more: Veritas Backup Exec Crashes after Windows Update

DELL iDRAC 6 virtual console runs on Java and has always been a major pain in the backside. Almost every Java update breaks something, and who wants to install Java these days anyway...

I recently had to revisit this topic. In order to avoid a long drive I needed to access a remote DELL PowerEdge server via iDRAC 6. First, without expecting much, I tried this on a Windows 11 PC with the latest version of Java 8.

Read more: Connecting to DELL PowerEdge iDRAC 6 Virtual Console from Windows 11 in 2023

Every night, at the same time Exchange 2010 server records following two errors in Application Logs:

Source: MSExchangeIS
Event ID: 9702
Level: Error
Task Category: Exchange VSS Writer
Description: Exchange VSS Writer (instance c939cecf-f703-4a02-b5ec-3a08606eeefb:67) failed with error code 1295 when processing the post-snapshot event.

Read more: Shadow copy errors on Exchange 2010 server (ESE - 2007 and VSS - 9702)

Issue

Windows Server 2016 (Hyper-V Host) shut down unexpectedly without any obvious external reason. The shutdown was graceful, not a crash or power cut.

Windows Event System Logs contain the following related entries:

Event ID: 109
Source: Kernel-Power
Description:
The kernel power manager has initiated a shutdown transition.
Shutdown Reason: Battery

Read more: The kernel power manager has initiated a shutdown transition - Shutdown Reason: Battery