TABLE OF CONTENTS


Background

We have had sporadic reports of this error from as far back as 2010. 


Unfortunately, at this point in time, there is no guaranteed fix for this issue.


We have invested hundreds of hours of research, testing, development time and debugging trying to get to the bottom of this error, we even employ a developer who taught our programming language in college, but we have had limited success in completely resolving this issue.


It appears this issue may relate to an unresolved bug in the programming language used to build Synergy.



Our very first reported instance of this error occurred when a customer was running Synergy across a wireless network, replacing this with a wired network resolved their issue. Since then, the issue has been reported on a variety of network types, including wired ethernet.


Most Common Processes Affected


According to our records, this error occurs most commonly in the following scenarios:

  1. Closing an Invoice
  2. Receiving purchase orders
  3. Reconciling Cashbook


There have been anecdotal reports of it occurring when saving invoices or adding parts to invoices, and when discontinuing products in the product list. 


Possible Fixes / Improvements


We have had limited success with some customers by undertaking the following:



Known Triggers/Agitators of this Error


And the following are known to exacerbate/increase the frequency of this error:


  • Running Synergy on a remote/hosted server (virtual server hosting)
  • Running Synergy on Windows "Server" based operating systems*
  • Running Synergy over a Wireless (WiFi) network*


*Per our System Requirements, we do not explicitly support 'Server' operating systems and Synergy is not supported on wireless networks (you can have wireless internet, but sharing your Synergy data/program files across a wireless network will cause issues, such as this error or worse...file corruption).


Report Your Error - Help Us to Help You...


While it is unlikely the bug in our programming language will ever be patched, with enough specific logging we may be able to one day code our way around this bug. For this reason it is worth reporting to us the area of the program and frequency you may experience this issue - even if the information below does not resolve the issue for you.


Information that can help are details such as what screen you had open, what recent activity you had in the program and even for how long you had the screen open but without any active inputs or changes into that screen.