I am trying to write from dynamo into an excel file using the dynamo node FILE. However, it keeps crashing out and prompting me to send the error message/situation to Autodesk revit. Please i really need an urgent response as i just started learning dynamo by myself. Its pain-staking and frustrating.
i feel u. first thing i would try is to open up task manager to see if there r a bunch of excel processes lingering around. terminate them and give it go.
if the file actually locates at a remote server, then it could be a server issue.
Thanks alot Bim Ambit for the quick response. Yes, i do not have revit at home so i go to the office to use the revit on our server. But i have moved the revit project to my remote desktop and open a new excel file for that case. Yet, it just disappears or crashes out the moment i connect to the node File Path. I checked the task manager and there are no excel data running at the moment. I am just stuck and canât go further. Its really driving me crazy.
below is a workaround i tried implementing to avoid revit/dynamo from crashing
However, i repeatedly got this error messages:
Data.ExportToExcel failed. The COM object of type âMicrosoft.Office.Interop.ExcelApplicationClassâ cannot be converted to the interface type âMicrosoft.Office.Interop.ExcelApplicationClassâ. This operation could not be performed because the QueryInterface call to the COM component for the interface with IID â{000208D5-0000-0000-C000-000000000046â could not be performed due to the following error: Element not found. (Exception from HRESULT: 0x8002802B) (TYPE_E_ELEMENTNOTFOUND))
Can someone please help me. thanks alot
im typing this with muddy brain and sleepy eyes. so take it with a grain of salt.
- no graph change â repair excel
- forget about interop â try openxml
hm.. this rhymes.
Definitely use the openxml node. Not sure why the other hasnât been removed by the team yet given how often it doesnât work.
Make sure files are all folder accessible such as not on onedrive or syncing to onedrive, can often cause issues in my xp.
Excel read/write was the straw that broke the canels back into c# for me. Getting excel readers to work in python is basically a celestial alignment type of thing, and having to constantly remind users to use openxml which comes with its own quirks is a hassle in itself.
Itâs been marked deprecated and will be removed in a coming version (4.0 is my guess).