Memory Error? 1

[CPaul]

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

 

[Arkance/PhoeNX]

If you can reproduce the error then log it to GTAC. The error can be any one of a number of causes. In. My experience there are so many factors that it's best looked at by the experts at GTAC. It sounds like you can make it happen at will so it will be much easier for them to solve.

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

 

[MickyV007]

This could be caused by a lack of RAM memory, or your part could be corrupt. First of all i would advise you to take a log file (Help--> Nx Log File) and see what it says. Then try a part cleanup, File --> utilities --> part cleanup.
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

 

[looslib]

Also, post your machine specs and the version of NX you are working in.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[CPaul]

system specs:
XP Pro SP3
T7200@2.00 GHz
2.00 Ghz, 2.00 GB of Ram

I'll try the part cleanup as well.

Thanks

 

[CPaul]

NX 7.0.0.9

 

[looslib]

Can be memory if you only have 2GB.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[Arkance/PhoeNX]

Also after having this type of error, it is wise to save all your parts and do a restart of NX.

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

 

[potrero]

@namdaci45,
What does sequentially "cleaning" the file actually do? Why does sequential cleaning work?

 

[cowski]

What's the latest official patch for NX7? Surely it is higher than 7.0.0.9 by now. I'd upgrade to the latest patch to see if it makes a difference.

 

[Arkance/PhoeNX]

The latest and only MR (maintenance release) is NX7.0.1. There will be MPs (maintenance packs) but all the major bug fixing is for NX7.5 so it would be best to upgrade to that rather than update NX7 if you have a choice. @potrero I can't answer why now but I will have a look as I know where I read it and I will post back here.

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

 

[cowski]

Why does sequential cleaning work?

There's no guarantee that it will work.
If the bug is in the function, no amount of part cleanup will get it to work correctly.

 

[Arkance/PhoeNX]

I found the response back re the saving after memory errors.
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

 

[MickyV007]

I never experienced any problems with corrupt parts after getting the NX memory error. But its becoming clear that this error is system independent even more feature/NX version/... independent.
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

 

[Arkance/PhoeNX]

My job is NX support and before that I was a user and sys admin. For about 16 years. I have seen that error be caused by NX, drivers, low memory, rubbish models from other systems, bad modeling practices, lack of modeling standards, crappy hardware, viruses and so on and so on. The error message is a generic one. The cause can be any one of thousands of reasons so the only real solution for anyone who sees that error message is to report to GTAC. As I have said before and I know I will say again if you replicate the problem, log it to GTAC. Even if you can't replicate it, whining about it on a forum isn't going to fix it. Log it to GTAC, that's what people pay maintenance for and it's why GTAC exists. If you don't see it getting fixed, keep the pressure on, because things do get fixed. I can speak from experience on that.

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

 

[looslib]

GTAC is the best source for troubleshooting these types of errors that are hard to trace. They have the resources to do it better than we can be guessing here.
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