I have crystal report 2010 installed with VS 2010.i have created a crystal report which is works fine in the localhost but the issue is once i publish my website to IIS the
I finally got it as explained below, in old and fixed version, because on my development server I need "~" which is not the case on development server, other than that I followed the link precisely. old one :
fixed one:
One, unbelievably simple reason this also occurs is that the server isn't configured correctly, meaning, static content is not enabled in Common HTTP features under server roles/Windows features.
Setting
<compilation debug="false">
in web.config worked for me.
The best answer for this question is here!
http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/thread/ef56f72b-7ede-47d8-ba9e-9e63b9ac0203
Copy C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\crystalreportviewers13 (you'll got it when you install -CRforVS_redist_install_32bit_13_0.exe) To your project such as (ProjectName/crystalreportviewers13)
copy this below to your web.config
3.1
<configSections>
<sectionGroup name="businessObjects">
<sectionGroup name="crystalReports">
<section name="rptBuildProvider" type="CrystalDecisions.Shared.RptBuildProviderHandler, CrystalDecisions.Shared, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, Custom=null" />
<section name="crystalReportViewer" type="System.Configuration.NameValueSectionHandler" />
</sectionGroup>
</sectionGroup>
</configSections>
3.2
<businessObjects>
<crystalReports>
<rptBuildProvider>
<add embedRptInResource="true" />
</rptBuildProvider>
<crystalReportViewer>
<add key="ResourceUri" value="/crystalreportviewers13" />
</crystalReportViewer>
</crystalReports>
</businessObjects>
3.4 Publish your web application with FTP Mode to your any folder,and copy this publish to your web server then TEST it!
I know it was asked some years ago. But this method worked for me. This is for people that someday will encounter this kind of problem.
I created my application in a 32 bit environment and changed to 64 bit. I deployed my web application in IIS web server (current 64 bit) and created my own application pool (having the "manage pipeline mode" into integrated).
Then when this report issue happened, i followed those instructions from the link. I changed the "manage pipeline mode" into classic and my application worked.
It can simply solve the problem if you copy your aspnet_client folder from C:\inetpub\wwwroot to the folder of your newly created website. For example if your website name is TestWebsite then place aspnet_client folder inside the TestWebsite folder. You do not need to make configuration changes in web.config