Deployment wizard and licenses

[Former Member]

I am working on an upgrade to SA 17 and I used the deployment wizard to build an msi file to deploy to my customer's 4 servers. What I don't understand is how to apply the activation keys without having to go to each server and use the dblic utility to apply the licenses. Is there an easier way?

Thanks.

[Former Member]

The documentation you refer to above describes silent installs of the full product. The documentation on silent installs won't help you with upgrading a deployment wizard MSI install.

The install built by the deployment wizard does not need a registration key to run. If your installer includes the server (dbsrv17.exe and/or dbeng17.exe) it will be governed by the license you created when you installed SQL Anywhere. The deployment wizard will include the file dbsrv17.lic when dbsrv17.exe is include (and/or dbeng17.lic when dbeng17.exe is included) in the deployment installer. So the deployment installer is essentially using the registration key you supplied when you originally installed SQL Anywhere.

If for some reason you need to change the license on the servers to which you've already deployed, then you will need to run the dblic.exe utility on each machine. (No doubt there are ways to automate that process.)

If you need to upgrade the version of SQL Anywhere on your servers using the deployment wizard, you will need to create an Upgrade MSI. The catch with creating an Upgrade MSI is that you need to have available your original deployment wizard generated MSI. This is so that the Upgrade MSI can generated components with the original MSI's component GUIDs.

Here is how you would go about doing the above:

1. To your existing installation of SQL Anywhere apply the SP you want to upgrade to, (say for example build 1384).
2. Run the deployment wizard and select "Upgrade Existing Install" instead of "Create New Install" MSI.
3. When you select Upgrade you will be prompted to provide the original MSI. (Note that your feature selection will be the same as that in the original MSI - you cannot change the feature selection.)
4. Be sure to name your Upgrade MSI differently from the original MSI, (e.g., sqlany17_upgrade_1384).
5. Complete the deployment wizard.
6. Run the Upgrade MSI on your servers using the following command:

msiexec.exe /i sqlany17_upgrade_1384.msi REINSTALL=ALL REINSTALLMODE=vomus

The above command will upgrade the image on your servers to build 1384 and will continue to use the existing dbsrv17.lic file as the license. You will not need to provide a registration key.

[Former Member]

How does that work when I will have 4 license keys? Can I just use one key for all four DBs and then just keep the keys to prove they were paid for? Second, I paid for the licenses a week ago and I still haven't gotten them. With what you have described, I will have to install at least one license before creating the MSI. I was hoping to get the install copied to all the servers (slow connections) before the upgrade on Saturday.

[Former Member]

Have you received your licenses? If you have great. If not, can you let me know how you purchased them (through the SAP store or a third party)?

[Former Member]

Found it on document xchange. http://dcx.sap.com/index.html#sqla170/en/html/8168a3fa6ce21014a346e584d7ae12a7.html

[VolkerBarth]

Could you tell how exactly that information helps to supply the activation keys to a MSI file?

[Former Member]

I was thinking that the msi file would work the same as setup.exe. Maybe I was mistaken?

d:\\pkg\\sqlanywhere\\setup.exe /l:1033 /s "/v: /qn REGKEY=NEEDA-REAL0-KEY12-34567-89012 INSTALLDIR=c:\\sa17 DIR_SAMPLES=c:\\sa17\\Samples"

[Former Member]

I would test it if I ever get my new keys :(.

[Former Member]

I just tried a temporary key and that didn't work. So my question was not answered.