Data Exchange Connector for Revit 2024 blocks dynamo's python node

Hey there,

some of my cypthon3 scripts in Revit24 run into errors after updating the Autodesk Connector.

"Warning

PythonEvaluator.Evaluate failed.
The method “DisposeAsync” in type “System.Text.Json.Utf8JsonWriter” from assembly
“DEXConnector, Version=1.10.0.0, Culture=neutral, PublicKeyToken=null”
does not have an implementation."

After disabling DEXConnector.addin under C:\ProgramData\Autodesk\Revit\Addins\2024 everything works again.

RVT24
Dynamo Core 2.19.3.6394
Dynamo Revit 2.19.4.13096

is this known behavior?
I would like to have the connector and cpython script working at the same time..
Or is the root cause somewhere else?

Thank You

this is an example python script that runs into the error:

import sys
import clr
clr.AddReference(‘ProtoGeometry’)
import System
from Autodesk.DesignScript.Geometry import *

import RevitServices
from RevitServices.Persistence import DocumentManager
from RevitServices.Transactions import TransactionManager

doc = DocumentManager.Instance.CurrentDBDocument

TransactionManager.Instance.EnsureInTransaction(doc)

fassaden= UnwrapElement(IN[0])
zuordnung_list =

for fassade in fassaden:
zuordnung = fassade.get_Parameter(System.Guid(“8c2154b9-0f47-455d-8d0c-acdf6acad219”)).AsString()
zuordnung_list.append(zuordnung)

TransactionManager.Instance.TransactionTaskDone()

OUT = zuordnung_list

need a bit more diagnostic data.

Can you confirm this is Desktop Connector (there are a LOT of things which call themselves connector in the Autodesk ecosystem)?

Which version of Desktop Connector are you using?

Post the revit journal and dynamo log produced after you do the following:

  1. Restart the CPU
  2. Launch revit
  3. Start a new file using ‘none’ for the template
  4. Launch Dynamo
  5. Open a graph that reproduces the problem
  6. Quit Revit
  7. Grab the Revit journal named journal.xxx.txt (no 'working in the name) with the newest date from %localappdata%\Autodesk\Revit\Autodesk Revit 2024\Journals.
  8. Grab the Dynamo log with the newest date from %appdata%\Dynamo\Dynamo Revit\2.19\Logs
  9. Post the Revit journal and Dynamo log here.

Here comes the diagnostic data.
journal.0912.txt (482.2 KB)
dynamoLog_d60f7d86-ad04-4791-95cf-407aa2f552f2.txt (83.1 KB)

I differed a bit from your instruction. Had to create a roof in the template first.

Thank you

1 Like

Thanks - is DEXConnector desktop connector?

I can confirm DEX is the issue - it’s using several common libraries which are not aligned with the larger ecosystem. It uses:

  • SSONET version 24.3.30.0 but version 24.3.40.0 was loaded by another component
  • System.Net.Http version 4.2.0.0 but version 4.0.0.0 was loaded by another component
  • Microsoft.Bcl.AsyncInterfaces version 1.0.0.0 but version 6.0.0.0 was loaded by another component

@Huettig please post which version of the connector you’re using so I can try to track down someone who can help.

1 Like

im struggeling to find the current version that is installed.

But i also just got the notification that an update is available..
they might have fixed it already. Will test it

Edit: The version that was installed and got me the errors is: v1.10.0

1 Like

i believe it is the Data Exchange Plugin. When i disabled it the button in revit to data exchange wasnt there.

1 Like

sadly even with the updated Data Exchange to version 1.11.0 the error occurs.


:upside_down_face: the version of dex is even in the error message .. didnt spot that myself :smiley:

1 Like

Ok - I have tried reaching out to a few folks internally, and will let you know where I get with that. In the meantime you can reach out to them via the support address show on the contact info page: Data Exchange Connector for Autodesk® Revit® | Revit | Autodesk App Store

1 Like

Support answer:

Yeah, this can happen due to classic cases of DLL conflicts. The only workaround is to disable the connector.

From Revit 2026 onwards, Revit has provided a mechanism to prevent such conflicts, but in lower versions 2024 and 2025, we will have to work. We will log a ticket internally for this.

Seems like disabling or updating to rvt26 is the way to go for now.