TOPIC: Unhandled exception

Unhandled exception 28 Jan 2022 10:57 #14294

  • Liam4
  • Liam4's Avatar
  • Offline
Hi,
we have used Logicity for several years and it has worked flawlessly. We are currently planning to upgrade our pharmacy stock control system and i am now getting an unhandled exception when running a report on any machine with the new version of the stock control software. the new version uses IRIS cache from intersystems. I have tried it on a machine with both versions installed and attempting to run logicity for a report which is looking at the original cache gives the same error.

below are the details from the 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.FileNotFoundException: Could not load file or assembly 'CrystalDecisions.CrystalReports.Engine, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
File name: 'CrystalDecisions.CrystalReports.Engine, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'
at Logicity_Desktop.ViewerForm..ctor(Int32 recordNumber, Array actList, Array parmList, Array setList, Array authList)
at Logicity_Desktop.ProgressForm.ProgressForm_Load(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.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: 4.0.0.0
Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
Logicity Desktop
Assembly Version: 1.9.4.0
Win32 Version: 1.9.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/SaberLogic/Logicity/Logicity%20Desktop.exe
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4320.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Logicity.Common
Assembly Version: 1.9.4.0
Win32 Version: 1.9.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/SaberLogic/Logicity/Logicity.Common.DLL
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.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.


any help with this would be much appreciated. I have crystal 2016 installed on this device and it gives the same error.

thanks
Liam
The administrator has disabled public write access.

Unhandled exception 28 Jan 2022 13:02 #14295

  • KCrane
  • KCrane's Avatar
  • Offline
Hi Liam - Recently on another topic - www.logicitysuite.com/forum/technical/13...on-has-occurred.html - it was realized Crystal Reports 2016 conflicts with the SAP Crystal Report Runtime installed and used by Logicity. Currently one of the applications would need to be installed on another machine.
The administrator has disabled public write access.

Unhandled exception 28 Jan 2022 13:43 #14297

  • Liam4
  • Liam4's Avatar
  • Offline
hi, we have ran it on a machine which doesn't have crystal installed and it still errors. We are using windows10 fresh installs and it only stops working when we install the new client and leave the old client also installed. I plan to test it on a machine without the old client and crystal next week.
Could it be the new client installs a newer version of the crystal runtime which logicity can't use?
The administrator has disabled public write access.

Unhandled exception 28 Jan 2022 14:39 #14298

  • KCrane
  • KCrane's Avatar
  • Offline
Hi Liam - Unfortunately yes, we do see this occasionally where an application will install Crystal Report components that conflict with Logicity.
The administrator has disabled public write access.