Is this an upgrade or a brand new install?  If a brand new install normally the first time you open database setup you enter 'admin as the old password.  After connecting the Store and Vault databases I've found the password reverts back to 'admin' and you have to change it again, instead of using the new password.  Also check your Password Policy on your Local Security settings on your SQL server to ensure they match Sage's recommendations under the "Sage 300 User Security" section.  I forgot to attach the Enhanced Security guide - if you follow the process in this guide it should help avoid the admin password issue.

Hi Singgih ,

Have you check your minimum password age is local security policy? 

When you just installed Sage 300 2024, your password is treated as a new password with 0 day of age. If your security policy having minimum password days age > 0 , you will need to change the minimum password days age to 0 to change your password immediately.

Okay, we have done your suggestion, and it works. 
Thank you!

Yeah, we must set minimum password age is 0 for first setup.
Thanks for your reply.

I assume you are referring to the local security policy on the server.  Why is this so complicated!

Sage are just making changes without any thought of how these work in the real world. Customers do not want to change their security policy on a server just for Sage to work. In larger customers their security team will not play ball on this. This new security is a complete mess and there is no good way to troubleshoot any issues encountered. Nearly every install or upgrade has issues and takes hours to resolve. This is precisely what drives customers to investigate alternative solutions and then we all lose out! Just put security in the product like everyone else does including Microsoft with Business Central :-/

There is another issue if you allow the DB Setup to create the ODBC connection when using SQL 18. This requires SSL certs on hte SQL server and if this is not in place the initial connection will fail. The cure for this is to change the ODBC settings to make the Connection Encryption OPTIONAL and the check box checked for Trust Server Certificate. If you create the ODBC before running DB Setup and make the changes you will not see the error in DB Setup. Just another assumption Sage made on new security with the V18 ODBC driver!

Hi oakley ,

Thank you for your insights on the setup challenges with Sage 300 2024.0. We strive to balance security with usability, and your feedback is crucial for us. 

The steps for setting up Sage 300, including those related to security and database connections, are designed with the intention of safeguarding data integrity and compliance with best practices in cybersecurity. We understand that these procedures can sometimes seem complex or cumbersome, particularly when transitioning from older versions or adapting to new security protocols.

Our goal is to ensure that Sage 300 remains both secure and user-friendly. To this end, we constantly review feedback from our community to identify areas where we can improve the setup experience without compromising on security. Your comments highlight a valuable area for our ongoing development efforts.

For specific issues or suggestions, please reach out. Your input helps us improve and we're here to support you through any setup challenges.

Warm Regards,
Erzsi