Hi Ingolf just confirming your System DSN entry is configured in 32-bit ODBC and not 64-bit, and have Encryption set to Optional if no Certificate and "Trust" ticked on i.e.:

Once your ODBC driver is confirmed, check you created a Sysadmin privileged SQL Auth account for your Sage300StoreOwner account to connect and configure your Sage300Vault and Sage300Store databases.

Aside from these two things there isn't much too it, so feel free to post a screenshot of your error to see if we can get a feel for the error and help you troubleshoot it.  Best of luck!

Thank you for your reply.

The ODBC Driver is setup as per your screenshot and instruction.  I have tried using both Native Client 11 and the ODBC Driver 18 for SQL Server.  The Connection Test passes for both drivers.  Using the ODBC Driver 18, it is setup and verified as per your instructions.

The Sage300VaultOwner is created with Sysadmin, public, dbcreator, and SecurityAdmin privileges checked. Including the Sysadmin, as it is not checked or requested for selection in the Sage Enhanced Security Sage300 guide.

The Error message I receive is as I have noted previously.  There is nothing else to the message.  At this time I can not include the screenshot.  I had to roll back the Sage 300 to 2023 PU1 so the client can continue to operate.

I had also created a different VaultOwner account with different databases. Still experiencing the same error.

Hi Ingolf can you log into the MSSQL Management Studio with the Sage300VaultOwner SQL Auth account succesfully?  Once in can you access the Vault and Store databases?  I know you shouldn't need to but perhaps open the Security Login properties for the Sage300VaultOwner account and ensure under Mappings you have mapped the roles to the vault and store databases.  If trying these two things doesn't help you discover anything I would recommend contacting your local Sage 300 Business Partner or Sage Support office for support.

Oh, one last thought, locate the connection error in the Event Viewer.  Often the detail in there can reveal the actual error thats occuring that you can then research for a solution.  Good luck!

Hi Accsys Consulting.  Thank you again for your replies.

I can successfully log into the VaultOwner in MSSQL Management Studio.  I can also successfully access the Vault and Store databases as VaultOwner.  The role mappings are correct.  I have done other upgrades the same way and have been successful to version 2024.  Some I have had to reset the ADMIN password during the process.

In this upgrade I can not reset the ADMIN password, using the ResetADMINPassword utility. I have tried this in case the upgrade process has a problem with the ADMIN password I am using.  It gives me an error code 14, whatever that means. I should not have to change the ADMIN password until after Database Configuration is complete in 2023 PU3. The ADMIN password works fine in 2023 PU1, and is ok to initiate the Database Configuration to 2023 PU3.  

I will check the error in Event Viewer.

Hi Ingolf hang on I have an idea.  Check your Local Security Policy on the SQL server and look for any restrictive policies that might be preventing you from resetting the ADMIN password - for example on my lab server I have very relaxed settings that prevent any problems with password changes etc:

Maybe review these settings in case they're causing the problem?

Good luck!

Couple of other things to look at.. the ODBC Data Source needs to be named the same as the SQL Server Instance.. so if your SQL Instance is called "SAGE300Server" then the datasource has to be named SAGE300Server".

Also, it's best to log on and do this directly on the server instance rather than from a workstation.. this is because Shared Data Directory cannot be UNC pathing for this part of the setup.. either create a mapped driver (if the Shared Data is on a different Server) or change it to a local path if set to UNC.  after the intitial setup, you can change back to UNC.

Other than that, we may need to get you to contact Customer Support and open a support ticket.