1,190
Hi there,
Does anyone have issues with the Crystal Report printing using Template in SL 2015 CU2?
It happens only in the workstations with the Windows 10 operating system. User gets the “Assertion failure” error when the report is printed using screen customization by utilizing the ROI template.
Please let me know if you have solutions.
Thanks,
Karthik
*This post is locked for comments
Good Day -
I have searched the Dynamics SL bugs and I do not find anything related to this issue. Specifically related to Windows 10, or as mentioned in later posts 'on select' workstations. Since this might be related to permissions a couple things that you can try is to delete all the ODBC connections on the workstation referencing the SL SQL Server and databases. Then re-run a Crystal report to recreate them.
If there were any updates to the ODBC connections (Windows or SQL) they would not have updated on these pre-existing connections.
Another option is to look at if your templates are using company ID as a criteria. Company ID will save to the template and can cause issues when run by a user that does not have access to that specific company.
I hope this helps.
Thank you,
Carolyn
MSDSL Technical Support
Hi Karthik,
Did you find any resolution for this? We've found that it is apparently a permissions issue. We can put a user experiencing this issue into the Administrators group and the issue disappears. But it's not a viable long term solution.
Thanks.
Hello, We are having an issue on select workstations as well since 2015 CU2. There is no issue running reports if the selections are made manually. However, if the selections are saved to a template, loading that same template for the report will cause ROI to crash when running the report.
Application: ROI.EXE
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
Stack:
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
at ROI.My.MyApplication.Main(System.String[])
Followed by
Faulting application name: ROI.EXE, version: 9.2.41201.2, time stamp: 0x58406b09
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23392, time stamp: 0x56eb2fb9
Exception code: 0xe0434352
Fault offset: 0x0000845d
Faulting process id: 0x17c4
Faulting application start time: 0x01d2a41019bdcc4b
Faulting application path: Q:\Path\ROI.EXE
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (