Troubleshooting a failed Sage 100 API Install.
Connection refused/can't reach page.
Error - Retrieving the COM class factory for component with CLSID.
The service won’t start.
If the service won't start, it could be due to one of two Cases.
- To determine the specific case, navigate to the Windows Event Viewer.
- On the left side, select Windows Logs, click on Application, and read the last error record of the Sage100APIService source.
Case A - Invalid path or nonexistent Lumino config file.
Cause: The Sage 100 REST API is unable to find the Lumino config file.
Solution 1: Install or reinstall the Lumino Remote Operator.
Solution 2: Re-install Sage 100 REST API to ensure it points to the correct Lumino config directory.
Solution 3 (Advanced): Edit the Sage 100 REST API config file manually. (Sage100WebAPI.exe.config) is located in the installation directory that was configured during the installation of the Sage 100 REST API, pointing to the correct directory.
Case B - Invalid Lumino API key.
Cause: The API key value or the environment that was entered in the Lumino Agent is incorrect.
Solution: Verify the information entered in the Lumino config file and change values as needed.
Connection refused/Can’t reach this page.
For one of several causes, the current request cannot reach the Sage 100 REST API.
Cause 1: The service is turned off.
Solution 1: Start the service by navigating to Windows Services.
Cause 2: Incorrect combination of domain, server name, or IP, and the Port configured during installation compared to the current request.
Solution 2: Verify that the current request address matches the configuration and change it if necessary.
Cause 3 (Advanced): The Firewall or Antivirus is blocking the requests.
Solution 3 (Advanced): Open, Forward or Add a rule to the Firewall or Antivirus to the same port that was configured during the installation process.
Error - Retrieving the COM class factory for component with CLSID.
The Sage 100 REST API cannot reach the instance of Sage 100 ERP and its Business Objects.
Cause 1: The Sage 100 ERP instance directory is different than that configured during the installation of Sage 100 REST API.
Solution 1.1: Re-install Sage 100 REST API pointing to the correct Sage 10 ERP instance directory.
Solution 1.2 (Advanced): Edit the Sage 100 REST API config file manually. (Sage100WebAPI.exe.config) is located in the installation directory that was configured during the installation of the Sage 100 REST API, pointing to the correct Sage 100 ERP instance directory.
Cause 2: The Sage 100 ERP instance directory is not accessible due to the permissions in the directory.
Solution 2: Verify the permissions to the Sage 100 ERP instance directory (MAS90\Home).
Cause 3: The Sage 100 ERP instance directory is not accessible due to the network visibility.
Solution 3: Verify that the Sage 100 ERP instance directory is accessible across the network and the server where the Sage 100 REST API is installed has visibility to that directory.