Solving Elliott 8.6 Installation Conflict with Root Directory BTR Files
Version: 8.6
Elliott 8.6 supports ReportDesk and PowerSearch features. Both features require installing BTR files at the Elliott root directory level. Some of these BTR files may change from time to time, which will be overridden during Elliott updates. If some of the Elliott 8.6 users do not exist at nighttime, they can still keep open some of Elliott root directory BTR files that require updating. This will prevent a successful installation of Elliott 8.6.
Typically, we can prevent this kind of problem by asking users to exit out of Elliott at nighttime in order to install and avoid open file conflicts. With larger organizations, sometimes this can be difficult and certain users simply do not follow instructions.
We could also stop/start the PSQL engine to clear all the open file connections. This is somewhat drastic and may create issues if you have a website that connects to Elliott's database on a 24x7 basis.
The following is an example of how we solve this issue without stopping/starting the PSQL server. We use the BUTIL -STARTBU and -ENDBU option to allow the installation to proceed.
Installation Conflict Message
During Elliott 8.6 installation, you may run into the following sample message:
Error 1306: Another Application has exclusive access to the file D:\Sys\macola\SYRDTASK.BTR. Please shut down all other applications, then click Retry.
See sample screen below:
What it means is the installation utility needs to update the SYRDTASK.BTR file in the Elliott root directory (i.e., D:\Sys\macola\) and another user is currently opening this file. The typical thing for you to do is to click "Cancel" and reverse any update so far.
Find Out Who Locked the File
Next, you need to find out who opened this file to see if you can ask that user to exit. You can do so by going to the PSQL Control Center, go to Tools on the top menu, and choose "Monitor." In the PSQL Monitor utility, go to the Active Files tab and locate this file. See sample screen below:
In this example, this file is opened by user jcarroll. If this is during the day, you can go to this user and ask him/her to exit out of Elliott to resume Elliott installation.
However, since we are installing this update late at night and we can't access user jcarroll's desktop to logout this user, we need a different method.
Using BUTIL -STARTBU
The BUTIL -STARTBU option means "Start Backup." This option can put a file into continuous operation mode. In this case, the PSQL engine will close SYRDTASK.BTR and create an extra file SYRDTASK.^01. All further changes to the SYRDTASK file will be written to SYRDTASK.^01 file. When you use BUTIL -STARTBU, you need to use the local path on the server. For example, this user runs Elliott from the M:\Macola folder. The corresponding location path on the server is D:\Sys\Macola, which is the one you need to use. Bring up a command prompt window, and make sure you have the appropriate admin rights. Type the following:
BUTIL -STARTBU D:\SYS\MACOLA\SYRDTASK.BTR
Note SYRDTASK.^01 is created now.
Continue Elliott Installation
Now, perform the Elliott installation again. If the Elliott installation is successful this time, you may receive a message at the very end asking if you wish to reboot the computer. Ignore the message by choosing "No."
Using BUTIL -ENDBU
It is very important that after using the -STARTBU option, you need to follow up with the -ENDBU. The BUTIL -ENDBU option means "End Backup." This option will write the net change in the SYRDTASK.^01 delta file to SYRDTASK.BTR, then delete the SYRDTASK.^01 file after. After this, the SYRDTASK.BTR is back to the normal mode. When you use BUTIL -ENDBU, you need to use the local path on the server. For example, this user runs Elliott from the M:\Macola folder. The corresponding location path on the server is D:\Sys\Macola, which is the one you need to use. Bring up a command prompt window to make sure you have the appropriate admin rights. Type the following:
BUTIL -ENDBU D:\SYS\MACOLA\SYRDTASK.BTR
See sample screen below:
See this related KB article: https://support.elliott.com/knowledgebase/articles/2015153-how-to-resolve-files-open-conflict-during-elliott
EMK