Error: "Failed to Establish the Vault and Store Databases" May Occur After Installing 2023 PU3 and Setting Up the Vault and Store Databases in Sage 300 Database Setup (A4WSETUP)

1 minute read time.

After installing 2023 Product Update 3 (2023.3) you may encounter the following error message during the initial configuration of the Database ID Vault and Store Databases.  

The assumption is that the Vault and Store Databases have been created in SQL Server Management Studio and the correct SQL Login ID and Password has been entered.

Possible reasons for this error could be:

  1. Run Database Setup - "As Administrator" (ie, right-click on A4WSETUP.exe and select "Run As Administrator". 
  2. The Sage 300 Shared Data Directory must not be UNC pathing, but either a mapped drive, or run from the Server. 
    1. To find out what your Shared Data directory is, run an A4WDIAG (System Diagnostic) and open the A4WDIAG.log in a text editor such as NotePad.. this will show you what the path is.. if the path is UNC then please, change it to a Mapped Drive.
  3. Make sure there is an ODBC System Datasource that is created using the same name as what is entered for the Server Name in the Configure Databases Section, and the Database Source test is successful when run in C:\Windows\SYSWOW64\odbcad32.exe using the correct SQL User and Password credentials.
  4. Ensure that there is no "Vault" folder created in the Shared Data\SITE folder prior to migration.. 
    1. if there is already a Vault folder, it means that you have to restore you SITE folder prior to installing 2023.3.. 
    2. Create a new Vault/Store database with a Different name then the original.
    3. Restart the server and re-run the Database Setup.

With these steps performed, you should now be able to configure and setup the Vault and Store Database IDs..

Parents
  • Also check the odbc that was setup by running PU3. It will have the name of the SQL server. If it is SQL 18 then check that the encryption is set to optional and the tick is below for trust server cert. PU3 does not set this in the ODBC and unless you have all the SSL setup and enabled in your SQL it will fail.

Comment
  • Also check the odbc that was setup by running PU3. It will have the name of the SQL server. If it is SQL 18 then check that the encryption is set to optional and the tick is below for trust server cert. PU3 does not set this in the ODBC and unless you have all the SSL setup and enabled in your SQL it will fail.

Children