Hi,
I am getting an error when trying to nest a generic model into a curtain panel family in Revit 2015. When trying to load it in, i get an error that says "Last type in system family 'Stacked Wall' cannot be deleted." Which to me makes no sense
has anybody else come across this error? any solutions?
Thanks,
Paul.
I tried creating a new Curtain Panel family, loaded a new Generic Model family into it, and then loaded the new Curtain Panel family into a new project without error.
Do you see this error if you start with new families (and project)?
If not, the article Tools for Troubleshooting Unexpected Behavior in Revit might help in finding what is different.
If you see the same issue with new files, then you may be going through different steps (from what I did). A Screencast video (or a video from another screen recording utility) would help us to understand the specific steps you are going through.
did you ever find a solution to this issue? we are seeing the same error when trying to insert a plumbing fixture into our project. thanks
First, make sure that Revit is updated (UR5).
If the project or family was upgraded from a prior version, try getting a copy of the prior version family file, and upgrade it in 2015 using the Audit checkbox. Once this is done, try loading it into the family.
If that doesn't work, take a look at the journal file recorded when loading the family, and see if there is additional information on what is happening.
Update RU5 seem unable to resolve Revit 2015 Error 'Last type in system family 'Stacked Wall' cannot be deleted'. This seems to remain a big big bug for those using Concept Mass RVT family for loading into a RVT Building Project.
Discovered a work around for this when trying to load an air terminal framily.
Created an Air Terminal family and when I tried to insert it into the job project we were working on I got the same error - "Last type in system family 'Stacked Wall' cannot be deleted."
Here's the trick I discovered...
A bit long winded but if you are looking to only load a type or two into the project could save some time.
maybe this?
in Project Browser go to families\walls\stacked wall and try to delete the last type manually
if you successed? try to reload your modified family.
Moshe
At this point we are up to UR7.
If you are continuing to see this with the latest updates, can you reply with a Screencast video (or a video from some other screen recording utility) showing the steps you are going through, and a small sample file (so that we can try reproducing what you are seing)?
Lance,
I'm having the same problem. See attached family. The problem happens whether I use a new empty project or our company template or the actual project for which I made this family.
After creating the family and discovering the problem, I opened this family with the Audit button checked, purged the family, and resaved.
I have loaded it into each of these projects by using the "load into project" button in the family.
I have loaded it into each project by using the "load family" command in the project.
I get the same error.
I'm not making a screencast as there's only one step involved in each case.
Thanks for your help,
Judy
Could someone having this issue post a screencast of the process from start to finish (including what family and project files are being used) and attach the problem files to the post so we can try and replicate the problem. i have tried to get the same error but all of the above explanations work perfectly fine for myself.
Would make it much easier to see the issue
Thanks
Here's a video for what it's worth:
https://screencast.autodesk.com/main/details/2ffb2c9f-bd43-4d51-a84f-4576779e51ec
and the file attached.
2015 - UR6
It looks like the following elements (in the family) are leading to the error:
558659, 558661,558663, 558665, 558665, 558669,558667, 558671, 558673, 558675, 558678, 558678, 558682, 558684, 558686, 558688, 558680, 558667
If you select these elements and delete them, the family will then load into the project (at least on my system Revit 2015 UR7 R2).
Thanks, that works for me.
Appears to work in all our troublesome families so must be somthing breaking when we update.
Anyway of knowing what those elements are?
If you select them individually, the properties and contextual ribbon panel will give you some information on the selected element.
I recall seeing some Analytical elements when selecting individually.
Afternoon Lance
I appear to be having the same issue regarding importing a block I created into the architectural template. The block imports ok into the electrical template but could you please advise on how we find the corrupt element numbers as you did previously?
I have attached the file for you to review.
Kind Regards
Garry Carter
I had a look at your family. I get the same error (Revit 2015). Loading it into my architectural template gives the stacked wall error. Loading it into a clean electrical template seems to work.
I tried deleting all the components (extrusions, annotations etc) from the family and still received the same error.
Loading a new electrical fixture template wall based and copying all the items (extrusions, voids, annotations) to that template and then loading it into a project did not give me an error anymore. Give it a try and see if it works for you.
Maybe there is a small glitch in your family which causes the error which can be solved by transferring it to a new template..
Louis
Please mention Revit version, especially when uploading Revit files.
LANCE, RESPOND TO MY OTHER MESSAGE! THIS IS NOT THE KIND OF SERVICE I EXPECT FROM AUTODESK.
The element IDs were listed in the journal file recorded by Revit.
The particular line of interest was the following (in this case the Element ID was 558659):
DBG_WARN: Family contains category id -2009630, gstyle type 2, gstyle id 558659. That category id and gstyle type map to a gstyle id of invalidElementId in the project.
Note: When I tested this again, I only saw one element listed, but after removing this one and retrying, the others were recorded in the journal. You may need to remove elements, retest, and review the journal again if the error continues.