When a recent update to Autodesk Desktop Connector forced a migration to Autodesk Docs, file paths were generally change like this:

FROM – C:\Users\USERNAME\BIM 360\YOURFOLDERS

TO – C:\Users\USERNAME\ACCDocs\YOURFOLDERS

 

If you were doing some interesting tricks with BIM 360 Docs, and sharing and federating Revit models as non-initiated files on BIM 360, you may find that links were broken and “Not Found” in Manage Links after that latest Desktop Connector installation.

 

But don’t worry! You can just set a symbolic link to point from the old BIM 360 Docs location, to the new location. The Command Prompt script looks like this:

if exist "C:\Users\%USERNAME%\BIM 360" rename "C:\Users\%USERNAME%\BIM 360" BIM360.old
mklink /d "C:\Users\%USERNAME%\BIM 360" C:\Users\%USERNAME%\ACCDocs
Run these commands to fix links Not Found

The moment after this script was run, I was able to hit Reload from Manage Links in Revit and the new location was detected and links were loaded successfully. Note that they still appear in Revit as if they are in the old location, but really it is reading the latest data from Autodesk Docs, and that new location is being updated by Autodesk Desktop Connector.

Related Note:

I had already setup a symbolic link to move my BIM 360 Revit Cache folder to a secondary hard drive.

At this stage it appears those links are still working, as the Revit CollaborationCache is a different technology to the simple file sharing mechanism of Autodesk Docs.

Try this first:

Using the latest installation file –

  • Uninstall Autodesk Desktop Connector
  • Restart
  • and then re-Install Autodesk Desktop Connector
  • Login with your details

Did it launch?

Other things to try:

Logout from Autodesk services prior to starting Desktop Connector. You can do this easily with the sign out option at top-right of Autodesk Desktop App.

Through Task Manager – Details, attempt to “End Task” on these. Probably AdskLicensingService.exe won’t close.

Then try to start Autodesk Desktop Connector again from the Start Menu.

You can monitor starting of Desktop Connector in the tray.

 

Other errors that may pop up:

A360 – Service Unavailable

“Requested service not available”

Just try again on this one. You can also check Autodesk Health Dashboard at https://health.autodesk.com/

Previously, this was all working with the old Desktop Connector and b360provider.exe (I think?) but the new versions of Desktop Connector seem to have broken the ability to ‘browse’ C4R Revit models on BIM 360… and guess what? There is no Solution. This functionality is in fact ‘by design’. You can copy and paste a non-C4R Revit model to BIM 360 Docs via the connector, and that RVT will be visible in Windows Explorer. But if you have C4R initialised Revit models on BIM 360 Docs, they will not be visible under the BIM 360 (Preview) node in Windows Explorer. You can only view those C4R Revit files in their folder structure by navigating through Revit 2018.3 or newer.

This is the feedback from Autodesk:

Revit cloud models (C4R models) are not supported in Desktop connector. They won’t be showing up in Desktop Connector. Published C4R models are only available in Revit and Docs.


For C4R models, published models will have all versions in BIM 360. This will be recommended workflow to manage models:
https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2016/ENU/Revit-CAR/files/GUID-AE6DBCDF-3DB1-41CB-9DC5-B0C336E6C851-htm.html

You can also save copies of the model locally to put in your backup system. Also from each user’s machine, C4R cache will be another source of backups. 

Also refer to How to backup Revit cloud models

I went looking for another answer, but there really isn’t one. Below is a list of steps I took to play around with the Desktop Connector installation. In the end, the only way I can foresee being able to ‘automate’ onsite BIM 360 Docs backups will be to leverage the CollaborationCache folder. You will need some Revit API know-how to forcibly populate this through some BIM 360 Reload methods (refer here).  Unfortunately this will be a flat list of files without descriptive names, so there will have to be some workarounds and cleanup scripts in place (we already have a system of BIM 360 file management in VirtualBuiltApp).  I intend to post some more about these workarounds in future.

Keep reading for excessive detail on my Desktop Connector journey …

___________________________________________________________________________________

I used Glary Utilities Uninstall tool:

Entry shown:

"C:\ProgramData\Package Cache\{b46602fe-a358-48c4-a0e0-905010df08e2}\DesktopConnector.exe" /modify

Uninstalled this old version. Interestingly, there were 3 different uninstall processors triggered? Like I had three different versions installed?

 

 

Also tried removing this folder and reinstalling:

I found a pile of errors in the diagnostic logs:

CDX pipleline builder output
Output=Warnings received from AddInStore.Rebuild
========================
Could not connect up a part in a pipeline to its neighbors: AddInAdapter Name: "ISecureSettingsProviderViewToContractAddInAdapter" Location: "AddInSideAdapters\Comet.AddInFramework.DataSourceProviders.ProviderAdapters.dll".

