Revit Server 2017

[rwebb0418]

Alright I'm at my wits end with Revit Server 2017.  Here's what I've got:

• 3 Servers
  • Windows 2012 running Revit Server 2014, 2015, 2016, 2017 (this is my company webserver)
  • Windows 2012 hosting models for Revit Server 2014, 2015, 2016 (company domain controller)
  • Windows 2008 running and hosting Revit Server 2014, 2014, 2015, 2016, 2017

Here's my problem: When I install Revit server 2017 on the webserver, and tell it I want to host the models on a network share (domain controller hosts all of our data) everything appears to install just fine.  When I try to add folders to the admin console they add, and then if I try to rename them in the console it errors saying "An Unexpected error occurred".  In the ModelService.Log I get ERROR TID(22) Unlockpathdoesnotexistexception.  And i'm left with a bunch of "New Folder" and New Folder (<insert number here>)" folders in the console.  Within Revit I can access the server, and view everything that's stored on the server (including all of the New folders) but I can't open any models from the server, and when I try to save a new model to the server I get the generic "Operation could not be completed" and the model does not save.

If I uninstall 2017 from the webserver, and then reinstall everything doing a default oob setup (including the model storage) on to the webserver it all works just fine.  

RevitServerService user is setup and works just fine, and has since we started using Revit Server in 2014.

Permissions have all been set correctly on the 2017 shared folder.

There is nothing different about the 2017 installation from any of the previous version installations, it just doesn't work.

[Anonymous]

You may have a missing C++ redistributasble:

https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles...

This happened to me on my new 2012 server.

[rwebb0418]

Both servers are up to date on Visual C++ 2010 Redistributable.  I've removed and reinstalled 2010 on both 2012 servers to ensure that was not the issue.

[Anonymous]

Make sure the SSL bindings for the 2017 applications are set correctly.

And check the Managed Pipeline setting is set to 'Integrated'

This is me just throwing things out there that tripped me up.

[rwebb0418]

Appreciate the help so far.

Never had to use the SSL settings on the previous versions so it's currently set to no SSL required and there is no SSL binding for the webpage.  Upon setting a SSL binding and attempting to access the HTTPS version of the page it throws "An unexpected error occured".  What should the SSL settings be?  

Http looks and loads fine, just can't use the page to do anything.

The Managed Pipeline is set to Integrated

[Anonymous]

My SSL setting for all apps/services is "Ignore"

It sure sounds like there may be an added security group in 2017 that needs created....  Especially since the previous versions are working.

[rwebb0418]

Okay that's what I've got as well (after removing the SSL binding that I added for testing). 

As for the security, on the share I've even gone so far as setting Everyone to full control for testing.  Still nothing.

One thing that I have noticed is that compared to the 2016 installation, the 2017 project folder is missing the ModelLocationTable.db3.  I don't know if this file is created only once you save a model to the server or if the initial files is created when the server starts.

[davidloe1]

I'm having the exact same problem.  Installation goes smooth.  Previous versions working.  Can't create a directory from web administrator and ModelLocationTable.db3 is missing.  I see in the AutoSyncLog.log file that it's erroring with and unable to open database file error but it gives no furthur detail.  I'm not sure what else to try.  

[rwebb0418]

And you're storing the project and cache files on a network store as well?

Hopefully someone has a solution, maybe Autodesk will actually chime in here sometime soon.  We've got a couple jobs starting up in 2017 soon here and if need be I'll store it all on one server, but there should be some fix for this as it's not been an issue on any previous version.

[davidloe1]

Yes. I've installed locally and it works as expected. Network does not. All other versions are stored on a network share.


David

Edited by request
Discussion_Admin

[Lance.Coffey · Accepted solution]

This behavior has been reported to our developers.

The following article has information on the current status of the investigation and will be updated when a solution is released:

Revit Server 2017: Remote Storage does not work

[Lance.Coffey]

@rwebb0418 Are you able to get Revit Server working by using Local storage (either on the original server, or loading Revit Server on the remote location you were trying to use)?

[rwebb0418]

I can get RS working if I install it using local storage on either machine. As soon as I install it using network storage it doesn't work. I've even tried installing it with local storage, verified that it works and then modifying the configuration files to point at network store and it stops working.

[Lance.Coffey]

At this point remote storage will not work (with the 2017 version), the only solution I've found so far is to use local storage either on the original system or install RS on the remote server.

Once a fix has been released for the issue (check the article above for updates) and the updated RS loaded, then you can move the project data as needed:

- If saving RS project data locally (not on remote server), you can transfer projects using the Revit Server Administrator webpage or by locking the server and copying the project files manually.

- If loading Revit Server on the remote server, you would not need to move the project data, but lock the server, uninstall RS from the remote server, and install RS on the original server (directed to the remote project folder) and unlock the server.

[rwebb0418]

Thank you for the response, I will continue to check the article and wait for a solution.