Network error

When I unplug my server from the network, I lose connection to SQL Server. I
don't understand why it is happening. All my applications have to be closed
and reopened to talk to the database again. Can anyone please let me know wh
y
this is happening?
I am using SQL Server 2005 SP1 and Windows Server 2003.
Any help is appreciated.FYI: I am connected to the local server and not to a server on the network.
"KMP" wrote:

> When I unplug my server from the network, I lose connection to SQL Server.
I
> don't understand why it is happening. All my applications have to be close
d
> and reopened to talk to the database again. Can anyone please let me know
why
> this is happening?
> I am using SQL Server 2005 SP1 and Windows Server 2003.
> Any help is appreciated.|||Please verify on your sql server what protocol is using if is using tcp/ip a
s
default thats why. also you can create a local host file with the localip or
just 127.0.0.1
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"KMP" wrote:
[vbcol=seagreen]
> FYI: I am connected to the local server and not to a server on the network
.
> "KMP" wrote:
>|||Thanks. But I don't understand what you are trying to tell me. Yes, SQL
Server is using TCP/IP. Can you be more specific on the host file thing?
"Santos Martinez" wrote:
[vbcol=seagreen]
> Please verify on your sql server what protocol is using if is using tcp/ip
as
> default thats why. also you can create a local host file with the localip
or
> just 127.0.0.1
>
> --
> Santos Martinez,MCSE, MCDBA, MCTS
> IT Community Staff of Puerto Rico
> http://www.itcspr.org
>
> "KMP" wrote:
>|||KMP wrote:
> Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> Server is using TCP/IP. Can you be more specific on the host file thing?
>
When you connect to a TCP/IP networked computer, you either do it by
specifying the IP address of the machine, or the hostname of the
machine. If you specify the hostname, then your computer will talk to a
DNS or WINS server to find out what IP address that hostname equates to.
If your machine is disconnected from the network, it can't communicate
with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
10.10.10.1, for example. Since you're connecting back to your own
machine, you can avoid this by specifying an IP address of 127.0.0.1, or
a machine name of "localhost" - either one will loop back to your own
machine. Basic networking stuff...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||So can you please tell me where and how I would be making the changes?
"Tracy McKibben" wrote:

> KMP wrote:
> When you connect to a TCP/IP networked computer, you either do it by
> specifying the IP address of the machine, or the hostname of the
> machine. If you specify the hostname, then your computer will talk to a
> DNS or WINS server to find out what IP address that hostname equates to.
> If your machine is disconnected from the network, it can't communicate
> with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
> 10.10.10.1, for example. Since you're connecting back to your own
> machine, you can avoid this by specifying an IP address of 127.0.0.1, or
> a machine name of "localhost" - either one will loop back to your own
> machine. Basic networking stuff...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Hi, Can someone help me get past this stumbling block? Thanks.
"KMP" wrote:
[vbcol=seagreen]
> So can you please tell me where and how I would be making the changes?
> "Tracy McKibben" wrote:
>|||KMP wrote:
> So can you please tell me where and how I would be making the changes?
>
I'm not sure what you're looking to change. As I stated, if you simply
connect to "127.0.0.1" or "localhost", things should work whether you're
on the network or not. Query Analyzer and/or Management Studio will
prompt you for a server name, use "localhost". In Enterprise Manager,
you'll have to register a new server to represent "localhost".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||have you try to modify the hosts on %windir%\system32\drivers\etc.
put localhost = 127.0.0.1 or yourmachinename = 127.0.0.1
also have you take a look into the network client network utility and server
network utility.
regards,
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Tracy McKibben" wrote:

> KMP wrote:
> I'm not sure what you're looking to change. As I stated, if you simply
> connect to "127.0.0.1" or "localhost", things should work whether you're
> on the network or not. Query Analyzer and/or Management Studio will
> prompt you for a server name, use "localhost". In Enterprise Manager,
> you'll have to register a new server to represent "localhost".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Network error

