Overcoming PDF Device Permissions issues

If you run into errors when trying to complete an auto update which refers to a permissions issue when trying to replace a certain file - it is likely that this will be the PDF writing component which has to be swapped out within the application itself - and this typically lies in a protected folder within Windows, so you may need to add specific additional permissions to allow it to complete its update

Firstly open Windows Explore and go to the Program Files (x86) folder and find you TBS application (typically called TBSv5) "

In here you should see a folder called 'xcomp' - this is the one we need to allow the user to change - so right click on that folder :

Choose the Properties :

Go to the Security tab :

Click on the Edit button in the middle :

Now highlight the local user and then click in the 'Full control' / 'Allow' box :

This will allow the local user to write the new file into this folder - so click on Apply - then close the windows....

Now the user should be able to start TBS and apply the update correctly and continue as normal thereafter

If you are running a Terminal Server and you have a single instance of the TBS application being shared by all Terminal Server users, there is a different approach required here. The above will work for the first person who encounters the issue on the Terminal Server - thereafter the issue becomes that other users have a list of the files that are current in their users AppData TBS folder, however if the update list contains a component of the application (which is shared) then their list may not know that the component has already been updated and you can end up in a round robin situation where the other users are asked to change the component each time they start (and may be refused permission to change an application component if not running as an administrator)

The solution here is to edit the other users 'installedfiles' file and manually add to their list that the component has been added

The list is typically found by going to a users profile and in to their AppData folder where you will see a TBS folder (or sometimes an Omnis folder) which contains an AutoUpdater folder and inside that a tbsApps5 folder :

Edit the installedfiles file (if it does not exist, copy one from another users profile) :

Ensure that the relevant line (as shown above) is added where shown (or in an equivalent place) :