ODBC Connection Problem

Hello,
I have an install of SQL that my users cannot connect to with an ODBC
connection. I have created Windows User logins on the SQL server through
Enterprise Manager, and have assigned them access to one specific database.
The specific user accounts have public, db_datareader and db_datawriter
permissions to the database. When the users attemtpt to create their ODBC
connections they receive an access denied message. What other permissions do
I need to give these users? Do they need any other permissions to the actual
server the SQL instance resides on?
Thanks,
JBaileyJBailey,
Please let me know the following:
- These accounts that you created to access that datbase, can they connect
and query the database from query analyser?
- Also, could you please created a UDL to test for connectivity (this gives
us a good idea if the odbc connection is ok). Also it could be that we
arent passing the correct 'connection string'?
Create a text file and name it <anything>.UDL. Rt-click the UDL file and
select Properties. The Connection tab contains all the fields exposed to
the application, and you choose the appropriate items to be filled in to
successfully "Test Connection" before you are able to use it. Once the Test
button works, click on OK and open up the UDL file in Notepad. Its just a
text file, and contains a provider string that you should be able to paste
into your application or whichever application is calling the sql server.
Cheers!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql

ODBC connection frequently drops in routed network

Hello,
we are having serious problems with an application that uses an ODBC
connection (System DSN) to a SQL Server in another subnet. The network is
fine, all network tests reveal nothing of consequence. However, the problem
does not appear when SQL server and client are in the same subnet.
The ODBC connection from the client gets dropped at seemingly random
intervals and in the logs one can see the following:
{NIL, 10054, [01000][10054][Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (send()).}
{NIL, 59, [01000][59][Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionWrite (WrapperWrite()).}
{NIL, -1, [08S01][0][Microsoft][ODBC SQL Server
Driver]Communication link failure}
We honestly don't know what else to look for. Maybe anyone has an idea?
Thanks in advance,
Thomas Liss
Well, after configuring "Flow Control" on the network cards of the SQL
Server, the problems were gone.
"Thomas Liss" <liss@.uipugmbh.com> wrote in message
news:upFsIo9TFHA.2664@.TK2MSFTNGP15.phx.gbl...
> Hello,
> we are having serious problems with an application that uses an ODBC
> connection (System DSN) to a SQL Server in another subnet. The network is
> fine, all network tests reveal nothing of consequence. However, the
> problem does not appear when SQL server and client are in the same subnet.
> The ODBC connection from the client gets dropped at seemingly random
> intervals and in the logs one can see the following:
> {NIL, 10054, [01000][10054][Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionWrite (send()).}
> {NIL, 59, [01000][59][Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionWrite (WrapperWrite()).}
> {NIL, -1, [08S01][0][Microsoft][ODBC SQL Server
> Driver]Communication link failure}
> We honestly don't know what else to look for. Maybe anyone has an idea?
>
> Thanks in advance,
>
> Thomas Liss
>
|||Could you please explain what was the old setting and what is the new one?
Regards,
Marko Erzen
"Thomas Liss" <liss@.uipugmbh.com> wrote in message
news:e2wez$JUFHA.2172@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Well, after configuring "Flow Control" on the network cards of the SQL
> Server, the problems were gone.
>
> "Thomas Liss" <liss@.uipugmbh.com> wrote in message
> news:upFsIo9TFHA.2664@.TK2MSFTNGP15.phx.gbl...
is[vbcol=seagreen]
subnet.
>
|||Thomas,
I just read your post and we are experiencing the same kind of error
here. The communication link failure is only occurring for clients
connecting from outside of the server's home subnet and the failure is
intermittent. Did you ever resolve your problems?
*** Sent via Developersdex http://www.codecomments.com ***

ODBC connection frequently drops in routed network

Hello,
we are having serious problems with an application that uses an ODBC
connection (System DSN) to a SQL Server in another subnet. The network is
fine, all network tests reveal nothing of consequence. However, the problem
does not appear when SQL server and client are in the same subnet.
The ODBC connection from the client gets dropped at seemingly random
intervals and in the logs one can see the following:
{NIL, 10054, [01000][10054][Microsoft][ODBC SQL Se
rver
Driver][DBNETLIB]ConnectionWrite (send()).}
{NIL, 59, [01000][59][Microsoft][ODBC SQL Serve
r
Driver][DBNETLIB]ConnectionWrite (WrapperWrite()).}
{NIL, -1, [08S01][0][Microsoft][ODBC SQL Server
Driver]Communication link failure}
We honestly don't know what else to look for. Maybe anyone has an idea?
Thanks in advance,
Thomas LissWell, after configuring "Flow Control" on the network cards of the SQL
Server, the problems were gone.
"Thomas Liss" <liss@.uipugmbh.com> wrote in message
news:upFsIo9TFHA.2664@.TK2MSFTNGP15.phx.gbl...
> Hello,
> we are having serious problems with an application that uses an ODBC
> connection (System DSN) to a SQL Server in another subnet. The network is
> fine, all network tests reveal nothing of consequence. However, the
> problem does not appear when SQL server and client are in the same subnet.
> The ODBC connection from the client gets dropped at seemingly random
> intervals and in the logs one can see the following:
> {NIL, 10054, [01000][10054][Microsoft][ODBC SQL
Server
> Driver][DBNETLIB]ConnectionWrite (send()).}
> {NIL, 59, [01000][59][Microsoft][ODBC SQL Ser
ver
> Driver][DBNETLIB]ConnectionWrite (WrapperWrite()).}
> {NIL, -1, [08S01][0][Microsoft][ODBC SQL Serv
er
> Driver]Communication link failure}
> We honestly don't know what else to look for. Maybe anyone has an idea?
>
> Thanks in advance,
>
> Thomas Liss
>|||Could you please explain what was the old setting and what is the new one?
Regards,
Marko Erzen
"Thomas Liss" <liss@.uipugmbh.com> wrote in message
news:e2wez$JUFHA.2172@.TK2MSFTNGP15.phx.gbl...
> Well, after configuring "Flow Control" on the network cards of the SQL
> Server, the problems were gone.
>
> "Thomas Liss" <liss@.uipugmbh.com> wrote in message
> news:upFsIo9TFHA.2664@.TK2MSFTNGP15.phx.gbl...
is[vbcol=seagreen]
subnet.[vbcol=seagreen]
>|||Thomas,
I just read your post and we are experiencing the same kind of error
here. The communication link failure is only occurring for clients
connecting from outside of the server's home subnet and the failure is
intermittent. Did you ever resolve your problems?
*** Sent via Developersdex http://www.codecomments.com ***sql

ODBC CONNECTION

I have an app which using Access front end and SQL server backend and ODBC
connection.
My app may access the SQL server backend database without ODBC
configuration.
Is it possible? If yes, where I can investigate the issue.
Any information is great appreciated,
Souris,
By "without ODBC" configuration, do you mean without a DSN?
Yes that's possible. You can find a lot of articles if you
search on dsn-less. This is what's returned from the
Knowledge Base:
http://support.microsoft.com/search/...px?qu=dsn-less
You can find examples of connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=80
-Sue
On Thu, 12 May 2005 00:16:45 -0400, "souris"
<soukkris@.viddotron.com> wrote:

>I have an app which using Access front end and SQL server backend and ODBC
>connection.
>My app may access the SQL server backend database without ODBC
>configuration.
>Is it possible? If yes, where I can investigate the issue.
>Any information is great appreciated,
>Souris,
>

ODBC Connection

I apologize if this isn't the right place to ask this,
but I'm looking for a way to copy an SQL/Server ODBC
connection from one PC to another (actually, many
others). I tried copying the ODBC.INI file but that
didn't seem to work. That seems to be the only file that
is updated when I create a new connection, so I was
hoping that was all I needed. Is this possible ? Or do I
have to go through the ODBC setup on each PC ?
The user and system DSN definitions are stored in the following two registry
keys:
HKLM\SOFTWARE\ODBC\ODBC.INI\
HKLM\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\
Mike O.
"Dave Ruhl" <anonymous@.discussions.microsoft.com> wrote in message
news:da9a01c41131$4a3d7d70$a001280a@.phx.gbl...
> I apologize if this isn't the right place to ask this,
> but I'm looking for a way to copy an SQL/Server ODBC
> connection from one PC to another (actually, many
> others). I tried copying the ODBC.INI file but that
> didn't seem to work. That seems to be the only file that
> is updated when I create a new connection, so I was
> hoping that was all I needed. Is this possible ? Or do I
> have to go through the ODBC setup on each PC ?

ODBC CONNECTION

I have an app which using Access front end and SQL server backend and ODBC
connection.
My app may access the SQL server backend database without ODBC
configuration.
Is it possible? If yes, where I can investigate the issue.
Any information is great appreciated,
Souris,By "without ODBC" configuration, do you mean without a DSN?
Yes that's possible. You can find a lot of articles if you
search on dsn-less. This is what's returned from the
Knowledge Base:
http://support.microsoft.com/search...spx?qu=dsn-less
You can find examples of connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=80
-Sue
On Thu, 12 May 2005 00:16:45 -0400, "souris"
<soukkris@.viddotron.com> wrote:

>I have an app which using Access front end and SQL server backend and ODBC
>connection.
>My app may access the SQL server backend database without ODBC
>configuration.
>Is it possible? If yes, where I can investigate the issue.
>Any information is great appreciated,
>Souris,
>