on 09-27-2012 3:25 AM
HI
Just recently, when ever i create a NEW report, and go to add more then 1 table to my report.
CR Crashes with the "windows message"
“Crystal reports has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.”
how can i work out what is causing this ?
its getting very frustrating as i have already lost A LOT work when it crashes.
i am running Windows 7
and the data is on our IBM server and connecting via ODBC connection to a Progress Data base.
any help would be much appreciated
Thanks
Mark
Hi Mark,
This is known issue. You may refer to this SAP Note for the resolution: 1621593 - Crystal Reports 2011 crashes when trying to link tables in DB2 iSeries
If you're not able to access the SAP Note; here's what it says:
Cause
ODBC Driver Access permission issue
Resolution
The following registry key resolves the problem:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database\ODBC\
"AccessMode" as a Reg_DWORD 0x00000000 (0)
Here are the steps:
1. Go to Registry Editor (Click Start > Run > type “regedit” > OK)
2. Navigate to :
for Crystal Reports 2011 on 64 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database
for Crystal Reports 2011 on 32 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database
for Crystal Reports 2008 on 64 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite 12.0\Crystal Reports\Database
for Crystal Reports 2008 on 32 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite 12.0\Crystal Reports\Database
3. Right click the “Database” registry key > select New > Key > name the key “ODBC”
4. Right click the “ODBC” key > select New > DWord value > name it “AccessMode”
5. Make sure the value is default: 0x00000000 (0)
6. Restart the Crystal Reports and try again
Let me know if this helped!
-Abhilash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Couple of other things to try / look for:
1) Make sure you do not have C:\temp directory - if you do, rename it
2) See if doing a repair will help
3) Final solution would be to uninstall and reinstall
- Ludek
Follow us on Twitter
Got Enhancement ideas? Try the SAP Idea Place
HI Abhilash and Ludek
Thanks for your replies
Abhilash,
first off i should mention , that i CANNOT view the SAP note above, it says the address is not valid or similar , so unfortunatley am unable to read the note in full.
also how can i create a ticket with SAP ?
i rang the SAP office, and was told to use this forum to fix the problem.
they wanted to charge me to create a ticket, but i dont feel i should have to pay anything, as we have already paid in full for the software so i am looking for support ?????
Ludek,
i did have a TEMP directory, under C: , so i renamed it , still same issue,
how do i do a repair ?
thanks for your help and assistance
Regards
Mark
Hi Mark,
Product License and Maintenance agreements are two different things!
Having a CR License does not make you eligible for Maintenance (support) unfortunately. You need to purchase the Maintenance License separately.
You can still get in touch with SAP Support by creating a "Single Case" here.
Hope this helps!
-Abhilash
Below is a copy of the KB:
Symptom
Crystal Reports 2011 crashes when trying to link tables in DB2 iSeries
Environment
Crystal Reports 2008
or
Crystal Reports 2011
IBM DB2 AS400 iSeries
Reproducing the Issue
Cause
ODBC Driver Access permission issue
Resolution
The following registry key resolves the problem:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database\ODBC\
"AccessMode" as a Reg_DWORD 0x00000000 (0)
Here are the steps:
1. Go to Registry Editor (Click Start > Run > type “regedit” > OK)
2. Navigate to :
for Crystal Reports 2011 on 64 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database
for Crystal Reports 2011 on 32 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\Database
for Crystal Reports 2008 on 64 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite 12.0\Crystal Reports\Database
for Crystal Reports 2008 on 32 bit machine
HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite 12.0\Crystal Reports\Database
3. Right click the “Database” registry key > select New > Key > name the key “ODBC”
4. Right click the “ODBC” key > select New > DWord value > name it “AccessMode”
5. Make sure the value is default: 0x00000000 (0)
6. Restart the Crystal Reports and try again.
Additionally make sure the access granted on all layers including DSN configuration. See the screenshot below:
Re. repair; Control Panel -> Programs and Features (or some such off of the Control Panel - depends on OS).
- Ludek
Hi,
we had the same issue with Crystal Reports 2008.and it was not related to a DB2 connection for us
We had the issue with a direct oracle and an ODBC connection too.
We tried the c:\temp deletion/renaming too - did not help us.
The only thing that helped was deinstalling the Report designer and then reinstall.
It was on my bosses Laptop, so we did not have that much time to trouble shoot, but what i saw he got a couple of updates in the last week.
After a deinstallation and re-installation everything worked as expected.
regards alex
Hello Alexander
Not sure if you're referring to the KBase(?). If you are not sure about how to do this, it will really be best if you find someone who is comfortable working with the registry. Working with registry is tricky and can result in the computer not working at all...
Or, you can obtain phone support at the below link and a support tech will help you out. The link:
One more thing to check; in Windows Explorer, look for C:\windows\temp diretory. If you find it, rename it so c:\Windows\tempX
- Ludek
Hi Ludek,
no i was not referring to the KBase, We just had the same issue this week.
What i wanted to say in my post , i think it is not related to any specific DB connection, because we ran into that issue while we were connecting to a) Oracle and b) to an ODBC connection.
I wanted to point out that we fixed it with a reinstallation.
and i guess it had something to do with the updates that were rolled out to that specific Laptop.
Maybe that led to confusion here.If that is the case i want to apologize for that.
regards alex
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
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.