Skip to main content
S
sbhattacharya-21-Visitor
1-Visitor
January 26, 2017
Solved

How can I recover unsaved Parts and assemblies in exact form after Fatal Error?

  • January 26, 2017
  • 4 replies
  • 20870 views

Dear all Creo Users,

Sometimes I encounter fatal error in creo after some repetitive failed attempt of selecting or some unknown reasons. I have used the searchbar and searched the ptc community for fatal error topic and find that some experts are saying about traceback. What are tracebacks? Are these trail files? Can it help to recover part,assembly files?

How can I recover my parts and assemblies and drawings in exact form after this error occurs. Usually ptc creo software completely shuts down after I click ok on fatal error.

Any suggestions, ideas, discussions regarding this will be helpful.

With regards,

Soumya

Best answer by cgorni

To close this community thread on Recovery of unsaved parts and assemblies after a fatal error

 

Summary of the exchanges and list of solutions:

  • As indicated in different replies, and article CS149125 , Creo does not create temporary files, therefore only the version of files explicitly saved can be reopened: 
    • So try to save on a regular basis.
    • Depending your configuration (option last_session_retrieval set to yes) you may get a Retrieval popup that can help getting the list of objects that were in memory, at the moment of the crash, but not at the unsaved states they were.
  • Traceback.log files contain the latest functions and libraries loaded when the program stopped, and could help PTC understands if you matched a known issue, see article CS49550
  • Trail.txt.# files may be used to replay the Creo session if the initial conditions of the previous session can be reset, see thread or article CS162905
  • If working connected to Windchill and the crash corrupted your Creo local cache you may review article CS104751
  • Also note that Undo - Redo actions are not available across different Creo sessions, or after an object is saved

4 replies

S
23-Emerald III
StephenW23-Emerald III
23-Emerald III
January 26, 2017

Unfortunately the solution to recovering unsaved work is to save more frequently!!

Traceback error log is a code that program generates that PTC can use to diagnose the problem. It is generally not for the user.

Trail files can sometimes be used to recover lost data. It's not necessarily easy. See Re: trail file for some help.

    T
    TomD.inPDX17-Peridot
    17-Peridot
    January 26, 2017

    There is an old adage I learned from CAD interaction... and other programming functions from day one...

    "SAVE WHEN YOU THINK ABOUT IT!"

    If your brain pops this up, SAVE!

    Creo is very dependent on everything in memory.  It would have to write that image to recover correctly.

    In many ways, it is better to back-step to the last known good save/interim save.

    Good thing is that this really doesn't happened too often.

    Once you get use to commands, you tend to trip up the system less.

    So if you are embarking on something that you are less than comfortable with, save.

    I am more than convinced that the user interaction has more to do with crashes than actual software bugs.

    If you can reproduce a crash even, PLEASE report it.

      S
      sbhattacharya-21-VisitorAuthor
      1-Visitor
      January 26, 2017

      Hi all,

      But after anyone save a part in creo he looses undo option. Undo option seems invisible after saving.

      Any idea to get rid of this?

      With regards,

      Soumya

      S
      23-Emerald III
      StephenW23-Emerald III
      23-Emerald III
      January 26, 2017

      Lose one step of work or lose all the work...doesn't seem like a tough option.

      There is a product idea for undo (actually several product ideas)

      Make UNDO actually undo across all of Creo

        C
        cgorni16-PearlAnswer
        16-Pearl
        January 12, 2022

        To close this community thread on Recovery of unsaved parts and assemblies after a fatal error

         

        Summary of the exchanges and list of solutions:

        • As indicated in different replies, and article CS149125 , Creo does not create temporary files, therefore only the version of files explicitly saved can be reopened: 
          • So try to save on a regular basis.
          • Depending your configuration (option last_session_retrieval set to yes) you may get a Retrieval popup that can help getting the list of objects that were in memory, at the moment of the crash, but not at the unsaved states they were.
        • Traceback.log files contain the latest functions and libraries loaded when the program stopped, and could help PTC understands if you matched a known issue, see article CS49550
        • Trail.txt.# files may be used to replay the Creo session if the initial conditions of the previous session can be reset, see thread or article CS162905
        • If working connected to Windchill and the crash corrupted your Creo local cache you may review article CS104751
        • Also note that Undo - Redo actions are not available across different Creo sessions, or after an object is saved
          Terms & ConditionsCookie settingsAccessibility statement