Error "memory could not be read" running some Crystal XI reports

I have a few crystal reports that work some times on a PC then after being run a few times get the following message. The report doesnt load and get a microsoft error:
"memory could not be read"
This happens on all spec of PC from low memory PCs to high memory PCs.

Reboot the computer. I have this issue occasionally with a high-mem computer.

Similar Messages

Upon exiting LV7: Application Error-Memory could not be read.

Upon terminating my application, I get the following error:
"LavVIEW: LabVIEW.exe - Application Error
The instruction at referenced memory at . The memory could not be 'read'."
So far the error seems non-critical. It does not appear to affect the performance of the program in any way. However, it is certainly unnerving for my end users (not to mention me)!
The error occurs in both the executable and the debugging mode. I have traced it to the VERY END of my application, which runs flawlessly until the very moment when I use the Exit instruction. I have also tried using Close FP with Abort VI, as well as Close FP with Exit. All threads in my application have successful
ly terminated, so aborting does not stop any action in mid-execution, as far as I am aware.
Searching for others in the forum who have had similar problems has turned up little useful help. Could this be a bug in the (god forbid!) runtime engine?!
Here's a link to a discussion of the closest thing I could find to my problem.
Thanks for any help you can give. Any whatsoever.
-Nick
"You keep using that word. I do not think it means what you think it means." - Inigo Montoya

> Hmmm... I'll look into it. Many or all of the DLLs that I call were
> written in Delphi, which has at least three string types that come
> into play: regular Pascal String, PChar (Delphi's re-creation of the C
> string type), and the ShortString type, which is sized to 256 bytes
> (if memory serves). From your response, it sounds as if I should
> search for those DLLs that use the ShortString type.
>
> Also, I encode many complex data forms and pass them into the DLLs as
> array pointers. These also sound like places to start looking.
>
> Thanks for the input. If I ever track down the problem, I'll update
> this discussion for posterity. In the meantime, if anyone else out
> there has any more thoughts, I'd sure appreciate them.
To h
elp track it down, if you can build a debugging version of the
Delphi DLLs, especially something that will validate memory references.
One of the great tools for tracking down memory overwrites is a well
implemented debugging memory library. Also, if you have some notion of
DLL calls that write to the string and return it to LV, that would be
the first place to look. And in the end, the solution is usually to
look at the assumption of the DLL and send in a larger preallocated
string. So in some cases it is easiest to look for the strings and
arrays going into DLL node calls and one at a time give them large input
sizes looking for the closing crash to go away. Then when the symptom
goes away, look at the code for that DLL.
Greg McKaskle

Application Error - memory could not be read

Hello all,
we are having a problem with certain users of Manager Self Service (MSS) that have a large number of staff available to report upon.
This problem occurs whenever these managers run any report for more than 63 employees. The IE error is:
iexplorer.exe - Application error
The instruction at xxxxxxxxx referenced memory at yyyyyyyyyy. The memory could not be "read".
OK to terminate.
CANCEL to debug.
The session closes whichever button is clicked so we can't view any expanded error help.
Could anyone please tell me where to look to determine the reason for this error - for example, would it be in the portal error logs or should I run an R3 trace?
Has anyone encountered this error before?
Many thanks in advance,
Keiron.

Hi Dion,
Check the Product Availiblity Matrix in Service Market Place and check the IE compatablity with your portal and business package version.
Note : If this is not working then mention your portal, business pacakge and IE version.
Reagrds,

Application Error Memory could not be read(Please Help)

Hi
I need help.
I am using Adobe Photoshop CS4 Extended Student Edition.
My computer is Windows XP
I continue to get the error Photoshop exe Aplication Error
Instructions at oxofa92c5b sometimes is states oxofc42c5b
reference memory oxoooooo28 Memory could not be read
Cancel or debug. Then it shuts down.not matter what you click.
It does this after I get the picture open and when I click on different tools.
This is newly installed on my computer and newly bought program.
Help would be greatly appreciated.

Those "bad memory" errors are usually caused by one of two things
One (fairly rare) is an actual bad memory stick
Two (most often) is a bad device driver... these are really hard to narrow down to the actual cause
Some things to try...
Go to the motherboard vendor and make sure you have the latest device drivers for your brand/model motherboard
Also make sure you have the latest device drivers for your brand/model video display card
Finally, any other device drivers you had to install

Referenced memory could not be read - error

Hey, In an application on stop command, I exit from labivew on exit I get an error the referenced memory could not be read click ok to terminate program can any one suggest why this error is seen
how this can be resolved?
enclosed a screen shot of error
Regards
anil
Attachments:
error log.PNG ‏6 KB

