Modeling operation error: missing logical in restore file

[Anonymous]

Does anyone have any idea what this error is and how to fix it?  I can not open my Finished Ground drawing without it crashing with an out of memory notification.  Before it crashes I get "modeling operation error: missing logical in restore file" prompt at the command line.  The file was working fine earlier this morning, but I was in several files so I can't track down when exactly it happened.  The same thing happens when I try to recover.

Problem is I'm supposed to have plans out tomorrow.

[Anonymous]

I had to go back to the bak file, could not find another solution.  Thankfully I didn't lose too much.

[Anonymous]

I have had the same problem with Civils 3D 2011. Is there any other solution to this that the bak file. The file opens up fine in 2010... Does anyone know what causes this problem.

[Anonymous]

I have had the same problem three times in the past two working days.  The first two I was able to get the .bak file, however today that did not work, the .bak file was bad too.  apparently you can open it in Map, audit it, save it, then open it in Civil3D, but I have not tried that yet.

[Anonymous]

Lets un-check this as being solved

[Anonymous]

This is very unfortunate problem.  I've had good luck with the bak files, but it has only happened twice.  I would say we need to report this problem with a service request if you are on subscription http://www.autodesk.com/subscriptionlogin or this feedback form http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=1109794.  

[Anonymous]

I think our cad guy did report it to thee subscription yesterday.

I was also trying to think about the three times its happened.  They were not all the same drawing, but I believe they were all in the same project.

[SethHall]

Hello all-

If you are experiencing this error message, please submit a Service Request with us in Support so we can test your drawings and send them up to Development for further review.

Thanks!!

[Anonymous]

It's happening again, but now I have a windows 7 pc and I can't end C3D.  I can't get to the task manager.  It seems like whenever C3D crashes on windows 7 you can't get to the task manager to end the process.  Update:  after about 10 minutes Windows finally gave me the option via a dialog box to end the process.  I selected end process, but still waiting.

[jalneal]

same problem here, but whatever caused it didn't kill a qsave, it nailed by bak file too. Tried running audit, froze the whole machine up.  This is in Windows 7 x64.  I'd send a service request, but I dropped subscription.  Found a backup, but still lost a days work 😞

[jalneal]

One thing to note, I was exclusively using alignments and profiles - I had imported pipe parts with a data shortcut, created an alignment, profile, and added the parts on a very small alignment (50 feet), but it was in the busiest file that had tons of data shortcuts in it (It was a final grading model file)  I qsave habitually, but the problem occured in a 5 minute span. Not the first time habitual qsave has been a bad rather than good habit. 

[Anonymous]

Has anyone gotten any closer to solving this? It's been haunting me on a certain project file. My C3D reseller tech support could not solve the problem, so they sent it to autodesk tech support. autodesk said they were aware of the problem but did not know how to fix it. The file I'm working with is fairly straight forward, only surfaces, feature lines and labels as far as C3D entities goes. I have been saving copies on the side, but when i eventually close C3D and try to reopen that I get the error. Then I never know how far back I have to go in opening my copied files (how much work I will lose). The bak files and autosave files all seem to be corrupted as well. I'm up against a deadline, so any advice or workarounds that anyone has found would be GREATLY appreciated!

[Anonymous]

Seth,

Was a solution to this problem ever found?  We are having the same issues, simple drawing containing alignments, feature lines, and profiles.  Tried to open it this morning and it fatal errored with this message on the command line.  Last 5 back ups are bad also.  Would appreciate any help.

Thanks!

[AlmasSuljevic]

Hello DANMETCALF2699,

You may try following workaround and see if it helps. Try to locate .BAK file (in the same directory as .DWG file) and rename it to .DWG. I think somebody already suggested this. Once you open it run AUDIT, -PURGE and save the drawing.

Other way to resolve it is (in case if you have AutoCAD Map 3D in your office (without Civil OE)) to open this drawing and run AUDIT and SAVE to recover it. This may fix the drawing, as well. 

[jalneal]

A little more information and another solution on my end.  I had this happen again, and I noticed that before it happened, things started going REALLY slow - it got to the point that it was using up resources to the extent it froze my machine (a core 2 duo on windows x64) for 15 minutes before I left it, I came back an hour later and it was done.  Saved, exited, and the file was toast.

