Finance | Project Operations, Human Resources, ...

GP exits with print dialog box

(0) Share

Report

Posted on by Richard Wheeler

75,848 Moderator

We have a client who sends all posting journals to the screen and to files. This allows them to file each module's journals to specific folders.We just applied 18.00.1461 and when they post. after the print dialog box for the GL posting journal appears GP just exits. No error message or any other message, it simply exits. There is nothing in the event viewer or DEXSQL.LOG. The only fix I found was to uninstall GP and remove all traces of GP and reinstall. Has anyone else experienced this behavior?

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (11)

Answers (0)

Hokuminaria 2,950 on at

Like (1)

Report
Hey Richard,

One of the most common causes for crashes after an upgrade, especially during printing, it the Report Dictionaries either being corrupt or out of synch.

The very first thing that we do in support when we get these is to redo the dictionaries and synchronize. I have provided the steps below we provide for this type of scenario.

Recreate and synchronize the modified forms and reports.

Please use the following article to recreate your Reports.dic:

KB 850465 support.microsoft.com/.../850465

If you have any modified forms\windows, you will want to recreate your Forms.dic as well.

KB 951767 support.microsoft.com/.../951767

To synchronize after recreating, use the steps below:

Start Great Plains Utilities. To do this, follow the appropriate step:

Click Start, point to All Programs, point to Microsoft Dynamics, point to GP (or appropriate version), and then click Utilities.

In the Additional Tasks window, click Synchronize forms and reports dictionaries, and then click Process.

Locate the Dynamics.set file on the client computer, and then click Next. (C:\Program Files (x86)\Microsoft Dynamics\GP 2018)

I hope this helps!

Thank you!

Brandon | Microsoft Support Engineer.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (1)

Report

Brandon, these standard steps were all tried. The only thing that worked was completely reinstalling GP. This makes me think it was the DYNAMICS.DIC dictionary that was corrupt.

Was this reply helpful? Yes No
David Musgrave MVP ... 14,095 Most Valuable Professional on at

Like (0)

Report

If you are using Named Printers, recreate the Printer IDs.

Comment out ST_MachineID in the Dex.ini to disable Named Printers to test.

David

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

No named printers here. All that changed was applying the latest update.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Has anyone else experienced these issues? This is now becoming extremely annoying. They print all day long and about every fifth time this happens? This happens when multiple print dialogs boxes appear. One for the transaction journal, the next one for the distribution and the third for the summary distribution.

Was this reply helpful? Yes No
Suggested answer

Needles 80 on at

Like (0)

Report

Hi Richard - you could try adding the Dynamics.exe to the DEP exclusions list. (advanced system settings>>performance>>settings>>data execution prevention). Maybe 1 on the reports had some vba code and that was causing the system to crash?

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Could this be something that has changed with the application of 18.4.1434? They were on 18.4.1173.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

I have found these events in event viewer. They all reference DYNAMICS.EXE and NTDLL.DLL.

Log Name:      Application

Source:        Application Error

Date:          8/11/2022 9:54:16 AM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      GSE86.WORKGROUP

Description:

Faulting application name: Dynamics.exe, version: 18.0.28.0, time stamp: 0x5f0f4d00

Faulting module name: ntdll.dll, version: 10.0.19041.1806, time stamp: 0x39cccd9d

Exception code: 0xc0000374

Fault offset: 0x000e6fe3

Faulting process id: 0xc94

Faulting application start time: 0x01d8ad7e4472e721

Faulting application path: C:\Program Files (x86)\Microsoft Dynamics\GP2018\Dynamics.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: 1e3f0971-7062-405c-8c37-c927e274f767

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>100</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2022-08-11T13:54:16.7120795Z" />

    <EventRecordID>79979</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>MYPC86.WORKGROUP</Computer>

    <Security />

</System>

<EventData>

    <Data>Dynamics.exe</Data>

    <Data>18.0.28.0</Data>

    <Data>5f0f4d00</Data>

    <Data>ntdll.dll</Data>

    <Data>10.0.19041.1806</Data>

    <Data>39cccd9d</Data>

    <Data>c0000374</Data>

    <Data>000e6fe3</Data>

    <Data>c94</Data>

    <Data>01d8ad7e4472e721</Data>

    <Data>C:\Program Files (x86)\Microsoft Dynamics\GP2018\Dynamics.exe</Data>

    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>

    <Data>1e3f0971-7062-405c-8c37-c927e274f767</Data>

    <Data>

    </Data>

  <Data>

    </Data>

</EventData>

</Event>

Was this reply helpful? Yes No
David Musgrave MVP ... 14,095 Most Valuable Professional on at

Like (0)

Report

Hi Richard

If you can replicate the crash each time, use GP Power Tools manual logging to capture logs.

The last script run in the script log will show the script where it crashed.

David

Was this reply helpful? Yes No
Suggested answer

Lisa at AonC.com 933 Super User 2025 Season 2 on at

Like (0)

Report

I know it seems illogical, but I have learned to rename the forms.dic and then try to print the report. If that works, forms.dic is the culprit. (As I see it happen the most with reports that include GL Accounts, my guess is that the account framework is searching for something in forms.dic. I'm sure someone out there with more knowledge has a better explanation for this behavior.)

Was this reply helpful? Yes No