Hi AndreasC,
This error message occurs when LabVIEW memory space goes corrupt and is often due a DLL or CIN code.
There can be two reasons for this:
1. Try removing all DLL calls in your code and see if it works. Most of the time, the corruption is traced to a call to a DLL function that has incorrectly passed inputs to the Call Library Function node, often by passing an uninitialized string or array, or by writing past the bounds of the string or array in the DLL function. Some DLL functions assume that a string buffer is presized to 256 bytes, 1 KB, or some other size. If a smaller sized string buffer is passed, the DLL can write past the buffer and corrupt the dataspace that follows.
2. This error can also be caused when running a LabVIEW built executable. If the VI calls a WinAPI DLL function and uses the full path to the DLL in the Call Library Function Node, the LabVIEW Application Builder will create a copy of the DLL in the data directory of the executable. Some DLLs such as WinAPI DLLs should only reside in one location, such as C:\WINDOWS\system32, otherwise errors/crashes can occur when called. To prevent this, remove the DLL path in the Call Library Function Node when calling WinAPI DLLs.
Some users have faced similar problems and the above solutions have worked for them.
Here are the links to those discussions:
http://forums.ni.com/ni/board/message?board.id=170&message.id=67230&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&thread.id=229434&view=by_date_ascending&page=1
Regards,
Ujjval

Nimax.exe - Application Error. Instruction at 0x6d8e3e61 referenced memory at 0x00000000. The memory could not be "read."

On startup I get a nimax.exe application error.
The instruction at "0x1ce30df7" referenced memory at "0x00000000". The memory could not be "read".
This happens every time I start the computer, run a vi with the initialize.vi or try to use the measurement and automation explorer.
I am running windows XP, Labview 7.1, and max 3.1.1

I had a similar problem in win2000 / max 3.1.1. I do not recall the exact memory location error.
It happened every time I started the computer, or once started, evrytime I load a vi that has some daqmx functionlity.
I reinstalled windows / Nidaq, and never had the error again.

Explorer exe. Application error" it says "The instruction at 0xf6628a87 referenced memory at 0x00000000 The Memory could not be read Click on OK to terminate the program

the other day i did the windows 2008 R2 Rebooting
Explorer exe. Application error" it says "The instruction at 0xf6628a87 referenced memory at 0x00000000 The Memory could not be read Click on OK to terminate the program
i just get this error message. If it is anything serious, there is nothing I can do.
the 2008R2 OS was hang out of control
what is a major cause of error message? is there any fix or Hotfix?

Hi,
Regarding the current issue, it may be caused by some third party software conflicting with explorer.exe or it could be a memory conflict with a driver.
Signs of low memory include poor performance, low-memory or out-of-memory notifications, and display problems. I would suggest you to follow the steps provided in these methods and check if
it helps in resolving the issue:
Method 1: Run System Maintenance troubleshooter:
Step 1 : Move your mouse to the right bottom and click on search.
Step 2 : Type Troubleshooting in the search box and click on it
Step 3 : On left pane click “View all” click on the "Run Maintenance task" under the System and Security.
Step 4 : Click on the "Next" in the System Maintenance interface.
Select "Try troubleshooting as an administrator
Method 2:
I would suggest you to run the Memory Diagnostic Tool and check if it helps.
a) Press
Windows key and type "memory".
b) Click "Settings" and then click the result "Diagnose your computer's memory problems".
c) Select the recommended option to run the tool.
Check if the issue still persists. If the issue persists, increase the virtual memory.
Change the size of virtual memory
http://windows.microsoft.com/en-in/windows-8/change-the-size-of-virtual-memory
Method 3: I would suggest you to run System File Checker tool (SFC.exe) and check if it helps. The System
File Checker tool (SFC.exe) scans for missing or corrupted system files and repairs them.
Run System File checker to see if you have any corrupted system files.
Use the System File Checker tool to repair missing or corrupted system files
http://support.microsoft.com/kb/929833/en-us
Method 4: If issue persists follow these steps:
I would also suggest you to check if the same issue occur in Safe Mode and check if the issue occurs there as well.
Step 1:
Start your computer in safe mode
http://windows.microsoft.com/en-US/windows-8/windows-startup-settings-including-safe-mode
Step 2:
Follow the Microsoft KB article to perform clean boot on the computer. A clean boot helps eliminate software conflicts.
How to perform a clean boot in Windows 8.1, Windows 8, Windows 7, or Windows Vista
http://support.microsoft.com/kb/929135
Disclaimer: After you have finished troubleshooting, follow these steps from section “How to
reset the computer to start as usual after clean boot troubleshooting” to reset the computer to start as usual.
Hope this helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Application Error: "The memory could not be 'read'."

