I am trying to create a batch process to upgrade from 220.127.116.113 to 18.104.22.16852 that is the recommended build from the Check for Updates option.
Based on the example on the documentation below, the process does start, the files got extracted from the exe but, after the "Computing space requirements" screen is closed, a next dialog screen displays and waits for user intervention with: Click Update to apply the Maintenance Release. Click Cancel to quit.
d:\software\sqlanywhere\setup.exe /l:1033 /s "/v: /qn REGKEY=[..snip..] INSTALLDIR=c:\sa12"
I already tried replacing /qn with /quiet and with /passive and those options didn't seem to make any difference.
Is anyone using a different set of parameters to launch unatended EBF installations?
There is a setup.exe and supporting setup files inside of SQLAnywhere1201.exe. To run the silent install you must unpack these files and run that setup.exe.
One way to get the unpacked install is to,
Alternatively, many compression utilities will also allow you to directly extract the the files from SQLAnywhere1201.exe.
Now you should be able to use the unpacked setup files with the command you list above.
I was able to figure out the reason of my issues with the batch file to silently launch the EBF setup.exe file.
Since users can install SA 12 under any local folder, I had to use the SQLANY12 environment variable to get the root path during an EBF install.
As the default target location for SA12 is the C:\Program Files\SQL Anywhere 12 folder, the spaces were causing the Windows Installer to always fail. This would not be the case had I used c:\sa12 or something similar as the target path.
After the INSTALLDIR parameter was properly escaped, the batch statement ran fine and the EBF was properly installed.