development vs server version issues

[#1]

I am migrating an old Web Service (WCS) from a windows 2008 R2 into a Windows 2002 Server. Web Service uses SAP Crystal Reports libraries to generate PDF reports, connecting to an Oracle DB.

Everything went well until I had to reinstall CR Runtime. In the old server, CR DLLs version is 13.0.0.99, while development environment uses VS 2019 and CR for VS 13.0.29.3671.

Which CR Runtime should I install on new server to get it matched with development environment? I had been searching something like SAP CR Runtime Engine 13.0.29, but I only found version for VS. I also tried to install CR 13.0.28 Runtime Engine, but it crashes when I try to run my web service (could not load information from DB).

Should development and server CR versions match, or else later CR versions are compatible with earlier ones?

[DonWilliams]

First thing you need to do is clarify your updated OS, you said WS 2002, did you mean 2022?

Like all software there are updates and minimum versions required to update.

Here's the home page for CR for VS, note it is version 13.x

https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html?locale=en-US

To comment on your versions, 13.0.0.99 is the original release of CR for VS.

13.0.29.xxx is an update released in 2020.

You should not mix the versions, bad things can happen, possibly why you are getting errors.

On the above link you'll find a link to download SP 40, latest version. Also note CR for VS does not have patches, they are full builds/installs only.

You'll also find a link to PAM here:

https://www.sap.com/documents/2016/06/f871031e-757c-0010-82c7-eda71af511fa.html

Under the supported OS's you'll see CR for VS does support Windows Server 2022 until SP 32 and above.

Also NOTE, always use the latest SP, if any issues are found they won't be fixed until the next release or higher....

Next Steps:

1. Download CR for VS SP 40, EXE for integration into Visual Studio, and MSI's are for distribution only, not required in VS integration. Note there are separate installers for VS 2010->2019 and a 64 bit installer for VS 2022 and above

Uninstall the previous version, both the EXE and MSI on Dev PC and the Server.

2. CR for VS now only supports 64 bit applications and IIS in 64 bit mode.

To upgrade your project see this Blog I wrote for upgrading:

Related Documents

• Crystal Reports for Visual Studio Licensing
• Upgrading a Visual Studio 2008->2022 .NET project with the latest CR .NET SDK packages for instructions on upgrading your existing project to the latest SP
• See these blogs on how to use Crystal Reports for Visual Studio sample applications:
  • How to use the new CR 2020 export to Microsoft Excel(XLXS) in Visual Studio .NET code (new)
  • How To: Parameters in Crystal Reports for Visual Studio .NET
  • Printing Crystal Reports in .NET
• SAP Crystal Reports for Visual Studio Installation Guide ( SP 21 and above)

Also note CR for VS now only supports 4.7 and 4.8 Windows Framework.

3. You may need to update each report manually to get the version of the report update to current version, as well as the newer Oracle CR Client dll's, you'll need to open each report in Crystal Reports Designer 2025, also 64 bit, and using an 64 bit ODBC DSN or OLE DB or XML etc. or in your case possibly the Oracle Native 64 bit Client, and then save the report in a new location, or at least have a backup of the original reports just in case.

If you have a lot of reports I suggest highering a Student to upgrade the reports....

You can get Crystal Reports 2025 from here:

https://www.sap.com/products/data-cloud/crystal-reports.html

That should get you going...

PS add CR for VS Tag to your post: https://community.sap.com/t5/c-khhcw49343/SAP+Crystal+Reports%25252C+version+for+Visual+Studio/pd-p/...

[ciceroan]

hello Don, of course new server OS is Windows 2022 Standard. I think I got to match development and server environment by installing CR Runtime Engine 13.0.29.3671. But I could not run reports from my Web Service. The issue is that CR runtime could not connect to database, even though Oracle driver is installed and properly set. In more details, Web Service is able to run an empty CR report (ie: without DB connection); but, when it tries to run a report connected to Oracle Database, it ends into a "Could not load information from Database" error. I tried to set Web Service App Pool to "Enable 32Bit Application=False"; then reset it to True, but nothing happens. maybe CR search for TNSNAMES,ORA in a different location then the ODAC home? Really I should re-engineer all my application? please help

[DonWilliams]

PAM indicates SP 29 is not supported on Windows Server 2022, you need to upgrade. Also, Current versions of CR will support Oracle Servers. SP 29's CR's Oracle Client dll may not support your version of Oracle. Also note do not use Windows Oracle Client dll, it has issue with CR and Oracle. Upgrade a I recommended...

See this KBA on how to enable CR's database logging component:

https://userapps.support.sap.com/sap/support/knowledge/en/1603398

[ciceroan]

I dont have VS installed on App Server. so, I trace CR behavior into a log file (I would send you one, if I could...). What I see in log, is that CR apparently binds all report and DB connection parameters (server name, user/password). execution always crashes on ReportDocument.VerifyDataBase, or (if I skip VerifyDataBase) on ReportDocument.ExportToDisk. Error message is "could not load information from DB. System.Runtime.InteropServices.COMException: Error on file REPORT 7856_9104_{C50D4E42-9CFE-4875-81C6-B81E5065962B}.rpt" and so on". so, which version of CR should I install to connect to Oracle 23.26.1.0.0? also, should I install the same version both on my development PC and on App Server? Finally, should I uninstall ODAC 11.2.0.3.20 from App Server?

[DonWilliams]

FYI - I retired from SAP a few years ago and no longer have all the parts to test with....

To clarify, please read all of the info in my first post.

You cannot mix CR runtime versions so install SP 40 on your development PC, use the 32 bit installer since you are using VS 2019.

REBUILD your app and distribute it to your IIS Server, you can set it to either 32 or 64 bit but be aware SP 40 only has 64 bit runtime which means your Oracle Client must also be 64 bits.

Now run the matching SP 40 MSI package on the Server where your app is installed. You cannot manually copy over the CR runtime, won't work, and note, Set the Assembly property Copy Local to false as my Blog notes.

Looking at the CR for VS PAM, that Windows Oracle client is not listed so it's not supported:

https://d.dam.sap.com/a/iN9wo5L/SAP_Crystal_Reports_2025_PAM.pdf?rc=10&inline=true

I suggest installing the Oracle Clients, ODBC, OLE DB or using Crystal Reports Oracle Client dll, connects directly to Oracle through Oracles Client OCI dll.

I don't have an Oracle Client Installed so I don't see it but in the Database Wizard when you select New connection you will see Oracle listed, if CRD can find the client, if you don't see it the client needs to be configured.

So likely cause of the error is CR is looking for a 64 bit client, I believe Oracle adds it's client install in the PATH statement, which is likely where CR is looking for it.

I no longer have access to an Oracle Server so no idea if the ODAC client can work or not. Since it's not listed in the CR PAM no testing has been done. SAP only lists what been test...