This is not one I am familiar with but a quick search suggests there may be some sort of SQL server anomaly in play. It may be that some components of your system are not quite aligned well for certain situations - there may be updates to apply.
However, although checking that is a starting point (if you have not already done so) the problem may yet persist. As I said, it's not one I have seen so other than vaguely pointing you in a direction that might be useful I can't add much.
Plan B, if you and/or your IT support don't find anything and have fully up to date Microsoft systems in place, will have to be contacting Datawatch Tech support to see if they have a known solution.
I have not done any deep searches. There may be more out there but I think it makes sense to check the basics first and at least find out what sort of things could influence the problem before trying to understand the on-line descriptions given for possible solutions!
If you have already done that then go right ahead and dive in deep!