How do I setup Crystal Reports 2008 on a remote webserver running Server 2008?

How do I setup Crystal Reports 2008 on a remote webserver running Server 2008 to deploy an asp.net web page with an embedded Crystal Report created with MS Visual Studio 2005 Pro?

Trying to implement the Crystal Report Viewer in our existing web application, have installed crystal reports 2008 and registered, not sure about the merge modules the business objects website has lots of dead links to those downloads.

When I copy over the web.config file and try to load any of the web applications pages I get an Error: 500 in the web browser.

I have changed the version to ver. 12 in the web.config code also, there has to be an easier way to do this!
LVL 1
prlitAsked:
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:
Did you use the CR2008 dlls when you built the application?

mlmcc
0
prlitAuthor Commented:
I was not sure where to find these dlls or how to install the merge modules, when I build the website locally (CR for VS 2005) on the dev machine they work perfectly.

When deployed to our web server (CR 2008 Installed) they do not, nor will the rest of our application after the web.config file references crystal report assemblies.

I downloaded the merge modules but cant find the documentation on how to install
0
mlmccCommented:
What includes did you use in the application?

mlmcc
0
CompTIA Network+

Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.

prlitAuthor Commented:
Here is my web.config file, all assemblies referenced by the application are here, ASP.NET/VB web pages import name spaces but I believe this is what you are referring to as includes.

The version of CR is 2008 Version=12.0.0.683 on the server and the local dev machine for VS 2005 version is 10.2.3600.0, so I had to modify the web.config file to the newer version:

<?xml version="1.0"?><!--
    Note: As an alternative to hand editing this file you can use the
    web admin tool to configure settings for your application. Use
    the Website->Asp.Net Configuration option in Visual Studio.
    A full list of settings and comments can be found in
    machine.config.comments usually located in
    \Windows\Microsoft.Net\Framework\v2.x\Config
--><configuration>
 <connectionStrings/>
      <system.web>
            <!--
            Set compilation debug="true" to insert debugging
            symbols into the compiled page. Because this
            affects performance, set this value to true only
            during development.

            Visual Basic options:
            Set strict="true" to disallow all data type conversions
            where data loss can occur.
            Set explicit="true" to force declaration of all variables.
        -->
            <compilation debug="true" strict="false" explicit="true">
                  <assemblies>
                        <add assembly="CrystalDecisions.CrystalReports.Engine, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
                        <add assembly="CrystalDecisions.ReportSource, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
                        <add assembly="CrystalDecisions.Shared, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
                        <add assembly="CrystalDecisions.Web, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
                        <add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
                        <add assembly="CrystalDecisions.Enterprise.Framework, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
                        <add assembly="CrystalDecisions.Enterprise.InfoStore, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></assemblies></compilation>
            <customErrors mode="Off"/>
            <pages>
                  <namespaces>
                        <clear/>
                        <add namespace="System"/>
                        <add namespace="System.Collections"/>
                        <add namespace="System.Collections.Specialized"/>
                        <add namespace="System.Configuration"/>
                        <add namespace="System.Text"/>
                        <add namespace="System.Text.RegularExpressions"/>
                        <add namespace="System.Web"/>
                        <add namespace="System.Web.Caching"/>
                        <add namespace="System.Web.SessionState"/>
                        <add namespace="System.Web.Security"/>
                        <add namespace="System.Web.Profile"/>
                        <add namespace="System.Web.UI"/>
                        <add namespace="System.Web.UI.WebControls"/>
                        <add namespace="System.Web.UI.WebControls.WebParts"/>
                        <add namespace="System.Web.UI.HtmlControls"/>
                  </namespaces>
            </pages>
            <!--
            The <authentication> section enables configuration
            of the security authentication mode used by
            ASP.NET to identify an incoming user.
        -->
            <authentication mode="Windows"/>
            <!--
            The <customErrors> section enables configuration
            of what to do if/when an unhandled error occurs
            during the execution of a request. Specifically,
            it enables developers to configure html error pages
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
        -->
      <httpHandlers><add verb="GET" path="CrystalImageHandler.aspx" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=12.0.0.683, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></httpHandlers></system.web>
       <location allowOverride="true" inheritInChildApplications="true">
           <appSettings>
               <add key="CrystalImageCleaner-AutoStart" value="true" />
               <add key="CrystalImageCleaner-Sleep" value="60000" />
               <add key="CrystalImageCleaner-Age" value="120000" />
           </appSettings>
       </location>
</configuration>
0
mlmccCommented:
I think the problem is the application still wants to use the 10.2 dlls.

You need to install CR2008 on the DEV machine so you can include or import the correct dlls.

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
prlitAuthor Commented:
Worked Thank You!

If I get past this last dll error message I will have it!

Parser Error Message: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=8.0.50727.1843, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I can find these dlls in the C:\Windows\Assembly folder and they are the same version as the code points to, I also tried placing them in the bin folder of the apps directory.

These are the dlls that belong to Report Viewer:

Microsoft.ReportViewer.WebForms (Throws the error) - Provides the ReportViewer control for ASP.NET pages.

Microsoft.ReportViewer.Common - Provides core reporting functionality that is common to the ReportViewer Windows forms control and Web server control.
 
Microsoft.ReportViewer.ProcessingObjectModel - Exposes the report object model so that it can be accessed programmatically at run time from expressions in the report definition.
 
Microsoft.ReportViewer.WinForms - Provides the ReportViewer control for Windows applications.

Thanks for the CR tip worked nicely!
0
prlitAuthor Commented:
Ran ReportViewer.exe on server and changed version in code and that last error disappeared.

Installing CR 2008 on the dev machine is what solved the major issue.

Worked like a charm! Thank You
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
DB Reporting Tools

From novice to tech pro — start learning today.