topic last operation error in Modeling

last operation error

Anonymous — Wed, 12 Oct 2005 13:21:18 GMT

Ok gang….out of the blue…this error message started cropping up…any takers…

Re: last operation error

Anonymous — Wed, 12 Oct 2005 15:31:48 GMT

well I deleted all of the preference files...and that doesn't seem to work...this error message only pops, right after I sign in and when the files closes....

Re: last operation error

Djordje — Wed, 12 Oct 2005 15:41:34 GMT

r wrote:
well I deleted all of the preference files...and that doesn't seem to work...this error message only pops, right after I sign in and when the files closes....

What was the last operation?

Sign in? Teamwork?

More details, please!

Re: last operation error

Anonymous — Wed, 12 Oct 2005 17:18:09 GMT

Djordje

most likely sign out, and in teamwork...at least for me...but it slow creeping through the office...which has me concerned...the first project that it occured, a member could not log on, his user name had to be changed.....

Re: last operation error

Anonymous — Wed, 12 Oct 2005 22:21:08 GMT

Any progress on this problem? I get it when opening section or 3d windows; increases with use of AC9se library objects and boolean operations on walls. However, also seems to be machine specific.

Perhaps this error message can be suppressed as it serves no useful purpose.

Re: last operation error

Anonymous — Thu, 13 Oct 2005 07:26:56 GMT

This error message deserves the "most useless message of the decade" award.

Seriously though I hope the next version removes this error message or better still advise what the real problem is.

In my experience this error can often be attributed to a corrupt drawing element eg section ref, object, door, window being the cause. If you can find it (no mean feat) and delete, this can fix the problem.

I have resorted to opening all doors, windows and objects one by one and seeing if an error message occurs until the offending parameter is corrected or delete and put in a new one.

Sometimes I even save the file and restart the PC and then the error message disappears.

Re: last operation error

Laszlo Nagy — Thu, 13 Oct 2005 21:34:03 GMT

There is a related article on ArchiGuide:

http://www.graphisoft.com/support/archicad/archiguide/Errorsduringlastop.html

Re: last operation error

Anonymous — Thu, 20 Oct 2005 19:24:51 GMT

Maurice wrote:
This error message deserves the "most useless message of the decade" award.

I agree - I haven't seen a message quite this perverse since Windows 3.1. (Shouldn't there be a "Not OK" button next to the "OK" button that would send a report to Graphisoft?)

Maurice wrote:
I have resorted to opening all doors, windows and objects one by one and seeing if an error message occurs until the offending parameter is corrected or delete and put in a new one.

...that way lies madness, not to mention low productivity - it shouldn't be your task to debug this pricey software package.

However, having said that, I've checked my "Report" and found that all the error messages (dozens per day) are the result of AC9SE Library (the latest) GDL object errors, mostly doors and windows - "Group operation errors" - and columns - "Too many CUTEND statements".
I get the feeling that the initial release of the AC9SE Library was a bit rushed - I came across dialogue boxes under the wrong tabs, and buttons that had been switched (the buttons performed their neighbour's function). The second release still seems to have problems and I hope these can be addressed soon as I'm using this library in a number of projects and am reluctant to switch libraries mid-project.

Re: last operation error

TomWaltz — Thu, 20 Oct 2005 19:47:54 GMT

no, THIS is the most useless.....

Re: last operation error

TomWaltz — Thu, 20 Oct 2005 19:48:30 GMT

but THIS remains my favorite:

Re: last operation error

Anonymous — Thu, 20 Oct 2005 23:28:22 GMT

Those are great - you Mac guys have all the fun.

However, I did once get the "Warning" warning message, I think with AC6. I just laughed at the time, but two days later I was fired (too much laughing and not enough CD's), so it wasn't entirely useless. It would have been more helpful, though, if it had said "Warning, You're Going To Be Fired In Two Days".
The second message I think I recognize from my Economics 101 as the formula for throwing good money after bad.

But seriously, as a GDL Guru you would know how easy or difficult it is to fix the code in these objects. I assume that "Too many CUTEND statements" isn't quite as bad as too few. As for "Group operation errors", I haven't a clue - maybe I put a zero where it's not allowed.

Re: last operation error

David Collins — Mon, 24 Oct 2005 10:17:09 GMT

TomWaltz wrote:
no, THIS is the most useless.....

I just got the blank-warning-exclamation point pop up myself for the first time. Very unnerving, I must say. I'm the boss in my office so my job is fairly secure, but what..? Fire? Earthquake? Divorce? Elections?

Seriously, I'm working on a monstrously complex model and I suspect I ate all the RAM. Does anybody have any idea at all what sets this one off?

Thanks