Component in rollback state; assembly is inaccessible now.

Really weird... The assembly has a mirrored sub-assembly. I then opened the
original, un-mirrored subassembly and added some parts. SW wouldn't let me
back into the main assembly, complaining about a component in rollback
state. Couldn't close the main assembly, and couldn't exit SW. I had to kill
it from Task Manager.

Any idea what's going on? It's one thing to not update the mirrored
subassembly, but it shouldn't invalidate the main assembly. It's fine after
restarting SW, but missing the new parts on the mirrored side. It sure would
be nice if SW would track things like this, maybe track the mirror as a
configuration rather than a separate assembly.

In general, how do you make best use of mirrored components and assemblies?

 

I have started using a technique that a guy here showed me. It isn't
automatic, but not bad.

Create the assy that has the parts mated as you wish. Then in that assy,
intelligently mirror the desired parts, deciding what needs to be mirror
parts, and which are instances, and fix them. Now add a new config (other,
mirrored, etc). In the main config, suppress the mirrored parts, and in the
other config suppress the original parts.

The advantage of this method is that it's fairly quick and usually the assy
with the mirrored parts fixed in it can then be used in the parent assy as
is by changing the config - the mates probably still apply properly, or at
least mostly.

The down side is that if you make changes to the original parts, you have to
remirror them - they don't update. But it only takes a short time to do it.
I've tried it a few times and it's not a bad method.

WT

 

I just got the same message after editing a sub assembly. Very
straight forward, no mirrored parts. I had to open some of the
components of the sub ass'y, move the roll back bar up and down again,
then save and close. I then regained access to the assembly.
I remember seeing this back around 2001 but have never seen it again
till now.