This document shows how to get the Sage 100/300 connector back online as well as a list of settings to check to ensure the Sage 100/300 connector does not go offline in the future.
In order for the integration to work, the Agave connector must be running at all times. Frequently folks will close the server that Sage 100/300 is running on and when the server is closed, all applications will close as well.
Option 1 (recommend): Create a background task so that even when regardless of if the server is being used, the Agave connector stays open.
Here is a step by step guide as well as additional notes from Siteline on each step: https://docs.agaveapi.com/source-systems/on-premise/agave-connector/set-always-on-with-task-scheduler
Step 3: Even if the user is not logged in you'll want the task to keep running which will keep the Agave Connector open. Otherwise if the user is not logged in (usually the IT person who set this up), the task scheduler will not continue to run.
Step 5: You want to ensure that that the task does not stop running if it runs longer than a specific amount of days, otherwise the
Step 7: You do NOT want to use the desktop file path; you'll want to use the actual file path. By using the actual file path, it will execute and start the Agave connector as a background process. You want to ensure you're running the local program as opposed to the Desktop application itself.
Step 8: The task settings should match this AND you also want to select if the task fails, restart ever 10 minutes up to 3 times.
Step 10: Many times folks will have this in a "ready" state rather than a run state.
Step 11: We recommend you close out of the desktop application at this point by clicking the X for the Agave connector.