Vault Update 2024.4 Changes the SQL Server "sa" Password

[dpeters3]

Autodesk_VaultServer_2024.4_Update changes the SQL Server "sa" password.  This was an issue on both of our vault servers - Pro and Basic.

I just updated two servers to 2024.4 and subsequently 2024.4.3.  We use a non-standard SQL "sa" password, as using the standard AutodeskVault@26200 password is considered a security risk by our team.

The 2024.4 update changed the SQL sa password (this happened on both servers), resulting in an inability to complete the process.  I discovered it when the Ob2bmigrate routine would not run (threw a SQL authentication error).  After some detective work, I reset the "sa" password to the one we are using, and was able to complete the 2024.4 update/migrate process.  The 2024.4.3 update then ran without issue.

I have not found anything on this issue via an online search.

[johnmondro4888]

@dpeters3  Thank you for this!! We'll be running through the same process next week, sure this would have been a head-scratcher without your guidance. Hopefully will resolve the "disappearing shortcuts" issue.

[dpeters3]

Make sure that you have another SQL Admin account set up (BEFORE you run the vault update), so you can fix sa if you have this problem.

[ihayesjr]

@dpeters3 

For clarity, where do you think the password was changed?

Vault does not store the SA password, nor can it change it in SQL. 

It will use the default SA password if one is not provided during command line execution.

[dpeters3]

I have no idea how the SA password got changed.

Here is the sequence of events I ran through:

Logged into SQL Studio with my SA credentials (non-default password).  Successful.

Ran the 2024.4 Server Update.

Opened ADMS Console and migrated all the DB.

Ran Ob2bmigrate with the command line, using our SA password.  Failed, with a SQL authentication error.

Tried to log into SQL Studio with my SA credentials.  Failed.

Logged into SQL Studio with Windows authentication.  Successful.

Re-set the SA password to ours.

Logged into SQL Studio with my SA password.  Successful.

Ran Ob2bmigrate with the command line, using our SA passoword.  Successful.

This happened exactly the same way on two different Vault 2024 servers (both had been at 2024.3.2 I believe) - Pro and Basic.  I have a ticket with our IT folks to see if they can shed any light on it.

[dpeters3]

One other point:

After running the Update, and opening ADMS Console, I was not prompted for an SA password before the migrate operation.  I am normally prompted for an SA password when I run ADMS Console.

[ihayesjr]

@dpeters3 

Thank you for the detailed steps. Can you create a support request so that we can track this and see if the update is indeed causing the password to be reset?

This way, we can ensure that it doesn't happen with future updates. Your steps indicate that the update is resetting the password and it shouldn't.

[dpeters3]

I'll be happy to create a support request, if you let me know how to do so.  Thanks.

[ihayesjr]

Account Basics | Using Autodesk Account | Autodesk Support

Support and Problem Solving | Autodesk Support

[dpeters3]

Case number
24099971

[dpeters3 · Accepted solution]

With the help from the Autodesk support case engineer, we were able to determine that the SA password was not changed - the SA account was locked after multiple failed access attempts.  It is not clear what part of the update process made those failed attempts.  Following the SA password reset, Ob2bmigrate ran successfully, and update 2024.4.3 was run successfully.

During the first full backup following this, the backup failed due to a permissions error on one library, 'AI2024_AOTC_MaterialsGuide', which was a training materials library left over from a previous training session.  This library was detached and reattached using ADMS Console, and the full backup then successfully ran.  The library was then deleted as unnecessary.  A separate support case, 24112884, was opened to address and resolve this issue.

So the SA lockout root cause was not determined, however the immediate situation(s) were resolved.