cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Creo 2.0 M010 corrupt files when save drawings with hatch view

pburtsev
7-Bedrock

Creo 2.0 M010 corrupt files when save drawings with hatch view

Hello everyone, sorry for my english. I have a problem with Creo 2.0 M010.

I have assembly model. When i create xsec in assembly i can save it, but when i create a drawing with hatch view and save it, creo shows me a error dialog "fatal error, information in traceback.log file". After this manipulation my assembly file are corrupted, and i open previous version.

If i create simple part model with xsec and paste hatch view in drawing - creo will be able to save it with no promlems.

 

Traceback.log

-------------------------------------------------

The datecode is: 2012130

The pro machine type is: x86e_win64

The process ID is: 3832

-------------------------------------------------

Exception EXCEPTION_ACCESS_VIOLATION has occurred in the thread 3924.

Main Thread 3924

=====================

0x000000014019C33C NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x103, 0x103, 0x64287c0, 0x64287c0 )

0x00000001421F15A5 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x0, 0x90bc19, 0x229953f8, 0x372725d0 )

0x0000000142F2B904 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x218c7d80, 0x36155178, 0x36a288c0, 0xffffffff )

0x0000000145480125 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x218c7d80, 0x45480090, 0x36a288c0, 0x4592e96c )

0x00000001458D19F0 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x1b189cb8, 0x0, 0x0, 0x0 )

0x00000001458D43EA NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x36a288c0, 0x1b189cb8, 0x0, 0x0 )

0x000000014548488C NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x36155178, 0x1b189e80, 0x0, 0x7 )

0x000000014548739B NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x0, 0x44b69650, 0x326dc118, 0xf04c933a )

0x0000000145488038 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x326dc118, 0x36155178, 0x90c1d0, 0x0 )

0x0000000142F2BBD4 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x2, 0x36155178, 0xffffffff, 0x1878 )

0x0000000142F2BC5C NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x1960, 0x8, 0xffffffff, 0x326dc118 )

0x0000000145472449 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x36155178, 0x0, 0x24, 0x3662b5e0 )

0x00000001454CA7D8 NULL (NULL:0) (xtop:0x000000013F5B0000) ( 0x0, 0x0, 0x0, 0x0 )


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
3 REPLIES 3

I have not run across a section error yet with Creo 2.0 M010. Usually, if a drawing has problems with a section you get a warning and the view fails, but never a fatal error.

Please report this to PTC Support. You need to submit the part file(s), assembly file, and drawing file. If you can also provide the tracking file, that is even better. Customer service told me they could do very little with the traceback.log file alone.

Errors when creating sections are common, but usually not fatal. I have reversed the section viewing direction and this would solve sections not drawn correctly.

Have you found solution for this problem? I am facing same problem.

mender
12-Amethyst
(To:gprajapati)

While the problem that originally started this thread was likely fixed a year or three ago, if you are facing an issue of crash on save that appears to depend on having a particular view in your drawing, try setting config 'save_drawing_picture_file no'.  Normally we store a picture of all sheets of the drawing along with it, so you can see it in Preview, etc., and turning that off skips that step, which from the description is likely the work we are doing at the time.

While that can be a workaround, I'd definitely advise making an SPR for it, to get whatever is going on in your case fixed.

Announcements


Top Tags