|
I'm trying to start a Mobilink synchronization server, and my connection string works with dbping -d -c "uid=xxx;pwd=yyy" ...but fails to work with 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) |
|
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. Thank you for the detailed explanation. is this documented anywhere clearly? The doc for mlsrv simply says that
(04 Sep '20, 09:05)
saurabhnanda
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?
(04 Sep '20, 09:06)
saurabhnanda
Presumably one could use dbping -m to force ODBC usage, when testing a connection path similar to MobiLink.
(04 Sep '20, 09:13)
Breck Carter
Breck, the tip about
(04 Sep '20, 09:19)
saurabhnanda
This the correct answer for the difference in behaviour of
(04 Sep '20, 09:23)
saurabhnanda
1
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*loio81c951cb6ce21014887280d342d9494d.
(04 Sep '20, 10:51)
Chris Keating
More comments hidden
|
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.
Thank you for this tip. I'll try with a full ODBC connection string and report back.
Reg, I might be missing something very basic about DSN here, but if I'm using a well-configured DSN (as
mlsrvexpects), I shouldn't have to specify anything else in the connection string, right?I configured a complete DSN and used
"dsn=xxx"and it worked as expected. Thank you, Reg.