Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Memory could no be read in Crystal Reports 2008

I'm getting the following error in Crystal Reports 2008 when I want to open the Format menu in the toolbar The moment Crystal Reports 2008 has just started (no report is loaded):

Crystal Reports: crw32.exe - Application Error

The Instruction at "0x00a1305d" referenced memory at "0x00000000". The memory could not be "read".

Click on OK to terminate the program

Click on CANCEL to debug the program

The moment I click on the format menu a process SVCHOST has 100% CPU Usage for some moments and after a few seconds the errormessage appears.

I'm working on a Microsoft Windows Server 2003 Standard Edition Service Pack 2 with 2 CPU's and 3 GB of memory.

The version of Crystal Reports is an evaluation version with Service Pack 2 on it (version = 12.0.0.840).

When I install the same Crystal Report version on the client, the error doesn't occurs.

What could be wrong on the server.?

replied

As the next step I would check and disable Data Execution Prevention.

Go to: Start> Right-click My Computer" select Properties> Advanced tab > click Performance settings> Data Execution Prevention tab.

If DEP turned on for all programs, then add Crystal Reports (crw32.exe) to except list.

If DEP is not cause of problems, then I would suggest Process Monitor to locate the reason or at least try to locate it.

You can download Process Monitor utility from the following page:

[http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx]

The same page will tell you how to use it. I would suggest the following steps:

Close all unnecessary applications/processes

1. Open Crystal Reports

2. Start the Process Monitor, stop capturing events (Cntrl-E), clean the display (Cntrl-X), add the following filter (Cntrl-L) "Process Name is crw32.exe then include", click ok.

3. Start capturing events (Cntrl-E)

4. Immediately click Format menu on Crystal Reports

5. Stop capturing events and save the log file

Now you can look at the log file to see what is going wrong. I would also advice to capture the same log on client machine to compare the sequence of events.

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question