Crystal Reports not loading when published on SQL Server 2005.

[VBMan10]

Hi everyone,

I am have created a web application with crystal reports. The crystal reports were created inside Visual Studio 2005. The reports load fine on my local machine, but when published to the server, they do not pull up.

I get this error:

Server Error in '/' Application.
________________________________________
Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Source Error:

Line 18: Height="1055px" ReportSourceID="TechncianCallsReportSource" ReuseParameterValuesOnRefresh="True"
Line 19: Width="789px" DisplayGroupTree="False" EnableDatabaseLogonPrompt="False" />
Line 20: <CR:CrystalReportSource ID="TechncianCallsReportSource" runat="server">
Line 21: <Report FileName="TechnicianCalls.rpt"></Report>
Line 22: </CR:CrystalReportSource>

Source File: E:\Marriane\Call Issue Tracking\Account\TechnicianCalls.aspx Line: 20

Assembly Load Trace: The following information can be helpful to determine why the assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.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].

Stack Trace:

[FileLoadException: Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
CrystalDecisions.CrystalReports.Engine.ReportDocument..cctor() +0

[TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception.]
CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor() +0
CrystalDecisions.ReportSource.CachedReport.get_ReportDocument() +39
CrystalDecisions.Web.CrystalReportSource.set_Report(Report value) +219
ASP.account_techniciancalls_aspx.__BuildControlTechncianCallsReportSource() in E:\Marriane\Call Issue Tracking\Account\TechnicianCalls.aspx:20
ASP.account_techniciancalls_aspx.__BuildControlform1() in E:\Marriane\Call Issue Tracking\Account\TechnicianCalls.aspx:15
ASP.account_techniciancalls_aspx.__BuildControlTree(account_techniciancalls_aspx __ctrl) in E:\Marriane\Call Issue Tracking\Account\TechnicianCalls.aspx:1
ASP.account_techniciancalls_aspx.FrameworkInitialize() +46
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +56
System.Web.UI.Page.ProcessRequest() +80
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.account_techniciancalls_aspx.ProcessRequest(HttpContext context) +37
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

________________________________________
Version Information: Microsoft .NET Framework Version:2.0

 

[hilfy]

It looks like the Crystal Merge Modules have not been loaded on the server, so the assemblies required to display Crystal reports are not there. You'll need to either download the Merge Modules or create an installer project in VS to install them.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.