When I unplug my server from the network, I lose connection to SQL Server. I
don't understand why it is happening. All my applications have to be closed
and reopened to talk to the database again. Can anyone please let me know why
this is happening?
I am using SQL Server 2005 SP1 and Windows Server 2003.
Any help is appreciated.FYI: I am connected to the local server and not to a server on the network.
"KMP" wrote:
> When I unplug my server from the network, I lose connection to SQL Server. I
> don't understand why it is happening. All my applications have to be closed
> and reopened to talk to the database again. Can anyone please let me know why
> this is happening?
> I am using SQL Server 2005 SP1 and Windows Server 2003.
> Any help is appreciated.|||Please verify on your sql server what protocol is using if is using tcp/ip as
default thats why. also you can create a local host file with the localip or
just 127.0.0.1
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"KMP" wrote:
> FYI: I am connected to the local server and not to a server on the network.
> "KMP" wrote:
> > When I unplug my server from the network, I lose connection to SQL Server. I
> > don't understand why it is happening. All my applications have to be closed
> > and reopened to talk to the database again. Can anyone please let me know why
> > this is happening?
> >
> > I am using SQL Server 2005 SP1 and Windows Server 2003.
> >
> > Any help is appreciated.|||Thanks. But I don't understand what you are trying to tell me. Yes, SQL
Server is using TCP/IP. Can you be more specific on the host file thing?
"Santos Martinez" wrote:
> Please verify on your sql server what protocol is using if is using tcp/ip as
> default thats why. also you can create a local host file with the localip or
> just 127.0.0.1
>
> --
> Santos Martinez,MCSE, MCDBA, MCTS
> IT Community Staff of Puerto Rico
> http://www.itcspr.org
>
> "KMP" wrote:
> > FYI: I am connected to the local server and not to a server on the network.
> >
> > "KMP" wrote:
> >
> > > When I unplug my server from the network, I lose connection to SQL Server. I
> > > don't understand why it is happening. All my applications have to be closed
> > > and reopened to talk to the database again. Can anyone please let me know why
> > > this is happening?
> > >
> > > I am using SQL Server 2005 SP1 and Windows Server 2003.
> > >
> > > Any help is appreciated.|||KMP wrote:
> Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> Server is using TCP/IP. Can you be more specific on the host file thing?
>
When you connect to a TCP/IP networked computer, you either do it by
specifying the IP address of the machine, or the hostname of the
machine. If you specify the hostname, then your computer will talk to a
DNS or WINS server to find out what IP address that hostname equates to.
If your machine is disconnected from the network, it can't communicate
with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
10.10.10.1, for example. Since you're connecting back to your own
machine, you can avoid this by specifying an IP address of 127.0.0.1, or
a machine name of "localhost" - either one will loop back to your own
machine. Basic networking stuff...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||So can you please tell me where and how I would be making the changes?
"Tracy McKibben" wrote:
> KMP wrote:
> > Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> > Server is using TCP/IP. Can you be more specific on the host file thing?
> >
> When you connect to a TCP/IP networked computer, you either do it by
> specifying the IP address of the machine, or the hostname of the
> machine. If you specify the hostname, then your computer will talk to a
> DNS or WINS server to find out what IP address that hostname equates to.
> If your machine is disconnected from the network, it can't communicate
> with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
> 10.10.10.1, for example. Since you're connecting back to your own
> machine, you can avoid this by specifying an IP address of 127.0.0.1, or
> a machine name of "localhost" - either one will loop back to your own
> machine. Basic networking stuff...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Hi, Can someone help me get past this stumbling block? Thanks.
"KMP" wrote:
> So can you please tell me where and how I would be making the changes?
> "Tracy McKibben" wrote:
> > KMP wrote:
> > > Thanks. But I don't understand what you are trying to tell me. Yes, SQL
> > > Server is using TCP/IP. Can you be more specific on the host file thing?
> > >
> >
> > When you connect to a TCP/IP networked computer, you either do it by
> > specifying the IP address of the machine, or the hostname of the
> > machine. If you specify the hostname, then your computer will talk to a
> > DNS or WINS server to find out what IP address that hostname equates to.
> > If your machine is disconnected from the network, it can't communicate
> > with a DNS or WINS, and therefore can't figure out that MACHINEX = IP
> > 10.10.10.1, for example. Since you're connecting back to your own
> > machine, you can avoid this by specifying an IP address of 127.0.0.1, or
> > a machine name of "localhost" - either one will loop back to your own
> > machine. Basic networking stuff...
> >
> >
> > --
> > Tracy McKibben
> > MCDBA
> > http://www.realsqlguy.com
> >|||KMP wrote:
> So can you please tell me where and how I would be making the changes?
>
I'm not sure what you're looking to change. As I stated, if you simply
connect to "127.0.0.1" or "localhost", things should work whether you're
on the network or not. Query Analyzer and/or Management Studio will
prompt you for a server name, use "localhost". In Enterprise Manager,
you'll have to register a new server to represent "localhost".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||have you try to modify the hosts on %windir%\system32\drivers\etc.
put localhost = 127.0.0.1 or yourmachinename = 127.0.0.1
also have you take a look into the network client network utility and server
network utility.
regards,
--
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Tracy McKibben" wrote:
> KMP wrote:
> > So can you please tell me where and how I would be making the changes?
> >
> I'm not sure what you're looking to change. As I stated, if you simply
> connect to "127.0.0.1" or "localhost", things should work whether you're
> on the network or not. Query Analyzer and/or Management Studio will
> prompt you for a server name, use "localhost". In Enterprise Manager,
> you'll have to register a new server to represent "localhost".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>sql

