If it is set to something different, then make note of it and enter a . for none and see if your saves are faster!

another troubleshooting tip is to turn off making the backup file to see if it makes a difference.

From the Help file:

MOVEBAK (Express Tool)

Changes the destination folder for drawing backup (BAK) files.

Once you specify a folder, the drawing's BAK file is placed in that folder after every save operation.

Enter new value for MOVEBAK, or . for none <current setting>:Enter a . (period) for none or type the folder nameIf you enter ".", the MOVEBAK folder name is cleared and new BAK files will be created in the original folder.Note: Creating BAK files is optional, but recommended. The system variable ISAVEBAK controls whether BAK files are created each time the drawing is saved. You can also enable this function from the Open and Save tab of the Options dialog box.

03/24/2017

A Revit Server network is designed to support worksharing of multiple central models across a wide area network (WAN). This allows you to "Host" the models at one of your offices and set up Accelerators at remote locations to improve performance when working on the model.

Install and set up doesn't seem to be quite as strait forward as one would like...so I will attempt to shed some light on Pre Install basics...I have a white paper of the full install process.

Let's start at the beginning...

It is recommended that Revit Server be installed on a dedicated server.

Projects and Cache will default to the C drive. If you want to install those on another drive on your server that is fine or you can store it remotely on a Network Server provided you created a domain user account named “RevitServerService” to enter during the install. Keep in mind that the drives must be in line with the system requirements.

Storage performance is a big piece of being successful with Revit Server so be mindful of the information in the system requirements.

Please also be aware that there are some Revit Server things that cannot be installed anywhere but the C drive so make sure you have plenty of open space since the logs can get pretty large...and low space on the C drive can cause other issues as well.

You should NEVERplace projects and/or cache on a NAS or SAN device. They are not supported by Autodeskand I speak from experience, I can guarantee you will have issues with accessing models.

RAM

The system requirements go as low as 4 for a minimum, but I would not recommend any less than 16, but prefer the performance recommendation of 32.

Virtualization

VMware® and Hyper-V® Support (See Revit Server Administrator’s Guide). But remember you must still meet the performance requirements. The IOPS (Input/output operations per second) performance of your setup should compare to the kind of physical drive Autodesk is looking for.

Note: Revit Server performance in a virtual environment such as VMWare needs careful tuning to avoid significant performance issues, and you should allow for additional overhead beyond the basic requirements listed here. It is recommended that you compare the performance of your virtual environment versus a physical environment. Test the network throughput and latency of your virtual environment versus your physical hardware and adjust accordingly for best performance.

Cloud Servers

WE have clients using Cloud Servers like Azure and we use them as well for some of our testing environments. The same rules apply here as with a Physical server or Virtual Machine.

Bandwidth

Per Autodesk, reasonable performance can be consistently achieved if available network bandwidth exceeds 3Mbit/sec.There are scenarios where more bandwidth may be required, please refer to the Autodesk Bandwidth Document for more detailed information.

Accelerators

If you have offices that are remotely located from the host you will need to setup a Revit Server Accelerator. The same system requirements apply here too.

After a few releases of no change to the file format this year we have a new file format.

A note from Autodesk:

The DWG format has been updated to provide improvements in the efficiency of open and save operations, especially for drawings that contain many annotative objects and viewports. Additionally, 3D solid and surface creation now uses the newest geometric modeler (ASM) which provides improved security and stability.

Here are some of the last few file formats and which versions of AutoCAD could open those files.

File Format: Versions of AutoCAD:

2004 2004, 2005 and 2006

2007 2007, 2008, 2009

2010 2010, 2011, 2012

2013 2013, 2014, 2015, 2016 and most of 2017

2018 2018

Let's hope that the 2018 dwg file format sticks around as long as the 2013 file format!

03/16/2017

While running an Autodesk installation you get a message that "The setup was unable to automatically close all requested applications. Please ensure that the applications holding files in use are closed before continuing with the installation."

This means that there are Autodesk services or software still running in the background.

You will want to open task manager and make sure that there are no Autodesk items running. Here is a few that might be running if you already have some Autodesk software installed on your machine.

If you see Autodesk component (32bit) this will be your installer so do not end this task. If you expand the task you can see what it is.

While running an Autodesk 2017 installation you get a message that "AutoCAD 2017 is not found on this computer. You will need to install AutoCAD 2017 to install this product specific pack."

The issue here is that your machine has a piece of this software already installed and is confused.

Solution:

You will need to do the following to remove anything Autodesk 2017:

Run the Microsoft Fixit tool to find any Autodesk 2017 software as well as ACAD Private and remove them. Here is how to use this tool: How to use the Microsoft fixit tool. You do have to run this tool for each Autodesk software you find in the list. Once you are finished reboot your machine.

Open your registry and manually delete the key HKEY_CLASSES_ROOT\Installer\Products\FEE98B82100000001320FCF3A3907BD7

When you are opening a Collaboration for Revit model (C4R) correctly but the title of the drawing is the long alpha-numerical name like 4e0357e2-13ea-4d72-bece-7254586ad23d.rvt which is the cached file name. This indicates there is something corrupt with the cache file data.

As a review you open any C4R model by going to your Revit Open dialog box and click on the BIM 360 TEAM icon. You then see the folder(s) that stores your model. The name of the file should show at the top of Revit not the cache name.

You will fix this by following the Autodesk Clear a corrupt/damaged C4R model

Solution:

Identify the Project and Model GUID for the affected model:

Open a journal file recorded when the error was presented and find the error within the journal file.

Above the error, look for text which starts with CLD:\\{Project GUID with numbers and dashes}(Project Name)\{Model GUID also with numbers and dashes}(Model Name).rvt

Note down the Project GUID, the first part in the brackets {}, and the Model GUID, the second part in the brackets.

Identify the Collaboration Cache Root folder:

Below the line with CLD:\\ look for a line that starts with SLOG Local=.

Make a note of the Collaboration Cache Root folder name after the CollaborationCache folder (it will be in all caps with numbers and or letters), by default this would be within:%LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit ####\CollaborationCache

Move the local copy of the model in the following path to another location (e.g. the Desktop)<Collaboration Cache Root>\<Project GUID>\<Model GUID>.rvt

Move the central cache file in the following path to another location (e.g. the Desktop)<Collaboration Cache Root>\<Project GUID>\CentralCache\<Model GUID>.rvt

Move the model folder in the PacCache to another location (e.g. the Desktop):C:\Users\%USERNAME%\AppData\Local\Autodesk\Revit\PacCache\<Model GUID>Note: Older versions of C4R stored the PACCache in “<Collaboration Cache Root>\<Project GUID>\PACCache\<Model GUID>”

Alternate SledgeHammer approach (this is easier but may break things again): Clear the entire CollaborationCache folder. Note: This would force all model data to be re-cached and there is the potential that whatever caused the initial corruption would re-occur either on this system or on another.

Don't have the updated version of Revit or Collaboration? Click on the links below to get the latest updates: