Admin users will be able to see when a file has a recent sync error, although a bit of decoding may be required. We're working on how we can untangle the 0s and 1s in the long term, but for the time being here's a library of common sync errors that arise across Xero, Quickbooks, Sage50 and Sage Business Cloud Accounting.
Your 'last sync error' button will appear when a sync error occurs. Simply click on the button as indicated below for more information.
If your error is missing from the list, please contact our Support team.
Common Sage50 errors
- Cannot find all files in the data path
about 1 hour ago: [Sage50] 08001 (0) Cannot find all files in data path: C:/Program Files (x86)/SfSync Sage50 _Live/lib/ruby/gems/2.1.0/gems/activerecord-odbc-adapter-openedge-2.3.7/lib/active_record/connection_adapters/odbc_adapter.rb:73:in `drvconnect'
Resolution: It looks like we can’t find all the files in the sync reference folder you gave us. Please try restoring the backup of the file and then try syncing again.
- Invalid User ID or Password
about 1 hour ago: [Sage50] 28000 (0) User ID or Password invalid: C:/Program Files (x86)/SfSync Sage50_Live/lib/ruby/gems/2.1.0/gems/activerecord-odbc-adapter-openedge-2.3.7/lib/active_record/connection_adapters/odbc_adapter.rb:73:in `drvconnect'
- Non-zero values in P&L accounts
about 1 hour ago: [Sage50] Found X P&L accounts with non-zero brought forward balance. [ Acc Number Acc Name > BF balance: XX ] It's required to post an adjustment to correct this, as explained on the following link: [https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200427112207652&page=1&position=8&q=post%2520into%2520closed%252%25200year] : C:/Program Files (x86)/SfSync Sage50/src/sage50.rb:608:in `fail_if_bf_presence_on_p_and_l!'
Resolution: Your incoming sync contains bought forward balances in the P&L codes as a result of posts made in Sage after the bookyear has been closed. This will cause an unbalanced alert in prior years. The error message will list the accounts and the values that are coming through, however it won't show the bookyear these are related to.
Please post an adjustment to amend this error and resync. Further details can be found on the Sage website
- Data files are the incorrect version
about 1 hour ago: 08001(0) Data files are wrong version: C:/Program Files (x86)/SfSync SageBob v25/lib/ruby/gems/2.1.0/gems/activerecord-odbc-adapter-openedge-2.3.7/lib/active_record/connection_adapters/odbc_adapter.rb:73:in `drvconnect'
Resolution: If you have no updated your sync version to v27, the version of your database file and the version of the sync do not match. For example, a v26 file can only sync using the allotted v26 version of the sync. You'll have to change which sync installation you are using or update your sync version. If you need help with this, please contact support.
- Missing account numbers in the bookkeeping Chart of Accounts
Common Xero errors
- Invalid Password
401 Unauthorized, company: Umbrella Corp Ltd
Resolution: It looks like the username and/or password you used to create this sync is no longer allowing us to access the data. re-add the integration, or check the credentials used for this sync.
- Server Error
Server error, company: Umbrella Corp Ltd
Resolution: We temporarily lost connection with the server, either because we were refused or because of internet loss. Please just try again, it should work now. If the error persists, please contact our support.
- Xero rate limit has been hit
Please wait before retrying the xero api, company: Umbrella Corp Ltd
Resolution: The Xero API limits us to either a minute lime of 60 calls in a rolling 60-second window, or a daily limit of 5000 calls in a rolling 24-hour window. This message appears we hit one of the two limits imposed by Xero for syncing. Please wait a while and try syncing again
Common QuickBooks errors
- Reauthentication required
Invalid_grant: Token invalid{"error_description":"Token invalid","error":"invalid_grant"}
Resolution: It appears the authentication details are no longer valid. Please reauthenticate by recreating the sync.
- Timeout error
Resolution: It appears the authentication details are no longer valid. Please reauthenticate by recreating the sync.
If you have applied these solutions and the error still occurs, or what you're seeing isn't reflected in this list, please contact Silverfin Support with the error message and we'll help.