Error when trying to access reports

[staceyn]

Hello,
I am getting the following errors when trying to open any reports in Crystal. I am using version 10 pro with an informix database.
Has anyone seen these errors or know how to resolve them?

This is the error from the event viewer:
Faulting application crw32.exe, version 10.0.0.533, faulting module crw32.exe, version 10.0.0.533, fault address 0x000e85ff.

This is the error in Crystal:
The instruction at "0x004e85ff" referenced memory at "0x000003c". The memory could not be read.

Thanks in advance for any help!

 

[synapsevampire]

This is an evil error, sometimes associated with a corrupt report.

I assume that Crystal is then shutting down.

Sometimes I can resolve these by removing all complexity from the report, such as SQL Expressions.

Other times I've corrected them by changing the connectivity.

I've even had this occur as a result of the Add Command when placing parameters.

The best advice is to install the latest service pack:

http://support.businessobjects.com/downloads/updates/service_packs/default.asp

If that fails, we need to know when the error starts occurring.

-k

 

[Turkbear]

HI,
I have also seen this error when the shortcut used to launch CR is set to a location in your Profile, instead of actually pointing to the crw32.exe file and starting in its directory..
If that is the case, edit the properties of the shortcut ( either on your desktop or on your start menu) to point directly to the crw32.exe file and to start in that file's directory..See if that helps ..







To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[staceyn]

Thanks, I will take a look at that if the service pack doesn't help. I am installing the service pack now.

 

[staceyn]

Ok, I have installed the latest service packs and monthly hot fixes for Crystal 10 and Crystal Enterprise 10.
Any report that we attempt to open in Crystal is still getting the errors. We get an option to select ok to debug or cancel. With either option Crystal shuts down immediately.

This error occurs when trying to open ANY existing report or when trying to create ANY new report.

I have also verified the shortcut is pointing to crw.exe file and it starting in the correct directory.

Also with installing the patches, the problem has become worse.

Everything was working fine yesterday, but this morning the errors started occuring.

Also, now that we have installed all patches, the CMS for enterprise won't work. I have tried restarting the service, but it starts and then stops automatically.
The event viewer shows:
Internal error: An unknown exception has occurred. Programmer error subsystem not available before use.
and
The root server reported an error Initialization Failure.
and
Could not read key (DatabaseDriver) from registry.

 

[synapsevampire]

Are you saying that tyhe problem exists on a CE server?

Where are you running the reports from, a dev workstation or CE?

-k

 

[staceyn]

Yes, this if for one of my customers. They have a windows 2000 server that runs enterprise. There is also a copy of Crystal Reports installed on the server. The customer only has 1 person who knows how to build reports. So when they want to build a new report, they use terminal services to access the 2k server, build the report, then publish it to enterprise.
This has worked successfully for about 9 months now. It supposedly started generating these errors this morning.

 

[synapsevampire]

CE does occasionally blow up.

Windows 2K Servers occaisonally blow up.

Crystal reports certainly blows up.

You need to state specifics at post time, I wouldn't have suggested the patch solution had you bothered to either post in the CE forum, or had stated the software being used originally.

Have you tested the reports on a CR machine without CE?

I'd guess that the server is hosed, which could be so many things that I won't even begin to try to describe it.

I'd restore last night's backup of the CE Server.

-k