I noticed that while doing nothing significant, the file size bloated by 4 megabytes - the file was originally 8, and after qsaving before closing it was 12. 

The bak files won't save you if you happen to keep trying to work and save again.  After this problem a couple of weeks ago, I searched and found a program called Acronis True Image Home 2011.  It's $50, but in light of the time I've lost from this modeling error problem, I'm more than happy to fork out the money.  It has a continuis backup system that keeps backups of each file version, so I disabled the backup of .bak files.  I set up an external drive to store backups to and voila, I could go back 20 versions now.

I'm almost convinced that this is related to grading objects - I have only had this error on sites with grading, and often I have started suffering other drawing integrity degradation (grading objects not rendering properly) when it gets to this point.  It seems Grading has always been the least stable - possibly a good reason to create one file per project for any surface work that needs grading objects - build your surface there, then data shortcut it in to everything else.  The place where this is falling apart is in my conceptual designs, where I often slap everything into one file to make rapid changes.  I do have one site per grading group, but in the latest crash today there were 4 sites, 2 grading groups, parcels, alignments, and two pipe networks all in one file. 

To those of you who have the problem, please note what Civil objects are in the drawing and some rough details, and any recollection of unusual behavior.  Maybe we can all identify the common thread here.

[Anonymous]

I agree with jalneal, i think it related to grading groups, but it could also be related to surfaces/feature lines. I have come up with a sort of a work around if anybody else needs it. I found that while I'm working in a not yet corrupted version of the drawing that I know will eventually corrupt, that you don't know if/when the drawing has been corrupted until you close and re-open Civil 3d, and either get that missing logical error or you don't. So what I did to get through my project and meet the deadline was this: Open the latest version of the corrupted file, work for 15-20 minutes, then close C3D altogether. Then ctrl-v a copy of your file in explorer, and re-open that file/c3d (a solid state hard drive will open c3d files about 5x faster). If it is not corrupted, then paste the file into a backup floder. I know it's a hassle, but autodesk has no solution. This will not cost you $50 and you can only lose 15-20 minutes of work at the most.

[Anonymous]

Having this problem too.  I have a good sized FG surface with a variety of objects including grading objects (with the accompanying surface pasted in), feature lines, points, the works.  Over time, TIN lines get deleted and replaced with other objects, TIN lines get swapped and later deleted, etc.  Anyway, I noticed that in the definition of the FG surface, there are a handful of operations with a red circle and slash next to them as if there were out of date.  I wonder if that is the modeling error...

I did an audit many versions ago and it did say something about getting rid of a missing operation in a surface but I forgot the exact language. 

I have unchecked the red slashed operations in the FG surface to see if that helps.  Will report back...

Jeff

[Anonymous]

Update...

Simply unchecking the out-of-date operations did not fix the problem.  What has seemed to help is the "Remove from Definition" option on those bad operations.  I was losing this particular file every couple of hours and now I have gone nearly two days with no crashes. 

Keeping fingers crossed.

Jeff

[jbear0000]

I just had this happen. I had a feature line that I used to create grading. I then copied the feature line to another location to use again and this error occurred. Civil 3D is frozen, I can end it in the task manager, but wanted to give it a chance to finish whatever it is doing.

[ChadBalser]

I have a user having this issue as well - currently working through possible fixes now

The original issue occurred in our Grading Drawing (we have learned to keep our grading separate)

Can not open the Grading drawing at all without immediate error and lockup (can open bak renamed to dwg)

We have an existing surface in another drawing Data Shortcut into the main Civil Drawing and the Grading Drawing

We made some changes to the Existing Surface (removed invalid items in the Surface properties Definition) in the Existing Surface Drawing and saved the drawing, the Civil drawing notifies us of changes to the Data Shortcuts - After synchronizing Data shortcuts we immediately had the same error in the Civil Drawing. (did not save the Civil Drawing)

Re-opened the Existing Surface Drawing and ran audit Found 2 errors and fixed 2 - saved.

Re-opened the Civil Drawing and resynchronized Data Shortcuts > no problem - audit > no errors

Renamed the Grading.BAK to Grading.DWG and opened it up.  Ran audit > a few errors found and fixed.  Saved and currently working.

I think this error is tied to Grading and Corrupt Surface Definition. Either  Inside the drawing, or Data Shortcut - the dynamic functions of the grading seems to find these issues quickly