TOPIC: v1.9 Pro - Purchased and not working

v1.9 Pro - Purchased and not working 27 Apr 2018 00:59 #2653

  • piqpst
  • piqpst's Avatar
  • Offline
I purchased and installed Logicity Pro v1.9. Upon running a report it says:
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

I know you say to uninstall Crystal RunTime and reinstall, however, I already have Crystal RunTime 13.0.8.1216 which is used by another program so I can not uninstall it. How do I get my paid for Logicity to work? Is there some other way besides the method of uninstalling CRuntime?
The administrator has disabled public write access.

v1.9 Pro - Purchased and not working 27 Apr 2018 12:47 #2654

  • KCrane
  • KCrane's Avatar
  • Offline
Can you confirm the other application will not work with the newer Crystal Reports Runtime used by Logicity? If the application should not work with the newer runtime, you can then re-install the 13.0.8 runtime via the following link:

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

Another option may be to try an earlier version of Logicity:

www.logicitysuite.com/resources/downloads.html
The administrator has disabled public write access.
The following user(s) said Thank You: piqpst

v1.9 Pro - Purchased and not working 27 Apr 2018 13:39 #2655

  • piqpst
  • piqpst's Avatar
  • Offline
Thank you. Going down one version works perfectly.
The administrator has disabled public write access.

v1.9 Pro - Purchased and not working 01 May 2018 19:12 #2663

  • vic23gon
  • vic23gon's Avatar
  • Offline
I had the same issue and attempted going down one version to v1.8. It works fine under the free version but my serial number won't activate my PRO version. I paid for the PRO version and it's not working. Any suggestions?
The administrator has disabled public write access.

v1.9 Pro - Purchased and not working 09 May 2018 17:20 #2670

  • grant@delecuona.com
  • grant@delecuona.com's Avatar
  • Offline
Same issue. I have not tried to go down a version - yet as have just purchase the licence and seeing the the previous post am hoping a fix will be forthcoming...

I did a full install, 'As Administrator'; including the Crystal Reports Runtime.
All elements seem to install OK and run OK, but I cannot successfully open an .rpt or run an .rrd

I have uninstalled and reinstalled and repeated the process with a fresh download.
The environment is…
• Win Server 2012 R2 64Bit
• MSSQL Server 2014
• SAP Crystal Reports for SAP Business One
• .Net Frameworks v2 to v4 – including v3.5.30729.4926

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.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.9.1.0
Win32 Version: 1.9.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.9.1.0
Win32 Version: 1.9.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.
The administrator has disabled public write access.

v1.9 Pro - Purchased and not working 10 May 2018 13:46 #2671

  • aellis
  • aellis's Avatar
  • Offline
Sorry for the late reply here - if you want to e-mail This email address is being protected from spambots. You need JavaScript enabled to view it. with your company name and keycode we will get you a key that will work with version 1.8.
The administrator has disabled public write access.

v1.9 Pro - Purchased and not working 10 May 2018 13:53 #2672

  • aellis
  • aellis's Avatar
  • Offline
Grant - did you try uninstalling the prior Crystal Reports Runtime before installing 1.9? The prior Crystal Reports Runtime does not seem to be upgrading automatically as it did with the previous releases (we don't control that - that is SAP). The 'Could not load file or assembly' is referring to Logicity looking for the latest version of that runtime. The earlier poster could not upgrade to the latest runtime due to requirements from other software using the older runtime so he is stuck at 1.8.
The administrator has disabled public write access.

v1.9 Pro - Purchased and not working 10 May 2018 16:26 #2673

  • grant@delecuona.com
  • grant@delecuona.com's Avatar
  • Offline
This has been confirmed as a SAP Crystal Reports Runtime compatibility issue. We were running V13.0.16.1954
Recommended solution - uninstall Logicity Pro
Uninstall SAP Crystal Reports Runtime
Reinstall Logicity Pro v1.9 with the Crystal Reports Runtime option enabled.

Since we are about to upgrade to SAP Crystal Reports Runtime V13.0.22 later this month, I elected to avoid the risk of disenfranchising the other SAP users on this server and reinstalled Logicity Free v1.8 - this is working. The v1.9 Pro key does not work with this, but Saberlogic have offered a key for v1.8.

I am advised that v1.9 should have no problems with SAP Crystal Reports Runtime V13.0.22. I will endeavour to remember to update this when I do that update.

Many thanks to the SaberLogic team - professional as ever.
The administrator has disabled public write access.

v1.9 Pro - Purchased and not working 06 Jun 2018 09:49 #2694

  • grant@delecuona.com
  • grant@delecuona.com's Avatar
  • Offline
Completed the Upgrade to SAP B1 and SAP Crystal (v14), reverted to Logicity 1.9 - Pro, Registered it - ALL WORKS BEAUTIFULLY.
Thanks for all your prompt co-operation and help
The administrator has disabled public write access.