Intelligence Report error. Excel Crashes with a ntdll.dll .

SUGGESTED

Our Sage 300ERP 2019 is generating a error.  Excel crashes with the following error. 

The Error showing the Server Log was. 

Faulting application name: EXCEL.EXE, version: 16.0.5017.1000, time stamp: 0x5ebb1f39
Faulting module name: ntdll.dll, version: 10.0.14393.3630, time stamp: 0x5e8d4386
Exception code: 0xc0000374
Fault offset: 0x00000000000f7a13
Faulting process id: 0xd5c
Faulting application start time: 0x01d644c887a10bb3
Faulting application path: C:\Program Files\Microsoft Office\Office16\EXCEL.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 723cfe25-31e0-4af0-845e-f9550af0e172
Faulting package full name:
Faulting package-relative application ID:

The error is consistent it is not user or server dependent.. 

WE have installed Sage3002019PU1 through  Sage3002019PU4.  we are using Office 2016 with the newest updates.   We are running SAGE 300 ERP 2019 on a Terminal Server Cluster on Windows 2016 Server  with patches for Office and Windows up the current month. 

Any Idea on a resolution would be greatly appreciated.

Parents
  • 0
    SUGGESTED

    The issue usually occurs when you have traces of multiple versions of Microsoft office stuck in the registry.

     A repair of office wont help rather please follow the below on workstation and server:

     Please back up your registry and if need be create a system restore point.

     Please download off the internet a free tool called Revo Uninstaller.

    Use the tool to uninstall all Microsoft office versions

    The tool after uninstall will give you options to scan the computer and registry to remove all traces of leftover filers, please allow this to run.

    Restart your computer and install the version of Microsoft office you want to use.

    Then test your report again

  • 0 in reply to NateP

    The server is  a fresh install, with no office version except for 2016.    

    I have additional data, the Report in question was created from a Excel report I believe. 

  • 0 in reply to SteveFromTO

    If you are getting the above error, you would NORMALLY get it for any Intelligence Report that you run, since it indicates an overall Environmental problem. When troubleshooting, I usually test the Out-of-the-Box SI Reports first, just to reduce the number of variables (since we know those are tried and tested as functional on lots of systems). I usually use the General Ledger Transaction Details report under the Financials folder as my 'troubleshooting report', since every client has at least the GL module (reports can error, with a different error than yours, if you don't have the applicable module). Generally, the sort of error message that you have requires Sage Technical Support. Have you tried connecting with Tech Support so they can remote onto your system and address the specifics of your Environment?

  • 0 in reply to Gabriela Yates

    The big PITA about this is that out of box reports work.  And a month ago, this report, worked.  Its just this report that suddenly stopped.  And consistently stopped at defining names ranges, with a excel crash.

  • 0 in reply to SteveFromTO

    Not familiar with your error, but always good to make sure that there are no illegal characters accidentally used in the naming of the template (< > : " / \ | ? *). I also try to save the template someplace safe and then strip the template from the report to see if it will run as just the raw data. If the raw data without a template DOES run, that usually means that I have to rebuild the template, or try to take an old version of the report from when it was working and try to save that as the template. If the raw data DOESN'T work, then it is a matter of trying to figure out what data connections this report is trying to make, that is not present in your out-of-the-box reports. No short cut to the easy answer, unfortunately, just patent and methodical elimination of variables.

Reply
  • 0 in reply to SteveFromTO

    Not familiar with your error, but always good to make sure that there are no illegal characters accidentally used in the naming of the template (< > : " / \ | ? *). I also try to save the template someplace safe and then strip the template from the report to see if it will run as just the raw data. If the raw data without a template DOES run, that usually means that I have to rebuild the template, or try to take an old version of the report from when it was working and try to save that as the template. If the raw data DOESN'T work, then it is a matter of trying to figure out what data connections this report is trying to make, that is not present in your out-of-the-box reports. No short cut to the easy answer, unfortunately, just patent and methodical elimination of variables.

Children
No Data