CrystalDecisions.CrystalReports.Engine.ReportDocument

CrystalDecisions.CrystalReports.Engine.ReportDocument

• vaishali.mspp

  I think this is probably the best place to start looking: it sounds like there is an assembly missing from your machine. You could also try a repair of the Crystal Reports install, or even uninstalling it and then re-installing it.

  The following article from Business Objects may help: http://support.businessobjects.com/library/kbase/articles/c2016508.asp

  
  
  

• toby1980

  Having the same problem as well, tried to remove and replace setup application dependant files associated with Crystal Reports:

  CrystalDecisions.CrystalReports.Engine.dll

  CrystalDecisions.ReportSource.dll

  CrystalDecisions.Shared.dll

  CrystalDecisions.Web.dll

  CrystalDecisions.Windows.Forms.dll

  These files were not added as dependant files even though they have been set in the references portion of the application. It was necessary to add them manually. The application, when running, gets a little bit farther, but as soon as you call Crystal Reports assembly in application, hard exception and the application closes, with a send report request on death.

  Here is the exception error message that is dropped at time of death:

  See the end of this message for details on invoking
  just-in-time (JIT) debugging instead of this dialog box.

  ************** Exception Text **************
  System.TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
  File name: 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'
  at CrystalDecisions.CrystalReports.Engine.ReportDocument..cctor()

  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].

  --- End of inner exception stack trace ---
  at CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor()
  at CrystalDecisions.CrystalReports.Engine.ReportClass..ctor()
  at LabelPrintingSystem.UI.Certification..ctor()
  at LabelPrintingSystem.UI.LabelPrintForm.PrepareReport()
  at LabelPrintingSystem.UI.LabelPrintForm.toolStripButton1_Click(Object sender, EventArgs e)
  at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
  at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
  at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
  at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
  at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
  at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
  at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
  at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
  at System.Windows.Forms.Control.WndProc(Message& m)
  at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
  at System.Windows.Forms.ToolStrip.WndProc(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

  
  ************** Loaded Assemblies **************
  mscorlib
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
  ----------------------------------------
  LabelPrintingSystem
  Assembly Version: 1.0.0.0
  Win32 Version: 1.0.0.0
  CodeBase: file:///C:/Program%20Files/Default%20Company%20Name/Tannehill%20Printing%20System/LabelPrintingSystem.exe
  ----------------------------------------
  System.Windows.Forms
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
  ----------------------------------------
  System
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
  ----------------------------------------
  System.Drawing
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
  ----------------------------------------
  System.Configuration
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
  ----------------------------------------
  System.Xml
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
  ----------------------------------------
  System.Data
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
  ----------------------------------------
  PickDB
  Assembly Version: 1.5.0.25680
  Win32 Version: 1.5.0.25680
  CodeBase: file:///C:/Program%20Files/Default%20Company%20Name/Tannehill%20Printing%20System/PickDB.DLL
  ----------------------------------------
  System.Web
  Assembly Version: 2.0.0.0
  Win32 Version: 2.0.50727.42 (RTM.050727-4200)
  CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
  ----------------------------------------
  CrystalDecisions.CrystalReports.Engine
  Assembly Version: 10.2.3600.0
  Win32 Version: 10.2.51014.0
  CodeBase: file:///C:/Program%20Files/Default%20Company%20Name/Tannehill%20Printing%20System/CrystalDecisions.CrystalReports.Engine.DLL
  ----------------------------------------
  CrystalDecisions.Shared
  Assembly Version: 10.2.3600.0
  Win32 Version: 10.2.51014.0
  CodeBase: file:///C:/Program%20Files/Default%20Company%20Name/Tannehill%20Printing%20System/CrystalDecisions.Shared.DLL
  ----------------------------------------

  ************** JIT Debugging **************
  To enable just-in-time (JIT) debugging, the .config file for this
  application or computer (machine.config) must have the
  jitDebugging value set in the system.windows.forms section.
  The application must also be compiled with debugging
  enabled.

  For example:

  <configuration>
  <system.windows.forms jitDebugging="true" />
  </configuration>

  When JIT debugging is enabled, any unhandled exception
  will be sent to the JIT debugger registered on the computer
  rather than be handled by this dialog box.

  
  Hope this helps someone figure out what the problem may be...

  DLS

  
  
  

• Db88Master

  No, I wouldn't expect your scenario to work, Dodge. You are not supposed to package Crystal Reports assemblies with your ClickOnce application. That work that was done to publish each referenced assembly It would have been better to make it impossible. This is because Business Objects (and presumably other vendors) doesn't want people to package and redistribute individual assemblies. First of all, package vendors have the most knowledge about how to correctly install their assemblies. Second, redistributing individual assemblies creates a servicing nightmare.

  Dodge, you need to make sure that Crystal Reports is installed on the end-users machine. This can be done via the bootstrapper. See the Prerequistes dialog off of the publish page.

  
  
  

• Hans Yadav

  To clarify: the crystal report is generated from a web service, right
  

• codecamel

  Same problem occurs with me.

  Why Microsoft is not giving a comprehensive deployment solution for all the development tools it had developed.

  Development tools with Microsoft are one of the best available in the market but the only drawback with it is you cannot deploy your developed application to any machine saying it was 100 % successfull.

  That the major reason why most of the developer leaving Microsoft development tools and going for others as if your application can't be successfully deployed on a machine all your efforts are useless.

  I hope if this continues Microsoft will find itself out of the software development market in immideate future.

  
  
  

• jdiazbejJuan

  Could you provide more details on your situation Is this a web app Does it work in one environment but not another
  

• metaza

  Nope.

  The Crystal report is generated by Client application on client computer. Service is .NET remoting and is only communicating with Oracle - nothing more.

  
  
  

• Alin Constantin

  Do you know where in your code you are using the CrystalDecisions.ReportAppServer.CommLayer assembly

  Did you install CrystalReports for .NET Framework 2.0 on the test machine

  
  

• troff

  Hello!

  Sure.

  It's a windows forms application in two parts. One part is service, which is running on the server, the second part is a client application. The client application reads data from Oracle base, makes XML file, which contains data for the Crystal Report.

  It's all running ok on my computer, but when I publish my client application by Click once on my test computer, the error pops up. Click once also installs Framework 2.0. and Click Once if there is none on computer.

  Thank you. :)

  
  
  

