2025 Jan 30 10:42 AM - edited 2025 Jan 30 11:24 AM
It is a old VB6 app, but have been running for years (from 2003) and the customer loves it. It even run perfect until a few days ago, when there was Windows 11 update.
It is confermed by the user that 23H2 - No problem. 24H2 - can not export.
It is possible to see the report, but it is not possible to export to PDF.
I get a dialog box withe heading: "Crystal REpoer Viewer", The message is: "Failed to export the report"
My CRViewer.dll has version 11.0.0.1282
I someone else experience this problem?
What can I do to fix it (other than rollback the windows update)?
Request clarification before answering.
Unfortunately CR 11 is VERY old and you should have updated to CR 11.5, but it too is no longer available.
Of course none of what you are using is supported by Windows either.
All I can suggest is upgrading to Visual Studio 2010->2022 and use the CR .NET components:
https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html
It's likely either permission or a dependency missing. You'll have to do more debugging...
Do all exports fail or some?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As of CR 9 SAP no longer ships nor supports the legacy COM SDK's, that includes crviewer.dll and the RDC craxdrt.dll and craxddrt.dll which are all COM based. CRR does still use COM dll's but those are all used internally and in .NET.
Microsoft no longer supports VB 6 or any of it's dependencies. So rather than trying to HACK your way through your issues it's time to bite the bullet and upgrade to VS 2022 and CR .NET.
The same for CR 11.5, yes it may fix your issues temporarily but in the short term Microsoft updates may break 11.5, the technology is the same as 11.0, it just supported later versions of the OS. Windows 11 is not supported in either though because CR 11.0/11.5 had no concept of Windows 11.
To answer your latest question, again NO, as of CR 9 Crystal Reports no longer installed the .NET SDK nor the COM components you are asking about. And NO you are not licensed to use the Legacy SDK's any more, .NET is the only one along with Java and RESTFul SDK's.
So to answer your questions, stop trying to hack your way around upgrading, you can tell your users to be Windows Compliant you and they need to upgrade. The download page has a few .NET test app's I wrote when I work for SAP, retired now, which you can use to get your started upgrading.
Good luck
Don
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry it's been so long since I've used VS 6 and CR XI I don't recall what the export dll is.
Current versions export dll's are crxf_*.dll, it could be the same for XI, I don't recall now what it used...
In CR Designer open the report and if you click on Help.. About... More Info it lists the dll's used, export the report and then look for something with PDF in the name. Then use Procmon or Dependency Walker on the dll, it may suggest what's missing.Try simplifying the report, no database connection and just a "Hello World" in a text box and see if that works, then take the report having problems and start removing parts and see if it works at any point.
You really need to update your app, there are ways to improve performance in .NET SDK, load a dummy report on when your app opens, that preloads all of the CR runtime so when you open a real reports it should right away.
You never mentioned at what point the customer complained about the speed in your new app?
Good luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
61 | |
8 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.