Troubleshooting a partially released batch in Accounts Payable in Microsoft Dynamics SL

Article ID: 871362 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to release a batch in Accounts Payable in Microsoft Dynamics SL, the batch does not release. When you investigate, you see that the batch in the Release AP Batches (03.400.00) dialog box has a status of Partially Released. You may see one of the following error messages in an event log:
System Message 8888 - An unexpected error has occurred while releasing batch %s. Please contact Solomon for assistance with this batch.
System Message 6019 - Batch is out of balance and not released.
System Message 6909 - Another process has already added the %s item. The program must be terminated.

CAUSE

There are several possible causes for the error messages.

Note: If none of the following causes apply, run a debug script. For more information about how to run a debug script, see resolution 2.

  • During the release process, the connection between Microsoft Dynamics SL and the instance of SQL Server was lost. See resolution 1.
  • During the release process, you clicked Cancel in the Release AP Batches (03.400.00) dialog box. See resolution 1.
  • The "System Message 6909" error message may occur when you try to release Check Reconciliation batches from the Check Reconciliation (03.060.00) dialog box after you tried to change the period to Post.

    For more information about how to correct this problem, click the following article number to view the article in the Microsoft Knowledge Base:
    848595 System Message 6909 "Another Process Already Added the Item" when you release an AP Check Reconciliation batch in Solomon
  • In Microsoft Business Solutions - Solomon 6.0, bug 7318 may cause the "System Message 6909" error message to appear.

    For more information about this bug, click the following article number to view the article in the Microsoft Knowledge Base:
    895221 In Solomon, you receive a "System Message 6909" error message when you release an Accounts Payable check batch, or you receive an "An error has occurred while validating check amounts" error message when you print AP checks

RESOLUTION

Note: If you are currently using Microsoft Dynamics SL 2011 or later versions, you may delete the batch from the data entry screen and re-enter it.

Resolution 1

Try to release the batch again. To do this, follow these steps:
  1. Open the Release AP Batches (03.400.00) dialog box.
  2. Click to select the Selected check box that is next to the batch number that is referenced in the event log.
  3. Click Begin Processing.

Resolution 2

If you are running Microsoft SQL Server 2000, run the AP_6019_DEBUG script in SQL Query Analyzer, and then send the script results and the event log to Microsoft Customer Support Services. To do this, follow these steps:
  1. Download the AP_6019_DEBUG.sql file.

    The following file is available for download from the Microsoft Dynamics File Exchange Server:

    AP_6019_DEBUG.sql
    Release Date: October 8, 2009

    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
  2. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.
  3. In the Connect to SQL Server dialog box, type the name of the instance of SQL Server name in the SQL Server box, and then click SQL Server Authentication.
  4. Type sa in the Login name box, type the password in the Password box, and then click OK.
  5. On the Query Analyzer toolbar, select the application database.
  6. On the Tools menu, click Options, and then click the Results tab.
  7. In the Default results target box, click Results to Text.
  8. In the Results output format box, click Tab Delimited, and then click OK.
  9. Replace XXXXXX with your six-digit batch number.
  10. To run the script, press F5.
  11. After the script finishes running, single-click the lower window.
  12. On the File menu, click Save As.
  13. In the File name box, type IncidentAP. Replace Incident with your actual incident number.
  14. In the Save as type box, click Report Files (*.rpt), and then click Save.
  15. Zip this file together with the event log, and then submit the files to Microsoft Customer Support Services.
If you are running Microsoft SQL Server 2005 or Microsoft SQL Server 2008, run the AP_6019_DEBUG script in SQL Server Management Studio, and then send the script results and the event log to Microsoft Customer Support Services. To do this, follow these steps:
  1. Download the AP_6019_DEBUG.sql debug file.

    The following file is available for download from the Microsoft Dynamics File Exchange Server:

    AP_6019_DEBUG.sql
    Release Date: October 8, 2009

    Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
  2. Start SQL Server Management Studio, log on to the server, and then change the output formatting. To do this, follow these steps:
    1. On the Tools menu, click Options.
    2. Click Query Results.
    3. In the Default Destination for Results box, click Results to text.
    4. Expand Query Results, and then expand the instance of SQL Server.
    5. Click Results to Text.
    6. In the Output format box, click Tab delimited.
    7. Click to select the Include column headers in the result set check box.
    8. Click OK to close the Options dialog box.
  3. On the File menu, click Open, locate the AP_6019_DEBUG.sql file, and then double-click the AP_6019_DEBUG.sql file.
  4. Replace the XXXXXX placeholder with the six-digit batch number of the suspended batch.
  5. Press F5.
  6. After the script finishes, left-click the lower pane of the window.
  7. On the File menu, click Save As.
  8. In the File name box, type IncidentAP.

    Note Replace the Incident placeholder with the batch number of the suspended batch.
  9. In the Save as type box, click Report Files (*.rpt).
  10. Click Save.
  11. Compress the file.
  12. Submit the compressed file together with the event log to Microsoft Customer Support Services.

Customers

Microsoft Business Solutions customers who are on the Enhancement plan or who are on a service plan can visit CustomerSource to submit a new support request. To do this, visit the following Microsoft Business Solutions Web site:
https://mbs.microsoft.com/customersource
Type your security key to gain access to the site. Click the Support link to visit the Support page. Under Support, click New Support Requests.

Business Solutions Partners

Certified Microsoft Business Solutions partners can visit PartnerSource to submit a new support request. To do this, visit the following Microsoft Business Solutions Web site:
https://mbs.microsoft.com/partnersource
Type your security key to gain access to the site. On the PartnerSource home page, click the Support link under Resources, and then click New Support Request.

General Information

Microsoft Business Solutions customers who are not on plans and other Microsoft partners can submit support requests and can review their support options on the Microsoft Support Web site. To do this, visit the following Microsoft Web site:
http://support.microsoft.com

Properties

Article ID: 871362 - Last Review: July 24, 2011 - Revision: 7.0
APPLIES TO
  • Microsoft Dynamics SL 2011
  • Microsoft Dynamics SL 7.0
  • Microsoft Dynamics SL 6.5, when used with:
    • Accounts Payable
Keywords: 
kbmbstransactionimport kberrmsg kbmbsmigrate kbprb KB871362

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com