I am programming an application in C#.
I am using an Acrobat Reader control on my form to display PDFs within my program.
I have tried a couple of different configurations with the form control. I have drag-and-dropped the control prior to runtime. I have also tried to add the control dynamically.
When I run the program, then activate the control and close the form, I get the following error.
"sw:name.exe - Application Error; The instruction at "0x0700609c" referenced memory at "0x00000014". The memory could not be 'read'. Click on OK to terminate the program."
I have googled this error for hours now, and cannot find anything that truly explains this error and how to fix it.
Thank you for any help.

To who may be interested, I managed to find a workaround for this bug in Adobe Reader 9.0.
It seems that, somehow, LabVIEW, and other programming tools, straggle with this version of Adobe (I assume that this is due to this bug) when closing the reference to Adobe created by the ActiveX container. So the solution would be closing "by hand" this reference, and telling Windows to free all the relation between the application (LabVIEW for us) and Adobe. The idea is that when we've done with the VI which displays the PDF via ActiveX, we should close the reference to the ActiveX control, close the reference to the VI, and:
- process all the Windows messages currently in the message queue (.NET: System.Windows.Form.Application -> DoEvents
- run CoFreeUnusedLibraries in "ole32.dll"
I hope this information can help somebody, as I wasted too much time to figure this out (finding eventually the answer in a forum of Adobe!)
P.S. For those who program in C# as well, check this link; this was my source.

Cannot Change Data Source - Error The memory could not be "read"

We have some reports that were created under Crystal Reports version 10 using a Sybase 12.5 database as the datasource. We have since upgraded to Sybase 15 ASE and we are also attempting to upgrade these reports to Crystal Reports version 11.5. The reports will convert to version 11.5 but will not work because of the following error:
"Failed to load database information. Details: The database connector 'crdb_p2ssyb10.dll' could not be loaded"
From previous experience we know that Sybase 15 is only supported via ODBC with Crystal Report 11.5, so we tried to change the datasource to ODBC, but when we do that we get the following error:
The instruction at "0x0e864b11" referenced memory at "0x00000004". The memory could not be "read".
Do we have any options at this point besides competely re-creating the reports?

We are using CR 11.5 and trying to change the data source to ODBC. I can create a new report and use the same stored procedures as a datasource via ODBC with no issues. I only have an issue when trying to change the data source on these existing reports.

Error 990 - Memory could not be read

When launching Flash Professional 8, the following
application error is generated as the splash screen indicates fonts
are initializing:
990: Flash.exe - Application error
The instruction at "0x6172676f" referenced memory at
"0x6172676f". The memory could not be "read".
Click on OK to terminate the program.
Click on Cancel to debug the program.
[OK] [Cancel]
With each uninstall and reinstallation of Flash the error
number changes as well as the memory address location.
Has anyone experienced this error and have a solution?
Reinstalling & rebooting did not solve it.

I had a similar problem with Flash MX 2004, and it turned out
to be related to a Quick Time problem. (I was also unable to play
any Quick Time files, so you might want to check that on your end
to help troubleshoot as your cause as well.)
QT was so corrupt on my system, I couldn't even uninstall it
using the normal methods. Our IT department had to manually remove
everything on my system related to Quick Time. After that, I
uninstalled/reinstalled Flash, and then reinstalled Quick Time, and
everything has been fine since. (In fact, I've upgrade to v8 since
then...)
I originally thought my problem was a corrupt font, since it
was during the "loading fonts" part of the start-up, but utlimately
the Quick Time issue fixed it. I worked with Macromedia (at the
time) tech support on it, but can't find the e-mail thread.
UPDATE:
I found the old thread, here is the pertinent message from
Macromedia Support that led to the resolution:
""I'm sorry to hear that you're still having the same issue,
I've been evaluating the said forum thread and I think I remember
something about the QuickTime player issue. For some reason, older
or broken components in QuickTime can also cause Flash to
malfunction as Flash needs it for some operations.
I recommend that you download the latest QuickTime, uninstall
your current version, reboot and install the new QuickTime player,
then uninstall and reinstall Flash using the same routine I
provided previously".

When I close Firefox, I get an error That says "The insstuctions at 0x7c911389 references memory at 0x0000010. The memory could not be read

When I exit Firefox, I get an error message that says The instuction at 0x7c911389 referenced memory at 0x000000010 The memory could not be read.

The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information.
Note: ''This will cause you to lose any Extensions, Open websites, and some Preferences.''
To Reset Firefox do the following:
#Go to Firefox > Help > Troubleshooting Information.
#Click the "Reset Firefox" button.
#Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
#Firefox will open with all factory defaults applied.
Further information can be found in the [[Reset Firefox – easily fix most problems]] article.
Did this fix your problems? Please report back to us!

Wfmlrgsm.exe error. The memory could not be read.

Dear experts,
I have this Installation:
Oracle apps 11 on Windows XP Pro. Visual C++, cygwin.
After I bring up the database listener, and Apache Server,
I then start the service,
OracleConcMgrTEST
which is:
C:\oapps11\testappl\fnd\11.5.0\bin\CCMSVC.exe TEST
But I keep getting a pop up error window:
Wfmlrgsm.exe – Application Error
The instruction at "7C911F52" referenced memory at "4543414F". The memory could not be "read".
Click ok to terminate
Click on Cancel to debug the program.
The file is:
$ find . -type f 2>/dev/null | grep -i "Wfmlrgsm.exe"
/cygdrive/c/oapps11/testappl/fnd/11.5.0/bin/WFMLRGSM.exe
When I have pressed cancel to debug, it brings up Visual C++ debugger.
I see:
7C911F22 E8 2C BA 04 00 E9 29 F0 FF FF 0F B7 C0 50 56 E8 è,º..é)ðÿÿ.·ÀPVè
7C911F32 CB 00 00 00 E9 34 65 00 00 3B 5F 14 0F 87 3B 83 Ë...é4e..;_..‡;ƒ
7C911F42 03 00 E9 72 97 00 00 8B 70 04 83 EE 08 89 75 C8 ..ér—..‹p.ƒî.‰uÈ
7C911F52 8A 46 05 88 45 E3 8D 4E 08 8B 39 89 BD 48 FE FF ŠF..Eã.N.‹9‰½Hþÿ
7C911F62 FF 8B 56 0C 89 95 78 FF FF FF 8B 12 3B 57 04 0F ÿ‹V.‰•xÿÿÿ‹.;W..
7C911F72 85 F3 23 02 00 3B D1 0F 85 EB 23 02 00 8B 8D 78 …ó#..;Ñ.…ë#..‹.x
7C911F82 FF FF FF 89 39 89 4F 04 3B F9 75 2F 0F B7 0E 8B ÿÿÿ‰9‰O.;ùu/.·.‹
7C911F92 D1 C1 EA 03 89 95 40 FE FF FF 83 E1 07 33 FF 47 ÑÁê.‰•@þÿÿƒá.3ÿG
7C911FA2 D3 E7 89 BD 50 FF FF FF 8D BC 1A 58 01 00 00 33 Óç‰½Pÿÿÿ.¼.X...3
454340FF ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543410F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543411F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543412F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543413F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543414F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543415F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543416F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543417F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543418F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
4543419F ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
454341AF ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ????????????????
Call stack:
NTDLL! 7c911f52()
MSVCRT! 77c2c3c9()
MSVCRT! 77c2c3e7()
MSVCRT! 77c2c42e()
FNDCORE! 7aa6c96e()
FNDCORE! 7aa9ae36()
WFMLRGSM! 004011ea()
WFMLRGSM! 00401567()
WFMLRGSM! 0040411d()
KERNEL32! 7c816fd7()
I've also got this error when I:
Bring up the tutorial on making Oracle Forms.
Any ideas on how to make this error go away?
Thanks

