Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Opening a 2016 Revit model in Revit 2023

3 ANTWORTEN 3
GELÖST
Antworten
Nachricht 1 von 4
curtisridenour
152 Aufrufe, 3 Antworten

Opening a 2016 Revit model in Revit 2023

 

I received a set of as-built model from a client. The mechanical one would not open and give up very soon into the upgrade. The other 3 models i had no issues with. I tried to open it in Revit versions 2018, 2021, 2023, 2025. I got the same warning shown below in each.

 

I followed the troubleshooter to the Autodesk site and tried deleting journal file and turning off the analysis settings. Bupkis. But one of my coworkers was able upgrade and open it with no issues whatsoever???

 

curtisridenour_1-1734104574019.png

If anyone has some insight on this, it would be much appreciated.

3 ANTWORTEN 3
Nachricht 2 von 4
GaryOrrMBI
als Antwort auf: curtisridenour

Out of curiosity, did the other user still have a copy of 2016 (and/or one version to either side of it) installed on his/her computer?

 

I have encountered similar issues with upgrades before and it actually seems to stem from the fact that the first thing that Revit does in the upgrade process is to audit the file... and therein lays the problem, it audits the file using the version of Revit that you are opening it in to determine if the entities within the file (and/or the file itself) are valid, but those entity definitions may have changed considerably in the intervening versions and, without that authoring version being installed on the computer, it can't determine what may have been valid in that older version, only that it is invalid in the current version. The Revit developers seem to have a habit of "leaving things behind" to keep from cluttering up the code base and/or increasing file size which means that they delete those old definitions every couple of versions and leave no path to verify the validity of the entities. So, the very thing that the dialog is telling you to try in the hopes of resolving the problem is actually what is causing the problem.

 

The best way, and sometimes the only way, to get a valid upgraded file is to open and audit the file in it's original version, then perform the upgrade... and, of course, that often isn't possible because we no longer have those old versions. In this latter case all that remains is to send the file to Autodesk for resolution.

 

-Gary

 

 

Gary J. Orr
GaryOrrMBI (MBI Companies 2014-Current)
aka (past user names):
Gary_J_Orr (GOMO Stuff 2008-2014);
OrrG (Forum Studio 2005-2008);
Gary J. Orr (LHB Inc 2002-2005);
Orr, Gary J. (Gossen Livingston 1997-2002)
Nachricht 3 von 4
curtisridenour
als Antwort auf: GaryOrrMBI

The individual has 2019 2021 2023 and 2025 installed.

Nachricht 4 von 4
GaryOrrMBI
als Antwort auf: curtisridenour

In truth it would be nearly impossible for us mere mortals to figure out the matrix of installed versions vs entities in the model of a given version that might be seen as invalid given those possible versions weighed against the version being upgraded to... whew...

 

Always try it on at least one other computer, preferably with a slightly different configuration (it could even come down to a different update/ service pack installed on one that isn't on the other). If that fails, that's where the last resort of opening a support case with Autodesk and sending it to them comes into play :zwinkerndes_Gesicht:

 

-G

Gary J. Orr
GaryOrrMBI (MBI Companies 2014-Current)
aka (past user names):
Gary_J_Orr (GOMO Stuff 2008-2014);
OrrG (Forum Studio 2005-2008);
Gary J. Orr (LHB Inc 2002-2005);
Orr, Gary J. (Gossen Livingston 1997-2002)

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report