Reports 3.0 "Memory could not be read" error

If the object referenced by a trigger is deleted without also deleting the trigger itself the following error message appears when attempting to access or delete the trigger:
R30DES32.EXE - Application Error
The instruction at "0x649e401e" referenced memory at "0x00000402". The memory
could not be "read".
Click on OK to terminate the application
Click on CANCEL to debug the application
<<OK>> <<Cancel>>
Clicking either button terminates the session.
How can I get rid of a trigger in this situation when to highlight it and press the delete key only results in needing to restart Reports?
TIA,
Dan Wilterding
[email protected] (aging e-dress, soon to go away)
[email protected] (newer, faster, shinier e-dress with better mpg)

GX is disabled since installing. I don't know what or who installed manycam but i will disable it and come with updates. Thank you, kind sir.
Later edit: OK Uninstalled manycam just changed the error code, but the error is still there. I attached the picture.
Attachments:
DSC_2877.JPG ‏2879 KB

Similar Messages

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

Skype 7.0 memory could not be read error on shutdo...

Hello, yestarday I upgraded to Skype 7.0.0.100 and when I shutdown the computer, restart or log off I get this error message: The instruction at 0x60afedfe referenced memory at 0x069b26a0. The memory could not be read.
I mention that I unchecked the option to "play a sound when I sign out" and I disabled uPnP (as mentioned in other threads).
This issue is the result of a conflict with the Asus Xonar DG SI 7.1 audio card, but unchecking the option to "play a sound when I sign out" fixed the problem in the previous version 6.
The error doesn't generate any kind of information in the event viewer.
My OS: Win 8.1 Pro
Any suggestions?
Attachments:
DSC_2877.JPG ‏2784 KB

GX is disabled since installing. I don't know what or who installed manycam but i will disable it and come with updates. Thank you, kind sir.
Later edit: OK Uninstalled manycam just changed the error code, but the error is still there. I attached the picture.
Attachments:
DSC_2877.JPG ‏2879 KB

ITunes 7: "memory could not be read" error

I am running the latest version of iTunes 7 and sometimes get the following error message:
"Instruction at Ox5ad71331 referenced memory at 0x00000014. Memory could not be read"
This happens after iTunes crashes. The appearance of the crash is that the font will become very dark/bold and dark lines will appear around the cells of the library, then the program will crash.
Is this related to iTunes 7 or Multi-Plugin, which I use to make my media buttons on my laptop work with iTunes? I have no skinning options chosen.
Thanks.

I uninstalled the Multi-plugin and haven't had the problem since, in fact, no crashes at all.

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

Memory could not be read error.

I keep getting the following error while using Form Designer 7:
The instruction at "0x022221b2" referenced memory at "0x0000001c". The memory could not be "read".
It happens, randomly, when doing a number of things:
inserting a static text area
moving a form field
resizing a static form field....
In other words, no one thing seems to be causing it. If anyone has any ideas on this one it would be most helpful. Right now it is a pain in the butt since I keep losing information everytime it crashes.

Can't help with why but.... If Designer crashes you can recover the last PDF that you previewed by going to C:\Documents and Settings\<username>\Local Settings\Temp and finding the most recent pdf with a name such as _12bs10afg3a40f3t7j.pdf. That should be the last version you Previewed. Rich Ruiz Novanis

Memory could not be read Distiller

I'm getting a memory could not be read error whenever i try to print to PDF.
The error shows when the distiller loader is at creating fonttables.
Tried opening Distiller directly but gives the same issue,
I'm not able to open the Distiller program cause it will go to the error while startup is loading (again the error comes up when it's creating fonttables)
Tried sofar:
     Reinstalling Adobe PDF and Distiller. (after full removal)
     Running in safe mode.
     Looking on google for the answer (countless hours of searching without a working solution)
     printing a file without any special fonts to no avail.
Please any help to resolve this issue would be much appreiciated.

Do you have a lot of extra fonts installed on your system? In the past there have been problems with huge numbers of fonts. Also, what version of Acrobat are you using and on what OS?

Illustrator CS error : "The memory could not be "read""

Hi,
If i close the Adobe illustrator CS in my pc(Windows XP). "The instruction at "0*00341469" referenced memory at "0*00000000". The memory could not be
"read"", error displayed. If i click ok, then only the illustrator closed. Could you please advice me how to solve this error.
Regards,
Maria Prabudass E

Possibly a bad font.
check
The memory could not be...

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.

Error Reported : The instruction at 0xe7c49714 referenced memory at 0x0000000. The Memory could not be read. Click on OK to terminate the program

Hi
All Got an Error Message when i was restarting the VM after some thing
Please look in to this
The instruction at 0xe7c49714 referenced memory at 0x0000000. The Memory could not be read.
Click on OK to terminate the program

Hi Ayaz_Shaikh,
What’s your host OS?
Do you install Windows 10 Technical Preview in Hyper-V? Or some else virtualization products?
Alex Zhao
TechNet Community Support

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.

When I close firefox I get an error message that says:The instruction at 0x7758144 referenced memory @ 0xffffffff, The memory could not be read, how to fix ths?

I get an error message that says , nsAppShell:EventWindow:firefox.exe... Application E...
The instruction at 0x7758e1144 referenced memory at 0xffffffff. the memory could not be read. Click on OK to terminate the program. What's wrong and how do I fix it?

I knew how to do that, sorry. I didn't know if you wanted a copy of each individual report or just the page. Here it is...
Submitted Crash Reports
Report ID Date Submitted
bp-af8afb9c-406f-4843-b5f0-f341c2140704 7/2/2014 7:12 PM
bp-500df430-465f-44ec-9a7e-c34372140702 7/2/2014 4:52 PM
bp-2c14d0a2-b4a2-4eee-a72d-85b912140702 7/2/2014 4:51 PM
bp-2e8bc220-7e16-4291-b3c3-59a7b2140702 7/2/2014 4:50 PM
bp-ea8a52d4-ff08-48f4-b641-539202140702 7/2/2014 4:49 PM
bp-7ff8483e-468a-4324-b788-336e02140702 7/2/2014 4:46 PM
bp-ee0edfa1-f678-428c-868d-1f80b2140702 7/2/2014 4:44 PM
bp-dd32ccd5-4a84-4582-baa9-d731a2140701 7/1/2014 5:29 PM
75d1f4f1-730e-4e6d-a9aa-7bf08527c14e 5/14/2014 7:40 PM
a5d77b9b-5adc-40ed-8926-245f9c1711b2 4/23/2014 6:24 PM
42ef8c1d-dd05-401f-b91c-15633c5080f5 2/17/2014 2:33 PM
0a233130-e0e9-4a78-ac7c-70ce42d07fcd 2/17/2014 2:33 PM
90b4e67a-5655-4dbf-96aa-b1ceb622cffb 2/17/2014 2:33 PM
1222611d-88cd-4c2b-a165-48dc2ae60888 2/17/2014 2:33 PM
921660a9-b14c-4b71-81c0-4864f246f531 2/17/2014 2:32 PM
84c51953-118a-4b16-a65c-5b0472c31885 2/17/2014 2:32 PM
b12c8c12-b5d2-4028-8804-7831fff1e059 2/17/2014 2:32 PM
fa608271-c2c6-4ff2-8fee-dd12d9cddca5 2/17/2014 2:32 PM
110a075b-5209-4b48-98fb-51f6c18747b7 2/17/2014 2:32 PM
f6b7c7f8-edb5-4c8a-9f9d-95cdf9dae28f 2/17/2014 2:32 PM
38df997b-6c08-4b04-9e10-79114e21b087 2/17/2014 2:32 PM
58e8b80b-0482-4df7-874e-e3c051e3a390 2/17/2014 2:32 PM
2649763b-3e51-414c-87a9-c429e2542a1c 2/17/2014 2:32 PM
f3323912-ee94-40ac-9378-891cf8d04454 2/17/2014 2:32 PM
db9a70c3-8de0-4b52-b7f2-999da7fa4584 2/17/2014 2:32 PM
ac6c20aa-fd8b-4068-8fee-777fddba34a9 2/17/2014 2:32 PM
86068336-7d23-42de-ae1e-30c58f38ed20 2/17/2014 2:32 PM
da68f0b9-1b9f-4fc6-b16d-1f7b3e57a111 2/17/2014 2:32 PM
a5a07386-14fb-44e3-aabe-2dcf350980f8 2/17/2014 2:32 PM
3f447cee-1105-416e-9b66-163fcb2f25fb 2/17/2014 2:32 PM
968c04e0-00bd-4489-8ac3-13e2100b0f70 2/17/2014 2:32 PM
84a12490-7aff-43a3-8b18-e596eef73ece 2/17/2014 2:32 PM
8f5bc390-2805-41df-8d60-48c2b6b61816 2/17/2014 2:32 PM
088af5c3-ec72-47a6-be3e-5635daf4bd7c 2/17/2014 2:32 PM
30f469f8-4802-4708-ad13-01b0f69a5087 2/17/2014 2:32 PM
33080078-0b63-4db7-8f06-0ae2547e8118 2/17/2014 2:32 PM
f03a4616-d0bb-41a6-b322-b5edfbaaede8 2/17/2014 2:32 PM
577bb1ab-2f33-4707-b3f5-a89fab3ecdfb 2/17/2014 2:32 PM
e05818d0-59b2-4e32-aa85-88a76401a12c 2/17/2014 2:32 PM
0d6c09fa-bc59-438a-b306-7775f4339846 2/17/2014 2:32 PM
95d256b1-f1d2-4443-99f1-2373246e2c40 2/17/2014 2:32 PM
fa943610-9b45-4e01-ba2e-137fff6b0278 2/17/2014 2:32 PM
1d918c94-c13e-4e1b-89f6-6931e0aa99a8 2/17/2014 2:32 PM
b7a0218c-de80-4a2f-9aea-8df9bda565fe 2/17/2014 2:32 PM
9b9d142f-e411-4529-840d-b0ad9bae57e6 2/17/2014 2:32 PM
cbdc8180-d488-4a74-954a-2b209954cee9 2/17/2014 2:32 PM
b0d7cb88-4f57-4650-8863-d085d7eaa255 2/17/2014 2:32 PM
fc56f033-1b12-4588-8ffb-8742245d8e0b 2/17/2014 2:32 PM
603c27c7-d40e-45bb-8a23-85cd5e3ad974 2/17/2014 2:32 PM
03778c8d-1e07-4532-a692-cc13200c9bd8 2/17/2014 2:32 PM
e8a1bcbd-9109-48a3-9d4b-7ad2c66ba12f 2/17/2014 2:32 PM
5c063da2-6949-44cf-9f8a-12d45e41b053 2/17/2014 2:32 PM
6758ff53-9c38-472f-83b0-466c7d38080a 2/17/2014 2:32 PM
a252f676-f745-415b-b640-5eb8df5cbc6d 2/17/2014 2:32 PM
a0ffc786-3e64-4d41-8518-1545ec39ca90 2/17/2014 2:32 PM
922ea6d5-6204-4a10-8208-68dddef1afcb 2/17/2014 2:32 PM
8bf8a1b9-33ce-48df-9f73-36d09da7d3b2 2/17/2014 2:00 PM

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!

