new version unable to open files

SUGGESTED

We are updating from Sage 50 Premium Accounting 2013 Server Version  (company files on a mapped drive) to Sage 50 Premium Accounting 2022 Standalone.  I copied the files off of the server on to a network drive, maintaining the folder structure.  When the user goes to open the company file, the program shows: "Opening database. Please wait...."  and eventually comes to this error :

Since its a local copy of the file, I don't get this error.  Any ideas ?

  • 0
    SUGGESTED

    Hi Martin65:

    If your data is stored on a server you must install Sage 50 on the server. There are 2 types of installs, one where you only are acting as a single user and using all features on that computer (meaning a full install of Sage 50), or the second one is just a server installation. I think you may not have installed the server version of Sage 50 on your server. The network drive has to be set up as a shared drive as well.

    Hope this helps!

  • 0 in reply to Agate

    We are switching from the server version to a standalone version.  As I understand it, I should just be able to move the files from the server to a local drive and have it work, which its not.

  • 0 in reply to Martin65

    Can you open the sample file?

    If not, then you may need to click on the link in the message to go to the Knowledgebase and look for information on changing the firewall settings.

    Did the computer open the file on the server ok before it was moved?

    Where did you put the file, which path?  It should have been put in some location like c:\Sage50Data.

  • 0 in reply to Richard S. Ridings

    Yes, I can open the sample file just fine (picked a C:\ location).  Also the prior version was able to open the files before being moved.  The prior file location was X:\Sage (mapped network drive that was shared from the server)  the new location is G:\Sage (a networked drive from our file server) 

    I did a test by moving the main database to C:\Sage and I can open it just fine. 

    It seems to have an issue with the file server location, which should appear to Sage as a local drive.  Is Sage not able to use a networked drive without its own server?

  • 0 in reply to Martin65

    Agate already gave you the answer to that one.  Your original message indicated you copied the file from a server to a network drive.  Typically the definition of a network drive is that it is on another computer eg. a file server.

    Then you said

    Since its a local copy of the file, I don't get this error.  Any ideas ?

    so I just assumed you meant the network drive was your local c: drive and everything is fine because you don't have an error now.

    A network drive that exists on a different computer is not a local drive.  Any drive specifically attached to your workstation computer is a local drive.  Having said that I would not be running Sage 50 files from a memory stick because they will eventually become too full to run properly.

    However the local c: drive as you have indicated c:\location should be fine.

    If you store the files on a different computer, the Connection Manager must be installed on it as Agate said.  It does not matter if the other computer is a true Windows Server or if it is a peer-to-peer networked workstation being used as a server.  It still has to have the Connection Manager installed through the process Agate mentions.  You can use the Full Install or Server install.  Full install allows you to run Sage 50 on that computer (assuming all licensing requirements are met).

  • 0 in reply to Richard S. Ridings

    Thanks for the responses.  I think I figured out that Sage needs the connection manager even with a file server as I was typing my my last reply!  Thanks again!

  • 0 in reply to Martin65

    Technically Sage 50 uses the Connection Manager on each computer, even when you open the sample file that resides on your local workstation hard drive.  It is installed with each installation and you can see it in your systray and display it from the Start Menu as well.  The Connection manager installed where the files are located is used to open and access the database.

  • 0

    Did you just copy the files/folders, or did you open Sage 2013 on the server, do a backup, and then restore it to the standalone location?  When changing locations, Sage is often 'happier' with restoring a backup in the new place rather than just having the files moved.

  • 0 in reply to C White

    I just did a copy.  But it seems Sage knows that files are still on a remote server and wants its connection manager.  I just went back to using them on the original server with an updated connection manager.

  • 0

    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.

  • 0 in reply to bahram rez

    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.  

  • 0 in reply to Martin65

    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

  • 0 in reply to bahram rez

    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?

  • 0 in reply to Richard S. Ridings

    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 ?

  • 0 in reply to bahram rez

    You didn't answer this question.

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

    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.