I've been experiencing a problem with eTransmit lately. I'm using it on a model that I've detached from central and saved separately. I'm the only one who uses this model, so once I close it, it's closed. Nonetheless, when I try to run eTransmit on the file, it gives me the error "Model has unsaved changes. The model ---- is open in Revit with unsaved changes. To include your changes, you must cancel and save the model before continuing."
Then it gives me the option to continue without unsaved changes, or cancel the transmittal. If I choose "Continue without unsaved changes", it runs, but does not process the model. The transmittal log says at the bottom that eTransmit could not open the file.
I haven't found anyone talking about this problem online, so I thought I'd post the problem and the solution(s) that worked for me. In my case, the main problem seems to be the length of the file path. We have a very structured file system so paths get long. I read somewhere that Windows has a limit to the file path length, and I think this might be messing eTransmit up. The solution to this is just to save the model somewhere with a short file path, like C:\Documents.
I've also tried using Collaborate->Relinquish All Mine when saving the model, and maybe that helps. Once, restarting Revit fixed it.
Here's a screenshot of the error:
Bei mir tritt das gleiche Problem auf, wenn ich nach einem etransmit erneut eine andere Datei transmittieren möchte. Ich breche den Vorgang ab. Nach Schließen von Revit und einem Neustart von Revit kann ich die Datei transmittieren ohne Fehlermeldung. Es scheint ein bug zu sein, denn etransmit funktionierte bisher reibungslos. Bei mir sind die Versionen 2021, 2023 und 2025 installiert.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.