BIM 360 "Linked document is not found" Error

[josh.roth.MEI]

We have been running into issues lately with projects that are in Revit 2021 and are on BIM 360 for some machines where my add-in is installed. When the user opens up the model they get the "Linked document (path.rvt) is not found. The link will be unloaded." error. When they open up Manage Links -> Reload From... The BIM 360 folder is empty.

If the user uninstalls my add-in, the BIM 360 folder contents show back up for some reason.

I use an External Resource DB Server for reloading keynotes (so that I don't have to load from a .txt file), and I'm wondering if there might be something there causing it? If that were the case, though I would think that it would be a universal issue, not just on some machines.

I tried rolling Newtonsoft.Json back to v12 per the suggestion in this thread: https://forums.autodesk.com/t5/revit-api-forum/bim-360-links-issue/m-p/10536461#M57603 but that didn't fix it.

I made an add-in update about a month and a half ago, but these issues seem to have only been popping up in the last week or two. I'm not sure if this is something to do with my add-in or if maybe something with Revit/BIM360 is being buggy. Any ideas?

[josh.roth.MEI]

Bumping this to see if anyone could help out. @jeremytammik do you have any ideas what might be causing this?

[jeremy_tammik]

I asked the development team for you.

[josh.roth.MEI · Accepted solution]

@jeremy_tammik I got a bit lucky and stumbled across the fix. One of these older bundles must have had a conflicting assembly (I'm guessing it was Newtonsoft.Json, based on the previous post with this issue) that caused BIM 360 linking to not work properly. When I cleared these out it fixed the issue.

[jeremy_tammik]

Great! Thank you for letting us know. Meanwhile, for completeness, here is what I discussed with the development team:

This still sounds like a 3rd party component conflict between user’s add-in and Revit, and the component may be different than newtonsoft.json. Do you have a journal? We may also want a problem report, so that we can a record, and add more weight on the need to resolve this issue in  systematic way.

Glad you were able to resolve it yourself.

[josh.roth.MEI]

Jeremy,

Unfortunately we've gone through and fixed all of the users machines that were having the issue, so it may be hard to replicate and get a journal file for this. I will try to track one down and will post here if I can find one, but it may take some digging.

Thanks,

Josh

[jeremy_tammik]

Please don't worry about it if it is any effort at all! You have resolved your issue, and that is the main thing.

[josh.roth.MEI]

@jeremy_tammik Found one! Didn't take me too long, and I'm certainly glad to contribute since I've benefitted so much from your and everyone else's contributions on this forum. Hope it helps!

[jeremy_tammik]

Cool! Thank you for the journal files and your appreciation. Glad we can be of help!