Memory Error?
Memory Error?
(OP)
Hi Guys,
This error keeps on popping up.
The window's title is "Enter Drafting Application" and the window reads:
"Error recovery completed for the following error: Internal error: memory access violation."
Am I running out of memory needed to run the program at these points? Right now it seems to be happening every time I drag a sketched line on one of my drawings.
Thanks,
Chris
This error keeps on popping up.
The window's title is "Enter Drafting Application" and the window reads:
"Error recovery completed for the following error: Internal error: memory access violation."
Am I running out of memory needed to run the program at these points? Right now it seems to be happening every time I drag a sketched line on one of my drawings.
Thanks,
Chris





RE: Memory Error?
Anthony Galante
Senior Support Engineer
PhoeNX PLM Pty Ltd
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.1.5
RE: Memory Error?
Also after having this type of error, it is wise to save all your parts and do a restart of NX.
Best regards,
Michäël.
NX4+TC9 / NX6+TC8Unified / NX7.5 native
RE: Memory Error?
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: Memory Error?
XP Pro SP3
T7200@2.00 GHz
2.00 Ghz, 2.00 GB of Ram
I'll try the part cleanup as well.
Thanks
RE: Memory Error?
RE: Memory Error?
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: Memory Error?
If you ever get an serious error, especially anything to do with memory you're best option is not to save as there is a greater likelihood of corrupting the file as the data stored in memory could now be damaged. . I received this advice a while back from GTAC in relation to a similar error message. I'll see if I can find more details to post here.
The best option is to make sure you have a backup of your files that are open, then run the part cleanup at least three times with all the options turned on. I even have a journal file that someone wrote a while back that runs the part cleanup 6 times sequentially.
Anthony Galante
Senior Support Engineer
PhoeNX PLM Pty Ltd
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.1.5
RE: Memory Error?
What does sequentially "cleaning" the file actually do? Why does sequential cleaning work?
RE: Memory Error?
RE: Memory Error?
Anthony Galante
Senior Support Engineer
PhoeNX PLM Pty Ltd http://www.phoenxplm.com.au
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.1.5
RE: Memory Error?
If the bug is in the function, no amount of part cleanup will get it to work correctly.
RE: Memory Error?
Basically once you have that error, the likelihood is if you do not close the session down, the error will compound and once you do save the file it could end up corrupted.
The advice was once you saw that error you are best off closing the session down and restarting NX.
As for the part cleanup, the multiple times to run it was to remove groups that might have been nested inside on another. The newer dialogs allow for that, but there were reports that multiple part cleanups does make a difference, so my attitude was with a journal, more than one is worth doing anyway.
Anthony Galante
Senior Support Engineer
PhoeNX PLM Pty Ltd http://www.phoenxplm.com.au
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.1.5
RE: Memory Error?
I do get corrupt parts when NX fails and closes without warning, like with a network/server crash. And indeed cleaning a part multiple times is sometimes necessary.
Still the question remains, why does everbody frequently get this NX memory errors and why does Siemens doesn't fix this issue??????
Best regards,
Michäël.
NX4+TC9 / NX6+TC8Unified / NX7.5 native
RE: Memory Error?
Anthony Galante
Senior Support Engineer
PhoeNX PLM Pty Ltd http://www.phoenxplm.com.au
NX4.0.4MP10, NX5.0.0->5.0.6, NX6.0.0->NX6.0.5, NX7.0.0->NX7.0.1 & NX7.5.0.32-> NX7.5.1.5
RE: Memory Error?
The folks in GTAC are some of the best users of NX you will find anywhere. They know the software and they have extra tools to help diagnose the problems. Also, by logging a call with them, it gets flagged and maybe your one call may be the clue to something that has been bothering the software designers for a while, but they just couldn't put all the pieces together.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli