cancel
Showing results for 
Search instead for 
Did you mean: 

CR for VS2008 10.5 error "This field name is not known" on Win2012 or later

Former Member
0 Kudos

I have a report that works fine in an ASP.NET 4.5 app in IIS on Windows 7 and Windows Server 2008 R2, but fails on Windows Server 2012 and Windows Server 2012 R2.

This is using Crystal Reports Basic Runtime for Visual Studio 2008 (10.5.0) x64. Installing 10.5 SP1 (10.5.1) did not help.

The datasource is an ADO.NET DataSet at runtime, with an XSD file at design-time.

I have debugged the app on the server to ensure the DataTable column is valid and present in the DataSet passed to CR.

The same report with the same database and query to build the DataSet runs normally up until it is run on Win2012 or later.

The error is "This filed name is not known."


CrystalDecisions.CrystalReports.Engine.FormulaException occurred

  HResult=-2147214848

  Message=This field name is not known.

Error in File C:\...{D106385F-1C37-4CE3-8106-E7798EF1F2F3}.rpt:

Error in formula  <Object_Visibility>.

'if ({ReportDetail_ds.DAY26} <> 'Y') then

'

This field name is not known.

  Source=CrystalDecisions.ReportAppServer.DataSetConversion

  StackTrace:

       at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)

       at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

       at CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)

       at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export(ExportRequestContext reqContext)

       at CrystalDecisions.CrystalReports.Engine.FormatEngine.Export()

       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Export()

...

       Source=""

       ErrorCode=-2147217383

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

Hi Kevin


CR 10.5 is not supported on Win 2012. please see the wiki Crystal Reports v. 9.1 to SAP Crystal Reports, developer version for Microsoft Visual Studio Runtime...

You have two options:

1) Upgrade to CR 2008 and you will still be able to use VS 2008

2) Upgrade to "SAP Crystal Reports, Developer Version for Visual Studio .NET" and use VS 2010 / 2012 / 2013

To upgrade to CR 2008 you will have to contact sales; 866-681-3435

Worldwide Office Locations | SAP

To upgrade to "SAP Crystal Reports, Developer Version for Visual Studio .NET", see Note that this version of CR does not support VS 2008.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow us on Twitter

Former Member
0 Kudos

Hi Ludek,

Thank you very much for your helpful reply.

Upgrading CR is on our product roadmap, but is a longer-term solution. We are hoping to find a shorter-term solution or workaround.

Understanding that this is an unsupported scenario, we have been using this report and numerous others without issue on Win2012+.

Are you able to provide any resources to help troubleshoot why this particular issue is cropping up now?

Our latest changes to the report added additional images that are conditionally hidden/shown with a Suppress formula.

74 images can be hidden/shown without issue, but now that there are 111 images, the report chokes. Is there a hard limit to images, OLE objects, Suppress formulas, etc?

Is there any way to troubleshoot or gain insight into what caused this functionality to suddenly break?

former_member183750
Active Contributor
0 Kudos

Ahhh - images and Crystal Reports. Not good news...

There is a Discussion posted in 2012 where I said the following:


Crystal Reports is limited in how it works with images - large images or a large number of images, etc. Much as CR is not a good database archiving tool, it's not a very good graphics presenter. Too many graphics, large graphics, high quality graphics, all of these may cause memory issue. A few tips:

  1. Make sure the picture  blob  what ever, never spills beyond the designer pane of the report.
  2. Limit the number of images
  3. Lower the resolution of the images
  4. See if a computer with more memory helps
  5. See if you get the same issue with a printer other than ADOBE PDF printer
  6. If you need actual PDF, do an export to PDF

Unfortunately, all of the above still applies even today to the latest CR releases...

- Ludek

Answers (0)