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.