Locating the Error Message
if a posting fail you will see link stating "Failed items" on the Postings screen.
Clicking on that link will display the failed items from that run as well as the associated error message.
1. Sage 50 Upgrade
Upgrading Sage 50 can disrupt the link with Weighsoft. For more details, refer to the article:
How Does a Sage 50 Upgrade Affect Weighsoft?
2. Sage Not Installed on the Server
To post invoices directly from Weighsoft into Sage 50, Sage must be installed on the same server as Weighsoft. This is because Weighsoft logs into Sage directly during the posting process.
If Sage 50 is not installed on the server, invoices must be posted using the Flat-File posting process. More details can be found here:
Flat-File Posting Process
Note: This is only a factor if Weighsoft is hosted on your own server. If you are using the Access-Hosted Weighsoft solution then Sage and Weighsoft cannot be installed on the same machine.
3. Issues Within Sage 50
Problems within Sage itself can cause the link to fail. Known issues include:
Sage 50 Account Service stuck in "Stopping" status
There is a known issue with the Sage Accounts Service getting stuck in the "Stopping" state which will prevent communication between Weighsoft and Sage 50. This issue is documented on Sage’s website at the below link and must be resolved by your IT team.Remote Data Services unavailable or account errors
These errors indicate internal Sage issues that require IT intervention.
4. Loss of Access to Sage Files
If you receive the error message:
"Missing Accounts ERROR: Failed to connect",
this indicates a loss of connection to Sage. Possible causes include:
Inaccessible file location (either due to the date being moved or user permissions being changed)
Sage encountering a connection error
Your IT team should investigate and restore access. In some cases, retrying the post shortly after may succeed.
5. Sage Data Has Been Moved
Server migrations or changes to the Sage data location can affect Weighsoft’s ability to connect. If this has occurred:
Raise a support case
Provide full details of the changes (e.g., new file path, permission updates, date of migration)
6. Missing Accounts in Sage
An account may exist in Weighsoft but not in Sage due to:
Manual creation in Weighsoft
Rollback of data in Sage after account creation
Ensure the account exists in both systems before posting.
Note: In order for data to sync back and forth the accounts must have identical account codes in Sage and Weighsoft.
7. Missing Nominal Codes
Invoices without valid nominal codes will not post. Use the Pre-Posting Report to identify missing codes.
For setup guidance, refer to the article:
Nominal Codes
If unresolved, raise a support case with full details.
8. Sage User Already Logged In
If the Sage user account used by Weighsoft is already logged in, posting will fail. Log out the user from Sage and retry the posting.
9. Sage User Deleted or Password Changed
If the Sage user account used by Weighsoft has been deleted or its password changed:
Create a new Sage user account
Raise a support case indicating the change
Support will contact you for the updated credentials
10. Issues with the "Cloud Service" (Access-Hosted systems only)
If your Weighsoft system is on an Access-Hosted server then communication between Weighsoft and Sage is handled by a "Cloud Service" which enables traffic between the Access Weighsoft server and your own Sage server.
Note: In order for the support team to look into this we will require a connection to your Sage server.