Case #04918346
We are using Veeam Agent for windows. The version of veeam is 5.0.0.4301 and it is working on Windows 10 pro. The error we are getting when trying to do a backup is "Error: Key not valid for use in specified state. "
WE have updated the system and the veeam software, rebooted the machine etc.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jul 16, 2021 3:49 pm
- Full Name: Synack Technology Services
- Contact:
-
- Veteran
- Posts: 3077
- Liked: 455 times
- Joined: Aug 07, 2018 3:11 pm
- Full Name: Fedor Maslov
- Contact:
Re: Error: Key not valid for use in specified state.
Hi Shaunp,
Please, work with our tech support engineers directly to get it sorted as debug logs analysis is required to understand and resolve the issue.
Thanks
Please, work with our tech support engineers directly to get it sorted as debug logs analysis is required to understand and resolve the issue.
Thanks
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jul 16, 2021 3:49 pm
- Full Name: Synack Technology Services
- Contact:
Re: Error: Key not valid for use in specified state.
Thank You. I have submitted the windows logs in my case.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Nov 09, 2017 7:46 pm
- Full Name: Derek Brown
- Contact:
Re: Error: Key not valid for use in specified state.
Did you happen to get this resolved? We are having the same error, but Veeam support told us they could not help.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Feb 27, 2024 3:16 pm
- Full Name: Dakota
- Contact:
Re: Error: Key not valid for use in specified state.
I contacted support about this issue since I couldn't find a forum post answer.
They told me it looked encryption key issue related. I ended up generating a new encryption key to be safe, and ran an active full backup of the affected job. That resolved the errors for me. The old key still works on the old data. So it's a strange issue. That was the resolution I found.
They told me it looked encryption key issue related. I ended up generating a new encryption key to be safe, and ran an active full backup of the affected job. That resolved the errors for me. The old key still works on the old data. So it's a strange issue. That was the resolution I found.
Who is online
Users browsing this forum: No registered users and 18 guests