Signal 11 trapped

A user is getting the signal 11 trapped error. and getting out of PDMS again and again..I am sure no user has been expunged...

Wat is the reason behind this and wat is the resolution  !! Pl help

Try deleting all of the user temp files in the %pdmsuser% location. When I get this error this is the first thing I do but, theywill need to setup ther desktop again. Does Anyone else have any ideas??

You might also try doing a dice check on the databases.

Hello,

I've got the same error message, when I've tried to run DRAFT in our standard project (it's dbs are used as references for others projects).

The problem was in the directory hierarchy. This project has empty iso,mac,pic folders and after some cleaning we've delete these folders by mistake and mentioned error started to appear.

After creating empty folders iso,mac,pic everything is fine and Signal 11 is no more showed.

Hope it helps.

Unfortunately I think there are multiple cases where a Signal 11 trapped error can occur.  I have it repeatedly on a model with clean Dice checks, and clean environment.  

In my case I am exporting a model to DGN and there is an element(s) in a stru that causes it to happen.  I can work around it by not exporting that particular stru.  I have DB listed it out, deleted it and ran the DB listing back in and it still occurs.

I still have yet to find the offending element since there are hundreds in this particular stru.  I will post once I find it.

[QUOTE=scottg;9893]In my case I am exporting a model to DGN and there is an element(s) in a stru that causes it to happen.  I can work around it by not exporting that particular stru.  I have DB listed it out, deleted it and ran the DB listing back in and it still occurs.

I still have yet to find the offending element since there are hundreds in this particular stru.  I will post once I find it.

Please send the datal into support, if you can, and mention my name, and I may be able to identify it for you (and fix the bug that it triggers for the next release, whenever that is)

Tim

In my case I am exporting a model to DGN and there is an element(s) in a stru that causes it to happen...

If the "signal 11" goes away with the "HOLES OFF" setting, then I may already have solved the issue in the dev version (not yet released) but I would still be able to find the element triggering it.

Tim

Good news, Holes OFF works, so you must be on track.  Bad news is I still need the holes.

I was able to fix individual panels (with multiple holes) by dblisting each panel out and running it back in.  Very tedious with the number of panels.

What's interesting though is if I dblist out the frmw, stru or zone it does NOT fix the problem...???

FYI - this part of our model originally came from Tribon.

I did as you advised and entered a help ticket (through AVEVA - US) with a request to have you copied.

We found this happened in Draft, sometimes it helped to move any section/cutting planes, holes off would also indicate that the Draft software is having graphical problems. Deleting and re-building wont change the cutting plane that maybe slicing something it cant handle, sometimes as little as 1mm will help.

HTH
Matt

[QUOTE=scottg;9901]Good news, Holes OFF works, so you must be on track.  Bad news is I still need the holes.

I was able to fix individual panels (with multiple holes) by dblisting each panel out and running it back in.  Very tedious with the number of panels.

What's interesting though is if I dblist out the frmw, stru or zone it does NOT fix the problem...???

FYI - this part of our model originally came from Tribon.

I did as you advised and entered a help ticket (through AVEVA - US) with a request to have you copied.

I found that to many holes on a PANE or SCTN will make PDMS crash on the next element it is trying to export.