Hello all,
I am somewhat confused at the moment. All graphs which contain the OOTB node Data.OpenXMLExportExcel are now failing with the error;
"Revit Dynamo Data.OpenXMLExportExcel failed could not load file or assembly “DocumentFormat.OpenXml, Version=2.12.3.0, Culture=neutral, PublicKeyToken=8fb0b64d019a17” Could not find or load specific file.”
The same error is present for the import node as well, both of which were working absolutely fine less than 24 hours ago. I have tested at home on the same version of Revit 2025 (25.4.10.45) and Dynamo (DC 3.3.0.6316 / DR 3.3.0.6523) and they work fine so I am assuming something has been updated by Microsoft, outside of the Revit / Dynamo environment.
Anyone have any ideas what might have happened, are you seeing the same thing and what can I ask our IT department to do to resolve? Whilst very simple nodes, they are pretty important within our workflow. More than happy to post images of the graph if required but its not specific to one graph, the node throws the same error on all of them.
aite what if u go to C:\Program Files\Autodesk\Revit 2025\AddIns\DynamoForRevit, see if u could find DocumentFormat.OpenXml.dll. if not, find a copy and throw it in. i bet ur home pc has it.
Interop had this issue before, that was an ez fix by just repairing excel. but openxml, hm.., worth a try though.
So that file was already there but we mistakenly thought you could update Dynamo for Revit with the latest builds without realising that they are standalone (Stupid right?).
The long and the short of it is that this then broke Dynamo anyway resulting in a reinstall of R2025 which you guessed it, seems to work fine.
it’s probably a library conflict with another addin or dynamo package
I thought that but I’ve tried it on another PC in the office of someone who doesn’t use Dynamo at all so has no packages installed and has no add-ins whatsoever in base revit, its throwing the same error. I’m leaning more toward a windows update as its breakage coincided with our IT pushing out a series of MS updates on Tuesday night.
1 Like
This is unlikely, but a possibility.
More likely is a conflict from a Revit add-in or Dynamo package as noted by @c.poupin. Check your Dynamo log for a conflict listing. Archi-Lab is one such package that introduces the issue.
