Loading...
Loading...
When the short date locale setting is configured to display the year as two digits (YY), the Veeam Kubernetes Service service fails to start automatically. When attempting to start the service manually, a pop-up appears with the error: Windows could not start the Veeam Kubernetes Service service on Local Computer. Error 1064: An exception occurred in the service when handling the control request.
Due to the short date locale setting being set to value using two digits to represent the year (YY), instead of four (YYYY), the service fails to process the certificate end date correctly. Validate Cause: Open the Veeam Kubernetes Service log file: C:\ProgramData\Veeam\Backup\Plugins\Kasten\Veeam.Kasten.PlatformSvc.log Locate the error "Certificate was not found." Scroll up and look for the log initialization section (Starting new log.), which will contain data about the system as the service starts. Specifically, look for the "UTC Time:" value. If the year is listed as two digits (see the example screenshot below), the system account's "Short date" format setting is causing the service to fail to start.
This issue was resolved in Kasten K10 Plugin for Veeam Backup & Replication 12.0.1.4. The latest version is available here:
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.