Your Revit Local server goes down, or you cannot connect to your Local Revit server to synchronize. Whatever the scenario, you may be looking for the next step to take; I’ve included a list of items to test [and what to collect should the troubleshooting need to go to the next level]. Keep in mind this post is targeted towards a Revit Local Server that was working as expected, not one being initially configured. If doing initial configuration, first visit my previous post here for initial troubleshooting.
1. Verify Central Server is Online
Before testing anything have a user temporarily connect to the Central Server under Collaborate > Synchronize > Connect to Revit Server. This way we can confirm this is just the Local server and not the entire server network.
2. All Users \ Models or Some Users \ Models?
Next verify how widespread the issue is. Aside from the first user who reported the issue, have a few other users attempt to either synchronize or connect to the same Local server. We want to verify if this issue affects all users and all models on the Revit server.
If all users are experiencing the issue, move onto step #3.
If it only affects one or a few users [not all of them], verify if any of these users have experienced this dialog:
If so, and you are running Revit Server 2011 or the initial release of Revit Server 2012 [update 1 not yet applied] have them take the following steps:
[A] In Windows Explorer, navigate to the Projects folder on the Central server.
[B] Delete the contents of the Users_Temp folder for the user experiencing the issue. This directory is located at [Revit Server Project Root]\[myModel]\Users_Temp\[my User].
For example, if a user “UserA” is having trouble syncing with the model “File.rvt” located in the folder “AllProjects,” and Revit Server’s project root is “d:\programdata\autodesk\revit server\projects” the contents of the folder "d:\programdata\autodesk\revit server\projects\AllProjects\File.rvt\users_temp\UserA" should be deleted.
[C] Repeat the same process for the Local Server. See if the specific user can connect \ synchronize with the server afterward.
3. Can you Connect via Revit Server Administrator or Remote Desktop?
Assuming no users can connect to a specific server through Revit, first attempt to open Revit Server Administrator from a client workstation. For example, they would open Internet Explorer and enter the following address, substituting <RevitLocalServerName> with their Revit Server name:
If nothing comes up the RevitServerAppPool may be stopped or the entire server may be physically down; ping the server to ensure it is up and running, and restart it if necessary. In addition make sure to verify the network integrity, and VPN connection if in place.
Next attempt to make a remote desktop connection to the server. Can you connect normally through Remote Desktop? If Remote Desktop is not configured, have a user physically log onto the Local server to verify.
Assuming you can connect via remote desktop from a client workstation [or log onto Local server] move onto step #4.
4. Verify the RevitServerAppPool and Autosync Service are Up and Running
Once connected to the Local server via Remote Desktop, verify the following areas:
[A] Open Internet Information Services Manager [Start > Run > INETMGR]. Expand Server name > highlight Application Pools > highlight RevitServerAppPool. Verify Status reads Started; if not click Start.
[B] Open Administrative Tools > Services [Start > Run > Services.msc]. Locate Revit Server AutoSync. Verify Status reads Started. If not right-click > Start.
Specifically related to [B] Autosync, it is also a good idea to take a look at the LocalService.log file in “C:\ProgramData\Autodesk\Revit Server\Logs”. If you see numerous repeating lines for the same model \ same process it may indicate that Autosync is not functioning properly.
Once you verify the items above check out, move onto step #5.
5. Has Anything Changed?
Before collecting data, step back and verify if anything has changed. Such as:
[A] Power \ Network Connectivity?
[B] Windows Updates?
[C] Did any users check Compact File when synchronizing with central?
[D] All users have unique usernames?
[E] Was this Local server recently brought online, or a large number of linked files saved to the server at once?
[F] What was the last successful action?
[G] And are there any project .lock files larger than 0 KB [See the page here for additional information]
6. Data Collection
If you get here and the server is still outside communication, data collection and analysis are most important. It is essential to collect data from a small period of time, focusing on recreating the issue.
Collect the following files using the attached process:
[A] Shut down Revit.
[B] Shut down Revit Server.
[C] Archive the logs on the Revit Server and then empty the Log folder [you can archive to another folder].
[D] Restart Revit and the Revit Server, then perform the action [that does not work] and then capture the log files and Revit journal file.
Additional information to include:
-The Revit Central and Local server names and IP addresses.
-Paths specified during installation if other than default.
-Confirm if they are physical or virtual servers. And if possible include their physical geographic locations.
-Windows Server 2008 or 2008 R2