Crystal Reports 10 from C# vs2008: error "missing parameter values" but all parameters have values?

We have converted a project from using .NET 1.1 to .NET 3.5 (to run nicely on a new server) and all works fine except for the Crystal Reports.  
We were using CR 9 and now have to use CR10, since there seems to be no way to reference CR9 DLLs under this project now.
When a report is generated we are getting the error "missing parameter values".  We have changed the order and the manner in which we assign values.  We are also checking so we know that immediately before the call to generate the report, all parameters do have values.  We have run with our usual situation (some parameters have a null or blank value) and with every param having a non-null, non-blank value.  All get the same error.
We have tried a dummy report with no parameters and that works fine, so it does look like a parameters problem of some kind.

In brief, without boring with code, we:
- load the report
- set up the database connection
- set the parameters (values from web page)
- for debug purposes check if all the report's parameters have a value
- export to PDF

The full error text is
CrystalDecisions.CrystalReports.Engine.ParameterFieldCurrentValueException was caught
  Message="Missing parameter values."
  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()
       at TARN.Report.ExportCrystal() in C:\Inetpub\wwwroot\TARN2008\TARN\Classes\Report.cs:line 917
  InnerException: System.Runtime.InteropServices.COMException
       Message="Missing parameter values."
       Source="Analysis Server"
       ErrorCode=-2147217394
       StackTrace:
            at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext)
            at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

This needs to go live 1st April and we didn't expect to have problems upgrading Crystal versions so it is pretty urgent now, any help gratefully acccepted.
LVL 1
keithfearnleyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mlmccCommented:
VS2008 is only compatible with CR 10.5 which is the version that comes with VS2008.  VS2008 isn't compatible with any of the standalone versions of Crystal

https://forums.sdn.sap.com/thread.jspa?threadID=1331234

mlmcc
0
keithfearnleyAuthor Commented:
Thanks for the reply...
Sorry, I should have been clearer with my version numbers - we are indeed using the version of 10 that comes with VS2008 - I was distinguishing that from v9 that we had used before when the project had been built under VS2003.

Yesterday we made a break-through in that we discovered how to referecce the old Crystal v9 dlls so that the project is back up and running again.  So our panic is over, but it would still be useful to know about this, in case it hits our next built-from-scratch project to use Crystal 10.5 from VS2008.

Do you know if attempting to use a standalone Crystal would cause that error message (maybe we inadvertently referenced our standalone DLLs when we thought we were using the VS version)?
0
mlmccCommented:
That might since the .Net versions are different.

mlmcc
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
keithfearnleyAuthor Commented:
Difficult to determine accuracy... we tried something different and it worked - we hadn't the time to investigate too much further.
Help appreciated
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.