Hi All,
Hoping you can help...
I've installed Logicity v1.8.0009 onto Windows Server 2012 R2 and upon opening Crystal Report within Logicity the following error message is shown and wont allow me to progress any further.
If you require additional information then please let me know.
Thanks!

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.2000.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.2000.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.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.8762 (QFE.050727-8700)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

---

Logicity Desktop
Assembly Version: 1.8.9.0
Win32 Version: 1.8.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/SaberLogic/Logicity/Logicity%20Desktop.exe

---

Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.8007 (FX35W81RTMGDR.050727-8000)
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.8770 (QFE.050727-8700)
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.8015 (FX35W81RTMGDR.050727-8000)
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.8019 (FX35W81RTMGDR.050727-8000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

---

Logicity.Common
Assembly Version: 1.8.9.0
Win32 Version: 1.8.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/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.

Verify the SAP Crystal Reports runtime engine for .NET Framework (32-bit) has been installed.

(Note you may see another acceptable version 13.0.16.1954 which is installed with Logicity)

I am receiving this same error. Could the error be due to the version of the runtime? An update to our ERP software required us to install version 13.0.22.2668 of the SAP Crystal Reports runtime engine for .NET Framework and now Logicity (free version) no longer works. If I uninstall version 22 and reinstall version 9, Logicity works again.
My understanding is that SAP will be releasing version 23 of the runtime in May. Hopefully this version of the runtime will correct a printing issue we have been having in our ERP but will this version break Logicity as well?

Please try downloading the latest version of Logicity (version 1.9.0001 at the time of this post):

www.logicitysuite.com/resources/downloads.html

Verifying compatibility with SAP Crystal Reports version 13.0.23 will be dependent on SAP's release.
A newer version of Logicity will then be released if needed.

That version worked great! Thank you so much!!!

I get this same exception after just installing version 1.9.0003 on MS Windows Server 2016 after SAP CR 2013 SP 6 and SAP Crystal Reports runtime engine for .NET Framework (32-bit) also installed.
Dan
Connex Software (CNX)

Dan,

We'd recommend uninstalling that older runtime and then reinstalling Logicity 1.9 in order to get the latest runtime installed automatically.

Hope this helps,
Adam

Following your instruction to uninstall the Crystal runtime and re-install LogiCity, just broke Crystal Reports 2013. It no longer starts from its short-cut. If I go to the .exe and open it I get the message in the attached image.

Please try downloading and installing the CR Runtime version 13.0.14 via the following link:

downloads.businessobjects.com/akdlm/crne...me_32bit_13_0_14.msi

This should restore the version that appears to be required by Crystal Reports 2013.

Please note if having the two versions of the CR Runtime on the same PC causes any issues with either Crystal Reports or Logicity, you will likely need to have these applications installed on different PCs.

The other thing I'll add here, if you are downgrading the runtime to 13.0.14 you will probably have better luck sticking with Logicity 1.8. The newer runtimes for Crystal Reports are incompatible with older products.