topic Re: Cannot write output file. (ifcxml) in Collaboration with other software

Cannot write output file. (ifcxml)

Anonymous — Wed, 04 Feb 2009 19:23:33 GMT

I've tried to save out to ifcxml as opposed to ifc.. and receive this error "cannot write output file." Does anyone know what this means?

Re: Cannot write output file. (ifcxml)

Laszlo Nagy — Fri, 06 Feb 2009 09:46:24 GMT

I would suspect in this case more of a file system situation (like permissions) causing this, rather then something in the Add-On.

Re: Cannot write output file. (ifcxml)

Da3dalus — Fri, 14 Jun 2013 21:39:34 GMT

I've received the same error. In the past, I know I've run in to permissions problems, but this time, that shouldn't be the case. I'm actually saving out several IFC files (shell, interior walls/zones, plumbing, etc.) because my consultant finds it easier to reference in Revit. All files are saved to the same folder on our server. All of the files work, except the one that has plumbing fixtures and casework. I suspect that one of the casework objects (the customized Unicabinet) has some sort of minor 3D error (I get an error message in the 3D window when casework is turned on).

I'll post more if I figure this out.

Re: Cannot write output file. (ifcxml)

Karl Ottenstein — Sat, 15 Jun 2013 03:37:17 GMT

Use the oft-suggested binary search method to track down if this is an issue with a model element, for example, a zero-height wall. Marquee or select for saving just a few very normal elements. If that saves, then: Marquee half the project, try to save, then the other half, try to save. Then half the half, etc. until you find the part of the model that is not saving properly.

Graphisoft tends to re-use some not-too-meaningful error messages where specific messages would help the user, but hopefully the above will help...

Re: Cannot write output file. (ifcxml)

Da3dalus — Tue, 06 Aug 2013 16:53:54 GMT

I've found that if I jump to the View I'm trying to export in IFC, and then refresh the 3D window prior to exporting, it typically works. I think it gives the system a chance to get the "Errors Occurred During the Last Operation" warning out of it's system, without interrupting the export.

Sometimes it still doesn't work, but if I sign out and back in, it's generally OK.

I've identified the rogue objects, but it is a part that my interior designers have used extensively (UniCabinet), and we've gone too far to remove it. It still shows up and exports fine, just with that error message. Some day when I have time, I'll dig through the GDL to try to fix the problem.