Announcement

Collapse
No announcement yet.

Non-Editable Workset:

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Non-Editable Workset:

    Good Afternoon all,

    Has anyone out there seen this error before?

    Non-editable workset 'Family' error message.JPGNon-editable workset warning.JPG

    I am trying to purge a file and this pops up when the purge operation is complete. I have no choice but to cancel the operation when it's complete and thus not purging the elements I want to purge.

    I have seen a fix posted on AUGI that involves a dedug.ini, but it doesn't seem to be working right now...

    Any ideas?

    #2
    I believe the fix with debug.ini does not work or only works for some elements with 2011. On the projects I have had the problem, I have simply selectively purge ununsed items rather than just purging all.

    You should be able to obtain the element ID with the error warning and get some idea of the element causing the problem, it is generally a group or some sort of family with nested elements. Hopefully they can fix this finally with the upcoming 2012 release!
    Revit BLOGGAGE

    http://www.revic.org.au

    Comment


      #3
      Originally posted by Ben-May View Post
      I believe the fix with debug.ini does not work or only works for some elements with 2011. On the projects I have had the problem, I have simply selectively purge ununsed items rather than just purging all.

      You should be able to obtain the element ID with the error warning and get some idea of the element causing the problem, it is generally a group or some sort of family with nested elements. Hopefully they can fix this finally with the upcoming 2012 release!
      We had to send a file to Autodesk to have this fixed. They disabled worksharing to fix the problem so we had to restore worksharing and all workset settings when we got the file back. Not ideal.
      Bruce McCallum
      Principal
      Next Architecture

      Comment


        #4
        Thanks for the responses guys. I was afraid this was the case - that it is not working for everything. The problem is defiantly isolated to a group. We have been able to work around it a bit, by trial and error and ungrouping / regrouping etc.... It's not pretty. Sending the files off would be nice, so it can get fixed, but we can't wait - even for a day. Hopefully we see this fixed. What a PITA!!!

        I really wish I could understand how this happens in the first place so we can make some provisions to avoid it. Maybe it's group management techniques?

        Comment


          #5
          In my post above I mentioned that Autodesk disabled worksharing to fix this problem. In 2012 we have the ability to disable worksharing ourselves so we should be able to fix these problems in-house.

          Has anyone tried? I've got a couple files with this problem and will test on 2012 when I get a chance.
          Bruce McCallum
          Principal
          Next Architecture

          Comment


            #6
            Let's hope so Bruce. I will test it out on our end too, and post if we come up with up anything.

            Thanks.

            Comment

            Loading...
            Working...
            X