Hi @Digitmasters firstly if you can't log into the MSSQL Management Studio as the Vault Owner using SQL Authentication then you're not going to be able to user the Sage credentials to do other things.  It sounds like the Vault Owner credentials may be entered wrong somewhere and are locking out the account intermittently?  In any case I would recommend turning on full login logging (the first option doesn't capture enough info):

Then restart the main MSSQL service

Now open the log file and see if you're getting a lot of login failures caused by Sage 300:

Hopefully you can troubleshoot the issue that way.  If you get really stuck make sure you set the Local Policy for password expiry to 0 and you can run the password reset tool if you really get stuck:  https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=223924150028378&page=1&position=1&q=Admin%20pasword%20reset

Good luck!

Hey Tim,

Thanks for the reply.  I tried to logging to SQL and change PWD for this '##S3_LOGIN_ADMIN##SAGE300VAULT' account. But still getting the same error.

Hi @Digitmasters, you can't change the password for '##S3_LOGIN_ADMIN##SAGE300VAULT' manually - that will never work as that user is created by the initial site establishment process during the generation of the Sage300Vault and VaultOwner databases.  If you're trying to recover the ADMIN password use the tool above or change the Local Policy.  I fear if you can't restore ##S3_LOGIN_ADMIN##SAGE300VAULT since before your change your only likely way forward is to blow the site away and set it up again.  Remember you need two SQL AUTH User Accounts - one for the company and system databases, and another for the Vault and VaultOwner databases.  The ##S3 login gets generated based on these details you enter at the very beginning.  The Enhanced Security guide explains all this.  Setup your databases and users as per this guide and connect them in Database Setup as the first thing you do before commencing with the system and company databases.  You should then be fine.  Take a snapshot of your VM before running Database Setup for the first time so you can quickly roll back and try again.  Sage300EnhancedSecurity.pdf