I had a similar though not identical situation. I believe - though I was not the DBA creating or maintaining the integrations - that my customer's situation had to do with queries. I asked in the group and I'm sure there's a thread somewhere here that has the answer but after 15 minutes of really really good faith effort at searching I cannot find the thread.
Here are my notes - just as an FYI - and with the caveat that this probably does not even apply to what your asking though it may apply to someone in the future if they search this topic.
Wayne,
Are there any SQL Queries or stored procedures access the Sage 100 work tables. We had what appear to be the exactly the same issue, after a lot of troubleshooting we determined that it was SQL queries running. Those queries were only doing read request and not doing any write functionality, but the were putting locks on tables all the same. We change the queries to use with (NOLOCK) and it resolved the problem (link below). In the meantime, until you track down the cause, when the program bombs out to the ProvideX command, have the user type RUN and hit enter it should restart the update without duplicating anything.
PS - Note to self - when making notes from 90 Mind HL always save a link to the original post
------------------------------
Wayne Schulz
wayne@s-consult.comSchulz Consulting
(860) 516-8990
Moodus, CT
------------------------------