Error Saving Family

Error Saving Family

L.Maas
Mentor Mentor
568 Views
2 Replies
Message 1 of 3

Error Saving Family

L.Maas
Mentor
Mentor

Today spent some time troubleshooting a family. I have a family with a type catalog.

 

I made some modifications to the family and it crashed Revit

Crash.png

 

Restarted computer, reloading the family, making some moidifcations, saving...crash.

 

Revit 2016 (20150714_1515(x64)).
OS Windows 7 with SP1.

I often use type catalogs and make use of csv file editors (e.g. excel)  to modify or fill the type catalogs.

 

Reproducing the error:
-Save the family and the type catalog together in a folder
-Open the family in the family editor
-Save the family.
-ERROR.

Cause:
-During export from csv file editor extra (empty) column was generated by mistake.

 

Type Catalog.png

Solution:
-Remove empty column (the last comma in every line).

However it is strange that while just saving the family in the family editor it should crash on the faulty type catalog.
Took a while to find cause of crash while first expecting something wrong with the family itself

Attached the family with type catalog used to create error.

Louis

EESignature

Please mention Revit version, especially when uploading Revit files.

0 Likes
569 Views
2 Replies
Replies (2)
Message 2 of 3

dzanta
Mentor
Mentor

Couple of things to check:

 

1.  Is there an extra space within your table that is causing the hiccup?

2.  Have you tried creating the table with Notepad software and not Excel to see if it crashes?


Dzan Ta, AEE, ASM, ACI.

EESignature



Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


Autodesk Community | Twitter | YouTube | Facebook | LinkedIn |

Win 11 Pro/DELL XPS 15 9510/i9 3.2GHz/32GB RAM/Nvidia RTX 3050Ti/1TB PCIe SSD/4K 15.4" Non-Touch Display

0 Likes
Message 3 of 3

L.Maas
Mentor
Mentor

The problem and solution are clear. When saving from excel it saved an extra (empty) column. This resulted in the comma at the end as shown in the screenshot of my earlier post. Removing those commas from the text file resolved the problem.

 

Strange thing was that when editing the family and then saving it 'crashed' Revit. I find it strange that wehn saving the family an error in the type catalog should crash revit. So it took me a while to find the solution (first thought it was the family itself that caused the problem).  

I think unrecoverable errors should not happen. It appears that this will be an easy 'bug' for Autodesk to resolve.

 

So I intended by my post to inform other people and Autodesk about this error (saving some troubleshooting time) and hopefully Autodesk will use it to remove this 'bug' from the software.

 

 

 

 

Louis

EESignature

Please mention Revit version, especially when uploading Revit files.

0 Likes