Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SQLServer 7.0 error 20016 and 20041 when on SQLConnect() using Ctd 1.1.2

260 views
Skip to first unread message

Jeffrey Mergler

unread,
Feb 15, 1999, 3:00:00 AM2/15/99
to
Getting the error:

20016 (and now lately 20041)

when using any ctd 1.1.2 built executables (via ODBC router) against a SQL
Server 7.0 database.

Sqltalk.exe works fine (same directory as the .exe) but the exes will not
connect on the client. Strangely enough, the executables WILL work if run
on the server running the SQL Server database (the NT server itself) but
again fails at the client PC's.

Anyone had similar experiences?

--

Jeffrey Mergler
Quality Systems International
201-848-8113
jeffrey...@qsius.com

Dmitry V. Kagansky

unread,
Feb 24, 1999, 3:00:00 AM2/24/99
to
We've gotten similar errors on 6.5 when we updated our ODBC drivers. A lot
of installation apps automatically upgrade (and potentially downgrade) your
ODBC manager and/or drivers. For example, SQLBase 6.1.x arbitrarily
overwrites your newest ODBC stuff with the version that it has.

The reason it runs on the server is there has been nothing new added since
the install. Try reinstalling the SQLServer 7 client pieces again and see
where that gets you.

I should add that using SQL Server ODBC driver 3.51x against WinLIMS was
impossible for us, and I downgraded our driver to 2.65. Yet I could connect
from the client, using the 3.51x driver via SQLTalk. I think there's
something 'squirrely' about the newest versions of SQLServer and ODBC
drivers from Microsoft.

For what its worth,
Dmitry Kagansky
Cabot Corporation

Jeffrey Mergler wrote in message <7aabq7$e8...@horizon.centurasoft.com>...

0 new messages