Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Crystal-based database reports run in 32-bit windows but not 64-bit

Status
Not open for further replies.
mbrayc

mbrayc

MIS
Jan 5, 2012
50
US
Hello all,

My company has a QA database that generates reports using Crystal Reports (our company currently runs Crystal XI Release 2). When attempting to run reports on a Windows 7 64-bit machine, the following error occurs:

"Could not load file or assembly 'CrystalDecisions.CrystalReports.Engine. Version 13.0.02000.0. Culture=neutral. PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the value specified."

Below is the full text of the exception error:

************** 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 TheNewRayco.frmDataNonConformance.PrintMe()
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.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.0.30319.261 (RTMGDR.030319-2600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
TheNewRayco
Assembly Version: 1.0.0.2
Win32 Version: 1.0.0.2
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/SetupRaycoQA/TheNewRayco.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
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.0.30319.261 built by: RTMGDR
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.0.30319.233 built by: RTMGDR
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.0.30319.235 built by: RTMGDR
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.0.30319.276 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
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.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.237 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.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 reports run fine on 32-bit systems. Any thoughts?
 
Sort by date Sort by votes
Hi lbass,

I looked at that thread, and double-checked the ODBC settings. The 32-bit DSN is pointed to correctly according to the odbcad32.exe program. The users having difficulty with the database in question can run other Crystal reports from the DSN. The problem is I'm not entirely sure where this QA database is supposed to point to. This database was custom-designed by an outside programmer, whom I have been unable to contact at this point. It's designed to get at least most of its data from our MAX database. However, I'm not 100% sure.

Thanks again,

Michael
 
Upvote 0 Downvote
Did you install the application ? Looks like crystal components for VS2010 are not installed.

Viewer, scheduler and report manager for Crystal reports and SSRS.
Send your report everywhere.
 
Upvote 0 Downvote
Hi RTag,

No, I did not install the application. This was an update of a 32-bit application that had been installed long before I came to this company, and just been updated for 64-bit use. That update happened after the initial discovery that this QA database would not run reports on 64-bit systems.

Thanks again,

Michael
 
Upvote 0 Downvote
Sounds similar to a problem I have with a local client. Their Delphi App uses a SQL database and Crystal 7. One user got a new Windows 7 Pc and found they couldn't run the application or Crystal Run time. Had to set up a VM with XP and install everything on that. All works fine now, just messy.

Typical Legacy app issue. App upgrades are expensive and risky, but face the risk of being left behind with Windows and Hardware upgrades.

Bruce Ferguson
 
Upvote 0 Downvote
This is VS2010 app and you may nedto install crystal runtime for vs2010

Viewer, scheduler and report manager for Crystal reports and SSRS.
Send your report everywhere.
 
Upvote 0 Downvote
Thank you RTag and Bruce for your input. I'm setting up a test machine and will try both solutions.

Michael
 
Upvote 0 Downvote
Here's what I have so far:

I tried installing the crystal runtime on the test machine, but the program crashed when I tried running the report.

Next I tried setting up a virtual machine and installing the database program and the crystal runtime on that, including joining the virtual machine to the company domain, mapping the network drives, and connecting to the same system dsn (tested ok). However, when trying to run the reports, I now get this message:

An unexpected Error Has occurred
Failed to load database information.
Error in File temp_676144b9-1b98--403e-be62-.f2S7c4d8eOec
{736D5417-9AAF-4Acc-90A1-6E986ccDAOOc}. rpt:
Failed to load database information.
OK

I suspect that the VM really isn't connecting to the database after all. I'll admit I'm a newbie when it comes to virtual machine setup. I didn't install our full-blown Crystal Reports software or our MRP software, but since they access the same DSN it shouldn't matter anyway.

Any additional input would be appreciated. Thanks again everyone for your help.
 
Upvote 0 Downvote
mbrayc , it is really hard to give you an advice without knowing what is going on.

If you go to "Uninstall program" dialog can you see:
SAP Crystal Reports runtime engine for .NET Framework4(32-bit)
or
SAP Crystal Reports runtime engine for .NET Framework4(64-bit)
 
Upvote 0 Downvote
Thanks for the reply epmo. I installed installed the 32-bit versions of the crystal runtime and .NET Framework 4 on the virtual machine created on the test machine. The test machine is windows 7 64-bit and the virtual machine is operating in XP Mode. (XP SP3 32-bit).

Please let me know if you need any further information.
 
Upvote 0 Downvote
I am not sure how this should be handled with the virtual machine, but you should be able to run the application in both 32 and 64 bits mode on your Windows 7 64 bits machine. Do you have SAP runtimes 32 or 64 installed on your Windows 7 64 bit machine ? ( check your "Uninstal or change programs" for the same lines "SAP Crystal ...")
 
Upvote 0 Downvote
Hello again all,

Just an additional item I just thought of: When setting up the virtual machine, when running the recommended test by Microsoft to see if the hardware on the test machine supported virtualization, the results came back negative (hardware virtualization not supported). I don't know how much that helps.
 
Upvote 0 Downvote
Hello again,

I only had the 64-bit version of the Crystal Runtime installed. I just installed the 32-bit version and tried running the database again. This time, I got a message similar to the one I originally posted, only this time there was no Crystal reference at all. Actual message contents follow:


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

************** Exception Text **************
System.TypeInitializationException: The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception. ---> System.TypeInitializationException: The type initializer for 'CrystalDecisions.Shared.SharedUtils' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
at CrystalDecisions.Shared.SharedUtils..cctor()
--- End of inner exception stack trace ---
at CrystalDecisions.Shared.SharedUtils.GetEffectiveCulture()
at CrystalDecisions.CrystalReports.Engine.CREngineRes.GetString(String name)
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 CrystalDecisions.CrystalReports.Engine.ReportClass..ctor()
at TheNewRayco.frmParent.MenuItemPastDueReport(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.261 (RTMGDR.030319-2600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
TheNewRayco
Assembly Version: 1.0.0.2
Win32 Version: 1.0.0.2
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft/SetupRaycoQA/TheNewRayco.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
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.0.30319.261 built by: RTMGDR
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.0.30319.233 built by: RTMGDR
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.0.30319.235 built by: RTMGDR
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.0.30319.276 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
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.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.237 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
CrystalDecisions.CrystalReports.Engine
Assembly Version: 13.0.2000.0
Win32 Version: 13.0.3.612
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.CrystalReports.Engine/13.0.2000.0__692fbea5521e1304/CrystalDecisions.CrystalReports.Engine.dll
----------------------------------------
CrystalDecisions.Shared
Assembly Version: 13.0.2000.0
Win32 Version: 13.0.3.612
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.Shared/13.0.2000.0__692fbea5521e1304/CrystalDecisions.Shared.dll
----------------------------------------
CrystalDecisions.Windows.Forms
Assembly Version: 13.0.2000.0
Win32 Version: 13.0.3.612
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.Windows.Forms/13.0.2000.0__692fbea5521e1304/CrystalDecisions.Windows.Forms.dll
----------------------------------------
CrystalDecisions.ReportAppServer.CommLayer
Assembly Version: 13.0.2000.0
Win32 Version: 13.0.3.612
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/CrystalDecisions.ReportAppServer.CommLayer/13.0.2000.0__692fbea5521e1304/CrystalDecisions.ReportAppServer.CommLayer.dll
----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.272 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Web/v4.0_4.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>
<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.


Hope this info helps.

Thanks again in advance for all of your suggestions.
 
Upvote 0 Downvote
As far as I can determine, it was not a web application. It was custom-designed for this purpose. How it was created I have no idea.
 
Upvote 0 Downvote
mbrayc, I would suggest you to install one of the products which are using crystal reports 13. A list is available here:

I am using R-tag and it worked out of the box. It is available here:
Other applications that use the same crystal engine are :
DataLink : Report Runner: but I never tried them.


You may install one of these application just to make sure that it will work on this machine. If it works then you need to contact your app provider because the problem is in your application. Otherwise the problem is in your machine and you may need to talk to your system administrator. BTW these application may fix the problem that you have now so try you app after the installation.

There will be an error if your version of SAP is older than the versions used in these apps. So you will need to uninstall SAP crystal reports ... before to start the installations.


If it is web app you can check "Enable 32-Bit Applications" option under the advanced settings for the Application Pool in IIS.
 
Upvote 0 Downvote
Hello again,

Took a little while to run through all of the possible solutions tested (plus other problems at the office-but that's another story). Unfortunately, none of them worked. Every time I tried to run a report, the database program crashed. I was able to get a hold of the program's original designer and they're researching how to proceed next.

Thanks again to everyone who responded to my post.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Insulations504
  • Locked
  • Question
Crystal Reports duplicating invoices
Replies
1
Views
330
dgillz
dgillz
Ivan Kok
  • Locked
  • Question
Crystal Reports Runtime causing AS/400 DB2 Database ID to be disabled intermittently
Replies
0
Views
317
Ivan Kok
Ivan Kok
Kennymc
  • Locked
  • Question
Crystal connection to Microsoft business central 365
Replies
0
Views
443
Kennymc
Kennymc
s_reddibathuni
  • Locked
  • Question
export multiline address field from crystal to excel
Replies
3
Views
411
hilfy
hilfy
BTPJayW
  • Locked
  • Question
Verify Database Not Working Against Stored Procedure
Replies
1
Views
354
hilfy
hilfy

Part and Inventory Search

Sponsor

Back
Top