What to know about SQL Server 2016 when planning to use it for Uniprint 9.0 R2
The Pharos Suite Operating System Support and Compatibility Chart shows that Uniprint 9.0 R2 is supported but notes possible conditions where a workaround may be required.
1. Uniprint 9.0 R2 will function where it has been installed already into an earlier version of SQL server, and then upgraded to SQL 2016.
2. It will also work when the Uniprint database has been moved from one SQL server to a new SQL 2016 server.
3. Uniprint 9.0 R2 may have trouble installing or upgrading when SQL 2016* server is used. If this happens, the following steps are a workaround:
a. Copy the file "osql_2000_80_760_0.exe" from the installation source from where Setup was started.
b. This file can be found in the "[Installation_Source]\Common\Wind32\osql" folder.
c. Copy this file into the root of the C: drive and rename it to be called "osql.exe"
d. Then re-run the installation or upgrade
e. Once the installation or upgrade has completed, this file can be removed from the root of C:
Further explanation about this workaround:
The installer searches for the file "osql.exe" during installation or upgrade. Testing has proven that, in some cases, this process finds the wrong file and fails. This workaround places the file in a location where it will be discovered quickly and therefore provides the proper file for the installer. Future versions of Uniprint will no longer require this workaround.
*Note: This problem has been reported on rare occasion with previous versions of SQL and the workaround is the same.
SQL 2017 support has been verified. See Pharos Suite Operating System Support and Compatibility Chart for details. The workaround, mentioned in this post may or may not be necessary for SQL 2016 or 2017. It is recommended to try installation without this workaround first. If that fails, the workaround my be necessary.