Hi everyone,
I’m getting this error in Revit:
Copy
A problem has occurred with the Updater Builder Dynamic Updater from another provider. Its process had to be canceled.
- What I’m Doing: I’m running Dynamo scripts, but I’m not using the IUpdater Interface or Dynamic Model Updater in my scripts.
- Plugins/Tools: We use PyRevit to create a custom toolbar from the dynamo and pyrevit scripts, Dynamo, and Autodesk Construction Cloud (ACC).
- Recent Issues: The error started appearing around the same time we had trouble linking files in ACC.
My Question:
- Is this error caused by my Dynamo script, ACC, or a conflict between ACC and my script?
- If it’s not my script, how can I find out what’s causing it?
Please note i am not using the IUpdater Interface / Dynamic Model Updater in my scripts
Any help is appreciated! Thanks!
Hey,
Could you give us a bit more context… What is your Dynamo trying to do? What other addins do you have (if any)? What Py hooks do you have? Is your process that you run a dynamo and this appears?
I think the iupdaters can be quite fragile… I can imagine that if you’re modifying an element that it could break whatever the iupdater is keeping track of…
Cheers,
Mark
Hi Mark,
Thanks for your response! Here’s more context:
- Dynamo Scripts: Used for space planning (importing rooms, placing masses, modifying walls/columns). No IUpdater or Dynamic Model Updaters.
- Add-Ins: PyRevit (no hooks), Speckle, ACC.
- Error Behavior: Pops up randomly in Revit, not during Dynamo/PyRevit use.
Could this be related to Speckle or ACC using IUpdaters?
Cheers,
Rebal
Hey,
We heavily use py, BIM360 and collaborate pro and a few others, but I don’t get that popup.
We have speckle but it’s not heavily used, so that would be where I would investigate…
Hope that’s useful,
Mark
1 Like
Hi Mark,
Thanks for the insight! Since you’re using similar tools (PyRevit, BIM 360, Collaborate Pro) without this issue, I’ll investigate Speckle further. I’ve already posted on the Speckle forum to check if it’s related.
This has been a nightmare—we had to do a clean install/uninstall of Revit, and now we’re dealing with missing files and reinstalls. Fingers crossed we can resolve this soon.
Appreciate your help!
Cheers,
Rebal
1 Like
Restart Revit, recreate the issue, and then force quit Revit. Then post your journal from that session here (it should have a creation date which aligns with when you started Revit). This will help us identify a bit more closely as to what the issue might be, as well as if any other add-ins are in use (often you aren’t even aware they are there as they can be put in place when other tools are installed).
1 Like
Hi @jacob.small,
thanks for your insight
its challenging to redo the same erorr again, however i searched for the journal file and through the large text i found this text
- Third-Party Updater:
- The line
Third Party Updater 'Results Builder Application: Results Builder Dynamic Updater' registered for all documents
confirms that the Results Builder Dynamic Updater (linked to the same add-in) is causing the error.
- This updater is likely trying to monitor or modify elements in the background but fails due to the API version conflict.
Many thanks
@Jaber.Rebal try changing the file extension of those initialization files at your add-in directory. at least it will make revit skip loading the problematic one.
1 Like
Best to post that full journal - it indicates that addins you’re using are leveraging different versions of the Revit API; this may be unrelated or it may be the smoking gun to solve the issue, however we can’t tell with what we see now.
1 Like
Hey @jacob.small,
I won’t be able to recreate the issue again as we’re currently cleaning up the machine. However, I do have a previous journal from the same machine, though it’s quite lengthy. Would it be possible to share this journal with you privately?
Many thanks
You may DM it to me here, though I may have to loop in some of my Autodesk colleagues if I can’t find the root cause. Will communicate in the DM if that is the case.
That said if you’re not able to reproduce the issue after cleaning the machine, it’s likely they were missing an update, had conflicting add-in version, or had a bad install.