Clever Geek Handbook

View Crystal Reports in ASP.NET3.5 Application

I have created an ASP.NET3.5 website with crystal reporting in it, it works great if I run visual studio 2008 or on my own machine. But when I deployed the project to a web server, it started giving me an error.

First, an error appeared on the first page that the CrystalDecision.web assembly was not found , after which I installed Crytal Runtime 2008 on my web server. After installation, the application looks fine, but when I opened the page using CrystalReportViewer, it gave me another error as shown below:

The installed assembly manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Any idea about this ??

+2


source to share


3 answers


After spending nearly 2 hours, I finally found a fix.

  • Remove the Crystal Reports runtime from the web server.

  • Make sure the webserver still has the \ program files \ Business object folder if it still exists and delete it. Make sure other applications don't depend on it.

  • Grant read / write permissions to the ASPNET user in the \ windows \ Temp folder

  • Set the Crystal Report runtime.
  • Restart IIS

By following these steps, you should fix the issue of viewing crystal report.



But then another problem comes up: Crystal Report Viewer does not show icons, the reason is because Crystal Report Viewer is looking for the aspnet_client \ system_web \ 2_0_50727 folder in the root folder of the website. In my case, I have several sites on my server, including .NET 1.1, 2.0 and ASP, so I have a wwwrootASP2.0 folder for this website. But by default the web server created the default folder aspnet_client \ system_web \ 2_0_50727 (wwwroot). So the fix, just copy the aspnet_client \ system_web \ 2_0_50727 folder to the root directory of your site. Bingo!!!!!! It works fine now.

I hope this helps,

Greetings.

+1


source


You probably have slightly different versions of crystal builds on the server and your development machine. Compare the version numbers in c: \ windows \ assembly on both and see if there is a difference. If so, either update the server or change the version numbers for the assemblies in the web.config.



Also, the located assembly manifest definition does not match the assembly reference

+1


source


I just wanted to add that it's easier to create a virtual directory under your aspnet_client web app that points to C: \ Inetpub \ wwwroot \ aspnet_client.

It also displays images in the Crystal Report viewport. It has been tested with visual studio 2008 crystal basic on IIS running on 2003 server.

I figured it out after reading http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/thread/e2dc93b3-e594-4ae6-ba92-9440ccc7f6be .

0


source






More articles:


All Articles