on 07-23-2008 12:20 PM
I have a Windows Form VB.NET application using Crystal XI R2 to produce reports. The application works flawlessly on other machines in Windows XP, but as soon as I try to load a report in Vista the program exits with the following message -
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: Manufact.exe
Application Version: 1.0.0.0
Application Timestamp: 487ed6c1
Fault Module Name: unknown
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 050e3ed0
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 3081
This happens (only in Vista) whether the report is sent direct to the printer or to the Crystal Report Viewer and occurs at the crReport.Load (direct print) or New CrystalDecisions.CrystalReports.Engine.ReportDocument (viewer) statements.
Despite having Try/Catch blocks and exception handling in place I get no other error messages apart from the above.
I have downloaded and installed all of the CR XI R2 service packs up to SP4 on the development machine.
I have rebuilt with CrystalReports11_5_NET_2005.msm dated 10/04/2008, re-installed but still doesn't fix problem.
I don't think it is a database issue because rest of program loads and displays data (from SQL Server) fine.
Stuart, please confirm this is happening on report load, not on app load.
Once the report loads, does it go to the viewer, is printed directly or is exported? If exported, to what format?
Have you checked the CR directory structure, just to check that the install went well? Look for c:\program files\business objects\common\3.5\bin. Also, check to see that the CR assemblies are in GAC and are of version 11.5.3700.
Assumption; you are using VB .NET 2005 - please confirm.
Ludek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The app loads fine in Vista and the database is accessible. When a report is sent to the viewer I get the error message immediately after executing
crReportDocument = New CrystalDecisions.CrystalReports.Engine.ReportDocument
The report viewer screen is visible in the background but no report is visible u2013 just the APPCRASH message.
If the report is sent directly to the printer, the error occurs directly after the statement u2013
CrystalReportsFolder=u201DC:\MANUFACT\REPORTSu201D
CrystalReportsFile=u201D\CUSTOMERINVOICE.RPTu201D
Try
oRpt.Load(CrystalReportsFolder & CrystalReportsFile)
I have checked the directory structure and everything in folder c:\program files\business objects\common\3.5\bin (e.g.crdb_ad0*.dll) is version 11.5.8.1237 .
All the CrystalDecisions and BusinessObjects files are in c:\Program Files\Business Objects\Common\3.5\managed\ and are version 11.5.8.1237 except for CrystalDecisions.CrystalReports.Engine.dll which is in folder c:\Program Files\Business Objects\Common\3.5\managed\dotnet2 -Version 11.5.9708.1237).
Yes I am running VB.Net 2005 with the latest service packs
I rebuilt the msi install file using CrystalReports11_5_NET_2005.msm dated 10/04/2008, then removed app and re-installed on the Vista machine.
I then checked all of the file versions in c:\program files\business objects\common\3.5\bin and in
c:\program files\business objects\common\3.5\managed and they are now version 11.5.10.1298 (previously 11.5.8.1237)
Now the reports print and preview without problem in Vista !
Thanks for your help
Stu
I am experiencing the same issue and have the Crystalreports11_5_net_2005.msm file from 4/10/2008. However when I install this it seems to install the 11.5.8.1237 version of the files. I got this file from the merge modules SP2.
Can you tell me where you got your version of the msm with the 11.5.10.1298 version.
The latest msm can be downloaded from here:
http://resources.businessobjects.com/support/additional_downloads/runtime.asp
Ludek
This note may be worth a look too 1196644.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rather strange...
You may want to download process monitor utility from here:
http://www.microsoft.com/technet/sysinternals/Utilities/SysinternalsSuite.mspx
and see if it helps you in tracing what file and / or registry entry is blocking the report from displaying.
One other thing. As the viewer does come up, check to see that the temp directory has read / write permissions.
Ludek
The application is probably being trapped by DEP, which would explain why you can't trap the errors. Try adding the application to the exclude list or disabling DEP altogether.
Disabling DEP on Vista:
1. Click Start
2. Click All Programs
3. Click Accessories
4. Right Click on Command Prompt
5. Left click on Run as Administrator
6. Click the Allow button if it asks you for permission
7. Type or copy and paste this into the command prompt window:
bcdedit.exe /set {current} nx AlwaysOff
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.