This Operation Could Not Be Completed

This error message came up for a customer of mine when they were upgrading a Revit 2013 project to 2014 and using Revit Server.  The file worked perfectly in 2013, but as soon as the file was upgraded to 2014, they couldn’t save it to Revit Server 2014…the above mentioned error popped up.

So, like I do with a lot of my customers, I had them send me the file so I could test it out on my end.  This allows me to test the file using my setup, which helps determine if it’s a file issue, Revit Server issue, or maybe both.  Now, you might be asking…”how do you know what issue it is?”  If I can replicate the error on my end, it’s likely a file issue or potentially both.  If I can’t replicate the issue, then chances are it’s an issue with their Revit Server.

While I was getting the file downloaded from the customer, I had them try another file (different project) and it worked perfectly.  Okay, that narrows it down to more than likely being a file issue…but I still wanted to verify that on my end to make sure.  Sure enough, I got the file and received the exact same error message when trying to save the file to Revit Server 2014.  Autodesk, here we come!

I worked with Autodesk support to get their take on the file. They attempted to do the same thing we did, get the file saved to Revit Server 2014…same error.  After they reviewed the journal and log files (which I looked at as well, but couldn’t decipher what was going on) they determined that it was an issue with the project’s permission data.  The “short-term” fix was to detach the central and blow away the worksharing…yep, bring it back to a single-user file.  Then, once that process was completed, re-enable worksharing.  By doing that process, the permission data was stripped out and re-established and the file could now be saved to Revit Server 2014.  However, the file was sent over to the development team for them to take a look at what was going on in the upgrade process since the file worked just fine in 2013.

The development team came back and said they found the issue, it was an invalid workset ID assigned to one of the elements.  They were able to fix the file by assigning a workset ID to the problem element.  They sent me the fixed file and it worked perfectly.  And they didn’t sent back the converted single-user file back, they sent back the original file with the original worksharing/worksets.  Sweet!

But, I couldn’t stop there….I had to ask the question; “Is this a fix I could have done, or does this issue need to be handled by the development team?”  The answer, they had to do it as we “end users” don’t have the ability to assign workset ID’s to elements.  However, you might be able to cut/paste the problem element once you know what element it is (by investigating the journals/logs) and fix it that way…

Challenge Accepted!! (when I get time to test it out …)

Autodesk BIM 360 Products

So I’ve been pretty quiet on the blog front this year (that’s kind-of an understatement!).  It’s not that I don’t have much to share, but it seems like every day passes way too fast.

The main reason though for my practical non-existence in the blogging world is that in the summer of 2013, I started the trek down the BIM 360 road with Glue and Field.  I was one of only a select few that were chosen by Autodesk to partake in being trained on the BIM 360 products in the US. The BIM 360 products are not like the majority of the Autodesk software and Autodesk didn’t release these products to all of the channel partners/resellers.  So much of my time that I have “free” (time that I’m not spending with customers around a handful of products), I’ve been diving into BIM 360 Glue and Field

I’m still involved in the Revit products, whether it’s teaching, consulting, implementing, supporting, etc., so I still have information to share around the Revit products.  This particular blog isn’t going to become a BIM 360 blog, I’m handling that over on my Navisworks/BIM 360 blog   I will however, be throwing some “nuggets” of information about how Revit works with BIM 360 Glue and Field on this blog, as well as hopefully posting more about Revit this year!  So hopefully you won’t be seeing a 9 month lapse in posts from me

System Requirements for Revit 2014 Products

Instead of copy/pasting a giant list of requirements that Autodesk has listed, below is a link to the System Requirements page on Autodesk’s website:

System requirements for Autodesk Revit Products

Please, please note that Windows XP is NOT listed!!  If you are still using XP (or even Vista, which I rarely run into), you’re going to need to upgrade your OS!  Not to say that Revit 2014 won’t install or run, but any issues relating back to the OS will not be supported.  Also note that Windows 8 32bit is not supported.  Autodesk has a page dedicated to OS compatibility for Revit, all versions - Operating system compatibility for Autodesk Revit Products

Out of the 3 configurations they list for system requirements, I would go for the Value: Balanced performance configuration at a minimum.  However, if you really look at the difference between that and the Performance: Large, complex models configuration, it’s mainly more RAM….so might as well stuff as much RAM in the machine as you can afford.

What’s New in Revit Architecture 2014

Yep, the wonderful time of the year when bloggers all across the globe push out their “version” of what’s new in the 2014 Autodesk software.  Instead of reposting a long list of enhancements, here’s a couple posts that do a great job of showing the new features…

• As always, David Light has his great post on the new features!  Click HERE to go to his post.
• Autodesk even got into the “game” this year and has provided a page with the new features (as well as many of the existing features).  Click HERE to see Autodesk’s page.

A couple items that probably won’t make the list for new features in Revit 2014 are integrations with Inventor and Vault. 

• Inventor 2014 can now export directly to a Revit Family (RFA) file.  I haven’t been able to work with an exported RFA file from Inventor yet since we had some version issues.  Once the products hit the streets, I’ll post more about this.
• Vault integration has been updated to now include search capability of the Family properties. I’ll be posting more about this as well in the future.

I also put together a video for our (MasterGraphics’s) YouTube channel. Once we get it uploaded, I’ll create a new post with it and update this post as well.

And now the wait begins until the software can be downloaded….

Flipping Stairs Flips Stringer Side

Little something I ran across during a class a couple weeks ago.  When working with Stairs in Revit 2013, someone asked about having a stringer on one side and not the other.  No problem with Component Stairs in Revit 2013. 

Then I went to show how you can change the “direction” of the stair by using the Flip Direction arrow at the top of the stair….and this happened:

Notice how the stringers also flipped sides, which is not the outcome that someone would want.  Sure, we can go in and remove/add the stringers to be on the appropriate side, but that’s just extra work!  Besides the fact that the stringers aren’t continuous …there’s a piece of stringer missing on one side of the landing (in the 2nd image).

Just a little something to be aware of when flipping stairs.  And it doesn’t even pertain to one sided stringers…it also pertains to each side having a separate profile being used!