Internal Error NX6.0.3.6

[solution58]

John,

Getting a lot of error notices trying to split, trim, subtract, unite, file becomes corrupt, can be exported as a Parasolid, brought back into NX6 into a newly created file and still not work, working in history free mode,the file is now corrupt, imported older versions of UG, non native translated data seems to be the problem, no sure at all though, no issues if parasolid or translated data imported into NX5.

Thank you
Hans

 

[JohnRBaker]

Please contact GTAC and get samples of files so that our development people can track this down. If it truly is related to legacy or imported non-native data, it will be very difficult for our people track this down without actual sample files, so please do not waste any time.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[JohnRBaker]

There's two other things you could try. First go to...

File ->Utilities -> Part Cleanup...

...and set all the options and repeat a couple of times. If that doesn't help, try...

File -> Export -> Heal Geometry...

...as this will eliminate any very small faces and edges and other 'tiny issues'. Note that the results will be an unparameterized model not unlike what you get when you did the Parasolid Export/Import, only in this case it will attempt to fix bad geometry.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[hudson888]

In a way if you think it could be possible that bad geometry is at fault then performing examine geometry checks would be recommended. There is the problem with the Heal Geometry function that it removes parameters from the bodies, so that while it may function as proof of the problem it may not be the desired fix.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[solution58]

Thank you for all the advice, heal geometry works, part cleanup does not in every case, removal of parameters is a none issue most of the time, we have gone back to 6.0.2.8 on
my lap top and no problems encountered, we will send data to GTAC, i will let you all know the outcome.

Hans

 

[solution58]

Hello John,

Sent data to GTAC, John, i can send you the PR #'s if you'd like, no resolution yet, we were told it needed to go to development.

Everyone at our Company has had lost data due to these errors, in some cases we are unable to open the file again,
we back up every 15 minutes so we are able to retrieve previous files prior to them being corrupted.

Export heal geometry as it turns out does not always work as do any of the other fixing and checking functions.

We export a Parasolid from NX6 and import that into NX5 and the NX5 file will not get corrupted, we can then save it off in NX6.

We will see what GTAC can find, are there any other NX6 users out there that have problems like this ?

Hans

 

[JohnRBaker]

Just post the PR number and I'll take a look, however I'll probably not have access to any files you submitted, but I will be able to read the contents of the PR itself.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[solution58]

PR # 6201079 and 6131949

Thank you John.

Hans

 

[JohnRBaker]

You should be getting an official letter from GTAC in the next week or so as both PR's (which as far as development was concerned covered the same problem) have recently (within the last couple of weeks) been resolved by development and the fix has been implemented in NX 7.0, due for release soon.

I hope this information helps.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[solution58]

Hello John,

Thank you for your help, any idea on the time frame for NX7 release?

Regards
Hans

 

[JohnRBaker]

It will be very soon.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[solution58]

Hello John,

Happy Labor day, we have been told that the 29th of September would be the NX7 release date, we can't wait! we are loosing data at an alarming rate, we have sent more data to GTAC, could you find out if there is a work around for now? we have a tremendous amount of data in NX6 so going back to NX5 is temporary,we have to update the NX6 components and assembly at some point.

One of designers was working Saturday the 5th on a change to a tool and received an Internal error notice and had to start all over, this is very FRUSTRATING.

Regards
Hans

 

[JohnRBaker]

At this stage, with a solution being available in 3 weeks, I doubt if there will be any other fixes made available in the mean time. From my discussion with the people responsible for finding and fixing the problem, it appeared that there was no other solution than what they implemented.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[solution58]

Hi John,

We hope NX7 will fix the problem, if i may ask, are there other users that have encountered this same problem?

Is it an NX6 problem?

We would like to know so we can rule out our internal structure.

Thank You
Hans

 

[JohnRBaker]

We are not aware of any other users reporting this problem, but we do know the cause and it could have happened to anyone under the right circumstances so it's not your configuration, just a bit of bad timing, but it has been resolved in NX 7.0, which will be available shortly.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[cowski]

When we first switched to NX 6 we had various problems with booleans, but the later patches seem to have worked that out. I'm curious to know what the 'right circumstances' are so that we can avoid them. Since the solution is known, will there be a patch for NX6? I ask because after less than a year on NX6, we will probably not jump to NX7 right away (if at all).

 

[JohnRBaker]

Running Part Cleanup should resolve these issues in the vast majority of cases. For the few cases where this does not help, doing a Parasolid Export to an NX 5.0 version of the file and then importing the PS transmit file into an NX 6.0 will generally address those few exceptional cases, which shouldn't be an issue since it appears that the problem only occurs when working in the History-Free mode of Synchronous Modeling.

As for getting a "patch" for NX 6.0, in addition to there being a workaround (Part Cleanup or NX 6.0 -> PS -> NX 6.0), it being fixed in NX 7.0 (the release of which is fast approaching) and the fact that NX 6.0's 'lifecycle' has reached the point where only critical maintenances fixes are being implemented, I don't see that happening.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[ingallspw]

Just an FYI, I have had minor problems similar to what you described, (maybe not a severe) but NX6 always seemed to recover. I had to reboot a few times to get it to stop but if you have worked with a majority of the other high end CAD systems, NX6 is a blessing... at least it keeps running and doesn't just bomb out instantly like others.

Keegan