I was recently trying to link Revit models to a federated file on Revit 2021. The models were failing to link, but no error message or warning was provided. The federated host model and the links were all initiated and ‘live’ collaborated models on the Autodesk Construction Cloud.



I had previously used this method ( Moving the Revit BIM360 CollaborationCache Folder to a Secondary Hard Drive ) to move the cache for BIM 360 / ACC Docs to a secondary hard drive. Windows Explorer showed this hard drive was essentially running out of space. So Revit was failing to link the model, but wasn’t providing a ‘insufficient hard drive space’ warning.

But why was the hard drive filling up?

I reviewed the files and folders and discovered that one particular program was generating massive log files:

The final resolution was quite simple – delete the massive log files, and then the files linked to Revit fine. I used 7-zip with the “Fastest” and “Delete files after compression” option to archive and delete those logs.

To future-proof this scenario, I’m considering writing a Powershell script to detect and possibly archive and delete the existence of massive log files.

Let’s say you get half way through extracting a very large (like 15gb) archive and for some reason the extraction fails.  For example, the BDSP 2013 media I downloaded had one RPC file corrupt, and the Adesk extractor failed to push through that problem.

7-zip is not only more robust, you can also “resume” a failed extraction attempt by using some switches:
-aos (skips files already there)
-y (prompts yes to every question)

The whole command looks something like this:
7z x {archive_name_and_path} -o{target dir} -aos -y