When trying to execute the free Logicity Desktop on a Windows Vista 64 bit machine, I am receiving the following error. Could anyone shed some light on this for me? I've been searching forums for hours...

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception. ---> CrystalDecisions.CrystalReports.Engine.LoadSaveReportException: An error has occurred while attempting to load the Crystal Reports runtime. Either the Crystal Reports registry key permissions are insufficient, or the Crystal Reports runtime is not installed correctly. Please install the appropriate Crystal Reports redistributable (CRRedist*.msi) containing the correct version of the Crystal Reports runtime (x86, x64, or Itanium) required. Please go to www.businessobjects.com/support for more information.
at CrystalDecisions.CrystalReports.Engine.ReportDocument.CheckForCrystalReportsRuntime()
at CrystalDecisions.CrystalReports.Engine.ReportDocument..cctor()
--- End of inner exception stack trace ---
at CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor()
at Logicity_Desktop.ViewerForm..ctor(Int32 recordNumber, Array actList, Array parmList, Array setList)
at Logicity_Desktop.ProgressForm.processActionList(Object startAt)
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.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.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

---

Logicity Desktop
Assembly Version: 1.6.3047.36241
Win32 Version: 1.6.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.1434 (REDBITS.050727-1400)
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.1434 (REDBITS.050727-1400)
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.1434 (REDBITS.050727-1400)
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.1434 (REDBITS.050727-1400)
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.1434 (REDBITS.050727-1400)
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%20(x86)/SaberLogic/Logicity/Logicity.Common.DLL

---

CrystalDecisions.CrystalReports.Engine
Assembly Version: 12.0.2000.0
Win32 Version: 12.0.2000.683
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.CrystalReports.Engine/12.0.2000.0__692fbea5521e1304/CrystalDecisions.CrystalReports.Engine.dll

---

CrystalDecisions.Shared
Assembly Version: 12.0.2000.0
Win32 Version: 12.0.2000.683
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.Shared/12.0.2000.0__692fbea5521e1304/CrystalDecisions.Shared.dll

---

CrystalDecisions.ReportAppServer.CommLayer
Assembly Version: 12.0.1100.0
Win32 Version: 12.0.1100.683
CodeBase: file:///C:/Windows/assembly/GAC/CrystalDecisions.ReportAppServer.CommLayer/12.0.1100.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.CommLayer.dll

---

System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

---

System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

---

System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_64/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.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>
="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.

Hi,

Well this is not something we have run into before, but it looks like the CR Runtime with Logicity did not register on your system, probably because of the 64bit OS (we have not tested with Vista 64 yet). You could possibly try installing the 64bit version of the CR runtime to get it to register but I don't know if that will help or not.

Thanks!
Brian

Where can I get the 64bit version of the CR runtime?

Hi,

I am not sure, it may be available from the SAP (Business Objects) website. Since I have never tested it or tried it I cannot really make any suggestions.

Thanks!
Brian

Would you provide better support if we purchase a pro version? It's sort of imperative that we get this working.

Hi,

If you look at the support page for Logicity:

www.logicitysuite.com/Support.html

You will see that the "Free Support Option" is meant as a forum for Logicity users to communicate with each other and assist each other. As you can see, by using the Free version of Logicity along with the Free Support Option, it does not really leave us with much to do things like develop, host the site, monitor forums, etc.

But as a service to our users, we do monitor the forums and try to assist whenever we can. One thing to keep in mind is that doing this actually costs us money, not only the time to offer the free support but many times people will get the free support and then never buy the product.

So as an answer I would say that yes, the correct thing would have been to bought the software, especially if you feel that it is imperative to your operations. That being said though, this question is not a support question, it is a custom development request.

We do not post a 64bit version of Logicity on our site. To make a 64bit version, we would have to have a Vista x64 system to test against and recompile our code to be 64bit compatible. For custom development opportunities like this, we typically have to either have a large enough user base for licensing that it makes sense or a customer pays for the development.

If someone makes a request and does not want to pay for the development, we suggest that they post their suggestion in the Feature Requests and Suggestions area of the forum. If we see enough user interest in that feature, we may add it to the next release.

So I do apologize that the level of free support that I offered for a free product did not meet your expectations.

Thanks!
Brian

We are also evaluating this software and have the same problem on our x64 systems.
The x64 runtimes are installed correctly, but we Logicity does not recognize this.

I have no issues on x32.

FYI, my test system was a Windows 2003 X64 server.

You misunderstand, or I misspoke. I am not unsatisfied with the level of support offered. I understand fully, and was truly interested if the problem could be resolved by purchasing the pro version.

From my scouring of the internet for a solution to this problem, I have found some forums that suggest simply assuring that the code is compiled for 32bit operation only may actually allow operation on 64bit machines. This document explains the situation:

tinyurl.com/65549h

Although I get that this is still a custom option, if it is correct, it seems a relatively simple one. I would be more than happy to pay for a pro version, plus a reasonable customization fee for the recompile, and test it personally on our 64bit machine.

This would of course not only make us very happy customers, it would also provide you a workable option for 64bit machines.

Please let me know who I should discuss this with. My direct email is This email address is being protected from spambots. You need JavaScript enabled to view it..

Hi,

Unfortunately the Internet does not always allow for the best conveyance of feeling.

That being said, I believe we have actually tried that at one point in time and still had an issue but I can certainly compile it again and see if it works.

I'll try that hopefully later today and post an exe for you to test.

Thanks!
Brian

Thank you! I look forward to testing it.