Error: "Sage 50 cannot be started..." and I’m unable to ping my server by name
Description
Cause
  • Domain Name Service (DNS) resolution problems
  • Antivirus / Firewall software is blocking TCP / IP communication to the server
  • A power outage resulting in one or more workstations dropping from the network
  • More than one network connection
Resolution
[BCB:3:Network warning:ECB]


Note: We recommend that you contact your Network Administrator and have them look into your DNS resolution.

Section 1: Modify Hosts file to show Local Host

  1. Click the Windows Start button.
  2. Type Notepad in the box.
  3. Right click Notepad and select Run as administrator.
  4. Click File, click Open.
  5. Browse to C:\Windows\System32\drivers\etc.
  6. On the bottom right, click the drop-down arrow and select All Files.
  7. Double-click and open the file called hosts.
  8. Remove the # in front of 127.0.0.1.
  9. Select File, then Save.
  10. Verify that you can now open Sage 50.

Section 2: Modify hosts file with IP address of the server

  1. Follow steps 1-7 in Section 1.
  2. Add a new line beginning with the IP address of the server, followed by a space (you can use the Tab key to add the space) and the name of the server with no spaces.
  3. Save the hosts file, then verify the workstation can ping the server by name and receive a response from the correct address.
  4. If it doesn’t initially resolve to the correct address, restart the workstation and verify again.

Note: Unless the server is using a static IP address, this is a temporary resolution until the workstation can successfully ping the server by name and receive the correct response without a hosts file entry present.

Section 3: Configure Firewall and antivirus

Follow Files to allow through firewall and antivirus.

Section 4: Multiple Network Connections

If multiple inactive network connections exist, disable one or more until there’s only one active network connection. Contact your IT group or local computer technician to disable unneeded network connections safely.

Section 5: The server has no IP Address

  1. Open Command Prompt on the Server.
  2. Type ipconfig /all.
  3. If the server isn’t displaying the IPV4 and / or IPV6 address, contact the Network Administrator for further troubleshooting.
    Note: If you perform a tracert [server name], it will resolve to the 127.0.0.1 loopback.


Need more help?

Chat now



Steps to duplicate
Related Solutions