This guide looks at errors that can appear with Rhino.Inside.Revit. This address most of the common errors we have seen. Please Contact Us whether any of these options worked or did not work. We are working to minimize any of these messages.

## Unsupported openNURBS

### Problem

When Rhino.Inside.Revit attempts to load, the error below appears.

This normally appears when there is a conflict when an older version of the Rhino file reader (openNURBS) has been loaded in Revit. This normally happens because:

1. A Rhino 3DM file was inserted into Revit before Rhino.Inside.Revit was loaded. Revit is shipped with a different version of the openNURBS module, and loading a Rhino model into the Revit document before activating Rhino.Inside.Revit, cause the conflict

### Workaround

Please follow the instructions on Submitting Debug Info to submit the error and debug information to Rhino.Inside.Revit development team.

Saving the project, then restarting Revit is usually the fastest workaround. If Rhino.Inside.Revit is loaded first, then everything should work with no issues.

Some plugins may need to be updated. Common conflicts are seen with older versions of:

We continue to work with all our partners on this error. Information gathered from the Error Reporting enables us to actively target these conflicts.

## Initialization Error -200

### Problem

When Rhino.Inside.Revit loads, the error below appears.

The underlying issue is that one of the Microsoft.WindowsAPICodePack or Microsoft.WindowsAPICodePack.Shell dlls that are shipped with the conflicting Revit add-in, does not have a public key, and the conflicting add-in is not compiled to use the exact version of these dlls that are shipped with the product. The latest version of both these dlls are installed by Rhino into the Global Assembly Cache (GAC) when Rhino is installed. When Rhino.Inside.Revit and the conflicting add-in are both loaded into Revit, one of them ends up using the incompatible dll version and this causes the error.

### Workaround

This normally appears when there is a conflict between Rhino.inside and one or more Revit plugins that have loaded already.

#### Preparing new DLL files

• Make sure you have a ZIP unpacker installed (e.g. 7zip)
• Unpack the package
• Browse to the lib/ directory inside the unpacked content. Copy the Microsoft.WindowsAPICodePack.dll
• Place inside add-in installation directory, overwriting existing files if any. The specific directory is listed below for known conflicting add-ins.
• Unpack the package
• Browse to the lib/ directory inside the unpacked content. Copy the Microsoft.WindowsAPICodePack.Shell.dll
• Place inside add-in installation directory, overwriting existing files if any. The specific directory is listed below for known conflicting add-ins.

#### Fixing the Conflict

Naviate Add-ins: A common conflict is with the suite of Naviate tools for Revit. Follow the steps listed above to download the necessary dlls and replace the existing ones inside the Naviate installation path (usually C:\Program Files\Symetri\Naviate\Revit 20XX\Dll\)

pyRevit Add-in: Another common conflict is with an older version (older than 4.7) of the pyRevit plugin. While the newer versions to pyRevit do not cause a problem, an older version might. Information on the pyRevit conflict can be found on issue #628. To update the older version of pyRevit, follow the steps listed above to download the necessary dlls and place them under the bin/ directory inside pyRevit installation (default path is %APPDATA%\pyRevit-Master\)

If this does not solve the problem, then using the Search for Conflicting Plugins section.

## JSON Error

### Problem

A Long JSON error shows up as shown below

### Workaround

Like the previous -200 error, this is a conflict with another plugin. See the Error - 200 solution for this problem, and the Search for Conflicting Plugins section below.