Hi Victor,
You are correct - this appears to be a bug in the SQL Anywhere 16 Deployment Wizard. As I have outlined on your question on the sqlanywhere-forum, there is a workaround available:
In the folder \Deployment
in your original SQL Anywhere 16 installation, there is a file 'master.xml'. You will need to edit this file in a text editor:
Find the line:
<featureid="CMN"hidden="true">
and add the following text below it:
<featureid="CMN"hidden="true">
<environmentname ="*=-SQLANY16"value ="[SQLANYDIR]."/>
<registryroot ="HKEY_LOCAL_MACHINE"path ="SOFTWARE\Sybase\SQL Anywhere\16.0">
<keyname ="Location"value ="[SQLANYDIR]"/>
<keyname ="Shared Location"value ="[SQLANYDIR]"/>
<keyname ="Language"value ="[LANGUAGE]"/>
</registry>
Just below that information, there are the lines:
<featureid="CMN32"hidden="true">
<includeid="common_registry_entries_32"/>
Add the following text:
<featureid="CMN32"hidden="true">
<includeid="common_registry_entries_32"/>
<environment name = "*=-PATH" value = "[~];[SQLANYDIR]bin32" />
Below that, there are the lines:
<feature id="CMN64" deploy64="true" hidden="true">
<include id="common_registry_entries_64" />
Add the following text:
<feature id="CMN64" deploy64="true" hidden="true">
<include id="common_registry_entries_64" />
<environmentname="*=-PATH"value="[~];[SQLANYDIR]bin64"/>
I have opened this issue for further investigation as CR #755094. Thank you for the bug report.
Regards,
Jeff Albion
SAP Active Global Support