PDF Generation Error

[mmodi]

Hello,

We are generating PDFs using Crystal Report via Windows service. Our current application is running on Windows 2012 and we are trying to migrate it to 'Windows Server 2022 Standard'. We have the same setup on both servers but are having an issue with one report on the new server. The below version is what is installed on the old and new servers.

I am getting below error when (.VerifyDatabase();) is being called.

This field name is not known. Details: errorKind Error in File RP979 12936_11848_{ECE325B5-9A38-471F-B000-6CED49D14B5E}.rpt: Error in formula Engine_Description: 'Replace ({v_RPT_Electronic_Check_IN_Sheet.Engine_Status_Description},"""" ,"'" ) ' This field name is not known. Details: errorKind

The same report works fine on the old server with the same parameters and same input values.

Any guidance would be highly appreciated.

Thanks.!

[AnnePetteroe]

Hello Mradul,

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers, as it provides tips for preparing questions that draw responses from our members.

Feel free to take our Q&A tutorial at https://developers.sap.com/tutorials/community-qa.html as well, as that will also help you when preparing questions for the community.

Should you wish, you can revise your question by selecting Actions, then Edit.

By adding a picture to your profile you encourage your readers to respond.

Kind regards,
Anne

[DellSC · Accepted solution]

Part of your problem may be due to the fact that you application is using SP 14 of the Crystal for VS SDK and Windows Server 2020 was not supported until SP 32. However, you can't just install the latest version of the runtime - the application needs to be upgraded to use the latest version of the SDK (currently SP 34).

For more information about the SDK, including a link to download the latest version, see SAP Crystal Reports, developer version for Microsoft Visual Studio.

-Dell

[mmodi · Accepted solution]

Thank you for your response. We have tested some 50+ reports that are working fine on new servers even with SP14. Since Windows 2012 is going to be out of support soon and we have 500+ reports, it could be a huge undertaking to upgrade all and might not finish in time.

I was hoping that this specific error could lead to some registry etc. settings that we are missing on new servers. Other reports are also connecting to the same SQL Server database and are using SQL view underneath to fetch data. They also have using formula fields to display data, but this single report is failing.

Appreciate your help.

[DellSC · Accepted solution]

You wouldn't have to upgrade the reports for a new version of the SDK, just the application and runtime.

Do you have the same version of the database drivers on both computers?

-Dell