How to Fix Sage 50 Network Error Occurred While Communicating With The Connection Manager


This blog is the complete discussion about the Sage 50: A Network Occurred While communicating with The connection Manager. This issue requires advanced solutions to get rid of all network issues. You can modify the window security issues correctly. As you know, Sage is not responsible for the operation bug issues. Before resolving this kind of issue, the user is required to create a backup file so whenever you restart your system you can easily restore your company files. 

User Navigation

What are the Reasons Behind Sage 50 A Network Error?

  • Corrupted or damaged share folder.
  • When your system runs on a different mode.
  • Ports utilized by the Sage 50 unable to open in the window firewall.
  • Sage 50 2018 and higher edition unable to work with Windows Vista,  Windows XP, and window Server 2008.

How to fix Sage 50 A Network Error Occurred while Communicating With the Connection Manager?

Things, you need to consider before stepping in to resolve it:

  • Check and verify the Sage 50 exceptions that have been added to the window firewall.
  • Must be sure about the server or the data location system has Sage 50 also downloaded.
  • Disable your firewall and anti-virus.
  • Check and ensure that your system meets minimum requirements.
  • Reboot the server and all systems that run on Sage 50.
  • Check and verify the connection managerโ€™s edition on all system.
  • Turned on Connection Manager and check the server.

Methods to Fix Sage 50: A Network Error Occurred While Communicating With The Connection Manager

Troubleshooting Guide 1: User required to open the company files by utilizing the primary system IP address:

๐Ÿ’  Click on the Sage 50 icon
๐Ÿ’  Choose the โ€œOpen an Existing Companyโ€ option
๐Ÿ’  Go to the Filename type: \\The IP Address of the computer where the data is stored\
๐Ÿ’  Now, you need to browse the data files
๐Ÿ’  At last, open your company file and you are all resolved with this error

Troubleshooting Guide 2: User need to add the port expectations to the windows firewall:

๐Ÿ’  From the window start menu, write cmd.
๐Ÿ’  Moving forward with displayed instructions and then choose โ€œRun as an Administratorโ€
๐Ÿ’  Now, you have to copy the displayedย  command
๐Ÿ’  And then, paste it into the command prompt after the C:\Windows\System32>
๐Ÿ’  Hit the Enter key and you are all resolved with this error

Troubleshooting 3: When my systems are associated over an internal router that is further linked with the internet service providerโ€™s router with the below-mentioned steps:

๐Ÿ’  Firstly, unplug the router cable which is linked to the internal router
๐Ÿ’  Then, remove the power plug of the internal router
๐Ÿ’  Again, plug the power into the router and then attempt to access the data
๐Ÿ’  If it still unable to work then it indicates the internal packets are just going via the internal router, then the internet service provider provides backup service to the internal router

There are only two reasons behind them:

๐Ÿ’  Internet source provider router blocks the packets through its firewall
๐Ÿ’  Internet service provider and internal router are utilizing the conflicting IP address

Troubleshooting Guide 4: Fix this error just by performing the following steps:

๐Ÿ’  Check and ensure about the given points before performing the troubleshooting guides
๐Ÿ’  Check and ensure about the connect manager running on the server and the workstation
๐Ÿ’  Then, must be sure about the database that works on both the local server and workstation
๐Ÿ’  Now, open your window explorer.
๐Ÿ’  After this, the unmarked โ€œUse Simple File Sharingโ€ option
๐Ÿ’  The next thing you have to do unmarked the โ€œUse Sharing Wizardโ€
๐Ÿ’  Hit the OK button and then try to open your company files

Step 1:

๐Ÿ’  Hit the right-click on โ€œMy Computerโ€
๐Ÿ’  Then Choose the properties
๐Ÿ’  Click on the โ€œComputer Nameโ€ tab
๐Ÿ’  Now, you need to compare the name for that specified groups on the server computer and the other workstation systems
๐Ÿ’  Now you need to enter the server IP address to open the company file

Step 2: Check and Verify all Systems that belong to the similar Workgroup

๐Ÿ’  Open the โ€œMy Computerโ€ field
๐Ÿ’  Chooseย  the โ€œPropertiesโ€ menu
๐Ÿ’  Hit the next click on the โ€œComputer Name Tabโ€
๐Ÿ’  Now, you need to compare the names for the workgroup on the server system and other workshops
After this, you require the serverโ€™s IP address to open the data over the workstation: Locate the IP address of the main server
๐Ÿ’  Go to your Company Window, then write the serverโ€™s IP address in the file nameย  sectionย  and then browse the folder where your company data is stored

Step 3: Check and verify that all systems on the same network

๐Ÿ’  Click on the Window Start
๐Ÿ’  Open theย  โ€œControl Panelโ€ section
๐Ÿ’  Choose the โ€œNetwork and Sharing Centreโ€
๐Ÿ’  Now, you need to see the basic network data and set up a connection
๐Ÿ’  Make sure the network name requires to be the same on all systems

