New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I recently upgraded a client from GP8 to GP2018. Whenever they try to do a Payables Inquiry by Document the system freezes (Inquiry – Purchasing – Transaction by Document). After waiting 5-10 minutes we have to use Task Manager to close GP. It happens to all users and on all workstations (and directly from the server). They only have 2 companies - Fabrikam and their live company. It works fine in Fabrikam. Any suggestions would be greatly appreciated.
I would run a trace while running the inquiry to see what is causing delay. GP Power Tools (GPPT)* can do this on the fly, or you can do it the old fashioned way by changing the dex.ini file. You need to open the dex.ini file in Notepad, and change the first three settings from FALSE to TRUE. The user then has to log out & back into GP, run the inquiry, kill GP if necessary, then go back into the dex.ini file & switch them back to FALSE. Then in the same folder as the dex.ini file, you will see a file called DEXSQL.log; the last (or near to last) sequence of steps should give you an idea of what is causing the issue.
* GPPT was developed by David Musgrave of Winthrop Development Consultants & is available through Mekorma
I'm not on GP2018 yet, so this might be a bug (known or unknown).
Let us know what you find, or if you need additional guidance.
What you're running into appears to be known performance quality issue in GP 2018 RTM (quality issue 91923). You can confirm this by waiting for the window to populate (it may take a long time).
This problem manifested in association with new sorting options added to that window with the release of GP 2018. Here is a link to the new feature:
The great news is this was fixed with the release of the January Hotfix for GP 2018:
I hope this helps!
Andrea Melroe | Sr. Technical Advisor | Microsoft Dynamics GP
Applying the latest service pack fixed the problem.
I ran into a similar situation after upgrading to GP2018 on a test server (GP2015R2 to GP2018 upgrade). I applied the June patch as well. GP Version is now 18.00.0496. But the issue still persists. It takes over 8-10 minutes before the window opens, and when it does it throws an error. The same on GP2015 R2 works just fine. Is there anything else that can be done to fix this? I can see the query executing in SQL Server and takes forever to complete.
It appears that the original question/poster's issue was resolved so I recommend starting a new thread for your issue since you found the same fix didn't work for you.
Thanks Jen, will do.
Just encountered the same error. Is it fixed in GP 2018 R2 - 18.00.0628?
Just upgraded to GP 2018 R2 - 18.00.0628. Still the same issue
Results from SQL profiler
BEGIN DECLARE @stored_proc_name char(36) DECLARE @retstat int DECLARE @param9 int set nocount on SELECT @stored_proc_name = 'MPL.dbo.pmBuildTrxInquiryByDateRange' EXEC @retstat = @stored_proc_name '##0924356', 1, '1900.01.01', '1900.01.01', '', '', '', '', @param9 OUT SELECT @retstat, @param9 set nocount on END
Simon - weird that they did not fix this in R2. I had to open a ticket with MS and they provided a stored procedure that needs to be run on all company databases. Once that was done, the issue was resolved.
Were you charged for this stored procedure? If not, could you share it with the community? I have not run into this issue with any of our clients.
Please could you email / post the SP?
A client just reports the same issue today after upgrading from 2013 to 2018R2. Does someone have the script that fixed this?
Hi, We have the same issue now in build 18.00. 0496. Please will you email us the script provided by Microsoft. Thank you
Per Microsoft, this will be fixed in the year-end service pack releasing the week of 11/19. They will not provide a fix for previous builds. The freeze is caused by the stored procedure pre-loading the entire work and history tables before opening the window. The fix is to open the window without preload (which it should have done in the first place, IMHO). The only option without applying the year-end SP is to remove data from the tables - again a non-option for most companies.
Business Applications communities