x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 6 replies
  • Subscribers 59 subscribers
  • Views 1459 views
  • Users 0 members are here
Browse Forums
Announcements
78
topics
166
replies
General Discussion
5k
topics
16k
replies
Installation and Upgrades
977
topics
2k
replies
Inventory, Projects, and Departments
337
topics
1k
replies
Payables and Receivables
1k
topics
4k
replies
Payroll
1k
topics
3k
replies
Reconciliation and Banking
317
topics
995
replies
Reporting and Analytics
206
topics
399
replies
Soutien Technique - Français
626
topics
1k
replies
Year End Activities
223
topics
595
replies
RMG_IT

Sage 50 company files will not open from remote workstations after update to 2024, "Sage 50 cannot map the network share to a local drive path on the computer *servername*. Check the network share's registry information."

Posted By

Hello everyone, I just updated our server and a few users to the new Sage 50 Canadian 2024 update, and we are now experiencing an issue with opening company files from the server.

We have 6 users that have a mapped drive on their local client that points to the folder where the Sage 50 files are located. We have been able to open them this way BEFORE the 2024 update was installed. I keep getting the error below when trying to open from a remote workstation (Note: opening them while logged into the server itself still works):

The connection manager and it's services are running on the server, but any form of UNC path to the server will not open the company files. They have already been updated to 2024 and can now only be opened while logged into the server.

Any ideas on what this error means and what I might be missing? There's not really much I found on here related to this specific error.

  • 0

    I solved my issue.. : for me I was still not running 2024 on the main PC ie: Server, I had installed.. but I think I was using my PINNED Icon which was 2023 version.. so when I used the 2024, it asked me to be single mode SysAdmin.. did it.. it backed up and upgraded data.. then i switched to Multi and other PC was able to log in.. but had to us the find or choose company it didn't like the bottom open company last worked on.. and it worked.. whew..

  • 0 in reply to Andrew A. Hopper

    I've tried opening the company files everyway possible and they only seem to open on the server, not on remote workstations. I've tried browsing to it over IP, hostname, DFS namespace and nothing is working. I get the "check network share registry error" or the general cannot connect to database error.

    Windows Firewall is off so there is no conflicts with that and I'm able to browse to the server where the files are stored and map a drive. This was NOT happening until the update to 2024.

  • 0 in reply to RMG_IT

    RMG-IT, are you able to open the sample file on the workstation?  If it does work, what program version shows up under Help, About Sage 50.... and under File, Properties?  Is it the same 2024.0.

    Have you tried mapping a different drive letter to the server to see if that works?  I can't see 6 computers with corrupted drive maps simultaneously but I have seen a workstation acting as a file server that would not allow drive mapping from any computer.  It had to have it's windows reinstalled before it would function and allow mapping again.

    Is it possible the server firewall didn't get updated with the new mysql version info?

    I am just guessing at this point because I didn't get the same error you have.  I upgraded my workstation, then upgraded a file on the workstation.  A few days later I upgraded my server with the server-only components and copied the company file to the server and it works fine from the workstation.

  • 0 in reply to Richard S. Ridings

    I am unable to open the sample file on my workstation to determine that info, it throws database engine errors. I've re-installed my Sage 50 multiple times now with the same issue. The version # is updated in the programs list and shows 2024.

    I also tried mapping to a new drive error, same registry error appears.

    New MySQL version info? I thought with the firewall being off it shouldn't  matter?

    I also upgraded the server side by going into Sage 50 itself to prompt for the update. The Connection Manager seems to have updated as well during that process so it should have updated the server side components.

  • 0 in reply to RMG_IT

    Sorry, missed the firewall off note.  Is that the server, workstation or both?

    If the server is running version 13 of the Connection Manager (as I am assuming it is because you can open files directly on the server), the issue is likely the workstation.

    Not being able to open the sample file needs to be resolved before you will move forward with this.  I would enter some of the text from the error messages into the search bar of the Knowledgebase and see if you get any information about resolving those issues.

    Otherwise, you will have to call Sage Tech support on Monday.

    Can you open the sample file in 2023?

*Community Hub is the new name for Sage City