TOPIC: .Net unhandled exception in VMWare environment

.Net unhandled exception in VMWare environment 08 Apr 2010 01:34 #595

  • dwb@connexsoftware.com
  • dwb@connexsoftware.com's Avatar
I've used Logicity successfully in Windows Server 2003 environments without issue for 2 years. Now in a new installation (downloaded today) I get the .Net error 'Unhandled exception has occurred in your application. Could not load file or assembly...'. I installed .Net 3.5 and then SP1. Still have the issue.

THIS IS UNDER VMWARE!

I've un-installed and re-installed Logicity

Any suggestions???
The administrator has disabled public write access.

Re:.Net unhandled exception in VMWare environment 08 Apr 2010 12:34 #596

  • aellis
  • aellis's Avatar
If you go to Add / Remove Programs, does the Crystal Reports Runtime show up as being installed?
The administrator has disabled public write access.

Re:.Net unhandled exception in VMWare environment 08 Apr 2010 15:39 #597

  • dwb@connexsoftware.com
  • dwb@connexsoftware.com's Avatar
Yes it does show there 2008 version - about 200 MB worth.
Last Edit: 08 Apr 2010 15:39 by dwb@connexsoftware.com.
The administrator has disabled public write access.

Re:.Net unhandled exception in VMWare environment 08 Apr 2010 16:01 #598

  • aellis
  • aellis's Avatar
Can you also try installing .Net 2.0? I don't remember for certain, but parts of the runtime may require that. If that doesn't do it, can you post the full details on the error (press the details button and copy and paste it all here).
The administrator has disabled public write access.

Re:.Net unhandled exception in VMWare environment 08 Apr 2010 16:42 #599

  • dwb@connexsoftware.com
  • dwb@connexsoftware.com's Avatar
Yes, I tried .Net 2 before I installed .Net 3.5.

Thank you for your help. Here are the details:

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

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'CrystalDecisions.CrystalReports.Engine, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
File name: 'CrystalDecisions.CrystalReports.Engine, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'
at Logicity_Desktop.ViewerForm..ctor(Int32 recordNumber, Array actList, Array parmList, Array setList)
at Logicity_Desktop.ProgressForm.ProgressForm_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(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.WmShowWindow(Message& m)
at System.Windows.Forms.Form.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
Logicity Desktop
Assembly Version: 1.6.3594.19372
Win32 Version:
CodeBase: file:///C:/Program%20Files/SaberLogic/Logicity/Logicity%20Desktop.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
Logicity.Common
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///C:/Program%20Files/SaberLogic/Logicity/Logicity.Common.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.
The administrator has disabled public write access.

Re:.Net unhandled exception in VMWare environment 08 Apr 2010 18:01 #600

  • aellis
  • aellis's Avatar
Ok, so that definitely has something to do with the Crystal Reports Runtime. Can you try this - uninstall Logicity *and* the Crystal Reports Runtime from Add / Remove programs. Then re-install Logicity and make sure to check the option for runtime during installation.
The administrator has disabled public write access.