VAS upgrade from 4.1.2.20 to 4.1.3.16 fails

When trying to upgrade the Virtual Application Server (VAS) from 4.1.2.20 to 4.1.3.16 fails with error message “The installation program was unable to read the SQL. upgrade files for the configuration database”, it is because I have seen this on other builds. The error message was; “The installation program was unable to read the SQL. upgrade […]

When trying to upgrade the Virtual Application Server (VAS) from 4.1.2.20 to 4.1.3.16 fails with error message “The installation program was unable to read the SQL. upgrade files for the configuration database”, it is because I have seen this on other builds. The error message was;

“The installation program was unable to read the SQL. upgrade files for the configuration database”

So lets dig into this a bit more…..”The installation program was unable to read the SQL. upgrade files for the configuration database” if you review your sft-server.log you should see an entry similar to ;

Couldn't open search handle for path ``C:\Program Files\Softricity\SoftGrid Server\schema\upgrade\*''.

Generally i have seen this where customer had installed the SoftGrid VAS to an alternate location. for example E:\Softricity\SoftGrid Server rather than the above. Reviewing the SoftGrid-server-setup.txt to spot the error and the installation rollback.

We copied the data from the 'E:\Softricity\SoftGrid Server\schema\upgrade' to the path 'C:\Program Files\Softricity\SoftGrid Server\schema\upgrade\*'' after we manually created the directory structure on C:. The installation then completed successfully.

There are several folders under the 'upgrade' folder and the number is based on how many upgrade the customer has done. The names there represent each version installed. (3.1, 3.2 4.0 ect...) The data under the 'upgrade' folder is the data that needs to be moved\copied.

Source:→ Microsoft