Dana - Did you figure this out?  We are having the same issue (different record) upon first attempt to retrieve in SA after upgrade to 2020.

Jim,

The database has not been available for me to look at yet.  I'll post what I find when I get to look at it.

Dana

Thanks, Dana.  Level 2 tech support is looking into it for us now.  Will let you know if they come up with anything.  Makes me wonder if this is a version 2020 issue, though I can't imagine that anything was changed that would do this.

Probably a collation order problem, database should be binary.

This client is on v2019.  I looked in the database and the duplicate data it complained about in the error message is from 2007.  The year 2007.  Batch 6, entry 1.  Doesn't make sense.

I ran the retrieve my self and it completed the retrieval from OE.  When it started AR it stopped and told me that an interest entry, something like INT0000015, was already in the data, do you want to skip it?

I said yes and it completed without issue.

I'm closing this case.

Dana

Yeah.  The data it is complaining about in mine is in 2011.  I found that if I click Yes to skip it goes to the next record of the same kind and stops there. I then have to "end task" and then restart the retrieve.  Unfortunately, in my case, there are thousands of these records, so working through them all manually, one by one, is not an option.

Yeah.  The data it is complaining about in mine is in 2011.  I found that if I click Yes to skip it goes to the next record of the same kind and stops there. I then have to "end task" and then restart the retrieve.  Unfortunately, in my case, there are thousands of these records, so working through them all manually, one by one, is not an option.

In my case there isn't much AR.  It retrieves mostly from OE.

I'm pretty sure that Sales Analysis stores the record it finished with last time it retrieved.  It saves the day end sequence or something like that so it doesn't try to read ALL the data next time it retrieves.  It's likely that in your case that saved record has been changed somehow so it's trying to read the same records over again.

Locate where that's saved and I think you'll solve the issue.

Dana

Thanks, Dana.  I had come to pretty much the same conclusion. Now the challenge is to find that record.