Unhandled exception at 0x00007FFC5891DACE (ucrtbase.dll) in Telerik.ReportDesigner.exe: Fatal program exit requested.

[Abdechafi]

I'm trying to modify my reports using Telerik Report Designer R3 2020, but every time I got a Telerik has stopped working.

I opened a new instance in VS 2019 to debug the program and this what I got:

 

Unhandled exception at 0x00007FFC5891DACE (ucrtbase.dll) in Telerik.ReportDesigner.exe: Fatal program exit requested.

[Eric R | Senior Technical Support Engineer]

Hi Abdechafi,

Thank you for providing the screenshot. However, I believe it just means that the debugger is missing the required DLL symbol to debug the application. This is typically unrelated to Telerik and usually an operating system issue.

Let me provide additional troubleshooting steps for the Standalone Report Designer below. 

Troubleshooting Standalone Report Designer Crashes

First, use the designer configuration to generate a log of the crash. To do this add the following code to the Telerik.ReportDesigner.x86.exe.config and the Telerik.ReportDesigner.exe.config files which will enable tracing.

Note that the initializeData folder path must exist on the machine.

<system.diagnostics>
    <trace autoflush="true" indentsize="4">
      <listeners>
        <add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\temp\StandaloneDesigner.LOG" />              
        <remove name="Default" />
      </listeners>
    </trace>
</system.diagnostics>

Second, use the Fuslogvw.exe to ensure their are no assembly binding errors. To do this following Microsoft's fuslogvw.exe documentation. 

Wrapping Up

From your previous ticket with the missing Microsoft.mshtml issue, I suspect that you are using Telerik Reporting solely on a Windows Server machine. Can you confirm if this is the case? 

In the meantime, please let me know if you need any additional information. Thank you for choosing Telerik Reporting.

Regards,

Eric R | Senior Technical Support Engineer
Progress Telerik

[Abdechafi]

Hello Eric R, 

Thank you for your reply, I'm using Windows 10 x64 not a Windows Server machine, so I think that the error is related to a missing DLL file.

I will check this.