Network connection problem when trying to use SSMS

I have two SQL servers that are having the same problem. I have
recently installed SSMS on my laptop, and when I try to connect to one
of my SQL Servers using SSMS, the NIC card dies. I have two NICs in
both of these servers, one on the normal LAN, and the other NIC is
used on a separate VLAN that the servers use to talk to each other.
After a minute or two of being connected to the SQL database, the
server just stops responding. I can't ping it, I can't RDP into it,
and I can't connect to any of the DBs on it from the LAN. I can still
access the server from one of the other servers, however, because that
NIC is not affected. As soon as I open a web browser from that server
and try to go to an external website, the NIC reactivates and I can
access it from the LAN again. I can manage the DBs on the other
server using SSMS without a problem, however. An associate of mine,
is having the exact same problem, but with the other server. He is
able to manage the server that I can't from the LAN using SSMS, and
vice versa. I've done some googling, but haven't had any luck as of
yet.
Has anyone else seen this and know how to fix it'
Thanks, in advance.Hi Matt
I assume you have tried changing the NICs?
Have you looked at the perfmon counters to see the NIC activity?
Are you using any monitoring, AV, IDS or software update software on your
networks?
John
"Matt" wrote:
> I have two SQL servers that are having the same problem. I have
> recently installed SSMS on my laptop, and when I try to connect to one
> of my SQL Servers using SSMS, the NIC card dies. I have two NICs in
> both of these servers, one on the normal LAN, and the other NIC is
> used on a separate VLAN that the servers use to talk to each other.
> After a minute or two of being connected to the SQL database, the
> server just stops responding. I can't ping it, I can't RDP into it,
> and I can't connect to any of the DBs on it from the LAN. I can still
> access the server from one of the other servers, however, because that
> NIC is not affected. As soon as I open a web browser from that server
> and try to go to an external website, the NIC reactivates and I can
> access it from the LAN again. I can manage the DBs on the other
> server using SSMS without a problem, however. An associate of mine,
> is having the exact same problem, but with the other server. He is
> able to manage the server that I can't from the LAN using SSMS, and
> vice versa. I've done some googling, but haven't had any luck as of
> yet.
> Has anyone else seen this and know how to fix it'
> Thanks, in advance.
>

