Can't Connect to SAP SQL Anywhere 17 server from Client

[Former Member]

We just purchased SAP SQL Anywhere 17 (4 core) - licensed to run our designed application on Power Builder 9.0. The database was migrated successfully from SQL Anywhere 5.5 to 17.0 and application currently running smoothly on the window server 12 R2 . Now the challenge is to run and connect the clients system to the database server. We installed the SAP SQL Anywhere 17 Client on a workstation but kept getting errors that the database not found. All network connections are in order and we can easily ping the server from the startup. How can we connect the client to the server successfully? Is there any executable file for the client? Thank you as we await your swift response in this regard.

[chris_keating]

To help, we need a little more details.

1) Are you running dbsrv17 on the server side. This is needed if you want to make connections from different machines.

2) What is the engine command line switches? You will need the <server_name> and database name(s) as well as the port if provided.

dbsrv17 -n server_name database1.db -n dbname_1 database2.db - n dbname_2 -x tcpip(port=12345)

3) I will assume that the connection is using ODBC. It will need to be a 32 bit DSN since PB9 is 32 bit. Add a new SA 17 based ODBC DSN.

• On the login tab, provide the user id and pwd.
• Set the Action dropdown to "Connect to a running server on another computer"
• Set the Server name to be the database engine name. In the example, it is the value supplied to the first -n or server_name. The database name is either dbname_1 or dbname 2 depending on which database you want to connect.
• Set Host, which is the machine name or IP where the engine is running and Port if supplied on the engine start line.

If you continue to have problems, please start the engine with -z -o <filespec> and set the LogFile to a file name on the Advanced tab of the DSN. Please provide those files for review.

[Former Member]

Thanks Chris,

We have successfully connected the client to the SAP SQL Anywhere 17 Server this morning, and our application successfully launched. We tried posting a transaction on the application from the client system but got an error that the application stopped working but the server didnot crash at all.

I know this might not be an SAP issues just need technical advise from an expert like you.The app is built with Powerbuilder 9.0 and placed on SQL Anywhere 17

[chris_keating]

What application stopped working? PowerBuilder? What was the type of transaction that was executed? Have you run PB in debug to see if it shows anything of interest. Or perhaps you can run with /pbtrace that may show more.

Please note that PB 9 is really old software and has not been actively supported for many years. Additionally, it was never tested with SQL Anywhere 17 so it is possible that there will be issues running it with SQL Anywhere 17.

[Former Member]

Thank you, will try that out and get back to you

[former_member188493]

FYI I just installed PowerBuilder 8 (couldn't find PB9) and successfully created a new DataWindow based on a table in a SQL Anywhere 17 database, and previewed the data in the DataWindow painter...

...so if you can describe your symptom, I might be able to help.

[former_member188493]

Did you create a brand new ODBC DSN for the SQL Anywhere 17 database? The ODBC client software for SQL Anywhere 5.5 involved a nasty component called dbclient.exe which absolutely is not the right thing to use with SQL Anywhere 17.