Step 4: Check and verify the connectivity between the workstation and the server

๐Ÿ’  Go to the workstation computer and then open the command prompt
๐Ÿ’  After this, try to telnet the port on the server
๐Ÿ’  user required to update the port range by opening the window explorer then browse to open the connection manager in the host system

Step 5: If you find any error while using telnet then perform the following steps:

๐Ÿ’  Ensure the firewall settings that will work on both server and workstations
๐Ÿ’  Check and verify the permission for the window user
๐Ÿ’  Then try to login into windows as a different user
๐Ÿ’  Now, you need to open the ports in the firewall and then power cycle the router for a few seconds
๐Ÿ’  After this, open the ports in the router if you are utilizing the static IP address on the server system and then attempt to forward the port to the main server
๐Ÿ’  From your server, open up the dbengine.ini file found in the C:\Program Files\Winsim\ConnectionManager\MySqlBinary\5.0.38ย and add the line “innodb_flush_method=normal
๐Ÿ’  This line makes new changes in the behavior of the MySQL database and is untested
๐Ÿ’  It is specifically designed for servers that are configured under level 2 or 3
๐Ÿ’  Once you are done with the above steps, then stop and begin the connection manager
๐Ÿ’  Now, try to ping the server from the workstation and vice-versa.

Step 6: Check the router

๐Ÿ’  First of all, share your company file on the router
๐Ÿ’  Must be sure about the connection speed, otherwise, Sage 50 will time out and it will lead to the error message
๐Ÿ’  Now, you have to configure the router to the port
๐Ÿ’  Then, forward both TCP including 13531 and 13540-13545
๐Ÿ’  Check and verify the advanced router that includes the MySQL features
๐Ÿ’  Now, reset the router

Step 7: Adding the server IP address to the workstations hosts file:

๐Ÿ’  Open your Notepad as an admin
๐Ÿ’  Choose the File and hit the Open button
๐Ÿ’  Browse to C:\Windows\system 32\drivers\etc\hostssss
๐Ÿ’  Click on the Hosts file
๐Ÿ’  Add a line with the IP address and the name of the server to finish the program

Step 8: Setup the new shared folder in the C driveย 

๐Ÿ’  Create a C:\Sage Data folder then put a copy of the current data file inside
๐Ÿ’  After this, you have to share your data with full controlย  to each group on the sharing as well as security tab
๐Ÿ’  Admin or concern person assign the security group from everyone to a custom group for security reasons if required

Troubleshooting 5: If your company file is on a stand-alone computer then perform the below steps:

๐Ÿ’  Firstly, you have to check the Sage Connection Manager is working or not
๐Ÿ’  Must be sure that you open the sample company
๐Ÿ’  Copy the file to a new folder
๐Ÿ’  At last, open this company file from the file location

Troubleshooting 6: Reboot the server:

๐Ÿ’  Click on the โ€œRebootโ€ button
๐Ÿ’  Then, perform on-screen guidelines until the program is finished
๐Ÿ’  Open your company file from the work station to check whether the issue is resolved or not

Troubleshooting 7: Install the complete version on the server:

๐Ÿ’  The initial step is to install the full version of Sage 50 on the server
๐Ÿ’  Now, you need to check the data works locally.


We hope the above information satisfies your concern about the Sage 50: A Network Error Occurred While Communicating the connection manager. If you require more information to resolve your all queries related to the Sage 50, feel free to connect with the Sage professionals.

Frequently Asked Questions

Q. What Sage 50: A network error occurred while communicating the connection manager defines?

Ans. This error defines the slow performance and it usually happens due to corrupted or damaged files. In any case, if your network connection speed is too slow then Sage 50 will time out and it will come out as an error message. Now, you just need to check and configure the router to port and then moving ahead to both TCP. While doing this process if you face any problem then reset the server.

Q. How can I fix the Sage 50: A network error occurred while communicating with the connection manager?

Ans. There are many ways to fix Sage 50: A network error occurred while communicating with the connection manager. But before going to resolve it, the user has to find the reason behind it and then pick a suitable solution for it. You can fix this error just by using the primary IP address to open the company file.

Q. How would I open the connection manager?

Ans. Click on the โ€œStart Menuโ€ and then choose โ€œSage 50 Accounting Connection Managerโ€ from Sage 50 accounting connection manager Now, open your Sage 50 accounting and then click on the setting setup and choose the โ€œConnection Managerโ€ and you are all done with this process.


A Network Error Occurred While Communicating With The Connection Manager
Article Name: How to Fix Sage 50 Network Error Occurred While Communicating With The Connection Manager
Description: Check the connection speed, if the network connection is too slow, Sage 50 will time out and it will also result in this error message "Network Error Occurred While Communicating With The Connection Manager"
Author Name: Harrison William
Publisher Name:

Further Reading



Book a meeting
Chat Now