Revit Export to DGN Fatal Errors out

[Anonymous]

In Revit 2017.2.3 everytime you click Export->DGN and click the seed file tab and check the "Use DGN Seed file for export:" box Revit has a Fatal error and asks for a recovery file. It has that behavior in a new (nothing in it) file, a sample file, a real project file. 

I get DGN is not where we want to go but it is a submission requirement, so I have to export my final model and drawings out. Any other people have the same issue? 

[L.Maas]

I only have Revit 2018 available. No problems there.

Check your journal files and see if something is in there that mention possible problems.

Other add-ins are also a common source for errors, so consider uninstalling them

[Anonymous]

It does exactly the same thing in 2018.2. Export -> DGN -> Check the box for Use DGN Seed file for export. Click the three dots to browse watch the blue wheel of death and boom! fatal error!

[L.Maas]

Did you manage to check your journal file?

I have no problem selecting the ...

[Anonymous]

nothing in the journal file its says "An unrecoverable error has occurred"

When it breaks on a blank file with no other actions don on it the issue has to be somewhere else. Two different version of Revit both fully updated on a fully updated windows 10 machine.

I can't even copy and paste in a path into the field which would be an annoying but palatable work around.

10-Jan-2018 07:57:09.202; 1:< logging finished virtualization services
'C 10-Jan-2018 07:57:09.202; 1:< logging finished worker services
'C 10-Jan-2018 07:57:09.202; 1:< logging erased queues
' 0.884583 1:<<<Terminating Slave Processes
' 0:< Unconverted MessageBox "An unrecoverable error has occurred. The program will now be terminated. All of your data has been recently saved, so there is no need to create recovery files."
' 0:< ::62:: Delta VM: Avail -13 -> 134181918 MB, Used +0 -> 938 MB; RAM: Avail -132 -> 25200 MB, Used 968 MB
' 0:< GUI Resource Usage GDI: Avail 8906, Used 1094, User: Used 579
'E 10-Jan-2018 07:58:39.579; 0:<
Jrn.AddInEvent "AddInJournaling" , "MessageBox(OK,Revit).Click(Cancel)"
'H 10-Jan-2018 07:58:39.585; 0:<
Jrn.Data "MessageBox" _
, "IDOK", "An unrecoverable error has occurred. The program will now be terminated. All of your data has been recently saved, so there is no need to create recovery files."
'C 10-Jan-2018 07:58:39.585; 0:< program terminated

[L.Maas]

I do not see clear indications what the cause might be, only generic error

' 0:< Exception occurred 
'C 10-Jan-2018 07:57:08.313;   0:< ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007FFFB38C2F55 

This would require some troubleshooting.

-Has something changed since the last successful export to DGN?

-Have you restarted your computer since problem occurred?

-Enough Free space on your drive?

-Try cleaning your Temp files (%TEMP%)

-Check if you have the folder as seen in my screenshot (C:\Program Files\Autodesk\Revit 2018\ACADInterop\)

-Do you have (dgn) files in those folders?

-Do you have read & write permissions to those folders?

-Try to switch of firewalls & virus scanners for a short time.

-Try to do a repair on your Revit installation.

-If it worked recently you could try to go to a previous windows restore point.

-Consider reinstalling your Revit installation.

[Anonymous]

This isn't a just my machine problem -- this is an every computer on the network problem. Thanks for your help, we are working with Autodesk. 

[L.Maas]

Can you post the cause and solution when you have worked it out with Autodesk?

I (and probably others) am interested to know what happened and how to solve it.

[Viveka_CD]

Hi @Anonymous

Can you post the case number? I can check back for details.

Also, see parent topic: Exporting to DGN

Regards,

[Anonymous]

I have the following case number 1377255513772555> from an email. I haven’t seen an update. Any information would be great!
13772555>

[Viveka_CD]

Hi @Anonymous

The case status is open.

Updating to Revit 2017.2.3 was suggested, and I see that you've posted your journal, awaiting any further updates from the team.

Regards,

[Anonymous]

I am on 2017.2.3 with no luck. Thanks for the update!