PDA

View Full Version : A serious error has occurred.



rodgersmatt66
2008-08-20, 09:56 PM
"A serious error has occurred. It is strongly recommended that you use Save As to save your work in a new file before continuing."

So we started getting this error lastweek when a user was creating detail sections for some windows. It has got progressively worse the past few days.

Steps I have taken to correct the issue:

1. Delete all local user files and backups
2. Delete central backup file
3. Audit/Purge ACAD linked files
4. Audit central file
5. Purge central file
6. Resave central and compact central file
7. Resave local files

None of this helped although it did reduce the file size of course.

My last effort was detaching and creating a new central file but even this had no affect.

Any ideas? I have been in contact with Autodesk support but it is slow going to get responses from them.

David Haynes
2008-08-21, 12:28 AM
Here are some answers that may be the problem.

http://revitize.blogspot.com/2008/05/serious-error-occured-text-style.html

http://www.revitcity.com/forums.php?action=viewthread&thread_id=4445

Also, have you enabled your 3GB switch...
http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=8018966&linkID=9243099

Hope this helps some.

rodgersmatt66
2008-08-21, 03:45 PM
I had seen those threads and done some research on those areas with no success.

The problem at the time seems to be section associated but extremely random. Sometimes I am able to just continue with my work and sometimes the error aborts the command but it never crashes the software.

Nice to hear from someone at Ideate, I use to go to the user group meetings in Sacramento with Abigayle. You guys rock!

***UPDATE***

' 3:< System exception in tweakGRepsInView
' 3:< for element 2809277 of class ProfileRoof
' 3:< in dbview 1050943 of class DBViewSection
' 3:< Error dialog data for transaction
' 3:< Error: A serious error has occurred. It is strongly recommended that you use Save As to save your work in a new file before continuing.
'H 21-Aug-2008 08:56:13.235; 3:<
Jrn.Data "Error dialog" _
, "1 failures, 0 errors, 0 warnings"
'C 21-Aug-2008 08:56:13.235; 3:< ADialog::doModal start
' 3:< DBG_WARN: Already cleaning! Please ignore this message if in the middle of crash protection.: line 1424 of .\DocView\DBViewImpl.cpp.
' 3:< DBG_WARN: Already cleaning! Please ignore this message if in the middle of crash protection.: line 1424 of .\DocView\DBViewImpl.cpp.
' 3:< DBG_WARN: Already cleaning! Please ignore this message if in the middle of crash protection.: line 1424 of .\DocView\DBViewImpl.cpp.
'E 21-Aug-2008 08:56:14.295; 3:<
Jrn.PushButton "Modal , Revit Architecture 2009 , Dialog_Revit_DocWarnDialog" _
, "Continue Without Save, IDABORT"
'H 21-Aug-2008 08:56:14.295; 3:<
Jrn.Directive "WindowSize" _
, "[07-108_RTI_CENTRAL.rvt]", "Section: EAST/WEST SECTION LOOKING SOUTH" _
, 1191, 510
' 3:< DBG_WARN: Already cleaning! Please ignore this message if in the middle of crash protection.: line 1424 of .\DocView\DBViewImpl.cpp.
' 3:< Resource usage: GDI 683 [expected 203], USER 486 [expected 225]
'C 21-Aug-2008 08:56:14.295; 3:< ADialog::doModal stop
' 1.189074 3:<<<;PERF;MISC;tweaking
'H 21-Aug-2008 08:56:14.389; 0:<

David Haynes
2008-08-22, 11:45 PM
Thanks for the kind words.
Do you have an element #2809277?
Sometimes when a crash is not consistent it is because it is an obscure element that only gets accessed every so often.

I am not a journal expert, but you could send the journal file to Autodesk Support, and they could take a look at it.

It looks like you might have found your problem as per:
http://forums.augi.com/showthread.php?p=879289#post879289

rodgersmatt66
2008-08-25, 04:53 PM
Yep! Thanks for the help.