Skip to content
logo Knowledgebase

Issue connecting with Sage .NET Remoting Service upon upgrading to Sage 300 2020

Created on  | Last modified on 

Summary

After upgrading to Sage 300 2020, your custom programs stop working. You can fix it by restoring the remoting setup files and running the configuration again.

Description

  • Custom programs use API calls to connect to the Sage .NET Remoting service
  • Connection fails after upgrading to Sage 300 2020

Cause

  • Sage removed Web Deployment in newer versions
  • The system no longer installs or supports the remoting service by default

Resolution

To resolve the issue, restore the remoting setup:

  1. Download: 187_20230425110605_WebDeploymentFiles2019.zip.
  2. Extract the file and copy the contents to the Sage 300 Application server runtime folder.
  3. Locate the a4wesconfig.exe file.
  4. Run the file to set up .NET Remoting.
  5. Allow the process to create the required registry keys.
  6. Confirm the system starts the .NET Remoting service.

Need more help?

Chat now