GP Environment - Batch Stuck

How to fix batches getting stuck within GP environments

1. If your dictionaries are shared, put them locally on the machine that the user is using that has this problem.
2. If you are using a Citrix or Terminal Server, install GP Locally on their machine and use this for a few weeks to determine if the Interruptions still occur.
3. Recreate and Synchronize the Forms and Reports to the GL Client that is being used.
   1. Please use the following article to recreate your Reports.dic:
      1. KB 850465 https://link.zixcentral.com/u/70ca398f/jFV06hoM7BGCSuMLh3soMg?u=http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F850465
   2. If you have any modified forms\windows, you will want to recreate your Forms.dic as well.
      1. KB 951767 https://link.zixcentral.com/u/5d5182ec/PtV06hoM7BGO__MLh3soMg?u=http%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F951767
   3. To synchronize after recreating, use the steps below:
      1. Open the Dex.ini. This is located in the Data folder in the GP Code Folder.
      2. Locate the Synchronization Line and change it from FALSE to TRUE.
      3. Save the changes.
      4. Start Great Plains Utilities. To do this, follow the appropriate step:
      5. Click Start, point to All Programs, point to Microsoft Dynamics, point to GP (or appropriate version), and then click Utilities.
      6. In the Additional Tasks window, click Synchronize forms and reports dictionaries, and then click Process.
      7. Locate the Dynamics.set file on the client computer, and then click Next. (C:\Program Files (x86)\Microsoft Dynamics\GP 2018)
4. As this has been happening for some time now, there are likely stuck records. Clear these out to make sure these are not the cause.
   1. Have all users log out.
   2. Log into SQL Server Management Studio.
   3. Backup all database.
   4. Right click on the SQL instance and click Restart.
   5. On the pop up, click Ok.
   6. Once back up all temp and activity tables should be cleared out.

Next, I would recommend the following after ruling out the above.
 

1. First, determine if it is a data issue or environmental issue. To do this, you will need to do the following:
   1. First, create a test company so backups can be restored.
   2. Before any printing/posting is done, create a backup of the database.
   3. Print/post the batch.
   4. If the issue occurs, restore the backup into test and try again.
   5. If it prints/posts without an issue, it is not an issue with the data and points to this being an environment issue.
      1. You can then dig into the Environment to troubleshoot this issue.
         1. I won’t be of any assistance of this part as I don’t know your environment.
   6. If the issue does occur, then we dig into the data in the batch and see what might be wrong.
2. Try creating a new user for the user having the problem as these can become corrupt over time.
3. Remove all Third Parties and see if the issue can be recreated.
   1. We can also rebuild the GP Code Folder at this time to verify the Code Folder is not damaged.
   2. Use Method 3 of the KB below to accomplish this.

KB - Steps to disable third-party products or temporarily disable additional products in the Dynamics.set file in Microsoft Dynamics GP
 

4. If you are using any modified reports for the printing process, set the security back to the core GP Reports to rule out the modified reports.
   1. Administration >> Setup >> System >> Alternate/Modified Forms and Reports.
5. Verify that the user is not using WIFI. WIFI is not good to use with ERP systems as you need to have a constant connection between the client and SQL.
   1. WIFI is notorious for connection drops.
6. Change out the Ethernet cord and try a different jack to verify there are no issues here.
7. Make sure the user is not leaving GP open and stepping away for some time or locking the PC.
   1. The nic card can go to sleep and cause a network drop.
   2. If the user does step away, have them log out and back in to refresh the connection.
8. Turn off any Antivirus and Firewall to determine if these are the cause.
9. Try having the user post directly on the server to determine if it is their machine.
10. Determine if it is only happening with check batches.
    1. If it is, part of the problem is likely changing the status back. We don’t want to do this.