cancel
Showing results for 
Search instead for 
Did you mean: 

CRVS2010 Beta - Error deploying a CR within an ASP.NET app using VS 2010

Former Member
0 Kudos

I am getting the following error:

Compiler Error Message: BC32206: *The project currently contains references to more than one version of CrystalDecisions.Web, a direct reference to version 12.0.2000.0 and an indirect reference (through 'rpt_UW.CrystalReportSource1') to version 14.0.2000.0. Change the direct reference to use version 14.0.2000.0 (or higher) of CrystalDecisions.Web.

I added the code exactly as instructed by SAP (in on-line documentation), as follows, and it works fine on my laptop when viewed in IIS, but not when deployed to the production server:

<configuration>

<runtime>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.CrystalReports.Engine" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.Shared" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.ReportSource" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.Windows.Forms" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.Enterprise.Framework" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.1100.0"/>

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.Enterprise.InfoStore" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.1100.0"/>

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.ReportAppServer.ClientDoc" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.1100.0"/>

</dependentAssembly>

<dependentAssembly>

<assemblyIdentity name="CrystalDecisions.Web" publicKeyToken="692fbea5521e1304" culture=""/>

<bindingRedirect oldVersion="14.0.2000.0" newVersion="12.0.2000.0"/>

</dependentAssembly>

</assemblyBinding>

</runtime>

Subject modified as per the sticky thread at the top of this forum:

[Crystal Reports for Visual Studio 2010 Beta - read before posting|;

Edited by: Ludek Uher on Jun 4, 2010 12:21 PM

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

Please search the forums before posting. See this thread:

http://forums.sdn.sap.com/click.jspa?searchID=43211462&messageID=9003667

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Former Member
0 Kudos

I followed that thread, but I don't see any solution to the problem. I am using a website, not an application. I have installed the Crystal 2008 runtime on the IIS server, and placed the crystalreportviewers12 folder in the root folder of the website, and I am using the correct binding Redirect code in the web.config file. I don't see any proposed solution anywhere in the thread. Can you point me to the solution that I am missing in the forum?

Thanks so much. I have been trying to get this to work for three weeks.

0 Kudos

Hi Jonathan,

Not sure which posts you have been reading but the distribution files have not been released yet and the work around is only for those to test but only as a suggestion. There is no for sure it's all going to work, and it scares me when you say you are distributing to a Production server... This is beta and beta's are never a good thing to put on a production server, there are no guarantee's or solutions if anything breaks.

All I can suggest is you continue testing on a server where you have VS and CR installed and use that as your web server for testing, forget about deploying the runtime only for now.

Thank you

Don

Answers (0)