If you encounter the error messages "A serious error has occurred. The current action has been cancelled.", or "A serious error has occurred. The current action has been cancelled. It is strongly recommended that you save your work in a new file before continuing. Would you like to save a recovery file?", start troubleshooting here.
Initial items to check
- Make sure that Revit has the latest update and hotfix installed: Update your software
- Narrow the scope of the behavior by checking if the issue occurs for:
- Just one Revit model: for these issues, look for solutions that would change the model. A good first step for this type of issue would be opening the model with an Audit.
- Only on one computer: for these issues, look for solutions that would make changes to the system (this could be Revit, Revit Add-ins, or external components like Windows).
- Only on one network (for Internet/Cloud related tasks): for these issues, look for solutions that change your network configuration (this could be local settings, or network settings outside of your system).
- Check Revit journal: it records more details on what is happening in Revit, and you can use this to get a better handle on what is happening at the time of an error.
Note: See the following document for information on
How to read the journal from Revit.
When reviewing the journals, check to see if any of the following entries are found, and use the link to find documentation on possible solutions:
- Please Reload
- DBG_WARN: PartMaker duplicate DPartKey.
- Missing ESSchema
- DBG_INFO: Recent Dynamic Added but not to Dynamics
- DBG_WARN: Transaction is pending after editing is canceled
- DBG_WARN: A linked MasterImportSymbol
- DBG_WARN: One of the given categories is not filterable
- DBG_WARN: AcDbDatabase::readDwgFile threw an exception
- Exception caught from managed method mscorlib::Boolean TryExpandShortFileName() <System.IO.PathTooLongException>
- Exception caught from managed method .Net SqlClient
Additional troubleshooting
If the entries above are not found, or the link does not lead to a solution, see the following link for more troubleshooting on this topic: A Serious Error Has Occurred.