The error message happens when the folder being restored to did not have the same UID VALIDITY as the original folder - ie, it is not the original folder. The "is opened" part is just reporting the status of the preceding call to open the folder. So we know that succeeded, but it found the UID VALIDITY is not the same.
But I'm not sure that will help you much.
Also, when you say "restore hangs", do you mean the imsrestore process which reported that error continues to exist but is not doing anything else? If so, please do pstack on it. If not, then exactly what do you mean?
I would also say to look in the default log file around the time of the error.
Yes, the restore has completed successfully, but I my case imsrestore is called throuht imsasm in a networker recover session.
After this message, the session does not terminate, so it seems that the recover was not successful.
Maybe the networker is confused about that error message.