web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / ERROR 6909
Microsoft Dynamics SL (Archived)

ERROR 6909

(0) ShareShare
ReportReport
Posted on by Community Member

My user is getting the error:

System Message 6909: Another process has already added the cursor=21 item. The program must be terminated. This is happening when they are using the payment selection screen in AP.  I don't have any customization on that screen.  Where can I look to fix this problem?

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Which method are they using (pay date, reference number or vendor id) and, at what point does the error occur?

  • Community Member Profile Picture
    Community Member on at

    Sorry I didn't respond earlier I would out Friday.  The user gets the error when they press begin processing and they are processing by reference number. 

  • Community Member Profile Picture
    Community Member on at

    The payment selection process ultimately populates the apcheck and apcheckdet tables.  A 6909 error is basically saying that there was an attempt to insert a record into a table that violates the unique key definition for that table.  Those unique key definitions for those 2 tables are such that a user should not normally cause such an error which makes me think that a prior selection has left some corruption in the database.  The first step in running this down would be to run a select query against both of these tables and see if there are any records in these tables.  If you do not find any records, let me know.  There may be records in those tables from another payment selection batch so pay attention to the batnbr field.

    Another possible step to take to find the issue would be to create a payment selection batch for one reference number in your set.  If it creates without error, delete that batch and try creating a new batch with the next reference number.  Repeat the process one batch/reference number at a time until you get the error and then we can look at that particular reference number.  By the way, I am assuming that the user is not attempting to select the same reference number more than once in the failing batch.

  • Community Member Profile Picture
    Community Member on at

    We are having the exact same issues.  We upgraded in March 2016 and this just started happening in the last 2 weeks.  When I look at the apcheckdet and apcheck tables they are blank  - no data.  Not sure what is happening.   We have been able to select vouchers one by one into the batch  and then run checks but this is not the answer.  I would really like to figure out what the issue is and resolve it.  Any ideas?

  • Community Member Profile Picture
    Community Member on at

    I checked wrkrelease it is empty as well.  Not sure what is causing this issue.

  • HolliV Profile Picture
    HolliV 235 on at

    Did you ever find a solution to this problem?  I installed a hot fix but the problem came back.  It does not occur all the time.

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi StanB

    I used to get this error and found that the reason was cause by duplicate refnbr. You can use SQL to check refnbr in APDOC table, if there are two lines with same refnbr that is problem. You can change refnbr one of two line in APDOC, APTRAN then try to release that batch.

  • Community Member Profile Picture
    Community Member on at

    This occurred for us. There were orphan rows in apcheckdet from 15 years ago. We'll see if it occurs again.

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    The problem was that payment selection by voucher number had duplicate numbers entered.

    My previous comment was orphaned APCheckDet rows, but that did not fix the problem. 

    While processing, received error "System Message 6909 - Another process has already added the cursor=21 item" followed by the screen crashing. Problem occurred when two of the same voucher numbers (duplicate) was entered and neither data entry nor the screen caught the problem though previous versions did catch the problem according to data entry. Deduping in Excel prior to entry in this screen caused the error to not occur again.

  • Community Member Profile Picture
    Community Member on at

    Duplicate. Please delete.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans