Revit 2015 R2 UR11 kills Revit Server?

[jheltz27]

Anyone else having issues with opening Revit Server files after updating to the Revit 2015 R2 UR11 that was posted last week?  All of our users who installed the update last week cannot open anything on our Revit Server Network while anyone who hasn't updated yet can.  I'm trying to start an incident report with Autodesk support but the website is flaking out.

[mattmas]

Quick-and-dirty workaround, that I cannot say is 100% safe - it just seems to work so far...

1. Go to C:\Program Files\Autodesk\Revit 2015.

2. Rename the file "Autodesk.Revit.Social.DLL" to "Autodesk.Revit.Social.v130.dll"

3. Copy the "Autodesk.Revit.Social.DLL" from the "RevitServerToolCommand" subfolder up to the "Revit 2015" folder.

This at least makes it possible to open things, but I can't stress enough that I don't know if this is a bad idea (or how bad).

I have reported it to Autodesk... Hopefully we can get a new UR11.

Best Regards,

Matt

[jheltz27]

I've opened up a case with Autodesk also Monday - sent them files from the Revit Server and everything. Haven't heard back from them yet on any resolution.

[kathryn.langan · Accepted solution]

UPDATE 12/31:

Regarding which methods to try... It will depend on whether you are using both Revit Server and Collaboration for Revit.

If you are using both Revit Server and Collaboration for Revit, then please use Method 2, as replacing the DLL is likely to interfere with the cloud workflow.

If you are NOT using Collaboration for Revit, please use Method 1, as if possible, it would be better to only replace the DLL than modify the config file.

-------------------------------------------------------------------------------------------------

Hi All,

Thanks for bringing this behavior to our attention. It has now been reported to our development team and they are currently investigating a resolution. In the meantime, we have established a few workarounds. Also, we have published an article to the Knowledge Network: Revit 2015 UR11 breaks Revit Server

There may be a slight lag before the article publishes live, so I've included the workarounds here as well. Going forward I would suggest referring back to the article though, as it will remain linked to the investigation and this post could possibly become outdated. Method 1 (like Matt's post above) is likely the easiest/fastest solution.

Method 1 (firms using Revit Server, but not Collaboration for Revit):

1. Go to C:\Program Files\Autodesk\Revit 2015
2. Rename Autodesk.RevitServer.Social.DLL to Autodesk.RevitServer.Social.DLL.UR11.
3. Go to C:\Program Files\Autodesk\Revit 2015\RevitServerToolCommand
4. Copy the Autodesk.RevitServer.Social.DLL file to C:\Program Files\Autodesk\Revit 2015.

Note: Once a final solution is released, revert the changes above before installing an update for Revit by deleting the copied Autodesk.RevitServer.Social.DLL and renaming the Autodesk.RevitServer.Social.DLL.UR11 back to its original name.

Method 2 (firms using both Revit Server & Collaboration for Revit):

1. Make a copy of the Revit.exe.config file to preserve its original state (including timestamps).
2. Edit the Revit.exe.config file (in a text editor like Notepad.exe).
3. Locate the following line:
   
   </assemblyBinding>
   
   
4. Insert the following BEFORE this line:
   
   <dependentAssembly>
        <assemblyIdentity name="Autodesk.RevitServer.Social" publicKeyToken="d672471c03b2c408" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.3.0.0" newVersion="1.3.0.0" />
   </dependentAssembly>
   
   
5. Save the changes and close the file.
6. Restart Revit.

Note: Once a final solution is released, revert the changes above before installing an update for Revit by going through the following steps:
(Failure to revert the changes updates may fail to update the Revit.exe.config file correctly.) 

1. Delete the modified Revit.exe.config file.
2. Rename the copy of the Revit.exe.config back to Revit.exe.config.
3. Restart Revit.

Method 3:

1. Reinstall Revit 2015 (without installing UR11).

I'm sorry for the trouble this has caused. I hope these workarounds help until a resolution is established by development. Thank you again for reporting the behavior. 

[risaku]

... and that's why we test this stuf ...