For single-user subscriptions, Autodesk 2018 products can experience an intermittent crash. A fatal error message may be shown, such as the following examples:
AutoCAD Error Aborting FATAL ERROR: Unhandled e06d7363h Exception at ee563c58h FATAL ERROR: Unhandled e06d7363h Exception at 8d6b3fb8h
The system displays an error dialog window to submit an error report.
Solution:
Download and install the Autodesk License Service 5.1.5 Hotfix 1.
To download updates and hotfixes, use the Autodesk Desktop App (see Where to get Product Updates, Add-ons, and Enhancements) or access the direct links below. Before installation, ensure the internet connection is working and repaired if needed.
The first point release of Revit 2019 is now available… Let the deployments begin. Your projects are now running out of excuses as to why they shouldn’t upgrade 🙂
Here are some direct links to the Revit and Navisworks update files.
In the new homepage for #Revit 2019.1 when you hover over a recent project, you get the path of the central, your local, and the file size! If it’s not workshared, then you get the filepath and size. Pretty sweet.
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.
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 …
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.
========================
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:
We have been using HoloBuilder to capture as-built conditions on a huge hospital project, in order to maintain the federated BIM dataset (BIM to FM / Asset Information Management). 360 photos are a very quick and easy way to capture the context of building elements, but not their geometry.
This tip comes from one of our local HoloBuilder experts, Lisa Verschoor:
How to move across an updated drawing/sheet in HoloBuilder and have the already existing waypoints attached to the earlier version carry over automatically
Open HoloBuilder
Select sheet you want to replace (in example pic below I’m replacing sheet 020-H-003)
Click on the “Exchange this sheet” button (two opposing arrows)
Prompt will ask “Do you really want to replace the current Sheet with a new one?”
You may have noticed that Revizto notifications now provide a direct link to Open that issue in Revizto. This special hyperlink will prompt to open Revizto, and it will jump to the correct issue in the Issue Tracker.
The special link is made of a few parts, notice the project number and issue ID in bold below:
Using the predictable syntax above, you can use your own Revizto regional server, project number and issue ID to create these hyperlinks yourself, either in Excel or programmatically.
You can leverage this mini-api in a number of ways:
you can paste these links into the Revizto Issue Tracker to allow you to jump between issues in Revizto
paste the links into Word or Excel or other emails as part of a larger report or conversation
inject these links into another BIM platform such as a Revit URL field, so that you can jump from a specific item in Revit to the related Revizto issue
use these special links in a project portal or project management system
This is just the beginning for a new era of connectedness between the Revizto Issue Tracker and other platforms… watch this space!