This article discusses what may cause an interruption when you post a transaction or a batch in Microsoft Dynamics GP .
Posting interruptions may occur periodically. If posting interruptions frequently occur, examine Microsoft Dynamics GP to determine the potential causes. The following troubleshooting suggestions can help you determine what may cause frequent posting interruptions.
- If the interruption occurs on a specific client computer every time, the client computer may have damaged code. If you have a client computer that does not experience posting interruptions, copy the code from the working client computer to the nonworking client computer. You may also reinstall Microsoft Dynamics GP on the nonworking client computer.
- Post a batch from the server. If you can post from the server, the problem may be in the network. Posting from the server may be more effective.
- If the interruption occurs for a specific user, the User ID may be damaged. Create a new User ID for the user.
- Verify that the check links process is run periodically in Microsoft Dynamics GP.
- When the posting interruption occurs, determine whether there is a common vendor, customer, item, or employee included in the batches. If there is a common vendor, customer, item, or employee in the batches, determine whether there is damage to the common vendor, customer, item, or employee.
- If the client computers experience power fluctuations or surges, you may experience posting interruptions.
- Corrupt Reports/Forms dictionaries. This may happen especially if you recently upgraded or updated to a new service pack. To verify the path for the forms and reports dictionaries, click on Microsoft Dynamics GP, point to Tools, point to Setup, point to System and click Edit Launch File. Under the product name, click on Microsoft Dynamics GP and then the location of the dictionaries will populate at the bottom of the window. Use KB 850465for steps on how to recreate the Reports.dic and KB 951767for steps on how to recreate the Forms.dic file.