-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The model could not be opened: Data in file an unnamed file is corrupt and needs to be manually recovered. #35
Comments
Hi @alexberd That is really odd. At first I thought it might be a combination of local file, detaching from it and upgrading, but I just setup a quick test of that scenario and I didn't have any issues. Is it possible to share that project file (or a stripped down project file that still exhibits the issue?). The element schema exception does look like a problem but it may not be the cause of this issue. |
Many thanks for your message Dan! I will provide a stripped down version of the project file shortly. |
Hi @DanRumery |
Thanks Alex. I was able replicate the issue (when upgrading that file from 2017 to 2018). I then wrote a simple addin command that uses the Application.OpenDocumentFile() function from the Revit API to open the file in Revit 2018 (i.e. without RBP). Strangely the same error occurs! That is, this appears to be a Revit API issue rather than an issue with RBP alone. I may post this issue to the Autodesk forums as it seems to be a bug in the Revit API. It doesn't occur if manually opening through the UI as you say. What's puzzling is why this particular file has this issue (I've never encountered it upgrading other files before...) |
@alexberd Ok so I've found a known issue on the Autodesk Revit forums. There is an explanation of the cause and a workaround mentioned there: Since this is a Revit API bug there isn't anything I can do for that unfortunately. |
@DanRumery, Many thanks for your time checking this issue! |
@alexberd I wouldn't think you'd need to recompile as the only place the VendorId exists is in the addin file(s). Is it possible that some other 3rd party addin (with a VendorID other than 'ADSK') that uses Extensible Storage has been used at some point while working on that model file? I think the fix worked for the user in that forum because the addin that created the Extensible Storage happened to have 'ADSK' as its vendor ID. So you'd have to figure out what addin created it in the first place (which is probably hard to figure out) and use its VendorID when upgrading. |
I receive the above error only when upgrading Revit 2017 Model to Revit 2018 by the use of Revit Batch Processor.
When upgrading the model by native Revit, it works fine!
I also checked the journals and found the following lines at the end of the journal file.
I don't really understand the "d:\ship\2018_px64\source\revit\revitdb\gensrc\Element.gen.cpp" part of it.
Would be really grateful if you could provide any help.
Regards.
The text was updated successfully, but these errors were encountered: