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) / System Message 6909 - ...
Microsoft Dynamics SL (Archived)

System Message 6909 - Another process has already added the cursor=DefaultCreated Item. The program must be terminated.

(0) ShareShare
ReportReport
Posted on by Derrick0828 65

We are experiencing System Message 6909 - Another process has already added the cursor=DefaultCreated Item. The program must be terminated. in Release AP Batches. Mostly the affected batch are those that came from Edit/Select Documents for Payments and Check Printing/Update. Already referred to Knowledge Based didn't found anything close to this scenario. I've run the APDEBUG and below is the  message:

(1 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

Msg 2627, Level 14, State 1, Procedure APDebug, Line 9

Violation of PRIMARY KEY constraint 'WrkRelease0'. Cannot insert duplicate key in object 'dbo.wrkrelease'.

The statement has been terminated.

13 May 2011 00:38:24:060

Debug...Step 250: Get EditScrnNbr

 

Batch Diagnostics

Batch okay, will release normally.

 

Rolling back transaction

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(0 row(s) affected)

(1 row(s) affected)

Can someone help me with this problem as we already have several batches with this scenario.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Jeff Trotman Profile Picture
    Jeff Trotman 275 on at

    Run "select * from wrkrelease" and I think you will find a record already there with the BatNbr value you are trying to release.  This table is normally empty and is only used temporarily during the release process.  Sounds like a release process died and these records didn't get cleaned up.

    If you delete those records from wrkrelease, you will probably be able to release the batches.

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    We had this problem as well. Entering voucher numbers in the Select for Payment screen, then while processing, received error "System Message 6909 - Another process has already added the cursor=21 item" followed by the screen crashing. Problem occurred when batch had two of the same voucher numbers (duplicate) that was not caught by data entry nor the screen. Deduping in Excel prior to entry in this screen caused the error to not occur again.

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