SQL Anywhere Help - Connection String Error?

[Former Member]

I'm trying to connect to an SQL Anywhere database on the network.

Any help is appreciated.

Thanks

Here is the connections string:

MICROS&Provider=SAOLEDB.11;UID=custom;PWD=custom;ENG=sqlmicros1;CON=SQL_DBC_190f07d8;LINKS='TCPIP(IP=10.4.0.40;PORT=2638)'

Here is the error I'm getting.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Data.OleDb.OleDbException (0x80040E4D): Connection error: Found server but communication error occurred
at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)

[Breck_Carter]

More diagnostic information might help; see http://dcx.sybase.com/index.html#1201/en/dbadmin/network-s-3532726.html

[Former Member]

Why are you specifying a connection name ("CON=SQL_DBC_190f07d8"), especially one which looks very similar to the names generated automatically?

If a connection with that name already exists, you are creating your own conflict in naming.

Try omitting the CON= parameter and see if your problem goes away with it.

[Breck_Carter]

AFAIK there's no rule against duplicate connection names, and SQL Anywhere certainly doesn't check for uniqueness. Maybe some application or other might get confused if it's expecting uniqueness but that would not explain the symptom here... IMO anyway. FWIW I just successfully created 10 dbisql sessions all with CON=SQL_DBC_190f07d8... the title bars all say exactly the same thing "SQL_DBC_190f07d8 - Interactive SQL"

[Former Member]

Dang, putting my ignorance out there is getting educational!

I never realized that the connection names aren't unique. That is interesting -- not terribly useful, but definitely interesting in a "I wouldn't do it that way" sense.

Thank you for the correction, Breck.