• peachy4

  Kasim Husaini wrote:

  Same problem occurs with me. Why Microsoft is not giving a comprehensive deployment solution for all the development tools it had developed. Development tools with Microsoft are one of the best available in the market but the only drawback with it is you cannot deploy your developed application to any machine saying it was 100 % successfull. That the major reason why most of the developer leaving Microsoft development tools and going for others as if your application can't be successfully deployed on a machine all your efforts are useless. I hope if this continues Microsoft will find itself out of the software development market in immideate future. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeLoadException: Method get_UID in type CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper from assembly CrystalDecisions.CrystalReports.Engine, Version=10.0.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304 does not have an implementation. at CrystalDecisions.CrystalReports.Engine.ReportDocument.u() at CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor() at CrystalDecisions.CrystalReports.Engine.ReportClass..ctor() at rptPaymentStatusReport..ctor() in C:\Visual .Net Projects\Ball In Court\Reports\rptPaymentStatusReport1.vb:line 25 --- End of inner exception stack trace --- at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at DCAEP.General.LoadObject(Form sender, DynamicClass dclObject) in C:\Visual .Net Projects\DCAEP Common Components\DCAEPCommonComponent\General.vb:line 532 at DCAEP.MainMenu.mnuPaymentStatusReport_Click(Object sender, EventArgs e) in C:\Visual .Net Projects\Ball In Court\ClassFiles\MainMenu.vb:line 1104 at System.Windows.Forms.MenuItem.OnClick(EventArgs e) at System.Windows.Forms.MenuItemData.Execute() at System.Windows.Forms.Command.Invoke() at System.Windows.Forms.Control.WmCommand(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll ---------------------------------------- BallInCourt Assembly Version: 2.0.2282.17501 Win32 Version: 2.0.2282.17501 CodeBase: file:///C:/Program%20Files/DCAEP/Projects%2020060402/BallInCourt.exe ---------------------------------------- System.Windows.Forms Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll ---------------------------------------- System Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll ---------------------------------------- System.Drawing Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll ---------------------------------------- DCAEPCommonComponent Assembly Version: 1.0.2282.17497 Win32 Version: 1.0.2282.17497 CodeBase: file:///C:/Program%20Files/DCAEP/Projects%2020060402/DCAEPCommonComponent.DLL ---------------------------------------- System.Data Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll ---------------------------------------- Microsoft.VisualBasic Assembly Version: 7.0.5000.0 Win32 Version: 7.10.6001.4 CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll ---------------------------------------- System.Xml Assembly Version: 1.0.5000.0 Win32 Version: 1.1.4322.2032 CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll ---------------------------------------- CrystalDecisions.CrystalReports.Engine Assembly Version: 10.0.3300.0 Win32 Version: 10.0.9500.18 CodeBase: file:///C:/Program%20Files/DCAEP/Projects%2020060402/CrystalDecisions.CrystalReports.Engine.DLL ---------------------------------------- CrystalDecisions.Shared Assembly Version: 10.0.3300.0 Win32 Version: 10.0.9500.16 CodeBase: file:///C:/Program%20Files/DCAEP/Projects%2020060402/CrystalDecisions.Shared.DLL ---------------------------------------- CrystalDecisions.ReportAppServer.CommLayer Assembly Version: 10.0.3300.0 Win32 Version: 10.0.9500.0 CodeBase: file:///C:/Program%20Files/DCAEP/Projects%2020060402/CrystalDecisions.ReportAppServer.CommLayer.DLL ---------------------------------------- CrystalDecisions.ReportAppServer.ClientDoc Assembly Version: 10.0.3300.0 Win32 Version: 10.0.9500.0 CodeBase: file:///C:/Program%20Files/DCAEP/Projects%2020060402/CrystalDecisions.ReportAppServer.ClientDoc.DLL ---------------------------------------- CrystalDecisions.ReportAppServer.DataSetConversion Assembly Version: 10.0.3300.0 Win32 Version: 10.0.9500.10 CodeBase: file:///C:/Program%20Files/DCAEP/Projects%2020060402/CrystalDecisions.ReportAppServer.DataSetConversion.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just in time (JIT) debugging, the config file for this application or machine (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the machine rather than being handled by this dialog.

  
  
  

