Home > Archive > microsoft.public.sqlserver.server > June 2002 > Connection Errors with ODBC and sa from an application





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Connection Errors with ODBC and sa from an application
Don

2002-06-27, 2:25 pm

I think it's related to sa being directed to hit master as
its default database in SQL. And, your application is
expecting some other db and hence the errors that follow.
In the ODBC configuration, I would associate sa to the
database you want. When you edit the ODBC configuration,
you will most likely see that sa is defaulting to master.
You'll have to put a check there and then select the right
database.

>-----Original Message-----
>I shall try again -
>
>I am trying to log onto an SQL7.0 SPK4 server using named

pipes and sa
>login through an ODBC connection as this is what this

software
>requires -
>
>The Application - "Cabletron Connection Services Manager"

( I did NOT
>write it AND it is no longer supported since the break up

of Cabletron
> ).
>
>
>When I attempt to login I get the following three

messages as pop up
>windows -
>
>
>Error Message 1 is -
>
>Number:0
>Text: S1000: [Microsoft][ODBC SQL Server Driver]Unknown

token received
>from SQL Server
>Source: ODBC
>SQL RetCode: -1
>SQLState: S1000
>
>
>Error Message 2 is -
>
>Number: 5701
>Text: 01000: [Microsoft][ODBC SQL Server Driver][SQL

Server] Changed
>Database Context To 'master'
>Source: ODBC
>SQLRetCode: -1
>SQLState: 01000
>
>
>Error Message 2 is -
>
>Number: 0
>Text: S1002:[Microsoft][ODBC SQL Server Driver] Invalid

Descriptor
>Index
>SQLRetCode: -1
>SQLState: S1002
>
>
>Does anyone know how to correct this problem ?
>
>Most appreciated and answers will be esteemed a great

favor.
>
>Jon Spartan
>
>
>.
>

Jon Spartan

2002-06-28, 5:25 am

I can't say that worked. Probelm still exists.


Jon




On Thu, 27 Jun 2002 12:21:44 -0700, "Don" <ddachner@esignal.com>
wrote:

>I think it's related to sa being directed to hit master as
>its default database in SQL. And, your application is
>expecting some other db and hence the errors that follow.
>In the ODBC configuration, I would associate sa to the
>database you want. When you edit the ODBC configuration,
>you will most likely see that sa is defaulting to master.
>You'll have to put a check there and then select the right
>database.
>
>>-----Original Message-----
>>I shall try again -
>>
>>I am trying to log onto an SQL7.0 SPK4 server using named

>pipes and sa
>>login through an ODBC connection as this is what this

>software
>>requires -
>>
>>The Application - "Cabletron Connection Services Manager"

>( I did NOT
>>write it AND it is no longer supported since the break up

>of Cabletron
>> ).
>>
>>
>>When I attempt to login I get the following three

>messages as pop up
>>windows -
>>
>>
>>Error Message 1 is -
>>
>>Number:0
>>Text: S1000: [Microsoft][ODBC SQL Server Driver]Unknown

>token received
>>from SQL Server
>>Source: ODBC
>>SQL RetCode: -1
>>SQLState: S1000
>>
>>
>>Error Message 2 is -
>>
>>Number: 5701
>>Text: 01000: [Microsoft][ODBC SQL Server Driver][SQL

>Server] Changed
>>Database Context To 'master'
>>Source: ODBC
>>SQLRetCode: -1
>>SQLState: 01000
>>
>>
>>Error Message 2 is -
>>
>>Number: 0
>>Text: S1002:[Microsoft][ODBC SQL Server Driver] Invalid

>Descriptor
>>Index
>>SQLRetCode: -1
>>SQLState: S1002
>>
>>
>>Does anyone know how to correct this problem ?
>>
>>Most appreciated and answers will be esteemed a great

>favor.
>>
>>Jon Spartan
>>
>>
>>.
>>


Sponsored Links





Free Braindumps | MCSE braindumps software forum

Copyright 2003 - 2008 examnotes.net