Network Connection

I installed MSDE on a 2003 server machine in an AD environment. During the
setup I used the disablenetworkprotocols=0 switch to enable network
connections. I also enable mixed mode authentication. However, I still
cannot connect to the server from a XP sp2 machine on the network. (firewall
is disabled) The error returned is sqlserver does not exist or access denied.
I tried connecting via windows autehntication and specifying a SQL account.
Does anyone know why I cannot connect or maybe a site that will help diagnose
the problem?
hi Joe,
Joe Kiaser wrote:
> I installed MSDE on a 2003 server machine in an AD environment.
> During the setup I used the disablenetworkprotocols=0 switch to
> enable network connections. I also enable mixed mode authentication.
> However, I still cannot connect to the server from a XP sp2 machine
> on the network. (firewall is disabled) The error returned is
> sqlserver does not exist or access denied.
>
please have a look at
http://support.microsoft.com/default...06&Product=sql
for some potential causes of this kind of problem..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I discoverd it was problem with DNS. <Webserver> was pointing to the wrong
IP so when we tried to connect using <webserver> it would fail. I
discovered this after pinging <webserver> and it returned 120.0.0.21...our
WSUS server. I just updated the DNS to point <webserver> to 120.0.0.23 and
it works flawlessly.
"Andrea Montanari" wrote:

> hi Joe,
> Joe Kiaser wrote:
> please have a look at
> http://support.microsoft.com/default...06&Product=sql
> for some potential causes of this kind of problem..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
sql

Netstat TIME_WAIT on SQL Server Connections

If I understand correctly, the TIME_WAIT Status when you do a NETSTAT on the
server indicates that the connection has been closed, and it is waiting to
clear. Is that right? If so, we have a lot of SQL Server connections that
are in TIME_WAIT status mode. We may have well over 100 or so of these, and
they do not clear out very fast. Why would they stick around like that, and
how do I get them to clear out sooner? Could they potentially be causing
problems by not clearing out?
Thanks,
Jesse
Hi
Connection Pooling on the Client MDAC stack. By default the SQL Driver will
keep the connection open for 120 seconds after a "close" has been issued. If
another request comes along and it uses the same credentials to the same
server, it does not have to re-setup the TCP/IP connection. Instead it puts
it on the connection that has been around the longest in the TIME_WAIT
state.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jesse" <nospam@.fake.com> wrote in message
news:u9T48m3OFHA.1176@.TK2MSFTNGP12.phx.gbl...
> If I understand correctly, the TIME_WAIT Status when you do a NETSTAT on
> the server indicates that the connection has been closed, and it is
> waiting to clear. Is that right? If so, we have a lot of SQL Server
> connections that are in TIME_WAIT status mode. We may have well over 100
> or so of these, and they do not clear out very fast. Why would they stick
> around like that, and how do I get them to clear out sooner? Could they
> potentially be causing problems by not clearing out?
> Thanks,
> Jesse
>
|||I have looked into those settings, and they are set up as you stated,
however, these are staying in TIME_WAIT long after the 120 seconds. For
instance, I can log on to our server at 8:00 or 9:00 at night, when there is
no one on the server, and there are well over 100 connections left in
TIME_WAIT status. Any ideas why?
Jesse
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:Ol4H%23U5OFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hi
> Connection Pooling on the Client MDAC stack. By default the SQL Driver
> will keep the connection open for 120 seconds after a "close" has been
> issued. If another request comes along and it uses the same credentials to
> the same server, it does not have to re-setup the TCP/IP connection.
> Instead it puts it on the connection that has been around the longest in
> the TIME_WAIT state.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Jesse" <nospam@.fake.com> wrote in message
> news:u9T48m3OFHA.1176@.TK2MSFTNGP12.phx.gbl...
>

Netstat TIME_WAIT on SQL Server Connections

If I understand correctly, the TIME_WAIT Status when you do a NETSTAT on the
server indicates that the connection has been closed, and it is waiting to
clear. Is that right? If so, we have a lot of SQL Server connections that
are in TIME_WAIT status mode. We may have well over 100 or so of these, and
they do not clear out very fast. Why would they stick around like that, and
how do I get them to clear out sooner? Could they potentially be causing
problems by not clearing out?
Thanks,
JesseHi
Connection Pooling on the Client MDAC stack. By default the SQL Driver will
keep the connection open for 120 seconds after a "close" has been issued. If
another request comes along and it uses the same credentials to the same
server, it does not have to re-setup the TCP/IP connection. Instead it puts
it on the connection that has been around the longest in the TIME_WAIT
state.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jesse" <nospam@.fake.com> wrote in message
news:u9T48m3OFHA.1176@.TK2MSFTNGP12.phx.gbl...
> If I understand correctly, the TIME_WAIT Status when you do a NETSTAT on
> the server indicates that the connection has been closed, and it is
> waiting to clear. Is that right? If so, we have a lot of SQL Server
> connections that are in TIME_WAIT status mode. We may have well over 100
> or so of these, and they do not clear out very fast. Why would they stick
> around like that, and how do I get them to clear out sooner? Could they
> potentially be causing problems by not clearing out?
> Thanks,
> Jesse
>|||I have looked into those settings, and they are set up as you stated,
however, these are staying in TIME_WAIT long after the 120 seconds. For
instance, I can log on to our server at 8:00 or 9:00 at night, when there is
no one on the server, and there are well over 100 connections left in
TIME_WAIT status. Any ideas why?
Jesse
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:Ol4H%23U5OFHA.3356@.TK2MSFTNGP12.phx.gbl...
> Hi
> Connection Pooling on the Client MDAC stack. By default the SQL Driver
> will keep the connection open for 120 seconds after a "close" has been
> issued. If another request comes along and it uses the same credentials to
> the same server, it does not have to re-setup the TCP/IP connection.
> Instead it puts it on the connection that has been around the longest in
> the TIME_WAIT state.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Jesse" <nospam@.fake.com> wrote in message
> news:u9T48m3OFHA.1176@.TK2MSFTNGP12.phx.gbl...
>

Needed: User, Login, Connection advice.

HI,
I'm still on the steep side of the learning curve with ASP.NET. I've looked through a number of threads on this forum, and have gotten pieces of the answer, but need help getting past a roadblock.

I haven't been able to get a simple test application to connect to the Pubs database loaded on my system running MSDE. The only control in the application is a WebDataForm created by the Wizard. Everything works well (even the Preview Data form the Data menu loads and displays the correct data), except when the form is viewed in a browser. Click the load button and an error:Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

Similar stories are common on this forum, and I tried to address the problem. I'm quite sure it's a autherization or authentication problem. I have Windows Server 2003 (with IIS 6.0), VS.NET 03 and MSDE as the SQL server on the same box. The MSDE server is using Windows Security mode. I Created a new user called ASPNET on the Windows Server. I added a login to the SQL Server 'WinServerName\ASPNET' using windows auth. Still get the same login failed message.

Is there something I'm missing? Do I have to add a new user to IIS?

For the record, what users/settings do I need to have in Windows, SQL-Server and IIS, get past this login problem.

Thanks for answering this basic question - one more time.Hi,
An Addendum to my message:

I found out that WINDOWS SERVER 2003 in native mode (default), running IIS 6.0 Uses "NETWORK SERVICE" rather than "ASPNET" as the default login user name for ASP.NET applications. I had not seen this in the messages I looked through in this forum.

When I, after a number of dead ends, created a new Login for my SQL Server - (as I'm using MSDE, I used The Web Data Administrator rather than Enterprise Manager or OSQL to create the new login) - with the name 'NT AUTHORITY\NETWORK SERVICE', the application was able to access the database through the VS and IE browswers.

As this test application is only used locally, I'm not concerned with the security ramifications of this method of access. However, I can see that it will be a big concern, and a lot of work to establish the appropriate methods when I have a production application to deploy.

I still would welcome advice on what strategies you have used to provide appropriate access privilages to ASP.NET applications and users that will need to access data from SQL Server databases in production environments.

I know that this is asking a lot - as there are so many permutations to consider. What I would hope you could provide, is a base line of "must" and "must never" stepsfor establishing data connections to data sources using ASP.NET.

If this is too open ended a question - let me know your thoughts on that as well. In looking through the messages of the past 3 months on this forum, I know that many have been frustrated by the complxity of getting a database connection established. Yes, the information to get it done is out there, but the sheer volume can be daunting.

Thanks for all you help with my questions.

Need your Help

Hi all,

I am using VB6, PostgreSQL 8.1 & Crystal Report 8.0. Now i am able to achieve the connection between a Crystal Report and postgresql database thru ODBC DSN which is hard coded in that crystal report @. design time. Is it possible to establish connection between postgresql and crystal report on run time thru VB6 code. I tried to use CR.Connect property but in vain since it is giving error as "Error detected by Database DLL"Make sure CR is installed properly
See if you find answer here
http://support.businessobjects.com/

Need urgent help about sql connection denied

From the same web server to sql server, ASP pages work fine, but .NET pages get "SQL Server does not exist or access denied" error message.
Environment:
both are Windows 2000 sp4,
sql server 2000 sp4
not firewall between
Everything is okay before I got some windows security updates fails on the sql server! and I reboot the sql server!
What happened with the security update? Why does it only effect the .NET pages not the ASP pages? They even use the same connection string!
Thanks for any comment

Are you using integrated security? That is, are you passing in a user name and password (in which case you are using SQL Server security) or not (in which case you are using integrated security). ASP and ASP.NET operate under different security contexts. ASP operates as IUSR_<machinename>, whereas ASP.NET operates under the security context of the ASPNET windows user.

I have no idea what the security update would have done.

|||

Thanks for the reply.
I do pass a user name and password in the connection string. it's the same string that I used in the ASP pages. it works fine. But I reboot the servers, only the ASP pages work.
the string looks like "DATABASE=fansion;server=dbsvr; uid=sa; pwd=password;"

|||Just tested, this problam only happens on the windows 2000 web server, windows 2003 is fine.|||

Did you ever get an answer for this re: sql connection - same string works under asp, not under asp.net, with userid= and password= and not with a dsn?

thanks a lot

Neil Jay warner

Need urgent help

Hi

I have a strange situation. We have a middle teir application (j2ee appserver) that uses connection pooling.

The client was working fine when all of a sudden it hangs.

I have checked the sp_lock and sp_who2 and there has been no locking/blocking whatsover. This problem stays until we restart the app server. Is there any way that I can further dig into this problem and find it out if it is the db that is causing the issue.

I used sql profiler and I could see some log entries made into the database while client is hanging after that. Also sp_who2 lists the spid for the middle tier connection. It does not however show any locks associated with it. The last batch date however is updated every time the client is opened (when it hangs).

Any pointers as to why this is happening,how to diagnose and prevent this is extermely helpful

From what you're saying, it looks like the problem does not reside in the database. If sp_who2 does not return any values in the BlkBy column then probably it is not a db problem.

Besides locking, another thing that can happen is to have an infinite loop in your T-SQL code. You can verify this by running SQL Profiler.

Just to make sure that the problem does not reside in your database you can kill your db connection (by using Kill SPID in Query Analyzer) and see if the client app still does not respond. If it still doesn't then the problem is in your client app and not in the database.

Hope it helps,

Doru

|||

You might be right......I had also killed the spid on the backend and the client still hangs.....Probably it has got to to do with the txactional setting placed on the middle tier connection,,,,Besides there are no infinite loops on the back end,,,,

Thanks for the post....