Skip to main content
All CollectionsTroubleshooting
Errors with the password rotation in Windows Server
Errors with the password rotation in Windows Server
Updated over 3 months ago

This article is used to troubleshoot the main errors with password rotation for Windows Server.

Error: “Response Code: This Problem…”.

Screenshot 2024-04-25 at 09.58.31.png

For the error above, it´s needed to verify the intern network of the computer and check if it is connecting to the VaultOne API.

Error: Active Directory user, access denied error in the script.

Screenshot 2024-04-25 at 10.00.49.png

The Script should be executed by a user with elevated permissions (Administrator). Or the user, without elevated permissions, needs to have the “Reset Password” permission enabled.

Error: “This credential doesn’t rotate because the version is different!”

Screenshot 2024-04-25 at 10.02.55.png

The password rotation couldn’t be completed because the last attempt returned an error. To regulate the problem, you need to go into your vault and look for your credential, after that click in actions > synchronize password. Select the current password for the user and click confirm.

Error: “You need administrator privileges to continue using this script”.

Screenshot 2024-04-25 at 10.04.58.png

The script for the password rotation needs to always be executed by an user with administrative permission.

Error: “Response Code: 429”

Screenshot 2024-04-25 at 10.05.56.png

Due to the sheer number of requests to password rotate, it’s needed to wait at least one hour to try again.

Error: “Could not authenticate in VaultOne API”

Screenshot 2024-04-25 at 10.59.00.png

This problem can occur when the credential in your vault don’t have the password rotation enabled, or the asset that make the password rotate was changed or updated, or the authentication key was changed in the vault, while not being changed in the script.

To change the authentication key, a new key needs to be generated, and in the computer that the script is running, delete the file “.passwordRotation” present in the directory “%LOCALAPPDATA%\VaultOne\PasswordRotation\<user of the credential>”. After that, restart the script to insert the new key.

Error: “<user> not found. Please, ensure the user exists and try again.”

Screenshot 2024-04-25 at 11.00.45.png

The user was not found in the local machine. Verify if the user exists in your Windows installation.

Error: “<user> not found in your domain. Please, ensure the user exists in your domain and try again.”

Screenshot 2024-04-25 at 13.48.18.png

The user was not found in the domain that your computer finds itself in. Verify if the user exists inside the domain.

In case of any doubt. Contact us [email protected]

Did this answer your question?