Pervasive Data Solutions, 1/10/2010 7:34 AM

During that sync (Pacific time) you created a duplicate entry of every single account in quickbooks.  Annoying for all the time it will take to merge the accounts together even though it seems the duplicates have no data stored in them.  Tons of error messages in your log file from that time.  Seems you wiped the entire database and then recreated it.

Our apologies for this. It seems during that time the integration ran out of API calls.

It however only shows 26 total Accounts being affected. Don't know if I am reading the logs incorrectly, but mind checking to see if only 26 were affected?

 Actually I'd say it's closer to 13 accounts once I was able to figure out how to limit the list to only those newly created accounts by Pervasive.  Either way, I've merged the accounts and things are fine now.  I'm also trying to get Salesforce to provide me the API history as well.

 So you know, Salesforce has a report called "API Calls Made Within Last 7 Days" which they can turn on (or it's on by default, not sure) which does a great job of tracking API calls.  I show a huge spike in API calls from you but something about that makes me feel the data is invalid... it's too high to be right.  I'm asking Salesforce for valid tracking again and we'll see.

I do wish your logs would make it easy for me to see every API call you make against Salesforce.  It would be easy for me to see where you could optimize since it really shouldn't be high at all with all the sub-joins you can do since API 15.

 And AGAIN!

 1/29/2010 5:04 AM (Pacific Time)

Looks like the same issue happened again.  Need to go correct the damage again.

 Nick,

 I will go through the logs and find out where this is happening. We are doing some more development with DataSynch this week, and we will look over the issues you are having and figure out how to ensure this does not happen again.

Our apologies for this issue. 

 And now again.  3/4/2010 5:37 PM Pacific time.

 The issue is related to us running out of API requests.  It turns out you guys aren't sucking tons of API requests like I had thought.  Salesforce has bad API counts on the NA2 instance and they've been working for the past month of so to fix the issue.  But anyways, we're out of API requests right now and that caused your program to *again* create many duplicate records.  23 or so of them.

 We are going to have to attack this in a different way.

 The code changes that optimize our API usage are currently in QA. Its a pretty big code change, so QA will take some time.

I am thinking that even after that code change, there is a possibility that we can see the same issue , and your explanation is a re-affirmation.