i have this problem with version 2023 ,  we have 2023 on our network and users open the Sage file from server , after install the last update my client can not open the same DB file which store on Map drive , we didnt have such issue before and users always store the sage DB on the network map drive and it work till last update break it ,  when i move the DB to a local hard drive it is working but when i move it again to map drive drive it is not working.

any advise appreciate.

For some reason, Sage knows that files aren't locally and needs the connection manager, regardless if they are on a mapped drive or network drive.  

For some reason, Sage knows that files aren't locally and needs the connection manager, regardless if they are on a mapped drive or network drive.  

yes , it is true ,   i am supporting multiple client inIT provider and have this issue on multiple network , i am not sure but it looks a bug ot something is wrong with Sage 2023

Have you checked to make sure the mysqld.exe and the SimplyConnectionManager,exe processes are being allowed through the firewall for the 2023 version as they were with the earlier version?

Did you install the 2023 Connection Manager (version 12.0) on the server?  Or is it still version 11 or earlier?

server is already update with version12 connection manager , the software was working on the same computers and network for years and this issue started happening after install the version 2023 , is this something has chnage for mysql conection on version 2023 ?

You didn't answer this question.

Richard S. Ridings said:

Have you checked to make sure the mysqld.exe and the SimplyConnectionManager,exe processes are being allowed through the firewall for the 2023 version

bahram rez said:

is this something has chnage for mysql conection on version 2023 ?

Yes, there was an upgrade from MySQL version 5.7.27 to 8.0.27 with the release of Sage 50 2023.0.

See the following path

C:\Program Files (x86)\winsim\ConnectionManager\MySqlBinary

and you will see how many versions of MySQL have been installed with Sage 50 on that computer.  Going from memory, it has changed around 2014, 2016 and 2020 before the change in 2022, since the original release in 2008, so it is not the same software for years.