Revit or Xrev Transmit crashing during Print & Export


You receive an error message from Revit stating "An unrecoverable error has occurred.  The program will now be terminated." or an error from Xrev Transmit stating "The Print & Export command encountered an error: AccessViolationException: Attempted to read or write protected memory.  This is often an indication that other memory is corrupt"


There are a couple of known issues that will cause these errors.  If the issue is occurring in Revit 2018 only:

There was a bug in the initial releases of Revit 2018 which would cause the Revit Print API to crash when running Xrev Transmit.  Autodesk resolved this with Revit build 2018.0.2 update.  Please update to the latest version of Revit 2018.

If the issue occurs in all versions of Revit:

A number of versions of Enscape do not play nicely with others.

  • Version 2.1.0 - Causes issues with all versions of Revit
  • Version 2.7.0+18848 - Causes issues with Revit 2016 & 2017
  • Version 2.7.1+20192 - Causes issues with Revit 2016 & 2017
  • Version 2.7.1+20886 - Causes issues with Revit 2016 & 2017
  • Version 2.7.2+23714 - Causes issues with Revit 2016 & 2017
  • Version 2.8.0 - Causes issues with Revit 2017

Version 2.1 of Enscape introduced some features to activate/deactivate their buttons on the ribbon at the appropriate times, however the method they used results in the crashing of other addins like Xrev Transmit as it attempts to run whilst another command is running.  This would result in the crashing of the Revit Print & Exporting API.  In Revit 2018 it only crashes Xrev Transmit, but in previous releases it will crash Revit completely.  Enscape resolved this with there 2.1.3 update.  Please update Enscape to the latest version.

We have contacted Enscape regarding the re-occurrence of the issue with version 2.7.x and had no response.

To temporarily disable Enscape (requires Administrator Privileges):

  1. Navigate to the Enscape Addin filefor the version of Revit you are using:


  2. Rename the 0_Enscape.addin file to 0_Enscape.addin.bak
  3. Restart Revit

This should temporarily stop Enscape from loading.  Test Xrev Transmit to see if it works.  If so, contact Enscape support and advise of their issue (we cannot fix this as the issue is caused by Enscape not playing nice with others).

Simply restore the addin file back to its original name to undo this action.

Related articles