web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Screen crashes after Upgrade to 2018 CU2

(0) ShareShare
ReportReport
Posted on by 1,348

Hi Everyone,

I am presently testing an upgrade from Dynamics 2015 CU1 to Dynamics 2018 CU2 and  when I press F3 to bring up the PV list the screen crashes.

This does not occur for all screens and the problem occurs on screens that are not customized.   I did some research and saw that this was reported by some persons who upgraded to Dynamics 2015 but the suggestions made did not help.

Has anyone experienced this issue and/or knows how to resolve this problem?  

Any suggestion will be greatly appreciated.

Thanks in advance.

I have the same question (0)
  • Suggested answer
    CFROTON Profile Picture
    4,710 on at

    Dear Lisa,

    It could be 38678 , are you going really fast? Slow down when you open PV and search for your lookup. I'm assuming its not crashing when you access the PV but only when you try and search/lookup when the window is open.

    Best Regards,

    Jana MacDonald

    Microsoft Dynamics Support

  • Cynthia Audain Profile Picture
    1,348 on at

    Dear Jana

    I want to assure you that I am not 'going really fast' and I slowed down at the required points.

    So let me explain my steps just before I crashed.  I clicked on the screen that I want to open, then almost in slow motion I clicked f3 on the keyboard and then I wait for about a minute or so with both hands off the keyboard.  Then a screen pops up stating that it stopped working.  The PV list does not even come up for me to do a search.

    On the pop up screen I clicked for further details and I get the following from one of the screen that crashes.  Maybe the below might help further.  It is as follows:

    Problem event name     - CLR20r3

    Problem signature 1      - 1001000 exe

    Problem signature 2      -  10.1.21108.0

    Problem signature 3      -  5be4bb5a

    Problem signature 4      -  mscorlib

    Problem signature 5      -  4.0.30319.34014

    Problem signature 6      -  52e0b679

    Problem signature 7      -  2bce

    Problem signature 8      -  17

    Could you assist further?

    Thanks for the response.

  • CFROTON Profile Picture
    4,710 on at

    Dear Lisa,

    What field are you using F3 on while you are in the screen. Have you tried standard mode...some custom code could be running

    Do you have a lot of records that would show in the PV list from that field?

    I've already mentioned one issue that has been documented and bugged for 2018, there are others.

    You might consider opening up a support case so an environment engineer to help you, or identify a bug :)

    Best Regards,

    Jana MacDonald

  • Community Member Profile Picture
    on at

    I'm currently experiencing this same issue on the IN Receipts screen (10.010.00). Wondering if anyone has found the root cause and a solution. Any and all feedback would be appreciated!

    When first opening up the screen the default field is the Batch Number. When hitting the F3 key, and not moving the focus off the batch field, the screen crashes after about 1-2min where the screen is unresponsive. My Test environment crashes the same as production. However, in our Development environment the F3 works without crashing. So it looks like the procedure is possibly failing based on data. I have not been able to confirm this yet. I'm currently double checking to ensure all environments are running the same code base as I have had to install a few hotfixes beyond the SL2015 CU2 that we are running.

    Manually running the PV procedure it brings back approx. 27,000 records.

    Doing an F3 lookup on the batch number field on the IN Issues screen (10.020.00) works without issue. And it brings back approx. 413,000 records when running the procedure directly in SQL Server Management Studio.

    Based on the tests I've done it does not appear to be an issue with the number of records being returned. 

  • CFROTON Profile Picture
    4,710 on at

    Hello,

    You can look for IN batch numbers that may be blank in the batch table, if its data that could be a cause .

    You can also run a sql trace when you run the F3 function lookup at the batch field on the IN Receipts screen, It may tell you if a trigger or custom proc is running, or if there is some long duration on a lookup..

    Best Regards,

    Jana MacDonald

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 672 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 534 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 289 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans