Hello EveryBody,
If SQL SERVER is configured as a Maximun concurrent user connections = 1 (I
know 0 = unlimited) in Connection tab of server property ? Who will able to
login to server ?
Because i have a similar case and not able to login with any other sql
server Login.
Is SQL SERVER admin (sa) will able to login ?
Pls let me know
I assume your single login is being used by Agent when it starts up so
nobody will be able to log in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:88C5F9E7-30C7-4B59-A9F5-06BDBF159CA7@.microsoft.com...
> Hello EveryBody,
> If SQL SERVER is configured as a Maximun concurrent user connections = 1
> (I
> know 0 = unlimited) in Connection tab of server property ? Who will able
> to
> login to server ?
> Because i have a similar case and not able to login with any other sql
> server Login.
> Is SQL SERVER admin (sa) will able to login ?
> Pls let me know
Showing posts with label everybody. Show all posts
Showing posts with label everybody. Show all posts
Monday, March 19, 2012
Connection Issue
Hello EveryBody,
If SQL SERVER is configured as a Maximun concurrent user connections = 1 (I
know 0 = unlimited) in Connection tab of server property ? Who will able to
login to server ?
Because i have a similar case and not able to login with any other sql
server Login.
Is SQL SERVER admin (sa) will able to login ?
Pls let me knowI assume your single login is being used by Agent when it starts up so
nobody will be able to log in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:88C5F9E7-30C7-4B59-A9F5-06BDBF159CA7@.microsoft.com...
> Hello EveryBody,
> If SQL SERVER is configured as a Maximun concurrent user connections = 1
> (I
> know 0 = unlimited) in Connection tab of server property ? Who will able
> to
> login to server ?
> Because i have a similar case and not able to login with any other sql
> server Login.
> Is SQL SERVER admin (sa) will able to login ?
> Pls let me know
If SQL SERVER is configured as a Maximun concurrent user connections = 1 (I
know 0 = unlimited) in Connection tab of server property ? Who will able to
login to server ?
Because i have a similar case and not able to login with any other sql
server Login.
Is SQL SERVER admin (sa) will able to login ?
Pls let me knowI assume your single login is being used by Agent when it starts up so
nobody will be able to log in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:88C5F9E7-30C7-4B59-A9F5-06BDBF159CA7@.microsoft.com...
> Hello EveryBody,
> If SQL SERVER is configured as a Maximun concurrent user connections = 1
> (I
> know 0 = unlimited) in Connection tab of server property ? Who will able
> to
> login to server ?
> Because i have a similar case and not able to login with any other sql
> server Login.
> Is SQL SERVER admin (sa) will able to login ?
> Pls let me know
Wednesday, March 7, 2012
connection failed
I have a sql server database and access as front end. Everybody except one user works on this database is fine. When this user open the database. It showed error message"
connection failed: SQLState:'s1000'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context.
Actually he worked fine before. Just today, it didn't work.
Can you help me how to solve this problem?
Many thanks.99% of the time, this is a networking problem, and most of those times it is simply Kerberos ticketing getting itself out-of-whack. I usually just power down the workstation (as in power off, not a Windows restart). Once it comes back up, the problem is usually gone.
-PatP|||Thanks. Yes, i think it is network problem. Can you explain to me what you mean power down the workstation. It is not mean restart the server? I did restart the user's computer, but it still didn't work. Thank you.|||I used the term "power down" instead of restart to avoid confusion. Different things happen when a machine (specifically its network interface) powers down (it is turned off, or better yet unplugged) than what happens when Windows is simply restarted. When the machine powers back up and the hardware is re-initialized, that seems to clear most of these problems for me.
-PatP|||Thank you very much for your explaination.
connection failed: SQLState:'s1000'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context.
Actually he worked fine before. Just today, it didn't work.
Can you help me how to solve this problem?
Many thanks.99% of the time, this is a networking problem, and most of those times it is simply Kerberos ticketing getting itself out-of-whack. I usually just power down the workstation (as in power off, not a Windows restart). Once it comes back up, the problem is usually gone.
-PatP|||Thanks. Yes, i think it is network problem. Can you explain to me what you mean power down the workstation. It is not mean restart the server? I did restart the user's computer, but it still didn't work. Thank you.|||I used the term "power down" instead of restart to avoid confusion. Different things happen when a machine (specifically its network interface) powers down (it is turned off, or better yet unplugged) than what happens when Windows is simply restarted. When the machine powers back up and the hardware is re-initialized, that seems to clear most of these problems for me.
-PatP|||Thank you very much for your explaination.
Saturday, February 25, 2012
Connection Error 18452 - Login failed for user '(null)'
Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus Wolff
This is always an authentication problem somewhere. The null indicates that
user cannot be validated and a null is being passsed to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Rand, what about a solution or al least pointing to one?
"Rand Boyd [MSFT]" wrote:
> This is always an authentication problem somewhere. The null indicates that
> user cannot be validated and a null is being passsed to SQL Server.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||It really depends on where the process is failing. You would
want to check the event logs on the PC having the problems
connecting. Check for any network related issues or
problems. Make sure that PC is contacting the domain
controllers without any problems and that they are
successfully logging into the network.
-Sue
On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
<JC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Rand, what about a solution or al least pointing to one?
>"Rand Boyd [MSFT]" wrote:
|||Login failed for user <null> usually means that on the SQL box, the user
account could not be found in the local security database or in the domain
controller's user database.
For example, on machine1 I log in as machine1\user1. Then I try to log into
SQL on machine2. On machine2 SQL takes the SID of the user and calls
LookupAccountSID API. This attempts to convert the SID to the user name.
LookupAccountSID first looks in local security database on machine2, and
does not find machine1\User1, then looks on domain controller, and still
does not find the SID.
So in general this points to problems with the user account. Perhaps the
user has the same account name defined on their local machine and when they
log in they don't realize that they are logging in as the local User1 versus
the domain User1. Go to the problematic machine and check the user
accounts. If this does not work, perhaps have the domain admin drop the
user account and recreate it.
Matt
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:jd4sr0ds5vna1pc5ph4ri66j5hmri6d51p@.4ax.com...
> It really depends on where the process is failing. You would
> want to check the event logs on the PC having the problems
> connecting. Check for any network related issues or
> problems. Make sure that PC is contacting the domain
> controllers without any problems and that they are
> successfully logging into the network.
> -Sue
> On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
> <JC@.discussions.microsoft.com> wrote:
>
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus Wolff
This is always an authentication problem somewhere. The null indicates that
user cannot be validated and a null is being passsed to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Rand, what about a solution or al least pointing to one?
"Rand Boyd [MSFT]" wrote:
> This is always an authentication problem somewhere. The null indicates that
> user cannot be validated and a null is being passsed to SQL Server.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||It really depends on where the process is failing. You would
want to check the event logs on the PC having the problems
connecting. Check for any network related issues or
problems. Make sure that PC is contacting the domain
controllers without any problems and that they are
successfully logging into the network.
-Sue
On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
<JC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Rand, what about a solution or al least pointing to one?
>"Rand Boyd [MSFT]" wrote:
|||Login failed for user <null> usually means that on the SQL box, the user
account could not be found in the local security database or in the domain
controller's user database.
For example, on machine1 I log in as machine1\user1. Then I try to log into
SQL on machine2. On machine2 SQL takes the SID of the user and calls
LookupAccountSID API. This attempts to convert the SID to the user name.
LookupAccountSID first looks in local security database on machine2, and
does not find machine1\User1, then looks on domain controller, and still
does not find the SID.
So in general this points to problems with the user account. Perhaps the
user has the same account name defined on their local machine and when they
log in they don't realize that they are logging in as the local User1 versus
the domain User1. Go to the problematic machine and check the user
accounts. If this does not work, perhaps have the domain admin drop the
user account and recreate it.
Matt
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:jd4sr0ds5vna1pc5ph4ri66j5hmri6d51p@.4ax.com...
> It really depends on where the process is failing. You would
> want to check the event logs on the PC having the problems
> connecting. Check for any network related issues or
> problems. Make sure that PC is contacting the domain
> controllers without any problems and that they are
> successfully logging into the network.
> -Sue
> On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
> <JC@.discussions.microsoft.com> wrote:
>
Connection Error 18452 - Login failed for user '(null)'
Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus WolffThis is always an authentication problem somewhere. The null indicates that
user cannot be validated and a null is being passsed to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand, what about a solution or al least pointing to one?
"Rand Boyd [MSFT]" wrote:
> This is always an authentication problem somewhere. The null indicates tha
t
> user cannot be validated and a null is being passsed to SQL Server.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||It really depends on where the process is failing. You would
want to check the event logs on the PC having the problems
connecting. Check for any network related issues or
problems. Make sure that PC is contacting the domain
controllers without any problems and that they are
successfully logging into the network.
-Sue
On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
<JC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Rand, what about a solution or al least pointing to one?
>"Rand Boyd [MSFT]" wrote:
>|||Login failed for user <null> usually means that on the SQL box, the user
account could not be found in the local security database or in the domain
controller's user database.
For example, on machine1 I log in as machine1\user1. Then I try to log into
SQL on machine2. On machine2 SQL takes the SID of the user and calls
LookupAccountSID API. This attempts to convert the SID to the user name.
LookupAccountSID first looks in local security database on machine2, and
does not find machine1\User1, then looks on domain controller, and still
does not find the SID.
So in general this points to problems with the user account. Perhaps the
user has the same account name defined on their local machine and when they
log in they don't realize that they are logging in as the local User1 versus
the domain User1. Go to the problematic machine and check the user
accounts. If this does not work, perhaps have the domain admin drop the
user account and recreate it.
Matt
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:jd4sr0ds5vna1pc5ph4ri66j5hmri6d51p@.
4ax.com...
> It really depends on where the process is failing. You would
> want to check the event logs on the PC having the problems
> connecting. Check for any network related issues or
> problems. Make sure that PC is contacting the domain
> controllers without any problems and that they are
> successfully logging into the network.
> -Sue
> On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
> <JC@.discussions.microsoft.com> wrote:
>
>
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus WolffThis is always an authentication problem somewhere. The null indicates that
user cannot be validated and a null is being passsed to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Rand, what about a solution or al least pointing to one?
"Rand Boyd [MSFT]" wrote:
> This is always an authentication problem somewhere. The null indicates tha
t
> user cannot be validated and a null is being passsed to SQL Server.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>|||It really depends on where the process is failing. You would
want to check the event logs on the PC having the problems
connecting. Check for any network related issues or
problems. Make sure that PC is contacting the domain
controllers without any problems and that they are
successfully logging into the network.
-Sue
On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
<JC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Rand, what about a solution or al least pointing to one?
>"Rand Boyd [MSFT]" wrote:
>|||Login failed for user <null> usually means that on the SQL box, the user
account could not be found in the local security database or in the domain
controller's user database.
For example, on machine1 I log in as machine1\user1. Then I try to log into
SQL on machine2. On machine2 SQL takes the SID of the user and calls
LookupAccountSID API. This attempts to convert the SID to the user name.
LookupAccountSID first looks in local security database on machine2, and
does not find machine1\User1, then looks on domain controller, and still
does not find the SID.
So in general this points to problems with the user account. Perhaps the
user has the same account name defined on their local machine and when they
log in they don't realize that they are logging in as the local User1 versus
the domain User1. Go to the problematic machine and check the user
accounts. If this does not work, perhaps have the domain admin drop the
user account and recreate it.
Matt
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:jd4sr0ds5vna1pc5ph4ri66j5hmri6d51p@.
4ax.com...
> It really depends on where the process is failing. You would
> want to check the event logs on the PC having the problems
> connecting. Check for any network related issues or
> problems. Make sure that PC is contacting the domain
> controllers without any problems and that they are
> successfully logging into the network.
> -Sue
> On Mon, 13 Dec 2004 08:25:02 -0800, "JC"
> <JC@.discussions.microsoft.com> wrote:
>
>
Connection Error 18452 - Login failed for user '(null)'
Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus Wolff
I have the same problem and this is a problem associated with trusted SQL
Server connections, there is a document out there that says that if you use
named pipes everything is great but using TCP/IP, then you need to configure
Active directory and possibly using kerberos (instead of NTLM). I was hoping
to get more info on how to set out systems at work so that trusted
connections can work.
"Markus Wolff" wrote:
> Hello everybody,
> one of our users gets an error message when trying to connect to our SQL
> Server database:
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> The problem occured suddenly during work. The user can connect to the server
> using another computer and other users can connect using his computer.
> Knowledge base didn't help so I'm asking you.
> Configuration
> Client: Windows XP professional (2002/SP1)
> ODBC driver: SQL Server (2000.81.9042.00)
> Client configuration: TCP/IP
> Server: Windows 2000 Server
> SQL Server 7.0
> Seems the network setup for the user is somehow corrupted, since the message
> states the user to be '(null)'.
> Any suggestions?
> Thanks in advance,
> Markus Wolff
>
>
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus Wolff
I have the same problem and this is a problem associated with trusted SQL
Server connections, there is a document out there that says that if you use
named pipes everything is great but using TCP/IP, then you need to configure
Active directory and possibly using kerberos (instead of NTLM). I was hoping
to get more info on how to set out systems at work so that trusted
connections can work.
"Markus Wolff" wrote:
> Hello everybody,
> one of our users gets an error message when trying to connect to our SQL
> Server database:
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> The problem occured suddenly during work. The user can connect to the server
> using another computer and other users can connect using his computer.
> Knowledge base didn't help so I'm asking you.
> Configuration
> Client: Windows XP professional (2002/SP1)
> ODBC driver: SQL Server (2000.81.9042.00)
> Client configuration: TCP/IP
> Server: Windows 2000 Server
> SQL Server 7.0
> Seems the network setup for the user is somehow corrupted, since the message
> states the user to be '(null)'.
> Any suggestions?
> Thanks in advance,
> Markus Wolff
>
>
Connection Error 18452 - Login failed for user '(null)'
Hello everybody,
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus WolffI have the same problem and this is a problem associated with trusted SQL
Server connections, there is a document out there that says that if you use
named pipes everything is great but using TCP/IP, then you need to configure
Active directory and possibly using kerberos (instead of NTLM). I was hoping
to get more info on how to set out systems at work so that trusted
connections can work.
"Markus Wolff" wrote:
> Hello everybody,
> one of our users gets an error message when trying to connect to our SQL
> Server database:
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> The problem occured suddenly during work. The user can connect to the serv
er
> using another computer and other users can connect using his computer.
> Knowledge base didn't help so I'm asking you.
> Configuration
> Client: Windows XP professional (2002/SP1)
> ODBC driver: SQL Server (2000.81.9042.00)
> Client configuration: TCP/IP
> Server: Windows 2000 Server
> SQL Server 7.0
> Seems the network setup for the user is somehow corrupted, since the messa
ge
> states the user to be '(null)'.
> Any suggestions?
> Thanks in advance,
> Markus Wolff
>
>
one of our users gets an error message when trying to connect to our SQL
Server database:
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
The problem occured suddenly during work. The user can connect to the server
using another computer and other users can connect using his computer.
Knowledge base didn't help so I'm asking you.
Configuration
Client: Windows XP professional (2002/SP1)
ODBC driver: SQL Server (2000.81.9042.00)
Client configuration: TCP/IP
Server: Windows 2000 Server
SQL Server 7.0
Seems the network setup for the user is somehow corrupted, since the message
states the user to be '(null)'.
Any suggestions?
Thanks in advance,
Markus WolffI have the same problem and this is a problem associated with trusted SQL
Server connections, there is a document out there that says that if you use
named pipes everything is great but using TCP/IP, then you need to configure
Active directory and possibly using kerberos (instead of NTLM). I was hoping
to get more info on how to set out systems at work so that trusted
connections can work.
"Markus Wolff" wrote:
> Hello everybody,
> one of our users gets an error message when trying to connect to our SQL
> Server database:
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> The problem occured suddenly during work. The user can connect to the serv
er
> using another computer and other users can connect using his computer.
> Knowledge base didn't help so I'm asking you.
> Configuration
> Client: Windows XP professional (2002/SP1)
> ODBC driver: SQL Server (2000.81.9042.00)
> Client configuration: TCP/IP
> Server: Windows 2000 Server
> SQL Server 7.0
> Seems the network setup for the user is somehow corrupted, since the messa
ge
> states the user to be '(null)'.
> Any suggestions?
> Thanks in advance,
> Markus Wolff
>
>
Friday, February 24, 2012
Connection Broken Error
Hello everybody,
I am running a simple cursor and it has arround 10 thousand rows to loop.
But after sometime i am getting connection broken error. Exact error message
is as following.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
Do u have any idea, Pls let me know asap.I did a quick search and I could not find much with that error:
http://support.microsoft.com/defaul...b;en-us;Q827452
http://support.microsoft.com/defaul...b;en-us;Q229564
http://support.microsoft.com/defaul...b;en-us;Q317261
http://groups-beta.google.com/group...922b8b490d9e0f?
Are you running the cursor through Query Analyzer or within an app?
What protocol are you using to connect to SQL Server?
If you execute the cursor via Query Analyzer when you are sitting at the
server does it work?
Keith
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:2CF2E59D-B18B-4E40-BD13-FE038B4610C5@.microsoft.com...
> Hello everybody,
> I am running a simple cursor and it has arround 10 thousand rows to loop.
> But after sometime i am getting connection broken error. Exact error
message
> is as following.
>
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> Do u have any idea, Pls let me know asap.|||Hi Keith,
I am not on server, i am running cursor from my m/c in query analyzer. In my
client net work utility
rightnow there are two protols 1) TCP/IP and 2) Named pipes.
I do not know what is going on. pls let me know.
thx,
mvp
"Keith Kratochvil" wrote:
> I did a quick search and I could not find much with that error:
> http://support.microsoft.com/defaul...b;en-us;Q827452
> http://support.microsoft.com/defaul...b;en-us;Q229564
> http://support.microsoft.com/defaul...b;en-us;Q317261
> http://groups-beta.google.com/group...922b8b490d9e0f?
> Are you running the cursor through Query Analyzer or within an app?
> What protocol are you using to connect to SQL Server?
> If you execute the cursor via Query Analyzer when you are sitting at the
> server does it work?
> --
> Keith
>
> "mvp" <mvp@.discussions.microsoft.com> wrote in message
> news:2CF2E59D-B18B-4E40-BD13-FE038B4610C5@.microsoft.com...
> message
> (WrapperRead()).
>|||I can only say, I have the same problem on different computers. I run a larg
e
Query which gives a lot of rows (about 1000), und I get the same error.
The solution for me: Run a job with this Query or Create a stored procedure
which runs the query, and create a job with the stored procedure. Perhaps
this is a solution for you, too.
"mvp" wrote:
> Hi Keith,
> I am not on server, i am running cursor from my m/c in query analyzer. In
my
> client net work utility
> rightnow there are two protols 1) TCP/IP and 2) Named pipes.
> I do not know what is going on. pls let me know.
> thx,
> mvp
>
> "Keith Kratochvil" wrote:
>|||Had a similar problem and narrowed it down to the network (WAN). Not sure if
it was a router or NAT that disconnected me, but queries running more than
20 min got disconnected in 99% of the cases. Some managed to run for much
longer though, so it was all very fuzzy.
Running it as a job was the easiest solution. If you can (and may) you can
always try to run it via Remote Desktop on the server itself, off course.
Good luck,
Roby
"Fabrice" <Fabrice@.discussions.microsoft.com> wrote in message
news:6D79359E-AF28-496E-90DD-8CFAD4597D37@.microsoft.com...
>I can only say, I have the same problem on different computers. I run a
>large
> Query which gives a lot of rows (about 1000), und I get the same error.
> The solution for me: Run a job with this Query or Create a stored
> procedure
> which runs the query, and create a job with the stored procedure. Perhaps
> this is a solution for you, too.
> "mvp" wrote:
>|||What version of MDAC is installed on your client machine?
Keith
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:6519F77A-1D59-4B67-91E6-9A32DEC509B4@.microsoft.com...
> Hi Keith,
> I am not on server, i am running cursor from my m/c in query analyzer. In
my
> client net work utility
> rightnow there are two protols 1) TCP/IP and 2) Named pipes.
> I do not know what is going on. pls let me know.
> thx,
> mvp
>
> "Keith Kratochvil" wrote:
>
http://groups-beta.google.com/group...922b8b490d9e0f?
loop.
I am running a simple cursor and it has arround 10 thousand rows to loop.
But after sometime i am getting connection broken error. Exact error message
is as following.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
Do u have any idea, Pls let me know asap.I did a quick search and I could not find much with that error:
http://support.microsoft.com/defaul...b;en-us;Q827452
http://support.microsoft.com/defaul...b;en-us;Q229564
http://support.microsoft.com/defaul...b;en-us;Q317261
http://groups-beta.google.com/group...922b8b490d9e0f?
Are you running the cursor through Query Analyzer or within an app?
What protocol are you using to connect to SQL Server?
If you execute the cursor via Query Analyzer when you are sitting at the
server does it work?
Keith
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:2CF2E59D-B18B-4E40-BD13-FE038B4610C5@.microsoft.com...
> Hello everybody,
> I am running a simple cursor and it has arround 10 thousand rows to loop.
> But after sometime i am getting connection broken error. Exact error
message
> is as following.
>
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> Do u have any idea, Pls let me know asap.|||Hi Keith,
I am not on server, i am running cursor from my m/c in query analyzer. In my
client net work utility
rightnow there are two protols 1) TCP/IP and 2) Named pipes.
I do not know what is going on. pls let me know.
thx,
mvp
"Keith Kratochvil" wrote:
> I did a quick search and I could not find much with that error:
> http://support.microsoft.com/defaul...b;en-us;Q827452
> http://support.microsoft.com/defaul...b;en-us;Q229564
> http://support.microsoft.com/defaul...b;en-us;Q317261
> http://groups-beta.google.com/group...922b8b490d9e0f?
> Are you running the cursor through Query Analyzer or within an app?
> What protocol are you using to connect to SQL Server?
> If you execute the cursor via Query Analyzer when you are sitting at the
> server does it work?
> --
> Keith
>
> "mvp" <mvp@.discussions.microsoft.com> wrote in message
> news:2CF2E59D-B18B-4E40-BD13-FE038B4610C5@.microsoft.com...
> message
> (WrapperRead()).
>|||I can only say, I have the same problem on different computers. I run a larg
e
Query which gives a lot of rows (about 1000), und I get the same error.
The solution for me: Run a job with this Query or Create a stored procedure
which runs the query, and create a job with the stored procedure. Perhaps
this is a solution for you, too.
"mvp" wrote:
> Hi Keith,
> I am not on server, i am running cursor from my m/c in query analyzer. In
my
> client net work utility
> rightnow there are two protols 1) TCP/IP and 2) Named pipes.
> I do not know what is going on. pls let me know.
> thx,
> mvp
>
> "Keith Kratochvil" wrote:
>|||Had a similar problem and narrowed it down to the network (WAN). Not sure if
it was a router or NAT that disconnected me, but queries running more than
20 min got disconnected in 99% of the cases. Some managed to run for much
longer though, so it was all very fuzzy.
Running it as a job was the easiest solution. If you can (and may) you can
always try to run it via Remote Desktop on the server itself, off course.
Good luck,
Roby
"Fabrice" <Fabrice@.discussions.microsoft.com> wrote in message
news:6D79359E-AF28-496E-90DD-8CFAD4597D37@.microsoft.com...
>I can only say, I have the same problem on different computers. I run a
>large
> Query which gives a lot of rows (about 1000), und I get the same error.
> The solution for me: Run a job with this Query or Create a stored
> procedure
> which runs the query, and create a job with the stored procedure. Perhaps
> this is a solution for you, too.
> "mvp" wrote:
>|||What version of MDAC is installed on your client machine?
Keith
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:6519F77A-1D59-4B67-91E6-9A32DEC509B4@.microsoft.com...
> Hi Keith,
> I am not on server, i am running cursor from my m/c in query analyzer. In
my
> client net work utility
> rightnow there are two protols 1) TCP/IP and 2) Named pipes.
> I do not know what is going on. pls let me know.
> thx,
> mvp
>
> "Keith Kratochvil" wrote:
>
http://groups-beta.google.com/group...922b8b490d9e0f?
loop.
Subscribe to:
Posts (Atom)