Under specific circumstances the build setup does not update files in the programdata directory when newer files exist in the build setup.

Under specific circumstances the build setup does not update files in the programdata directory when newer files exist in the build setup.

Summary

The build setup normally updates files in the programdata directory when newer files are included in the build setup, and the existing files are not modified by the customer. In order to establish a change by the customer, the build setup compares the originally installed files in the programdatabackup directory, with the programdata directory by creating a md5 hash. If however any file in the programdatabackup directory is write-protected, the creation of the md5 hash fails and the files cannot be compared. This results in no files being updated in the programdata directory by the build setup.

Description

The build setup normally updates files in the programdata directory when newer files are included in the build setup, and the existing files are not modified by the customer. In order to establish a change by the customer, the build setup compares the originally installed files in the programdatabackup directory, with the programdata directory by creating a md5 hash. If however any file in the programdatabackup directory is write-protected, the creation of the md5 hash fails and the files cannot be compared. This results in no files being updated in the programdata directory by the build setup.

Solution

The build setup now removes the write protection so that a md5 hash can be generated and it can be established if files were changed, so they can be updated by the build setup if newer files are included in the build setup and the original files were not modified by the customer.

Issue Number: 30251
Fixed on Date: 27.8.2013
Versions: 7.10 0 BUILD 7770