Having a miserable time with this upgrade...

[petervanko]

I am floored by how hard it is to upgrade the software if worksets and shared coordinates have been established. I get errors galore, and dialog boxes that keep telling me to open anothr session of Revit becasue some of our users need to relinquish all worksets. I mean...what a pain. Why can't one just open the central file with the new version and"SAVE." Then, users open their local files with the new version and "SAVE." What in the world is going on??????

[Elmo]

There is nothing wrong with doing what you just said. Go ahead and open the Central File and get your users to create new local files.

[petervanko]

But it won't even allow me to save it because of its dependencies.

[patricks]

dependencies? I open project central files all the time that were last saved in an older version and then I save it in the new version. I've never had a problem.

[patricks]

That message is saying that you have other files w/ worksets linked into that file, and you need to open those other files and relinquish all worksets in those files first. Makes sense to me, even though we don't really link other Revit files very much and so we've never run into that.

[petervanko]

I only wish it was that easy. I've done that and no luck.

This is an absolute joke and a nightmare. I can't save, can't move forward. Boo

[patricks]

So you are opening the linked files, saving and relinquishing so that it is upgraded to the new version, and then do you update your links in the other file?

[petervanko]

Yeah, that's pretty much it. I've gotten rid of those warning dialog boxes...it just demanded a few gutsy/scary steps.

1. open central file and do a SAVEAS right there, overwriting the central file immediately
2. notify each user to open the newly upgraded central file and make their local copies acordingly
3. open all linked central files and do the same for each.

Ok, I'm out of the woods, but this might have been my most stressful morning with Revit yet. Super scary...I just imagined myself having to limp to the partners, telling them how this high-profile Revit project just tanked because of an upgrade they just paid for.

Nonetheless, I thank you for your help, and my apologies for my frustration...

[david.metcalf]

Peter,

Thanks for sharing that information.

David

[Wes Macaulay]

Another thing you could have tried is opening the central file and choosing Detach from Central so that you are really free and clear from everything. Then off you go. Do that for all your "worksetted" files...

[dbaldacchino]

Ok, that error you're getting has been termed by Autodesk as a "harmless error message that will be taken off in a future version" (filed SR a few months back on this). I don't know the specifics as to WHY this error comes and goes. We got that throughout the project where we had an RB9 file linked into an RS3 file and vice versa. Sometimes it disappears, sometimes it comes back. Notice that it just has an OK button. In my projects, there were instances where RS users would get the message and RB users wouldn't, and there were cases where the inverse was true. And at times we both got the message (each party would get a message including the linked file name of the other discipline). Running an audit and re-saving didn't help. So don't stress out about it, because it WILL reappear on you. Just click OK and chill :)

[ajayholland]

OK – Here’s an explanation for the warning and a procedure that, to my knowledge, has not been documented anywhere.

Ever wondered what the “Local Alias” is for?

When using worksharing, the common procedure for linking files is to establish a direct link to another shared central file. The problem arises because with shared positioning, a user does not necessarily have “permission” to modify the Project Info settings in the linked central file.

When a link is established to a local copy of the shared file, Revit automatically creates a link to the central file. Notice that in the "Share Coordinates" dialog for the linked file, the coordinate information is passed directly to the central file.

If the warning dialog said, “Reload a local copy of the link in this session” there would probably be less confusion.

The limitation to this procedure is that, when users make new local copies of the central file, the file path to the local copies of the linked files must be re-established.

~AJH

[dbaldacchino]

Jay, in my experience, the error mentioned in this thread occurs with linked central files and is an intermittent error. It comes and goes....sometimes it pops up on the screen of the structural guys, others on the screen of architectural.....or both (assuming those are the only linked models in the project). And at other times it goes away for a while, and all this without either group ever moving the link in any way (and we never linked locals). I'm not sure I'm understanding your post.