<< Click to Display Table of Contents >> Navigation:  Installation and Update Guide > Server installation > Possible problem when renaming existing directory

If you are updating an existing installation by making a new installation in the same directory as the old installation – which is generally a good idea – a problem might occur when the old directory is renamed to make room for the new installation and to create a backup in one single operation.

 

The renaming of an existing directory – if one exists – may fail. If that happens, the message shown in the figure below will be displayed.

 

 

If so, it is in most cases not necessary to abort the installation. If you can find the reason for the problem and solve it, you can simply click the OK button afterwards. The renaming will then be retried. If successful, the installation procedure will continue as if nothing had happened. If not successful, the message will turn up again, giving you yet another chance to solve the problem.

 

This is a common problem in network installations, and it might be quite difficult to find out what is causing it. In such cases, it will be necessary to use some force to throw out the users that are blocking the renaming, even if you do not know who they are. An easy way of doing that is to remove the share of the directory in which the cadett ELSA main directory is located. When doing so, anybody accessing the installation will be thrown out. The share can then be immediately restored.

 

If you throw out all users as suggested above and still face the same issue, you are probably stepping on your own toes, meaning that the guilty party is you! The most common reason is that a program of some kind is locking one of the files or directories in the cadett ELSA installation. For example Microsoft Excel, Notepad, or Windows File Explorer, The Command Prompt or similar could have been used to check something in the old installation before the installation was started. If so, simply exit the program in question.

 

More details about how you can throw out other users by force are found in a sub-topic named Throw out other users by force.

 

If the error message shown in the figure above does not turn up, or if it does, but you have solved the problem, you can continue with the next topic, which is listed below.

 

•The files are copied and the program is registered