Case #07443206 — Username and Password errors
Build 12.2.0.334
Task failed. Error: Cannot complete login due to an incorrect user name or password.
Processing finished with errors at 9/30/2024 6:23:06 AM
We get these errors/failures on our replication jobs. This will happen on the first 3 automated attempts. The 4th, manually ran, retries will be successful. Reference back to a past case where we had the same problem. Solution was to go into the credential manager and update the passwords, but the passwords are correct now, just as they were back then. I have not found a solution elsewhere in the forums.
Case #07283080 — Replication Error Username or Password Incorrect
Thank you!
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Sep 30, 2024 1:48 pm
- Full Name: Josh Cochran
- Contact:
-
- Veeam Software
- Posts: 2578
- Liked: 605 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Intermittent Username / Password errors
Hi Josh, welcome to the forums.
Thank you for sharing the case numbers; I can see the previous case was closed with confirmation that updating the password helped, but the issue seems to have re-appeared.
Since the new case was just opened, please allow Veeam Support time to review the information.
> This will happen on the first 3 automated attempts. The 4th, manually ran, retries will be successful.
A bit of a long-shot here, but any chance you're backing up your vCenter ( vcsa ) in any of the jobs? That it's failing the first few times with a failed password issue and then succeeding later starts me thinking towards if the vCenter is maybe not handling the connections well, and particularly if the vCenter is being backed up this can happen as noted in our KB article here.
I would check it, but if it's not relevant, then let's wait for Support to review the logs.
Thanks!
Thank you for sharing the case numbers; I can see the previous case was closed with confirmation that updating the password helped, but the issue seems to have re-appeared.
Since the new case was just opened, please allow Veeam Support time to review the information.
> This will happen on the first 3 automated attempts. The 4th, manually ran, retries will be successful.
A bit of a long-shot here, but any chance you're backing up your vCenter ( vcsa ) in any of the jobs? That it's failing the first few times with a failed password issue and then succeeding later starts me thinking towards if the vCenter is maybe not handling the connections well, and particularly if the vCenter is being backed up this can happen as noted in our KB article here.
I would check it, but if it's not relevant, then let's wait for Support to review the logs.
Thanks!
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Bing [Bot] and 77 guests