Pro/E 2001exits - Signal number 11

[harichennai]

Hi all,


ProE 2001 exited prematurely while just browsing in the workspace window.


I use build code 200270 and Ilink 3.2 buildcode 2002270, in a Windows NT work station.


When i see the std1.err file it reads


"RAISING SIGNAL : Signal number : 11"


also the std.out file reads


"type ABS; type ABS; type ABS; type ABS; "


such exits are difficult to simulate, so what is a good option to deal with them?


Is this resolved only by going ahead with next best build code..or can wedo some thing about this with the way of working in workspace and Proe..


Your expert comments are most welcome..


Iam a novice in admin role, the seniors here , please help me out!!





Thanks in advance!
Edited by: harichennai

 

[tazbaby]

We use 2001 and this happens to us too.. It's something that happens when simply rotating a part or creating a simple round.. If proe doesn't like it, it just shuts down. I dont know wether this bug is fixed in WF, but it's something that we have just learned to live with.


Save as often as possible..


If there is a fix for this... id be interested in hearing it aswell.


Taz

 

[conrat]

I called PTC tech support about this very problem. They had me
add a line to the config.pro (I can't remember what it was) which was
supposed to disable hardware acceleration on the video card. The
guy thought it was a video card problem, but it was not. I was
asked what type of system I was using and when I told him it was a
company built PC, he told me they only support approved
computers. I guess HP and Dell have PCs on their approved list.



Anyway, we still have the problem.



The only way I have been able to replicate this problem is to try and
do a copy of a note in a drawing. That is sure to cause Pro/E to
go "poof", with no errorbox and only the "RAISING SIGNAL : Signal
number : 11" error.



Also, I do not get the "type ABS; type ABS; type ABS; type ABS; " in the std.out.



I heard this is not as much of a problem in WF2, but unfortunately, we have not yet upgraded.



Jim

 

[FishNut]

We've been on 2001 for quite some time. Most times you never can tell what caused the crash when it is non-repeatable. If you have toolkit apps running it can crash pro easily if they have an error inside them.


As for the crashing going away in WF2 I wouldn't count on it. I have had it crash in testing, and it even crashed at a training course for 2001 to WF2 upgrade, while the instructor was demonstrating with it. Others will tell you it doesn't crash but not everyone uses it the same way. We do mostly sheetmetal, with parts & assembliesthat are pro-programmed to death, and we probably crash more because of it.

 

[conrat]

That is curious. We use Pro/Program and Sheet Metal extensively also. Maybe it is a bug in the Sheet Metal module.



We are not using any toolkit apps. We are exploring J/Link, as 20K for the Toolkit is not in our budget.



Interesting...very interesting.



Jim

 

[james.lynch]

I've come across signal 11 before - nothing to odo with sheetmetal or anything from what I've heard.


one of my mates used to wirk for Rand when they handled tech suport - he said that signal 11 simply refers to an error which PTC cannot explain and covers almost all nonrepetable unexplained exits!





bit of a bummer eh?


James

 

[Dell_Boy]

Why on earth are you using a build code that is so old. Can you not get
hold of a newer build code to see if that fixes the problem. I didn't
even start using 2001 until well after this build code and though I
can't guarantee a newer build will prevent crashes, it should at least
reduce their frequency.



Officially, the last build of 2001 was 2005030 though I have found an
important bug in that build so I use 2004290 when I need it.





DB



Edited by: Dell_Boy

 

[tazbaby]

we're using 2004290.. But can't get any updates without maintenance.. Infact we've only got that datecode coz of some recent training done through a ptc re-seller..


I still get the crashes...


PS.. I use WF2 at University and there are still plenty of bugs.. which include pro going " poof "


Taz

 

[Dell_Boy]

I get about 1-2 crashes a week and even then, they only seem to happen
after opening and closing a lot of different big top-level assemblies.



Considering I use Pro/E pretty much full time I don't consider it much
of a problem and in 18 years of using MCAD software nothing has been
totally free from crashes and I don't expect that to change anytime
soon.









DB



P.S. I hardly ever lose anything because I save the files very
regularly. e.g. I have developed a habit of always saving part and assemby files before patterning
a feature or components in case the pattern does not work out as
intended.



Edited by: Dell_Boy

 

[conrat]

DB,



I agree that the old adage, Save Early, Save Often comes into play
here. Pro/E (at least as far as I know) does not have an
auto-save so I typically save a lot.



It isn't that we lose work so much as the hassle of having to re-open Pro/E and the time to get back to where you were working.



Just a P.I.T.A.



Anyway, I hope the new WF3 will resolve many problems.



We hope to be up to WF2 by the end of the month and will move quickly
to WF3 once they vet out the initial bugs for that release.



Later,

Jim

 

[tazbaby]

Oops... There it goes again !!..

DB - We run the same Datecode of 2001 and yet mine seems to shutdown several times a day at the moment.. and im talking basic 2 part assemblies, or just rotating a singlepart !!


I save after every feature created.. which is a PITA, but at least nothing is lost..


Beginning to think im doing something wrong !!.. LOL.. oh well...


Taz

 

[conrat]

I doubt it is you, tazbaby.



Go into a drawing, select a note, and click the copy button (under Edit, I think)



Anyway, I get the crash everytime I do this and I know this is not a user error.



Others I talk to can copy notes with no problem, but anyone using our
release gets the crash. It is either a hardware issue or a build
issue.



PTC tech support could nto help.



Jim

 

[tazbaby]

And again..... forgot to flippin save this time

...


Oh.. and to finish off this fab day im having.. i now have to wear clothes the same color as a post-it note!!

.. can life get any worse ??

 

[harichennai]

Hi all,


Taz, LOL !!


Iam sorry, Iam using Proe 2001 date code 2004010. and not 2002270..


But I guess iam not having the "Best Build" of ProE 2001..


I am thinking of updating to best builds like 2004090 or 2004290, What build you guys would suggest , to atleast minimise such exits?


I will update the result in this thread..after updating a better build as suggested by all of you..


Thanks a lot for being very informative..Have a Nice day!

 

[Dell_Boy]

Conrat,



I went into a drawing with build 2004290, selected a note, then Edit
Paste and a Get Select 1 menu pops up in the top right hand corner with
Pick highlighted.



Now what do you do to get it to crash?







DB

 

[Dell_Boy]

See if you can guess the "right" answers to the following questions.





Is ALL your hardware certified or supported for the version of Pro/E you are running.



Is your graphics card certified or supported.



Is your graphics driver version PTC certified. (newer is not always better)



Have you configured your graphics driver for Pro/E.



What OS and Service Pack are you running.



Was the OS a clean install or an upgrade from a different OS



Is the OS a true install or just a generic image loaded by your IT department or non PTC-certified vendor



Is Pro/E installed locally or is it a network install.



Are your working files local or on a network share.



Is trail.txt and regen directory written locally or on a network share.



Is your build code of Pro/E up to date (newer is not always better)



Is your current install of Pro/E an update of an earlier build code or is it a clean or parallel install.



Have you ONLY one Pro/E <loadpoint>\bin variable in your User (and system) path environmental variables.



Have you tried running vanilla Pro/E (No config.pro config.sup
config.win menu_def.pro etc.) to isolate potential problems in these
files



Have you tried win32_gdi instead of OpenGL



Are your partitions formatted NTFS



Are all partitions less than 70% full



Are all partitions reasonably defragmented



Is your paging file(s) bigger than your RAM



Is your paging file(s) fully defragmented



Have you disabled real-time virus scanning



Have you stopped or disabled ALL non-critical processes. Assuming you
are not running the license manager locally; approximate achievable
minimum Task Manager process totals at boot for a workstation are

NT4-SP6a 16 tasks + video + optional mouse

Win2k-SP4 13 tasks + video + optional mouse

WinXP-SP2 16 tasks + video + optional mouse



Have you removed or disabled all non-critical hardware (USB hubs, external hard drives, exotic mice, sound cards, printers etc.)



Have you logged your problem with PTC Technical Support





While it is not essential to have all of these correct, the more "wrong"
answers you have, the more likely you will have an on-going hardware
problem.





DB









Edited by: Dell_Boy

 

[tazbaby]

Mine doesn't crash when copying notes !! and so far nothing has gone wrong... Oh.. apart from the new hard hat to match the high viz jacket n pants !!.. really not impressed !!


You actually can't see the post-it notes when you stick em on the jacket !

 

[conrat]

DB,



I select edit - copy. Select a note. Then, when I click my
middle button to accept, Pro/E goes "poof" and I get the error in my
"std.err" file. We are running build 2002100. I know it is
a bit dated, but we are hoping to be to WF2 by the end of March.



I did call PTC tech support, but when I told him it was a "company
built" PC, he said he couldn't help, though he did have be disable
opengl, which did not fix the problem.



As for your second post, I will look into these items.



It is just a little frustrating, but we know how to avoid it.



One other thing that causes the same error is, if we reorder punches on
an NC Sheet Metal Tape, so that our punch is directly below a supressed
punch, it causes the same crash.



Like I said, I hope WF2 fixes.



Jim

 

[harichennai]

HI all,


The crashes have greatly reduced when i upgraded to build code 2004290..


but,.


I have a proE2001 crash in unix (IBM AIX).. Iam opening a new thread on it...


Thanks all