Skip to main content
K
Kevin761-Visitor
1-Visitor
January 11, 2018
Solved

Creo 3.0 M140 Crashing on Drawings

  • January 11, 2018
  • 1 reply
  • 6975 views

I currently have a problem working in some drawings, that a colleague with an identical machine does not have.  I open a drawing and can move text, move views, etc with no problems.  If I attempt to edit annotation or open the properties window of an annotation, I will crash with the fatal error message.  Like I said, I have asked a colleague to try, who has an identical computer as mine, and they can do whatever they want with the drawing and do not crash.  I am thinking this is a JAVA issue, but we even have alike JAVA Versions.  I have even tried a new workspace and gotten the same results.

 

Can anyone offer me some advice to troubleshoot this before I open a ticket with PTC?  I have read through some other likewise threads, and tried the graphics opengl and win32_gdi, with no change in issue resolution.

 

Kind Regards,

 

Kevin

Best answer by StephenW

My go to answer on this is (do each one separately):

1. re-download the files (in windchill, make a new workspace), make sure you don't have any of the files in on your startup directory

2. remove the config.pro completely and start creo and try again.

3. try opening the assemblies/parts first, before the drawing

 

1 reply

S
23-Emerald III
StephenW23-Emerald IIIAnswer
23-Emerald III
January 11, 2018

My go to answer on this is (do each one separately):

1. re-download the files (in windchill, make a new workspace), make sure you don't have any of the files in on your startup directory

2. remove the config.pro completely and start creo and try again.

3. try opening the assemblies/parts first, before the drawing

 

    K
    Kevin761-VisitorAuthor
    1-Visitor
    January 11, 2018

    Stephen,

     

    Thanks for the suggestion.  As a general practice, I never store anything unnecessary in my startup directory and I always open the assemblies/parts before the drawing....old school practices I suppose. 

     

    As for the fix, once I moved my config.pro to a location that the software wouldn't find it during startup (took 3 tries and putting it on a folder on another server), that seemed to be the fix.  This concerns me though, as being the System Admin, everyone else is using a copy of my config.pro (with their modifications of course, it's just a starting place for everyone), yet my colleague didn't have the issue that I did.  Well, when it starts happening for him, at least I will know where to start.

     

    Regards,

    Kevin

    S
    23-Emerald III
    StephenW23-Emerald III
    23-Emerald III
    January 11, 2018

    So occasionally something can "sneak" in to the config that you didn't really mean to put in.

    My normal troubleshooting for the config is to remove 1/2 of the config and then try again. If the problem is in that 1/2, you will see the failure. If not, try the other 1/2. I keep cutting it in 1/2 until I get down to just a few and then look for the most likely culprits. Usually goes fairly quickly if the problem is really in the config.

     

    Another way is a line by line compare with another users "good" config. Sometimes it works quicker. there are some good line by line comparison programs for text files but I can't remember any names right off hand.

     

    Good luck

     

     

    Terms & ConditionsCookie settingsAccessibility statement