Dynamics GP Error Messages – 5 Common Year-end Messages

Here are some common GP error messages received when doing your Year-ends in Microsoft Dynamics GP 9, 10.0, or 2010. For additional information please view our year-end closing checklist, or visit Microsoft’s site.

Q1: I tried to run the year-end closing routine by using a divisional retained earnings account, but I received the following error message:

Retained Earnings account not found.

 

What can I do to resolve the problem that causes this error message?

A1: Before the routine can continue, the year-end closing routine must validate that all the required divisional retained earnings accounts exist. For example, the Fabrikam, Inc. demonstration company uses an account format of nnn-nnnn-nn. The first segment represents the department. A retained earnings account must exist for each department that has a profit and loss account. For example, if sales account 400-4100-00 exists, but no 400-nnnn-nn retained earnings account exists, you receive this error message.

For more information about how to close to divisional retained earnings accounts, click the following article numbers to view the articles in the Microsoft Knowledge Base:

850615: (http://support.microsoft.com/kb/850615/ )

How to use divisional retained earnings accounts in General Ledger in Microsoft Dynamics GP

850741: (http://support.microsoft.com/kb/850741/ )

Error message when you try to perform the year-end closing process in General Ledger in Microsoft Dynamics GP: “Retained Earnings account not found”

An Automated Solution script may be available to perform this task, as well as other basic checks on your accounting data to help you prepare to close your fiscal year. For more information, visit the following Microsoft Dynamics Web site:

https://mbs.microsoft.com/customersource/support/selfsupport/AutomatedSolutions.htm

 

Q2: When I try to post a batch in the General Ledger module, I receive the following message:

Batches cannot be posted while the Year-End Close is in progress.

The year-end closing routine is not being run in General Ledger. What should I do?

A2: To resolve this issue, have all users close all transaction entry windows. Then, delete the SY00800 file if you are running a Microsoft SQL Server database. To do this, run the following statement on the DYNAMICS database.

delete SY00800 where BACHNUMB = ‘GL_Close’

For more information, click the following article number to view the article in the Microsoft Knowledge Base: 856550: (http://support.microsoft.com/kb/856550/ )

Error message when you try to post a transaction in General Ledger in Microsoft Dynamics GP after the year is closed: “Year End Close is still in process and batches cannot be posted”

 

Q3: I receive the following message when I try to close the year in General Ledger:

Sorry, another user is closing the year.

No one else is trying to close the year. What should I do?

A3: To resolve this issue, delete the SY00800 file if you are using a Microsoft SQL Server database. To do this, run the following statement in SQL Query Analyzer on the DYNAMICS database.

delete SY00800 where BACHNUMB = ‘GL_Close’

 

Q4: When I tried to perform the year-end closing routine, I received an error message that stated that a single-use batch or a quick journal transaction had not been posted. What does this error message mean?

A4: When you try to perform the year-end closing routine, you may receive the following error message:

A single use batch or quick journal transaction has not been posted yet. Do you want to continue closing?

You receive this error message if an unposted single-use batch or an unposted quick journal transaction exists in General Ledger. This error message does not prevent you from continuing with the year-end closing routine. If you do not want to post the single-use batch or the quick journal transaction, continue with the year-end closing routine.

Q5: When I try to perform the year-end closing routine in General Ledger, why do I receive the following error message:

[Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint ‘PK##0671112’. Cannot insert duplicate key in object ‘##0671112’
A5: The year-end closing transactions contain a currency that is not assigned to an account. For more information about how to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base: 950019 (http://support.microsoft.com/kb/950019/ ) Error message when you try to perform the year-end closing routine in General Ledger in Microsoft Dynamics GP: “Violation of PRIMARY KEY constraint ‘PK##0671112′”

Webinar - Dynamics GP Coffee Break | Changes in Charts, Vendors, Customers & Items in Dynamics GP

Did you know that Dynamics GP offers the ability to change and merge accounts, items, vendors, and customers to clean up your data for more efficient use?

March 19
9:00 am – 9:25 am PST

Register here

Webinar - Charts, Vendors, Customomers in GP

Mar. 19
9:00 am – 9:25 am PST

Register