Dynamics 365 CommunityForums Microsoft Dynamics GP (Archived) Voiding in SOP Causes ...

Voiding in SOP Causes GP to Freeze

(0) Share

Report

Posted on by Community Member Microsoft Employee

We recently migrated from GP2013 R2 to GP2016. We did so with a fresh installation on a new server and brought in the last 2 years of data instead of the entire 10+ years that were in GP2013.

We have two companies performing SOP operations, plus a test company in the Dynamics instance. The freezing only occurs in one of the companies. Cannot recreate it in the other two databases.

Symptoms are:

1. If an order is created, but the batch is not saved, then the order can be deleted or voided with no issue.

2. Once the batch is saved, if you try t o void an order in the batch, it causes GP to freeze and the only resolution is to terminate GP via task manager.

We enlisted Microsoft tech support 6 weeks ago and the issue is still not resolved.

Has anyone seen this type of behavior before, and (crossing my fingers), if so found a resolution?

Thank you.

*This post is locked for comments

All responses (1)

Answers (0)

Lisa at AonC.com 3,132 on at

Like (0)

Report

RE: Voiding in SOP Causes GP to Freeze

Are there any differences between the Doc ID setup between the companies that may help isolate the issue?
Are you able to duplicate this when logged into GP as sa?
Have you confirmed DYNSA is the DBO and run grant.sql?
Have you done a SQL Trace/Profile to confirm that GP is truly not responding (as opposed to in a potential Dead Lock situation)?
Are there any third party product differences (especially an Alternate GP Sales Transaction Entry window) that may explain it?
If you duplicate the "broken" company as a fourth company (following Test Company restore procedures), does the problem persist in the fourth company?