Weight... for what?

I received this screen capture of an error message from one of my Power Revit Users... 
Thanks Deb!

First time I've seen this error before... we were having network issues so I suspect it was related to that.

I'm kind of thinking that when they wrote this error message (and obviously the Revit programmers have put an awful lot of thought into this message) that it was a spelling error and should really say "Wait"... or "Please wait while I try and figure out what to do next"..!

Weight.... really? 
Can you please add a little more detail...??!

Kind of reminds me of the joke where the radio operator of a sinking vessel put out the mayday call stating that they are sinking... and received a reply asking what they were thinking about?
But once again I digress.....

I did read one blog after doing a search for this error message and found this... 
" I am still trying to figure this one out, are the programmers hacking my webcam and calling me fat?  Or is my building going to somehow throw off the earths gravitational spin if the model is actually built?" http://bdmackeyconsulting.com/revit-weight-warning/

That made me laugh!!... but then again this project is a high-rise.. just in case I'll ask structural what this building weighs....

Filing this error message under "Ridiculous".

Sc

Update: Ok, so we got this message again and I couldn't remember how we got around it last time... this time we couldn't even close the file...

So we blitzed (deleted) the back up files, saved and this time the sync worked!

Inches to the forth power error message

Received another weird error message from Revit.

Not quite sure what prompted this error message....
I did some research on this message and this is basically what I found was that in some cases it is caused by insufficient disc space. 

I found some information regarding this error on Jeremy Tammik's blog "The Building Coder" where he talks about when Revit  was first developed in the US it was based upon Imperial units. When Metric and other units were introduced into Revit the basic existing database (based upon Imperial) remained.
Jeremy mentions "When Revit's API was introduced, the simplest method of introduction was to expose the database values directly. Thus feet for length, metric for everything else".

Thus I believe the reason for the verbiage of the error message. 

In my case it wasn't a large file and running a audit on the file seemed to have resolved any issues.

Just got this reply from Autodesk Technical Support...

The error is incorrect and should read "end of file".

From the description, the file on the server is not a full version of the file, but a full version does get written when you try the command again.

If you have not already, I would purge the file to reduce the file size. I would also make sure that no one else is accessing the central file when others are saving or syncing.

It was quite a quick response from Autodesk.

I'm starting to collect a variety of "Weird" Revit error messages!

Sc

Past it's End Error! Have you ever been past your end?

In a previous post I wrote about a warning message that stated that there were no warnings!
Warning... there are no Warnings!!

Kind or reminded me of the "Lost in Space" Robot.... 

Warning Will Robinson, Warning.... There are No Warnings !!!

Well...!

I now have another funny error message produced by Revit!

Now, I've never heard of my Central File being "Past it's End" before, its kind of like my project has a expiry date? Or maybe Revit decided that my project is now complete and we have passed the end of the project?? 

Once I passed the rear end of my car but that's not really Revit related.....I digress.

Not really sure exactly what Revit means by this statement...? I believe it was caused by one user pushing a large amount of data to the Central file as another user was trying to pull information from the Central file...and basically Revit timed out with the sync...  Once the "push" of information was complete the "pull" resulted in no error messages.

I've had similar issues before with many people working on one project and having syncing issues, using the Revit Server resolves a lot of these issues.... 

Once the Riverbed issue is resolved the Universe can once again regain stability and there will be no Warnings from the Revit Robot.  

Nostalgic TV...

Sc

Revit Error: "Extension Layers at the base of the wall must be adjacent"

Came across this error that really perplexed me... it was the verbiage that Revit used that I didn't understand...

 
After hunting through the actual wall assembly I found what the problem was and the message then made sense.

what I found that if you have more than one wall layer component at the base (or top) that is unlocked to make it extendable they need to be next to each other. You cannot have one layer unlocked and it's adjacent layer locked.

This only applies when you have multiple layers that are unlocked. you can have a single layer unlocked anywhere along the assembly but as soon as you unlock another layer they need to be next to each other.

Here are some examples:

Any one Wall Component Layer Unlocked is OK.

Any two or more Wall Component Layers Unlocked that are next to each other (or adjacent) is also OK.

Revit will not allow two or more Wall component Layers that are unlocked that NOT next to each other. Hence the error message that you cannot ignore.