Firefox.exe - Application Error Ox6bea400c referenced memory at Ox702b2260; memory could not be read. I received this message when exiting windows after previously using Firefox.

Application Error Ox6bea400c referenced memory at Ox702b2260 that memory could not be read. This just recently started happening and only appears when I'm shutting down windows.

Sometimes a problem with Firefox may be a result of malware installed on your computer, that you may not be aware of.
You can try these free programs to scan for malware, which work with your existing antivirus software:
* [http://www.microsoft.com/security/scanner/default.aspx Microsoft Safety Scanner]
* [http://www.malwarebytes.org/products/malwarebytes_free/ MalwareBytes' Anti-Malware]
* [http://support.kaspersky.com/faq/?qid=208283363 TDSSKiller - AntiRootkit Utility]
* [http://www.surfright.nl/en/hitmanpro/ Hitman Pro]
* [http://www.eset.com/us/online-scanner/ ESET Online Scanner]
[http://windows.microsoft.com/MSE Microsoft Security Essentials] is a good permanent antivirus for Windows 7/Vista/XP if you don't already have one.
Further information can be found in the [[Troubleshoot Firefox issues caused by malware]] article.
Did this fix your problems? Please report back to us!

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,

Reports 3.0 "Memory could not be read" error

Similar Messages

Maybe you are looking for