Skip to content

x Want to ask a question or reply? Click here to join the group.
DCrampton
Related
Recommended

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.. 
    2. if there is already a Vault folder, it means that you have to restore you SITE folder prior to installing 2023.3.. 
    3. Create a new Vault/Store database with a Different name then the original.
    4. 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..

  • Had the issue.

    ODBC profile had the correct trust cert option checked.  The database populated with the tables so it appears to have worked.  I copied the vault folder with the .ini file out of sites before exiting database setup and then moved it back to sites before launching database setup again and it worked. 

    The new vault database was created and populated with tables in sql server so it appeared to have finished when the error was showing up.  The new vault folder appeared inside the sites folder and the ini file had the correct server info so everything looked ok except it wasn't proceeding to the next stage.  

    It asked me to change admin password because it wasn't complex enough on the second run.  I think the issue in my case was admin password.  I suggest changing admin password to meet complexity requirements before the upgrade. 

    Was going from 2021 to 2025.  Maybe a bug where it is both migrating the users and admin needs a password change at the same time for my case. 

  • Had the issue.  ODBC had the correct trust cert option checked.  The database populated with the tables so it appears to have worked.  I copied the vault folder with the .ini file inside out of sites before exiting database setup and then moved it back to sites before launching database setup again and it worked.  It asked me to change admin password because it wasn't complex enough on the second run.  I think the issue in my case was admin password.  I suggest changing admin password to meet complexity requirements before the upgrade.

  • in reply to DCrampton

    You need to set an ODBC first after you will be able to view the odbc connection you made in datasource section 

  • in reply to Collin

    I kept getting the same issue on one of my 2023 dev machines. I had to delete some extra files (that I previously created) in my SITE directory. I had an orgs.ismBAK backup file that I created earlier. Once removed, the vault/store setup worked.

    Odd error too as I saw that it created tables in vault/store, and imported the Sage300 users into SQL, but it still came up with the error - failed to establish the vault and store.

  • in reply to Erick Katikiro

    Hi Erick, if you select Data Source or Server, it still requires a Data Source name the same as the Server.  

*Community Hub is the new name for Sage City