• zeffy

  I have the same problem.

  Any Help

  
  

• eatbingo

  I use Crystal Reports XI myself, so there may be a difference with Crystal Reports in Visual Studio in terms of assemblies, though I'm not so sure. I recently deployed a WinForm App to a user with no Crystal Reports DLL files registered on the machine, and installing Crystal Reports for .NET Framework 2.0 was sufficient.

  Go to c:\windows\assembly on the test machine and check to see if you can find CrystalDecisions.ReportAppServer.CommLayer there. I would check both the test computer that doesn't work and the one that does. Based on your error message, my hunch is that you are missing it on the one that doesn't work but have it on the one that does.

  
  

• Monkey Boy

  Hello!

  Have same problem. Did anyone find solution

  Thank you.

  
  
  

• Moura

  Application is installed on my test computer by ClickOnce and Crystal report is marked as prerequisite. Also if I check installed programs in Add and Remove Programs I can se "Crystal Reports for .NET Framework 2.0. x86"

  I don't know where in my code I use assembly your asking about. I never worked with crystal report before. I just made crystal report in Visual Studio using wizard, I made a form with a Crystal report viewer nad displayed the report.

  The funny thing is, that the reports are working on another test machine. I don't know what is the difference between them...

  
  
  
• CrystalDecisions.CrystalReports.Engine.ReportDocument