And which versions of Speckle Connector?
I am using Revit connector 2.17 and speckle manager version is 2.12.2.
is this a new issue for you, have you used previous versions which worked?
It is first time I installed speckle on my pc. I never used it before.
1 Like
I am having the same issue. Here is what i can provide about my situation:
- Revit 2023
- Connector version is 2.17.0
- No VPN
- on my laptop (not a virtual machine)
- it worked 2 or so weeks ago on this computer. (im not sure what version of the connectors i was using at that time)
- I tried moving the Revit connector back to 2.15.2 because the speckle server Iām using is 2.15.0. This worked.
- With 2.15.2 I couldnāt receive any geometry that was sent from Rhino. Rhino sent the geometry using 2.17.0.
- I also tried sending geometry to Speckle from Revit using the 2.15.2 and it sent it fine. But im unable to receive it in Rhino using 2.17.0. It gives me a error that was something like a version mismatch (something like that)
error for reference:
If i search for āsentryā in the ā¦\AppData\Roaming\Autodesk\Revit\Addins\2023
the dll is only located in Speckle folder:
Update: I rolled both Rhino and Revit connectors back to 2.16.3 and it seems to be working just fine. I was able to receive geometry in both without issue.
1 Like
Thank you to you all for your reports and further details. We think we have identified the cause and will now raise a development ticket to address it as soon as we can.
2 Likes
Hi again, is the problem solved ?
1 Like
Hey Eray,
Weāre still working hard to get this issue sorted out. I really appreciate your patience.
2 Likes
Hi there,
Iām really curious to try Speckle & Blender out for our architectural renderings, however Iāve run into the same issue as above; Revit could not complete the external commandā¦
I have removed all old plugins that arenāt neccessary to me to no avail, and I couldnāt find PnlDmodeler.dll on my computer as advised above. The only other plugin that could be interfering is Rhino Inside Revit, though I donāt have that active when I try to start the Speckle Revit Connector. And I donāt have the Rhino, Grasshopper or Dynamo speckle connectors installed. Iām running Revit 2022, and have tried R2024 but received a similar message.
Any ideas? Many thanks.
@Schippeaux I have moved your report to a different but the same issue from the thread you replied to.
We are actively working on this fix due in the coming release.
I installed speckle for Revit 2020. After launching the speckle connector I am receiving the following error.
Good to know Iām not the only person with this issue. Figured it was because of my VPN or firewall like most of these problems but it doesnāt seem like it.
Edit: seems to be an issue with 2.17.0 as 2.16.3 works fine for me.
My setup:
- Windows 11
- VPN
- Revit 2023
Edit 2: looks like the 2.17.0 powerbi visualizer doesnāt work with 2.16.3 Revit connector but the 2.15.0 does 
(just in case anyone runs into the same issue)
1 Like
There can indeed be several causes. What we are working on is that the reporting to you (and also us) is clearer on what the actions should be.
1 Like
Hi @Schippeaux @Siva ,
This looks like due to a conflict with another plugin installed, please see here the steps for identifying it and search for the Sentry dll intead: Revit Connector Error - #11 by teocomi
Thank you for seeking help! Our friendly community is here to assist you. 
To assist you better, please consider providing:
-
Objective: Open/use speckle in RVT 2022
-
Issue: Get error when trying to open Speckle
-
Example: See picture below
-
Speckle link:
-
Logs:
Hi @Agni_M could you please list all your Revit and Dynamo addins?
This seems like a conflict.
Thanks
Could you please check if any Dynamo plugin in use might have such sentry.dll anywhere?
Matteo,
Many thanks!
Here the addins I have in RVT 2022:
When I tryed to load/open Dynamo within Rvt I get the following:
Should I try to dissable something?
Some early reports seem to indicate that Autodesk Data Exchange Connector is the cause of the conflict, but it could also be another plugin.
One (slow and boring) way to find the source of the conflict is to temporarily move, one by one, each .addin file that you see in the list above to a different location (eg your desktop).
Weāre working on our end to find a solution, but the above might be faster.