The information in this article applies to:
I sometimes encounter a Warning message that says,
This file cannot be saved to the specified location. Try a location with a shorter path name. If saving to a removable drive, make sure it is accessible.
Could not open the file to write. This may be because the drive you are attempting to write to has been ejected. If this is a temporary drive you can reconnect it and try again.
I am not saving to a removable disk, so why am I seeing this message?
This message will display whenever the program tries to save a file to a particular location but isn't able to.
There are a number of specific reasons why this Warning message might display:
Since there are a number of possible reasons why these warning messages might display, there are also a number of different possible resolutions.
If you are working on a file that is saved somewhere other than your local hard drive - for example, on a network server or on a removable USB drive - begin by confirming that you can actually browse to that location in Windows Explorer. If you cannot do it, the program will not be able to either.
If you can access the network or removable location, bear in mind that the process of saving in Chief Architect will be slower to that location than if the file were located on your local machine.
We do not recommend that you work in this fashion for a number of reasons, including program slowness; but if you do this, expect to be patient when saving files - particularly with large files. To learn more, visit the article on "Troubleshooting Slowness in Chief Architect Plans" linked in the Related Articles section.
If you attempt to save a plan or layout file when Chief Architect is still in the process of performing the last save command, this message will display. Click OK and wait a few moments while the program finishes saving.
Chief Architect automatically saves Archive files for your named files in the program's Data folder. More information can be found in the "Accessing Your Archive Files" linked in the Related Articles section.
By default, the Data folder is located in your Documents directory.
If you specify a non-default location for the Data folder that is either not the local hard drive or not writable per your Windows operating system, this Warning message may display whenever the program saves an Archive file.
Similarly, if you specify a non-default location for your Documents directory that is either not located on the local hard drive or not allowed by your operating system, this message may display when the program saves an Archive file.
A similar situation can occur if you specify a non-default location for your Chief Architect Undo directory. If you choose a location that is not on the local hard drive, or not allowed by Windows, this Warning may display when the program writes an Undo file or when you try to use the Undo command.
There are a variety of different programs that can temporarily lock files on your computer while they are running - for example, backup utilities and anti-virus or other security software. Consider scheduling file backups and hard drive scans during the times when you are typically not working, or schedule them less frequently during those times.
On occasion, your Windows operating system may identify a file as locked, or accessed by another program, when it is not. Usually, if you wait a few minutes the issue will resolve itself; however, you may find it necessary to reboot your computer.
Windows allows a maximum file path name length of 260 characters, and it is very important to remember that a file name is not the same thing as its full path name.
MacOS allows a maximum file path name length of 255 characters.
Bear in mind that Chief Architect creates Archive and Auto Save copies of named plan and layout files on a regular basis, and that these files' path names are typically longer than those of the original files. For example:
When choosing a file naming convention and file management system, therefore, try to use short file names and limit the use of folders nested within other folders.
To learn more about unwritable locations in Windows Vista and newer versions, refer to Microsoft Support article 927387: Common file and registry virtualization issues in Windows.