1,780
*This post is locked for comments
Hello Punugu,
I just wanted to mention also, while I'm sure you're aware, that Dynamics GP 10.0 is no longer supported at all by MBS Dynamics Support, so you'll want to look at getting upgraded to a supported version before too long.
The last thing we'd want to see, if you're not able to get support from a forum like this, is to have your production environment on an unsupported state, where we wouldn't be able to assist with any technical support, other than if you were actually in the process of upgrading to a supported version.
Thank you!!
I found this list of Batch Statuses from Accolade's old web site:
www.accoladepublications.com/.../393-batch-status-codes.html
0 Available
1 Batch is currently posting.
2 Batch is currently being deleted.
3 Batch currently receiving transactions from outside the module.
4 Batch is done posting.
5 Batch is currently being printed.
6 Batch is currently being updated.
7 Batch was interrupted during posting.
8 Batch was interrupted during printing.
9 Batch was interrupted during updating of tables.
10 Recurring batch has application errors and one or more transactions did not post.
11 Single-use batch has application errors and one or more transactions did not post.
15 A posting error occurred while trying to post a batch of computer checks.
20 Batch was interrupted during the processing of computer checks.
25 Batch was interrupted during the printing of the computer check alignment.
30 Batch was interrupted during the printing of computer checks.
35 Batch was interrupted during the printing of a check alignment form before reprinting checks.
40 Batch was interrupted during the voiding of computer checks.
45 Batch was interrupted during the reprinting of computer checks.
50 Batch was interrupted during the processing of the remittance report.
55 Batch was interrupted during the processing of the remittance Alignment report.
60 Batch was interrupted during the printing of the remittance report.
100 Batch is processing computer checks.
This Batch Status field is in the SY00500 table in the company database.
Also, if you have any modified forms or reports, export them to a package file, create an empty reports dictionary and try again. Next, import the package files you created earlier into the blank reports dictionary.
You could also try to rebuild the auto procs by dropping and recreating them in the SQL maintenance window.
The last thing I can think of is to go into the Database Maintenance Utility and recreate the stored procedures.
Kind regards,
Leslie
Fixed my isssue. Thank you
I think I fixed my problem. I took out my modified reports dictionaries and everything worked properly. I then re-imported from a package file and everything still worked. I then put the old dictionaries back and everything broke again. I exported a reports package from the bad dictionaries, took out the dictionaries, and imported that package in and everything worked.
I have two systems with the same issue described in this thread happening in all companies. If we tell it to not print any of the reports, the error does not occure. Both systems are running 10.00.1411 and Windows Server 2008 R2. 10.00.1424 has been released since this systems were installed, but when I checked the fix list, there is no mention of this issue. I'm going to try dropping and recreating the auto procedures tonight.
I will go under the assumption that you are using GP 10.
I have seen this issue a number of times when, for whatever esoteric reason, the Batch Header table auto-stored procedures become corrupted. In order to fix, you will need to use the SQL Maintenance option under MSDGP > Maintenance > SQL to locate the Batch Header tables and drop and recreate the table auto procedures.
If this does not fix the problem, then you can attempt to rebuild all stored procedures using the Microsoft Dynamics GP Database Maintenance utility. For more on the Database Maintenance utility read my article Microsoft Dynamics GP Database Maintenance Utility.
Hi, easy to fix, but hard to diagnose!!
Does this happen every time you try and post a GL batch?...or is it intermittent?
Did you try running the following queries? (Get everyone to logout of GP first)
Does this sort the issue and allow you to post? Do you have any bespoke developments? Where are the GL journals coming from...i.e. are they manually entered?
Are users logging over Remote Desktop? Are they closing out of GP properly before killing their RDP session?
Best regards,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (