Vault Server Basic 2018 Installation, Old SQL Server

[brent_e_barbour]

I'm upgrading Vault Server Basic 2017 to 2018.  When it ran the system check, I got the error "An older version of SQL server is used for an existing Vault database instance."  So, I installed SQL Server 2016 express and rebooted the server for good measure.  When I attempted the reinstall VBS2018, I got the same error.  When I viewed the log file, it said "Vault database instance SQL Version = 10.0.5500."  See attached.  Is updating to SQL Server 2016 not enough?  Do I somehow need to migrate the database file over to SQL 2016?  If so, can someone please enlighten me on how to do that?

Thank you,

        Brent

[mflayler]

What version of SQL are you coming from?  That database version is 2008 SP3 if I am not mistaken and wasn't even supported for 2017.  Are you jumping from 2015/2016 to 2017 first?

You may have to do a SQL jump first.  Also you should let Autodesk Vault install the SQL Express as it puts it into a compatibility mode that Vault needs to use.  This shouldn't be a problem since your 2017 database already exists.

[brent_e_barbour]

On my first attempt to resolve this, I followed [path to installation files for vault basic server]\3rdParty\Sql2012Express\x64 included in the Vault Basic download which searched for a later version of SQL with no resolution so it proceeded to install SQL 2012.  That didn't work so I searched for the latest SQL myself and came across SQL 2016.  I installed that and still no resolution.  I check the programs and have SQL versions 2008, 2012, and 2016 installed on the server.  According to the log file, the Vault database was version 10.0.5500.  I'm upgrading from Vault 2017 to 2018.

[brent_e_barbour]

What version of SQL are you coming from?  I'm not sure.  I noticed I have SQL 2008, 2012, and 2016 all on my system after I attempted to install the latest.  I'm not sure if 2012 was already installed or if it was a new install.  I believe the SQL version was 2008 because the log file said "Please use SQL Server 2008 Service Pack 1 or higher for Vault instance."  The log file also said "Vault database instance SQL Version = 10.0.5500"

Are you jumping from 2015/2016 to 2017 first?  No, I'm not jumping.  The previous "working" version of vault was 2017.

You may have to do a SQL jump first.  How do I do that?

Also you should let Autodesk Vault install the SQL Express as it puts it into a compatibility mode that Vault needs to use.  How do I do that?  I followed the steps at https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles...  I saw no other options during the Vault install to update the SQL Server.

[mflayler]

When you installed Vault 2017 it seems like you may never have upgraded your SQL instance.  You may have to upgrade your SQL instance in your production box before your backup and restore to 2018.

If your Vault 2017 is running on a full SQL version and not express you would have had to do that during your 2017 upgrade as a methodical extra step.

Use this to check which version your AutodeskVault instance is running on.

https://support.cch.com/kb/solution.aspx/sw1873

[brent_e_barbour]

According to the instructions of the link you provided, I believe the version is SQL Server 2008 Express Edition Service Pack 3.  See attached.  Now, what do I need to do to upgrade the version of my (AUTODESKVAULT) SQL database?

[mflayler]

https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/CloudHelp/cloudhelp/2016/...

This should have happened automatically during your Vault 2017 upgrade.  Not sure why it didn't happen.  But these steps should allow you to upgrade your instance.

[brent_e_barbour]

Thanks for hanging in there with me Mark.  I feel like we might be getting somewhere.  However, I hit another roadblock.  I attempted to reinstall SQL 2012.  When I got to update features, I got a validation error.  See attached "Validation errors.jpg"  I hit "OK" and there's nothing to click on the bottom.  See attached "no features.jpg"  Everything I click takes me back to "Validation errors.jpg" or I can cancel.

I believe the first time I ran through this installation, I might have clicked "next" through the "update feature" section because the window seemed blank when it was actually still processing.  Afterwards, I installed SQL 2016 express because I knew 2012 was not the latest.  Now, how can I set things back so I can upgrade "AUTODESKVAULT"?  Is it a matter of uninstalling SQL 2016 and 2012 or is there another way?

[mflayler]

It won't let you hit Next?

[brent_e_barbour]

I can hit "Next" but it loops back to the validation error.

[mflayler]

Looks like you might have to take out 2016 and 2012 as well as some of the shared components.  Keep in mind you have your backup ready in the event of disaster recovery.

[ihayesjr · Accepted solution]

@brent_e_barbour,

I believe your problem is that the SQL 2008 edition you have installed is 32-bit and you are trying to upgrade to SQL 2016 64-bit.  You will not be able to perform this upgrade as Microsoft doesn't support upgrading a 32-bit version of SQL to a 64-bit version.  You will have to uninstall all of SQL 2008 and it's components then install Vault 2018 and let it install SQL 2016.  You will need to have an ADMS Backup before proceeding so you can perform an ADMS Restore when you go to Vault 2018.

[brent_e_barbour]

It was a long and painful process, but I...

1. Backed up my Vault through ADMS
2. Downloaded SQL Management Studio so I could backup the SQL database of my Vault as an extra precaution
3. Uninstalled all of SQL
4. Installed ADMS 2018.  It automatically installed 64 bit SQL 2012.  SQL 2016 is available at Microsoft.com but since SQL 2012 is what came with ADMS 2018 and since nothing else on that server uses SQL, I decided to stop there.  Perhaps ADMS 2019 will upgrade SQL to something later.
5. Once ADMS 2018 was installed, I restored my ADMS backup.  Everything appears to be in tact.  I guess the SQL backup isn't needed but I'll hang on to it for a while just incase.

This wasn't as straight forward as all of that.  There were many errors along the way.