12.5 Account keep getting locked out when creating location for backup
Multiple people have tried but having same issue. When we try to add a network location it looks like it connects fine and displays list of folders but when we click on the location (we just added) to see the contents, our account (which was used to provide network credentials) get locked even though credentials were correct.

- Log in to post comments

From Acronis console, we click on Backups and "Add Locations" and provide the network share path \\sharenams\folder etc.
We then click the arrow --> and then it displays only 2 things: our company's main domain name and "NT AUTHORITY".
After this we click "Done" on the bottom right side of the screen and it asks for network credentials which we provide domain-name\username and password, It then start displaying list of folders including the one we mapped.
We click "Done" again on the bottom right side.
It then either displays lockout message immediately or when you click on the mapped location (within Acronis). I have just did all these steps while writing this to you and account got locked out immediately.
I have attached Error Message and its details here.
If account didn't get locked out immediately then Acronis console will show that it has mapped the location on left (within Acronis). And if you click on that location then immediately it shows that account is locked.
We can mount same share using Windows explorer and don't get this issue.
We don't have this issue in Acronis 11.5, so obviously something has changed they way 12.5 is handling network credentials.
Attachment | Size |
---|---|
461269-152206.JPG | 18.96 KB |
461269-152209.JPG | 24.37 KB |
- Log in to post comments

Our IT Security teams has identified that credentials are trying to be applied 17 times per second which is the reason for lockout.
- Log in to post comments

Thank you for sharing more details on the issue! I'm afraid the issue you encountered is quite unusual and would require more in-depth investigation with the help of Acronis engineers. I'd recommend raising a support ticket at https://www.acronis.com/en-eu/support/contact-us/ Please let us know the outcome of the investigation so that other users can find it on forum.
- Log in to post comments

There is already a ticket and we are going back and forth with support for past many months but no resolution yet.
- Log in to post comments

Hi,
Sorry to hear about your your disappointment. Looks like the issue is really tricky, but I'm sure our engineers will find the root cause. I'll keep an eye on the investigation process.
- Log in to post comments

hi
i have the same issue...
Provide the support now an solution to this issue?
BR
- Log in to post comments

Hello Kevin,
Sorry to know that you experience this issue too. Have you already contacted Acronis Support Team? This issue requires deep testing/investigation on their side.
The solution to the issue reported by Mumtaz Ali is not available yet, it is in waiting status for the next product update release.
- Log in to post comments


Hello George,
I've discussed this topic with the development team and according to my colleagues investigation didn't reveal a common root-cause for such issues, which means each case should be investigated separately. Please open a support ticket and post the ticket ID here, so that we can follow the investigation progress.
Thank you!
- Log in to post comments

Hello Mumtaz Ali,
I am just wondering if the issue has been resolved so far. If yes, I would appreciate if you share the solution with the community.
If you have any additional questions, please let me know.
- Log in to post comments

Add me in on this account lock out issue. Still must be an issue.
- Log in to post comments

Hello Eric,
thank you for posting on Acronis forums!
As Ekaterina has mentioned above, each case needs to be individually investigated. Please open a support ticket and post the ticket ID here, so that we can follow the investigation progress.
- Log in to post comments

Having the same issue, and no solution yet.
Backup failed
Windows error: (0x80070775) The referenced account is currently locked out and may not be logged on to
Error code 4
- Log in to post comments

Dragan Bogoevski wrote:Having the same issue, and no solution yet.
Backup failed
Windows error: (0x80070775) The referenced account is currently locked out and may not be logged on to
Error code 4
Hello Dragan.
Thanks for participating.
To resolve this issue, you have a few options:
-
Wait for the account to unlock: User accounts can become locked out due to various reasons, such as too many failed login attempts or a security policy in place. In some cases, the lockout period may expire automatically, and you can try logging in again later.
-
Contact your system administrator: If you are using a managed network or organization, reach out to your system administrator or IT support team. They will have the necessary permissions to unlock your account or provide you with an alternative solution.
-
Use a different user account: If you have another user account with administrative privileges, you can try using that account to perform the backup. Make sure the account is not locked out and has the necessary permissions to access the files you want to back up.
-
Reset the locked-out account's password: If you have the appropriate administrative rights, you can try resetting the password for the locked-out account. This can be done through the "Computer Management" tool or the command-line interface using the "net user" command.
-
Reboot the machine and retry the backup manually.
-
Check the VSS - https://www.acronis.com/en-eu/products/vss-doctor/ ( note this doesn't fix the issues with the VSS, it's a simple tool for diagnosis. You should run the tool and download the output. At the bottom of the output you will find the Windows errors with the VSS. If there are errors, you should fix them or contact Microsoft to do it because that's required to make the backups to work ).
Thanks in advance!
- Log in to post comments

Hello Dragan,
Make sure the account the storage node service is running under has full access to the location you want to add, as well as to the deduplication DB path if you are using deduplication.
-- Peter
- Log in to post comments