What other reasons are there and what is so important that it causes Pro/E to fail to save the assembly that ultimately uses the failed family table item?
Mind that once the family table item is locked and cannot itself be saved, then the assembly can be saved, so it isn't to enforce some synchronization need.