Sydneyandy
Top achievements
Rank 1
Rank 1
Sydneyandy
asked on 12 Sep 2022, 03:17 AM
Currently, I am facing an issue when exporting the pdf report from the winform report viewer, the preview is fine, but when I try to use the export pdf button and then select folder as desktop, the entire app will be closed without any exception, the app just closed itself. If I select a different folder, it works fine. For the same PDF I use the PdfViewer to test, the same issue. I suspect some shared components failed around PDF export. The version is 2022.2.622
Faulting application name: CustomDecoder.exe, version: 1.0.0.0, time stamp: 0x631d7036Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
Exception code: 0xc0000417
Fault offset: 0x0008af3e
Faulting process id: 0x4a20
Faulting application start time: 0x01d8c65568c81b08
Faulting application path: C:\dev\Telerik\winforms-sdk\PdfViewer\CustomDecoder\CustomDecoderCS\CustomDecoder\bin\Debug\CustomDecoder.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR100.dll
Report Id: 2571b31a-1468-4eb5-b7f3-c51355fa69d4
Faulting package full name:
Faulting package-relative application ID:
Does this problem happen only when saving on the Desktop? Can you save files on the desktop from other projects?
I think this may be a permissions issue, please check that your user has the necessary permissions, for sake of testing try with full permissions and if it works go from there.
If you would need further assistance, please record a trace log from the WinForms application - How to: Create and Initialize Trace Listeners - .NET Framework | Microsoft Docs
Thanks Dimitar,
I tried the following steps:
1. Run the app under administrator permission, same issue.
2. Create a new project and export the pdf, same issue.
2. Use Telerik Report Designer export PDF, it allows me to select Desktop and export successfully.
3. Run the app and export pdf to c:\ success.
4. I have generated the trace file as attached.
Hello Andrew,
I went through the log but didn't see any errors in it, was the export operation performed while the trace listener was running?
If not, please record the log again and ensure that you have reproduced the issue while the trace listener is listening.
Besides that, It would be great if you could attach a runnable project where the issue is reproduced so that I may debug it locally.
Hi Dimitar,
Thanks for helping, and yes, I the export operation performed while a trace is running. I have run the same exe on the other computer, looks like it works. Not sure why my dev machine didn't work. I suspect maybe the c++ runtime version for some reason is mixed up.
Hi Andrew,
In such a case, you may try using the Fuslogvw.exe to help you diagnose why the .NET Framework cannot locate the assembly/es at run time - Fuslogvw.exe (Assembly Binding Log Viewer) - .NET Framework | Microsoft Learn.
You may pretty much do what is suggested in the Assembly Used in ObjectDataSource is Not Loaded by the Standalone Report Designer | Telerik Reporting KB article except that you do not need to add the assemblies again. Just start the fuslog, give it a folder to write the logs to, and reproduce the error.
Hope this helps.