[Hardik Gupta]

Up

0

Down

::

Hi @stephengpcore-ca

GP has been heavily affected by recent Microsoft updates, especially post-CAD Tax Table changes. Your diagnostic approach is solid (data is clean = report-level issue).

Quick fixes to try:

1. Rebuild RW files: Export affected reports → Delete → Reimport
2. Reindex GL tables (GL00100/GL00101) in SQL
3. Clear report cache: Delete C:\Program Files\Microsoft Dynamics\GP\Data\Reports
4. Rebuild report dictionary: Admin > Reports > Rebuild All
5. Verify GL Account segment configuration matches post-update CAD table setup

Root cause: Post-update, reports reference old segment indices, which drops the main Segment from account strings.

Let me know if any of these work for you.

• This reply was modified 1 month ago by  Kerry Hataley.

[Stephen Hoffort]

Up

1

Down

::

Part of the update process … is to use GP Utilities to rebuild the RW (Report Writer file ,,, or Reports dictionaries) .. I never use this process as I find it more problematic than rebuilding. I always rebuild all RW files every update .. so step 1 has been done but will be done once more. Step 3. Clear Report Cache is basically delete the dictionary … again .. was done during the update …

I will perform all GP SQL rebuilds on the databases tonight after backups and take care of any steps mentioned here. Updates to follow.

[Stephen Hoffort]

Up

1

Down

::

All steps have been taken as suggested. Report dictionaries were purged and rebuilt from package files. All GL indexes have been purged and rebuilt using Check Links.

The GL account on both financial and payroll posting reports is still not using the account mask, and therefor isn’t separating by GL segment. This is particularly an issue for Trial Balance Detail reports.

I doubt that the issue of GP crashing has been resolved.

I can be reached at stephen@gpcore.ca

I cannot work on any of this during business hours and they have employees working across all of Canada. As a result business hours begin 6:30 AM Eastern and run until 6 PM Pacific.

[Hardik Gupta]

Up

0

Down

::

Hi Stephen,

How are things going?

[Brandon Jarrett]

Up

1

Down

::

Hey Stephen,

Based on your information, this a dictionary issue and it can cause crashing as well when running reports. Sometimes it takes a specific order of operation as well to correct this.

I would suggest the below:

First, export all your Modified Forms and Reports.

Next, rename the forms and reports dictionaries to be .old.

Set the Synchronization and Initial line to TRUE in the Dex.ini.

Run through the Synchronization Process in GP Utilities.

Imported the Forms and Reports that were exported so they create new Reports and Forms Dictionaries.

Revert the Initial line in the Dex.ini back to false. Synchronization line to change back on its own.

Might need to run through the Synchronization process again once the Reports and Forms are imported.

Repeat for each workstation that you have that is having this problem

As mentioned above, the order that these are done in can change the outcome and suggest the order above.

To add onto this a great test that can be done is to set security back to the core report and determine if the Core Report does the same thing. The reason for this is because the core report comes from the Dynamics Dictionary and not the Reports.dic. If it happens with the core one, you might need to rebuild the GP Code Folder by renaming it and running a repair. This will rebuild the code folder to its default state, and you will need to add your customizations / third parties back in.

I hope this helps!

Thank you!

Microsoft Dynamics ERP and cloud partner | Enavate