and a few of these

========================
Could not connect 2 valid add-in model parts.
========================

========================
While inspecting an assembly, caught a BadImageFormatException: The file is not a valid binary: C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServices.dll This occurred while inspecting assembly C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServices.dll.
========================

========================
While inspecting an assembly, caught a BadImageFormatException: The file is not a valid binary: C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServicesUI.dll This occurred while inspecting assembly C:\Program Files\Autodesk\Desktop Connector\AddIns\ADriveConnector\AdWebServicesUI.dll.
========================

This note seemed useful:

Starting CDX pipline builder: C:\Program Files\Autodesk\Desktop Connector\Comet.Applications.PipelineBuilder.exe C:\Program Files\Autodesk\Desktop Connector

 

I scanned through the Registry and deleted old references to Desktop Connector.

 

Found this link with the command line switches: here

Tried an install from elevated command prompt:

C:\Temp>DesktopConnector-x64.exe /install /quiet

Note: you do not actually need the Desktop Connector to collaborate on BIM 360 Revit projects in the cloud. You only need Revit 2018.3 or newer, and the relevant license for Revit Cloud Collaboration (too hard to keep track of the names but I think ‘BIM 360 Design’ is the current terminology).

You will be able to see this link in Revit 2018.3 or newer:

When ‘linking’ Revit models, CAD files, and other resources, you will see this option when working in a cloud workshared model:

These models will be temporarily stored in the CollaborationCache folder:

From Autodesk: Here is the URL to download the Desktop Connector. Please download and install the latest version to continue to use the Desktop Connector.

PLESE NOTE: This update must be completed by July 31 in order to continue to use the Desktop Connector.

This update also includes the following improvements:

  • Support for right-click functionality to delete files & folders, rename folders, and create folders
  • Improved caching to improve the user experience and performance
  • Recent bug fixes. For updates, view our list of known issues.

Please download and install this new version to take advantage of these updates. NOTE: The new installer will remove any previous installations of the Desktop Connector automatically.

DOWNLOAD THE UPDATE
For additional details on the updates to the Desktop Connector and the latest BIM 360 releases, please visit the BIM 360 Release Notes.

If you are still running a relatively small SSD (like 512gb), you might see that your C drive fills up pretty quickly while working on a large BIM 360 Design Revit cloud worksharing project. See below image, where the CollaborationCache folder is using almost 50gb of space on my machine:

 

While I realise that the SSD is the best place to have that data in terms of performance, if you don’t have the space available you may consider moving your CollaborationCache folder to a secondary, larger hard drive. I used a symbolic link to do this, with the script below:

if exist "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache" rename "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache" E:\C4R
if not exist E:\C4R MD E:\C4R
robocopy /mir "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache.old" E:\C4R

 

This creates a folder called C4R on your E drive, copies the CollaborationCache over, and sets up the symbolic link. To use it:

  1. Sync all Revit instances and shut down Revit completely
  2. Make a CMD from the code above and run it as Administrator (elevated privileges required for mklink )
  3. In Explorer, confirm you have the symlink and delete the .old folder :

  4. Start Revit 2018

 

Please use the script with care 🙂

You can also refer to my previous post where I did the same with the Tekla BIMsight cache folder.

 

Here is the CMD script to move the folder for Revit 2018 to a drive with R drive letter:

if exist "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache" rename "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache" R:\B3D\R2018
if not exist R:\B3D MD R:\B3D
if not exist R:\B3D\R2018 MD R:\B3D\R2018
robocopy /mir "%localappdata%\Autodesk\Revit\Autodesk Revit 2018\CollaborationCache.old" R:\B3D\R2018

 

Here is the CMD script to move the folder for Revit 2019 to a drive with R drive letter:

if exist "%localappdata%\Autodesk\Revit\Autodesk Revit 2019\CollaborationCache" rename "%localappdata%\Autodesk\Revit\Autodesk Revit 2019\CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%\Autodesk\Revit\Autodesk Revit 2019\CollaborationCache" R:\B3D\R2019
if not exist R:\B3D MD R:\B3D
if not exist R:\B3DR2019 MD R:\B3D\R2019
robocopy /mir "%localappdata%\Autodesk\Revit\Autodesk Revit 2019\CollaborationCache.old" R:\B3D\R2019

 

Here is the CMD script to move the BIM 360 cache folder for Revit 2020 to a drive with R drive letter:

if exist "%localappdata%\Autodesk\Revit\Autodesk Revit 2020\CollaborationCache" rename "%localappdata%\Autodesk\Revit\Autodesk Revit 2020\CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%\Autodesk\Revit\Autodesk Revit 2020\CollaborationCache" R:\B3D\R2020
if not exist R:\B3D MD R:\B3D
if not exist R:\B3D\R2020 MD R:\B3D\R2020
robocopy /mir "%localappdata%\Autodesk\Revit\Autodesk Revit 2020\CollaborationCache.old" R:\B3D\R2020

 

