Tagged: MySQL OLE DB
Really hoping someone can point me in the right direction here, just paid for premium support here so hoping for at least a suggestion on where to start here within the next 24hrs.
Our clients who’s infrastructure we manage has an OpenSync task (EstimateByJobReport) that syncs between their MySQL database (updated by a web form) and Quickbooks, it’s been failing for over a month and we’re stuck. I’m not getting a whole lot of information from the logs:
2019-06-17 08:26:43 0 WorkTracker Starting task: EstimateByJobReport
2019-06-17 08:26:43 0 BackWorker ExecuteBackground Begin
2019-06-17 08:27:24 0 BackWorker MakeQbConnection: Connection Opened
2019-06-17 08:27:25 0 BackWorker GetReport
2019-06-17 08:27:26 0 BackWorker Processing table: ESTIMATEREPORT
2019-06-17 09:38:10 -2147217887 BackWorker ExecuteBackground Error: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
2019-06-17 09:38:14 0 BackWorker CloseQbConnection: Close Connection
2019-06-17 09:38:14 -1 WorkTracker Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.:-2147217887
2019-06-17 12:58:12 0 OpenSync:Poller Shutdown
The CoreObjXDB log provides no additional information. The sync fails somewhere around the 47,000th record out of about 65,000
We had this happen a while ago and the issue ended up being an Emdash copy pasted into one of the records. We’ve had them look over the records and have not found any Emdashes in their Quickbooks entries.
From my research it sounds like one of the records either exceeds maximum length of the field, or contains an invalid character (such as an emdash). I don’t know where to start as far as how to query Quickbooks or the MySQL database to check for this.
Any help would be appreciated.
Which version of OpenSync and QuickBooks are you using?
MySQL Connector/ODBC 5.3
Quickbooks Enterprise Contractor Edition 17
Updating to Opensync 3.0.25 seems to have done trick for now, sync successfully completed with no other changed variables that we can see at the moment.
Good that you got the latest version. I was about to suggest to do so.
You must be logged in to reply to this topic.