Veeam Kubernetes Service Fails to Start - Error 1064
Challenge
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.
When this occurs, the following error is written to the Veeam Kubernetes Service log file:
C:\ProgramData\Veeam\Backup\Plugins\Kasten\Veeam.Kasten.PlatformSvc.log
Error Failed to run Kasten Platform Service. Error Certificate was not found. Thumbprint: 'ABFD8B5FBCDFF6260D48470BE10FAA3762ABD310' (Veeam.Backup.PlatformServices.Kasten.CertificateNotFoundException)
Cause
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.
Solution
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.