Here is the CMD script to move the BIM360 cache folder for Revit 2021 to a drive with R drive letter:

if exist "%localappdata%\Autodesk\Revit\Autodesk Revit 2021\CollaborationCache" rename "%localappdata%\Autodesk\Revit\Autodesk Revit 2021\CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%\Autodesk\Revit\Autodesk Revit 2021\CollaborationCache" R:\B3D\R2021
if not exist R:\B3D MD R:\B3D
if not exist R:\B3D\R2021 MD R:\B3D\R2021
robocopy /mir "%localappdata%\Autodesk\Revit\Autodesk Revit 2021\CollaborationCache.old" R:\B3D\R2021

Here is the CMD script to move the BIM360 cache folder for Revit 2022 to a drive with R drive letter:

if exist "%localappdata%\Autodesk\Revit\Autodesk Revit 2022\CollaborationCache" rename "%localappdata%\Autodesk\Revit\Autodesk Revit 2022\CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%\Autodesk\Revit\Autodesk Revit 2022\CollaborationCache" R:\B3D\R2022
if not exist R:\B3D MD R:\B3D
if not exist R:\B3D\R2022 MD R:\B3D\R2022
robocopy /mir "%localappdata%\Autodesk\Revit\Autodesk Revit 2022\CollaborationCache.old" R:\B3D\R2022

Here is the CMD script to move the BIM360 cache folder for Revit 2023 to a drive with R drive letter:

if exist "%localappdata%\Autodesk\Revit\Autodesk Revit 2023\CollaborationCache" rename "%localappdata%\Autodesk\Revit\Autodesk Revit 2023\CollaborationCache" CollaborationCache.old
mklink /d "%localappdata%\Autodesk\Revit\Autodesk Revit 2023\CollaborationCache" R:\B3D\R2023
if not exist R:\B3D MD R:\B3D
if not exist R:\B3D\R2023 MD R:\B3D\R2023
robocopy /mir "%localappdata%\Autodesk\Revit\Autodesk Revit 2023\CollaborationCache.old" R:\B3D\R2023

 

Here is a way to store your Outlook signatures on OneDrive using a symlink:

if exist %userprofile%\AppData\Roaming\Microsoft\Signatures rename %userprofile%\AppData\Roaming\Microsoft\Signatures Signatures.old
mklink /d %userprofile%\AppData\Roaming\Microsoft\Signatures E:\LukeOneDrive\USERPROFILE\Microsoft\Signatures

Previously the Desktop Connector was built for BIM 360 Team projects running C4R. With the shift to B3D (BIM 360 Docs) platform, you need to:

From the help:

This plugin is a connector that establishes BIM 360 Docs as a recognized data source for the Desktop Connector – making it available in your desktop folder and file structure for easy file management.

As with Desktop Connector, this means your BIM 360 Docs files are replicated in a connected drive. You can manage files in BIM 360 Docs through the connected drive, just as you would any other folder on your machine. Changes made on the desktop are automatically uploaded to BIM 360 Docs.

How do you get it?

After install, you will see this in Windows Explorer:

Over the years, Autodesk has provided various means for us to access, sync, backup and share files. Most recently we used “A360 Desktop” (see end of this post) and more recently “A360 Drive“. Autodesk recently released the Autodesk Desktop Connector, which allows you to:

  • Manage remote files from your desktop
  • Connect to Team Hubs
  • Work offline or online

Desktop Connector gives you access to your production A360 data. Using Desktop Connector  to modify files that reside in production A360 will automatically sync changes, updating your production file in A360.

You will see a link on your BIM 360 Team hub like this:

You can install from here which links to these downloads (Help page for install here).

x64

x86

mac

 

You need to sign in:

You should now see a BIM 360 Team link in Windows Explorer:

You can use the tray icon to “Work Offline”.

More Information

Release notes here

Getting Started guide here

Some notes about A360 Desktop retirement

A360 Desktop older versions will get this message:

A360 Desktop current versions:

  • A360 desktop Windows Updater: All users except 2018 AutoCAD products
Windows 32-bit installer – A360 desktop Version 7.3 (exe – 362MB)
Windows 64-bit installer – A360 desktop Version 7.3 (exe – 409MB)
  • A360 desktop Windows Updater: For AutoCAD 2018 product users only
Windows 32-bit installer – A360 desktop Version 9.5 (exe – 373MB)
Windows 64-bit installer – A360 desktop Version 9.5 (exe – 409MB)

 

A360 Desktop Expiration link: