Workset Crash Solved

Thanks to some folks who left comments here on my previous post, I have figured out the reason for my Revit Workset Crash! Thanks very much.

Here is a cross-post of the solution. This is my response to the AUGI thread that ultimately led to the solution.
If you want to read the entire AUGI thread, you can find it here.

--

I was having a similar issue. I placed a post about it on my blog and got some comments back, one of which directed me to this thread. Steve's reply about the factory post (and disabling addons) did the trick! (Isn't the Internet great? Blog post > Comment > Link to AUGI > Post > Link to Factory > Success! )

Anyhow, here is the summary: In Revit Arch and MEP 2011, I could create a Workshared project, but the next time I tried to open the Worksets dialog, I would crash Revit. STC worked, Save worked, just if you click Worksets, poof.

So, I dragged all Addins to my desktop, tried it, it worked fine. SOOO, I began adding them back to the folder one at a time.

Worksharing monitor - check
Batch Plot - check
MEP Space Naming - check
Revit DB Link - check
Model Review - check
Google Link - check
Avatech Utilities - check (so glad this wasn't it. I use these tools all the time - great stuff).
Revit Extensions - POOF - This is the one!

When I launch, I get the following error:

Revit cannot run the external application "ARECRevitStart" contact the provide of this external tool with the information below

System.IO.FileLoadException
System.IO.FileLoadException: Could not load file or assembly 'AREXManager,
Version=2011.0.0.1408, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The
parameter is incorrect. ﴾Exception from HRESULT: 0x80070057 ﴾E_INVALIDARG﴿﴿
File name: 'AREXManager, Version=2011.0.0.1408, Culture=neutral, PublicKeyToken=null' ‐‐‐>
System.ArgumentException: The path is not of a legal form.
   at System.IO.Path.NormalizePathFast﴾String path, Boolean fullCheck﴿
   at System.IO.Path.GetFullPathInternal﴾String path﴿
   at System.IO.Directory.InternalGetFileDirectoryNames﴾String path, String userPathOriginal,
String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption﴿
   at System.IO.Directory.GetDirectories﴾String path, String searchPattern, SearchOption
searchOption﴿
   at System.IO.Directory.GetDirectories﴾String path﴿
   at 16X1KUK4svrrlwHMOP.vhGAR3PPbtEL1aD7bU.7KsIl5cW4﴾Object , ResolveEventArgs , String ,
Assembly ﴿
   at System.AppDomain.OnAssemblyResolveEvent﴾String assemblyFullName﴿
   at REX.Common.Start.REXStartProxy.OnStartup﴾﴿
   at REX.AREXRevitStart.AREXRevitStart.OnStartup﴾UIControlledApplication application﴿
   at revitManagedAppStartup﴾MFCApp* pMFCApp, AString* assemblyName, AString* className,
AString* exceptionName, AString* exceptionMessage﴿


You can click CLose and continue. Now admitedly, this is not the first time I have seen this error. I just figured, well, until I need that addon, I won't worry about it. :-) Silly me. Well, I have uninstalled it, submitted the report to Autodesk and all systems seem to be a go now.

Thanks to the folks who posted on my blog and helped out here.

Workset Crash

Anyone else having this issue? In Revit 2011, anytime I try to access the Workset dialog, Revit crashes. Happens both when I click the Worksets button and when I try to use the Specify option during open.

What is most annoying is that I get this message about four times before it finishes crashing. Even worse than that, it happens in both Revit Architecture and Revit MEP 2011. I don't have Revit Structure installed, but i suspect it would happen there too.

Anyone have a potential solution? I have tried the repair and reinstall options. I have not tried to uninstall and reinstall yet, because I am not looking forward to having to do that and wait an hour or so for the process to complete, but that is coming next...

Central and Local Files

Many of the large Revit firms (HOK, SOM, many others) have developed scripts or macros to assist users in creating their Local files from the Central in Revit. Autodesk threw their hat in the ring this year in 2010 with the new "Create New Local" functionality. I am very pleased with this new feature which has mostly flown under the radar but I think is a HUGE benefit to all the firms that DO NOT have a home-grown routine. The little check box in the open box allows you to select a Central file, but when you click Open, Revit actually creates a new Local file on your hard drive with your user name appended. Very cool. Long overdue.

However, now this raises the inevitable file naming / office standards debate. The problem revolves around the word "Central" that most firms have been appending their Central file names with. Should this practice continue? It is an interesting question that I think will take some time to resolve. Here is a passage the I just penned for the Worksharing appendix in my new edition of Mastering Revit Architecture (due out soon):

BIM Manager Note: There is some debate as to what the “proper” name for a Central file ought to be. It is current common practice in many firms for the word “Central” to be added to the name. This has been the defacto standard for many years. However, with the 2010 release and its ability to automatically create a Local file (see the “Creating a Local File” topic below), some now question the wisdom of including “Central” in the file name. When you let Revit create a Local file automatically, it will use the same file name as the Central file and append a suffix with your user name. You can see an example below in Figure B.14. This may cause confusion for some since the word “Central” will now be included in their Local file name as well. The most important thing is that it is clear to all team members which file is the Central file and that they do not open it and work directly in it. The traditional reason for appending the “Central” suffix has always been to help make it clear to users which file is the Central. However, with the new functionality to create Local files, it may be a moot point. Consider that even without the “Central” suffix; the file names will always be unique because Revit will automatically append the user name to Local files. So in summary, you may now want to consider a new policy for file naming: Name the Central file without the “Central” suffix such as: ABC Office Towers.rvt. When you create a local file, it will become ABC Office Towers_User Name.rvt. further, since the Central file will always be on the network server and the Local is typically in the My Documents folder (by default), this should also further clarify the difference. What even naming convention and procedure you adopt, make sure it is clearly communicated to all project team members and that all are required to follow it.

Many other bloggers are discussing this topic as well:
Do U Revit?
Revit OpEd

Thought? Comments?