none
Fault opening reports within vb.net RRS feed

  • Question

  • Hello,

    I've created a little program but I'm having some problems opening reports within the program. The program is build on VB.NET (Visual Studio 2008), I create an install file on Visual Studio 2008. The build succeeded! When I install the program on a different computer I've having the following error:

    See the end of this message for details on invoking 
    
    just-in-time (JIT) debugging instead of this dialog box.
    
    
    
    ************** Exception Text **************
    
    System.IO.FileLoadException: Could not load file or assembly 'CrystalDecisions.Windows.Forms, Version=10.5.3700.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)
    
    File name: 'CrystalDecisions.Windows.Forms, Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'
    
       at Verkiezingen.fcls_RptDeelnProeven.InitializeComponent()
    
       at Verkiezingen.fcls_RptDeelnProeven..ctor()
    
       at Verkiezingen.fcls_HoofdScherm.mnu_rpt_deelnemers_proeven_Click(Object sender, EventArgs e)
    
       at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
    
       at System.Windows.Forms.ToolStripMenuItem.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.ToolStripDropDown.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.ToolStripDropDown.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)
    
    
    
    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].
    
    
    
    
    
    
    
    ************** Loaded Assemblies **************
    
    mscorlib
    
        Assembly Version: 2.0.0.0
    
        Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    
        CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    
    ----------------------------------------
    
    Verkiezingen
    
        Assembly Version: 1.0.0.0
    
        Win32 Version: 1.0.0.0
    
        CodeBase: file:///C:/Program%20Files/Raad%20der%20Bommels/Raad%20der%20Bommels/Verkiezingen.exe
    
    ----------------------------------------
    
    Microsoft.VisualBasic
    
        Assembly Version: 8.0.0.0
    
        Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
    
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    
    ----------------------------------------
    
    System
    
        Assembly Version: 2.0.0.0
    
        Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    
    ----------------------------------------
    
    System.Windows.Forms
    
        Assembly Version: 2.0.0.0
    
        Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    
    ----------------------------------------
    
    System.Drawing
    
        Assembly Version: 2.0.0.0
    
        Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    
    ----------------------------------------
    
    System.Runtime.Remoting
    
        Assembly Version: 2.0.0.0
    
        Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    
        CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.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.
    
    
    
    
     I include some DLL file into the project build such as:
    * CrystalDecisions.Enterprise.desktop.report.dll
    * CrystalDecisions.Enterprise.viewing.reportsource.dll
    * CrystalDecisions.Reportappserver.Prompting.dll
    * CrystalDecisions.CrystalReports.Design.dll
    * CrystalDecisions.CrystalReports.Engine.dll
    * CrystalDecisions.ReportAppServer.CommLayer.dll
    * CrystalDecisions.ReportAppServer.DataSetConversion.dll
    * CrystalDecisions.ReportSource.dll
    * CrystalDecisions.Shared.dll
    * CrystalDecisions.Web.dll
    * CrystalDecisions.Windows.Forms.dll

    Thats all what I included into the project.

    Do I need for???????? Or something else??????

    Thank you very much

    Gregory



    Tuesday, May 26, 2009 8:07 AM

Answers

All replies

  • Greg,
    I never faced this problem. Just by looking at the error, the system is trying to load Crystal Decisions.Windows. Forms which is version 10.5. Please check the version of CrystalDecisions.Windows.Forms.dll on the PC where it is working fine and try to copy the same dll to the PC which is giving errors. I'm pretty sure, it is version related. Please check and update. I'm curious too.

    Thanks

    Chandra

     

    Tuesday, May 26, 2009 1:15 PM
  • Thx for the reply,

    I'm running the program within Visual studio by pressing on the play button, then everything works fine!!
    Where can I find the version of the specified dll in the debug mode????

    On the setup.exe (it is build from visual studio) it doesn't work?

    Tuesday, May 26, 2009 2:12 PM
  • Tantie,
    I think you are missing Crystal Reports as a pre-requisite for your build. Please put "Crystal Reports for .Net 2.0" as a pre-requisite and then create a setup.exe. This should first install Crystal Reports on the client PC before installing your windows application. I think this link below may be of help.
    http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/thread/c9df7a18-513e-4c26-8b65-9578d3bddef0
    • Marked as answer by tantie Tuesday, May 26, 2009 9:08 PM
    Tuesday, May 26, 2009 2:23 PM
  • Chandrasekhar is probably correct, you need to pre-req Crystal reports as part of your setup.

    If that doesn't work, you will probably get better help on the Crystal forum. This is actually the Microsoft ReportViewer forum. The Crystal forum is here:

    http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/threads

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by tantie Tuesday, May 26, 2009 9:08 PM
    Tuesday, May 26, 2009 5:40 PM
  • Problem solved,

    the solution was the pre-req off crystal reports.

    For your information: in Visual Studio 2008 the pre-req is called:

    "Crystal Reports Basic for Visual Studio 2008".

    Thank you for the helpful replies!!!!!

    Tuesday, May 26, 2009 9:13 PM