Dynamics GP Troubleshooting-I

I. While trying to post a batch, the user receives an error saying the batch is being posted even though no other user is posting the same?

Make sure you have a valid backup of dynamics GP data. Run the following script to verify the status in your company database (Login to SQL Server Management Studio). While being posted, the batch status would be set to 5 and now it has to be changed back to 0.

UPDATE SY00500 SET BCHSTTUS =0 where BACHNUMB = ‘XXX’
---Replace XXX with your batch number

II. Sometimes a user by mistake prints a SOP transaction and then try to delete it, he doesn’t find an option to delete the same and instead, it has to be voided?

For control purposes, it is always advisable to void the document and not delete the same. However, If it specifically has to be deleted, we can use the following script

UPDATE SOP10100 SET TIMESPRT = 0 WHERE SOPNUMBE = ‘XXX’
---Replace XXX with your Sop Number

III. While doing a Dynamics GP Upgrade, Utilities give an error that the selected company is being updated by another client?

Make sure no users are logged into the company being upgraded and then run the following script

USE DYNAMICS
DELETE DuLck

IV. When the User attempts to close the year in General Ledger, the following error message appears despite no one else is doing the same?

“Sorry, another user is closing the year.”

Run the following script against the company database

DELETE GL50100

V. When attempting to post a batch in GL, the following message appears though any year-end process is not happening?

“ Batches cannot be posted while the year-end close is in progress”

Have all the users log out of the Dynamics GP, Run the following scripts against the respective databases

DELETE SY00800 (DYNAMICS)
DELETE DEX_SESSION (TEMPDB)
DELETE DEX_LOCK (TEMPDB)

VI.While attempting to do an Year-end close, the user gets the following error?

Violation of PRIMARY KEY constraint ‘PKSY00800’. Attempt to insert duplicate key in object ‘SY00800’

Recreate the PKSY00800 Index for the SY00800 table. Run the following script in DYNAMICS DB

alter table SY00800 drop constraint PKSY00800

Then, run the following script again

alter table SY00800 add constraint PKSY00800 PRIMARY KEY nonclustered (USERID, CMPNYNAM, BACHNUMB, BCHSOURC, WINTYPE)

VII. User gets the error message “All Call Stacks are in Use. Cannot start Script”

Change the Regional Settings to English United States in control panel. Then Come to ODBC settings for Dynamics GP, Click Configure, come to screen where it shows perform Translation for character data, unmark it if marked. Make sure Use ANSI Quoted Identifiers and Use ANSI Nulls, paddings and warnings are all unmarked.

I’ll try to put more troubleshooting tips in my future posts. Please note that the above methods are unsupported and users are cautioned to do proper backups of data prior to executing any scripts.