Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you post a batch in the general ledger in Microsoft Dynamics GP: "The Stored Procedure GLpBatchCleanup Returned the Following Results: DBMS: 0, Dynamics: 20486"


View products that this article applies to.

SYMPTOMS

When you post a batch in the general ledger in Microsoft Dynamics GP or in Microsoft Business Solutions - Great Plains, you receive the following error message:

The stored procedure glpBatchCleanup returned the following results: DBMS: 0, Dynamics: 20486

If you click More Info , you receive the following error message:

glpBatchCleanup. Error occurred attempting to update the Batch Headers

↑ Back to the top


CAUSE

This problem can have either of the following causes.

 

Cause 1

This problem occurs if the current year that is being posted to is marked as a historical year. See Resolution 1.

 

Cause 2

This problem occurs if invalid records exist in the SY00800 table or in the SY00801 table. See Resolution 2.

 

↑ Back to the top


RESOLUTION

Resolution 1 
To resolve this problem, change the setting for the historical year. To do this, follow these steps:

1.  In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup , point to Company , and then click Fiscal Periods
 
 2.  Click to clear the Historical Year check box, and then click Save .  

3.  On the Transactions menu, point to Financial , and then click Batches .  

4.  Post the batch.  

 

Resolution 2 
To resolve this problem, clear the records in the SY00800 table or in the SY00801 table. To do this, follow these steps: 1.  Back up the Microsoft Dynamics GP company database.  

2.  Back up the Dynamics database.  

3.  Have all users log out of Microsoft Dynamics GP.  

4.  Stop and then start the computer that is running Microsoft SQL Server to clear out the temporary tables.  

5.  Start SQL Server Management Studio. To do this, use the appropriate step depending on the program that you are using: 
 
• If you are using SQL Server 2005, start SQL Server Management Studio. To do this, click Start , point to All Programs , point to Microsoft SQL Server 2005 , and then click SQL Server Management Studio . 

• If you are using SQL Server 2008, start SQL Server Management Studio. To do this, click Start , point to All Programs , point to Microsoft SQL Server 2008 , and then click SQL Server Management Studio . 

• If you are using SQL Server 2012, start SQL Server Management Studio. To do this, click Start , point to All Programs , point to Microsoft SQL Server 2012 , and then click SQL Server Management Studio . 
 
6.  Select the Dynamics database. Then, use the following statements to delete all the records from the ACTIVITY table, the SY00800 table, and the SY00801 table: 

• DELETE DYNAMICS..ACTIVITY 
• DELETE DYNAMICS..SY00800 
• DELETE DYNAMICS..SY00801 
 
7.  Select the TEMPDB database. Then, use the following statements to delete all the records from the DEX_LOCK table and the DEX_SESSION table: 

• DELETE TEMPDB..DEX_LOCK 
• DELETE TEMPDB..DEX_SESSION 
 

↑ Back to the top


MORE INFORMATION

The SY00800 table is the Batch Activity table. This table is used to track the status of batches. If a batch record is in this table, the batch is being edited, posted, posted to, or deleted.

The SY00801 table is the Resource Activity table. This is typically used by batches. This table is used to report some items or information that could not be updated.

↑ Back to the top


Keywords: kb, gp, kbmbsmigrate, kbmbspartner

↑ Back to the top

Article Info
Article ID : 860710
Revision : 3
Created on : 5/1/2018
Published on : 5/1/2018
Exists online : False
Views : 436