Upgrade from CRforVS2010 Beta to CRforVS2010 production results in errors

[Former Member]

Hello all,

I'm looking for some help with an upgrade issue. I am a newbie in this area so I apologize for my lack of knowledge.

I'm taking over a web site with crystal reports for visual studio 2010. The site is quite complicated. The main site is located on one server(external web hosting) and the reporting feature is located on another (internal office hosting).

When I upgrade to CRforVS2010 production release, the reporting feature bombed. Giving me the following error:

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'CrystalDecisions.Web, Version=14.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 56:

Line 57: <httpHandlers>

Line 58: <add verb="GET" path="CrystalImageHandler.aspx" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>

Line 59: </httpHandlers>

Line 60:

Source File: C:\inetpub\arcswppi\reporting\web.config Line: 58

Assembly Load Trace: The following information can be helpful to determine why the assembly 'CrystalDecisions.Web, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' could not be loaded.

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

My web.config is below

Can anyone help me with this?

[former_member11696 · Accepted solution]

Hi John,

Sorry to say when the BETA was released we warned people hundreds of times not to install Beta's onto a production server. Unfortunately our warnings were ignored. And now you have to clean it up.....

If you search here you'll find postings from Ludek on how to possibly get it cleaned up, uninstall, un-GAC the dll's if any were left over, then delete the folder and registry keys etc.....

Stop the WEB server so it unloads the CR runtime first also.

It also means updating and recompiling your project so the references get updated from Version 14 to Version 13.

Good Luck

Don

[Former Member · Accepted solution]

Thanks for the quick reply.

Yup, I feel like the clean up crew alright.

John

[former_member183750 · Accepted solution]

I wrote a KB on this:

[1535325 - How to remove CRVS2010 Beta 2|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533333335333333323335%7D.do]

- Ludek

[Former Member · Accepted solution]

Ludek,

Thanks for the link.

John