Visual C++ Help, About, gives:
Visual C++ 6.0
BTW, Service Pack 3 that you mentioned in the other thread:
Re: Install of apps 11.5.8 on Windows - Problems with PreReqs
Is it the service pack for XP? Or, for C++?
Windows Event Viewer logs:
EvntAgnt
TraceFileName parameter not located in registry; Default trace file used is .
TraceLevel parameter not located in registry; Default trace level used is 32.
TraceFileName parameter not located in registry; Default trace file used is .
TraceLevel parameter not located in registry; Default trace level used is 32.
OracleFormsServer-Form
The description for Event ID ( 0 ) in Source ( OracleFormsServer-Forms60TEST ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: OracleFormsServer-Forms60TEST Started.
Here are the files I found:
OracleApps@green /cygdrive/c/oapps11
$ find . -type f | grep -i "adadmin"
./testappl/ad/11.5.0/bin/adadmin.exe
./testappl/ad/11.5.0/lib/adadmin.obj
./testappl/ad/11.5.0/res/adadmin.res
To relink, what do I do? Shut everything down, and run the exe?
Thanks a lot!

App Error "...memory could not be read."

DLACTRL.EXE Application Error
The instruction at "0xfd2a2ad0" referenced memory at "0xfd2a2ad0." The memory could not be "read." Click OK to terminate program.
Fresh install of Comm Suite with Captivate 3 -- today -- on a completely new never used before Dell computer running Windows XP Service Pack 3, 3.0 GB RAM
Only concurrent program running was IE browser
I see in other forums this happens a lot with Creative Suite programs. Captivate too?
I ran updates for Captivate and Windows XP after the "crash"
I saw one advisory to avoid recording IE so I am trying FireFox and so far so good but it's been only for a few minutes.
Question:
Why does this happen?
How can I stop it from happening?
Can damage can be done to my computer or other programs when this happens?
Thank you!

Here are 22 threads with a similar question:
http://search.java.sun.com/Search/java?col=javafrm&qp=%2Bforum%3A4&qt=%22NT+service%22&x=14&y=8
The first one refers to a commercial product that may or may not help.

Memory could not be read Error Fixed

At least 6 months ago, I noticed that every time I opened my
default page in Dreamweaver and closed it, Dreamweaver would crash.
I would get the famous Application Error, "The instruction at
"0x5ad71531" referenced memory at "0x00000014". The memory could
not be "read". Click OK to terminate the program."
What I figured out is that right about that time, I had
switched my default browser for viewing to Firefox Mozilla.
Today, while I was testing some things out, I noticed that
the Check Browser Support list, only had Internet Explorer and
Netscape.
After I added Firefox Mozilla to the list of browser to check
compatibility for, the problem disappeared.
Go figure.

> At least 6 months ago, I noticed that every time I
opened my default page in
> Dreamweaver and closed it, Dreamweaver would crash. I
would get the famous
> Application Error, "The instruction at "0x5ad71531"
referenced memory at
> "0x00000014". The memory could not be "read". Click OK
to terminate the
> program."
>
> What I figured out is that right about that time, I had
switched my default
> browser for viewing to Firefox Mozilla.
>
> Today, while I was testing some things out, I noticed
that the Check Browser
> Support list, only had Internet Explorer and Netscape.
>
> After I added Firefox Mozilla to the list of browser to
check compatibility
> for, the problem disappeared.
Great detective work!
I can't seem to reproduce this problem. What version of DW do
you use?
Was Internet Explorer or Netscape defined as either Primary
or Secondary
browsers? Any other details to help me reproduce this so we
can fix it
if it's still in the code?
Thanks,
Randy

Application error The memory could not be read 0x00000014

Hi everyone,
I would like to know if any of you have come across this issue.
I'm running an application built by me in a computer with LabVIEW Run-time 9 in which I display a PDF file using an ActiveX control:
The target computer runs Adboe Reader 9.0. Everything works perfect until the application is closed. From time to time (nearly most of the times), I've got the next windows error:
"Application Error: The instruction at "0x0ffd609c" referenced memory at "0x00000014". The memory could not be "read". Click on OK to terminate the program".
Trying to find out the reason, I found a couple of forums which claim that the reason is a bug in Adobe 9.0 (actually, I've tried running the application with Adobe Reader 8 and I cannot repeat the error). Any of you have had this error before and found a solution? Those links weren't about LabVIEW and I have no idea how to get around this issue.
Any help is appreciate it.
Thanks in advance.
Dani
Solved!
Go to Solution.

To who may be interested, I managed to find a workaround for this bug in Adobe Reader 9.0.
It seems that, somehow, LabVIEW, and other programming tools, straggle with this version of Adobe (I assume that this is due to this bug) when closing the reference to Adobe created by the ActiveX container. So the solution would be closing "by hand" this reference, and telling Windows to free all the relation between the application (LabVIEW for us) and Adobe. The idea is that when we've done with the VI which displays the PDF via ActiveX, we should close the reference to the ActiveX control, close the reference to the VI, and:
- process all the Windows messages currently in the message queue (.NET: System.Windows.Form.Application -> DoEvents
- run CoFreeUnusedLibraries in "ole32.dll"
I hope this information can help somebody, as I wasted too much time to figure this out (finding eventually the answer in a forum of Adobe!)
P.S. For those who program in C# as well, check this link; this was my source.

Error "memory could not be read" running some Crystal XI reports

Similar Messages

Maybe you are looking for