Mobilink > Connection string works with dbping but not with mlsrv

[former_SQLA_member1694904]

I'm trying to start a Mobilink synchronization server, and my connection string works with dbping...

dbping -d -c "uid=xxx;pwd=yyy"

...but fails to work with mlsrv

mlsrv -c "uid=xxx;pwd=yyy" -dl

The error is:

<Main> [-10002] Consolidated database server or ODBC error:  ODBC: [SAP][ODBC Driver][SQL Anywhere]Invalid user ID or password (ODBC State = 28000, Native error code = -103)

[regdomaratzki]

As someone who only talks to customers when they have problems or questions, I would strongly suggest providing the ServerName and DatabaseName connection parameters in your connection string for the MobiLink Server. Connecting to the default database running on the default engine on the local machine is a recipe for accidentally connecting to the wrong database at some point in the future.

[former_SQLA_member1694904]

Thank you for this tip. I'll try with a full ODBC connection string and report back.

[former_SQLA_member1694904]

Reg, I might be missing something very basic about DSN here, but if I'm using a well-configured DSN (as mlsrv expects), I shouldn't have to specify anything else in the connection string, right?

[former_SQLA_member1694904]

I configured a complete DSN and used "dsn=xxx" and it worked as expected. Thank you, Reg.

[regdomaratzki · Accepted solution]

The DSN parameter is required in the connection string for the MobiLink Server.

dbping only connects to SQL Anywhere databases, so when it connects to a database it will by default use dblib (i.e. SQL Anywhere native communication stream), but mlsrv17 is an ODBC application that can connect to a number of different RDBMS, so uses ODBC only, and never used dblib.

[former_SQLA_member1694904 · Accepted solution]

Thank you for the detailed explanation. is this documented anywhere clearly? The doc for mlsrv simply says that -c needs to be passed a connection string, and no further details about ODBC or reqd components within that connection string.

[former_SQLA_member1694904 · Accepted solution]

Also, I tried putting a DSN, if I remember correctly, but got the same behaviour. I'll recehck once I'm on my computer. Is there any specific the DSN needs to be setup with windows?

[Breck_Carter · Accepted solution]

Presumably one could use dbping -m to force ODBC usage, when testing a connection path similar to MobiLink.

[former_SQLA_member1694904 · Accepted solution]

Breck, the tip about -m is very useful. The connection string now fails with dbping as well -- so at least I'm seeing consistent behaviour now.

[former_SQLA_member1694904 · Accepted solution]

This the correct answer for the difference in behaviour of dbping and mlsrv. I'm opening a separate question related to DSN.

[chris_keating · Accepted solution]

The documentation does indicate that the value supplied to the mlsrv17 -c option should be "ODBC database connection parameters for your consolidated database." See http://dcx.sap.com/index.html#sqla170/en/html/81c951cb6ce21014887280d342d9494d.html*loio81c951cb6ce2...