Include license file with SQL Anywhere 17 deployment

[former_member1049648]

We have been using a version 17.0.0 msm file for deploying our application with a SQL Anywhere database using an ODBC connection. I would like to include the latest SQL Anywhere 17 client files so I used the deployment wizard. The deployment wizard for the latest version (6800) does not appear to include the dbeng17.lic file and when I use the SQL Anywhere client I get the message "Connection failed: Unable to start database server: missing license file."

Does/can the deployment wizard include the dbeng17.lic file and if not how do I include it and where do I get the file? I have tried creating the deployment file as an msi and I have tried creating it from my development machine with a developer license and I have tried creating it from my production machine with a production license.

The 17.0.0 msm file includes the dbeng17.lic file. It is possible I put it there but it is also possible that the SQL Anywhere deployment wizard for 17.0.0 put it there. That license file appears to work for the 17.0.0 client files but not the latest version of SQL Anywhere. I have tried copying the dbeng17.lic file from my development machine and also copying it from my production machine, replacing the dbeng17.lic file from the original 17.0.0 msm file. In all these cases I still get the same Connection Failed message.

[chris_keating]

The short answer is that a client-only install will not have license files because it would not include any of the server components that the license files are associated.

Can you confirm that the environment where this problem occurs has all Build 6800 binaries? Add File version property to the File Explorer Details view as in

Can you confirm what features that you have selected in the deployment wizard? For the dbeng17.lic file to be included, you will need to ensure that you have selected Database | SQL Anywhere Server | Personal Server which will install the dbeng17.exe, dbeng17.lic, and other files needed by the personal server assuming that the source machine on which the Deployment Wizard has those files. In addition to the msi or msm that is built by the deployment wizard, there is also a *.log file that records the files that are packaged. It would be helpful to compare the log to the Features that were selected.

What error(s), if any are reported when running dbeng17 -n test or dblic dbeng17.lic?

Please also confirm that sapcrypto.dll is installed in this environment. This replaces OpenSSL and is needed to read the license file.

[former_member1049648]

With Chris Keating's helpful feedback I believe I have everything working.

Part of the problem is that my initial installation was a 32-bit installation. The files that needed to be overwritten were in the 32-bit Program Files folder (Program Files (x86)). When I was using a 64-bit installation the files went to the 64-bit Program Files folder which left 2 conflicting sets of files and some weird behavior. The other problem was that when I created a 32-bit installation from a 64-bit installation of SQL Anywhere on my development machine the option to include the personal server was not available, so no ability to include the .lic license file.

The solution was to create a 32-bit VM and install SQL Anywhere so I had a 32-bit SQL Anywhere installation. When I created a deployment .MSI file from that VM then the 32-bit installation had the option to include the server components which meant the .MSI could also include the .lic file. Since this was a 32-bit installation it overwrote the existing 32-bit client files on the client machine when I installed it, so no duplicate/conflicting sets of client files. After this installation on the client I was able to connect to my database using version 17.0.11.6800 of the SQL Anywhere client software. Success!