Deadlock with Port: 0

I've been diagnosing deadlocks for a last couple weeks at a client site and I understand the KEY: and TAB: locks issues. However, the client recently experienced a series of multi-branch deadlocks for which I can find no information. Attached is the deadlock text from the ERRORLOG. Any help would be much appreciated.

NickHave you tried to capture deadlocks with the profiler ? It is surely clearer than errorlogs.|||Unfortunately I don't have access to the production system this is running on. I have run profiler traces but that still doesn't tell me anything about Port: 0.

Deadlock Issue

Hi all,
I am using Visual Foxpro as front end and SQL Server at
backend. This is a Client/Server Database App. I am facing
deadlock problems in this environment. Please provice me
any help in this regard.
Thgank in advance.
That is a very open eneded question. You can read SQL Server 2000 Books
Online to understand, what a dead lock is, and how to avoid and troubleshoot
deadlocks in SQL Server Books Online. Believe me, there's a lot of
information in Books Online.
Additionally, you could try out the following link, to learn how to log
additional information about deadlocks into SQL Server error log:
http://vyaskn.tripod.com/administration_faq.htm#q14
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Muhammad Saleem" <anonymous@.discussions.microsoft.com> wrote in message
news:958501c49711$dbde1760$a601280a@.phx.gbl...
> Hi all,
> I am using Visual Foxpro as front end and SQL Server at
> backend. This is a Client/Server Database App. I am facing
> deadlock problems in this environment. Please provice me
> any help in this regard.
> Thgank in advance.

Deadlock detection problem! help

Hello faculties,

i'm encountering a strange a deadlock problem on my remote server
which is used to give application demo to the client. It has happened
that on one of the databases a deadlock situation is taking place.

What is the most detailed way to detect such the cause of such a
deadlock to the innermost level of detail, like what statements, stored
procedures and locks are causing the deadlock to occur.

Guys! please help me out!

Thanks in advance
Debian

*** Sent via Developersdex http://www.developersdex.com ***debian mojo (debian_mojo@.yahoo.com) writes:
> i'm encountering a strange a deadlock problem on my remote server
> which is used to give application demo to the client. It has happened
> that on one of the databases a deadlock situation is taking place.
> What is the most detailed way to detect such the cause of such a
> deadlock to the innermost level of detail, like what statements, stored
> procedures and locks are causing the deadlock to occur.

DBCC TRACEON (1204, 1)
DBCC TRACEON (3605, 1)

It's common to add these as start up parameters (best done from Enterprise
Manager).

This gives you a deadlock trace to the SQL Server log. Unfortunately,
though, it's a bit cryptic.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Deadlock

Hi there!
In my database client application (C#) I sometimes get an exception telling
me, that my application (which runs a some kind ob batch job) was selected
as deadlock victim and the active transaction was terminated.
No I want to get mor information about, which other application causes the
deadlock.
I thought about executing "sp_lock" just after I received the
deadlock-exception, but I think that this is too late, because my
transaction will be already terminated at this time, and ther won't be a
deadlock any longer.
Can anyone tell me, what would be the best way to receive information about
the active database-connections and their locks, BEFORE the deadlock
situation is cleared by the database-engine?
Is there some kind of trigger or sth. like that?
As the problem doesn't occur regularly, and it's only on the productive
machine, I absolutely don't want to have the profiler active!
Thanks in advance!
Max
Markus
Take a look at sp_who2 stored procedure on clolumn blkby (If I remember
well) . That tells you who is blocked and by whom.
Regarding to DEADLOCKS please visit at this site
http://www.sql-server-performance.com/deadlocks.asp
"Markus Emayr" <essmayr/at/racon-linz.at> wrote in message
news:%23GGruXUfFHA.1412@.TK2MSFTNGP09.phx.gbl...
> Hi there!
> In my database client application (C#) I sometimes get an exception
telling
> me, that my application (which runs a some kind ob batch job) was selected
> as deadlock victim and the active transaction was terminated.
> No I want to get mor information about, which other application causes the
> deadlock.
> I thought about executing "sp_lock" just after I received the
> deadlock-exception, but I think that this is too late, because my
> transaction will be already terminated at this time, and ther won't be a
> deadlock any longer.
> Can anyone tell me, what would be the best way to receive information
about
> the active database-connections and their locks, BEFORE the deadlock
> situation is cleared by the database-engine?
> Is there some kind of trigger or sth. like that?
> As the problem doesn't occur regularly, and it's only on the productive
> machine, I absolutely don't want to have the profiler active!
> Thanks in advance!
> Max
>
|||Use the trace flag 1024 to receive notifications about deadlocks.
DBCC TRACEON (1024, -1)
[]s
Luciano Caixeta Moreira
Meu blog: http://br.thespoke.net/MyBlog/Luti/MyBlog.aspx
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OMKxokUfFHA.1044@.tk2msftngp13.phx.gbl...
> Markus
> Take a look at sp_who2 stored procedure on clolumn blkby (If I remember
> well) . That tells you who is blocked and by whom.
> Regarding to DEADLOCKS please visit at this site
> http://www.sql-server-performance.com/deadlocks.asp
>
>
> "Markus Emayr" <essmayr/at/racon-linz.at> wrote in message
> news:%23GGruXUfFHA.1412@.TK2MSFTNGP09.phx.gbl...
> telling
> about
>

DBPROCESS is dead or not enabled - HELP!

I am using MSDE on a network with multiple PCs. One PC has the MSDE Database
and client applications connected to the database. The other PCs also have
Client applications connected to the database.
When one of the Client PCs is logged off and shut down, the Applications on
the Database's PC get the error "DBPROCESS is dead or not enabled", Error
Code: 10005.
Can anyone help please?
Regards,
Loz Moz
"Loz Moz" <LozMoz@.hotmail.com> ha scritto nel messaggio
news:4125e38e$0$29908$cc9e4d1f@.news.dial.pipex.com ...
> I am using MSDE on a network with multiple PCs. One PC has the MSDE
Database
> and client applications connected to the database. The other PCs also have
> Client applications connected to the database.
> When one of the Client PCs is logged off and shut down, the Applications
on
> the Database's PC get the error "DBPROCESS is dead or not enabled", Error
> Code: 10005.
> Can anyone help please?
The [DBProcess is dead or not enabled message] is a generic error meaning
the client has lost the connection to the server, and, unfortunately,
there's plenty of conditions that can cause this to happen, from network
problems to timeout problems to server down problems.
further ideas at
http://www.winnetmag.com/Article/Art...019/14019.html
http://tinyurl.com/3w37b
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

dbo.master database

We have some client software developed by 3rd party that is used internally
and requires use of our SQL server. We've had some problems with this
software in the past and the developers solution was to add the dbclient
login (used by the client software) to the dbo (owner) group of the SQL
master database. This is concerns me. Is there any reason that client
software should have full access to the SQL master database? We have many
other production databases in use on this server. I'm considering
installing a separate instance of SQL 2005 (their newest version uses SQL
2005, the version we're using now uses SQL 2000) so that they can have full
ownership access of the master database without having to worry about this
affecting other existing databases. Thanks for any advice.
RyanHi,
No need to have DBO role in Master database. Just verify the sp_who
contineously for some time and confirm the
application user connects to Master database (You could also use profiler).
Once you confirmed revove the dbo role for the application user from Master
database and see what happends.
If it is production I recommend you to do during a offtime during
weekends...
Thanks
Hari
SQL Server MVP
"Ryan" <Tyveil@.newsgroups.nospam> wrote in message
news:Obzny9huGHA.5044@.TK2MSFTNGP05.phx.gbl...
> We have some client software developed by 3rd party that is used
> internally and requires use of our SQL server. We've had some problems
> with this software in the past and the developers solution was to add the
> dbclient login (used by the client software) to the dbo (owner) group of
> the SQL master database. This is concerns me. Is there any reason that
> client software should have full access to the SQL master database? We
> have many other production databases in use on this server. I'm
> considering installing a separate instance of SQL 2005 (their newest
> version uses SQL 2005, the version we're using now uses SQL 2000) so that
> they can have full ownership access of the master database without having
> to worry about this affecting other existing databases. Thanks for any
> advice.
> Ryan
>|||> This is concerns me.
That seems like an unreasonable response on the part of a DBA.
Concerned is far too mild. I think terrified would be reasonable.
This sounds like a quick fix that avoided having to actually figure
out what the real problem is. It is not something that I would allow
even on a development server, and on production any auditor (if they
knew the first thing about SQL Server) would have a field day.
Perhaps if someone does the analysis to identify the actual
requirement a more reasonable solution can be found. Otherwise I
would say that running on a separate instance is probably the only
answer.
Roy Harvey
Beacon Falls, CT
On Mon, 7 Aug 2006 07:43:38 -0500, "Ryan" <Tyveil@.newsgroups.nospam>
wrote:

>We have some client software developed by 3rd party that is used internally
>and requires use of our SQL server. We've had some problems with this
>software in the past and the developers solution was to add the dbclient
>login (used by the client software) to the dbo (owner) group of the SQL
>master database. This is concerns me. Is there any reason that client
>software should have full access to the SQL master database? We have many
>other production databases in use on this server. I'm considering
>installing a separate instance of SQL 2005 (their newest version uses SQL
>2005, the version we're using now uses SQL 2000) so that they can have full
>ownership access of the master database without having to worry about this
>affecting other existing databases. Thanks for any advice.
>Ryan
>|||Roy Harvey wrote:
> That seems like an unreasonable response on the part of a DBA.
> Concerned is far too mild. I think terrified would be reasonable.
> This sounds like a quick fix that avoided having to actually figure
> out what the real problem is. It is not something that I would allow
> even on a development server, and on production any auditor (if they
> knew the first thing about SQL Server) would have a field day.
> Perhaps if someone does the analysis to identify the actual
> requirement a more reasonable solution can be found. Otherwise I
> would say that running on a separate instance is probably the only
> answer.
When in doubt, make everybody an admin, right? ;-)
Tracy McKibben
MCDBA
http://www.realsqlguy.com

dbo.master database

We have some client software developed by 3rd party that is used internally
and requires use of our SQL server. We've had some problems with this
software in the past and the developers solution was to add the dbclient
login (used by the client software) to the dbo (owner) group of the SQL
master database. This is concerns me. Is there any reason that client
software should have full access to the SQL master database? We have many
other production databases in use on this server. I'm considering
installing a separate instance of SQL 2005 (their newest version uses SQL
2005, the version we're using now uses SQL 2000) so that they can have full
ownership access of the master database without having to worry about this
affecting other existing databases. Thanks for any advice.
RyanHi,
No need to have DBO role in Master database. Just verify the sp_who
contineously for some time and confirm the
application user connects to Master database (You could also use profiler).
Once you confirmed revove the dbo role for the application user from Master
database and see what happends.
If it is production I recommend you to do during a offtime during
weekends...
Thanks
Hari
SQL Server MVP
"Ryan" <Tyveil@.newsgroups.nospam> wrote in message
news:Obzny9huGHA.5044@.TK2MSFTNGP05.phx.gbl...
> We have some client software developed by 3rd party that is used
> internally and requires use of our SQL server. We've had some problems
> with this software in the past and the developers solution was to add the
> dbclient login (used by the client software) to the dbo (owner) group of
> the SQL master database. This is concerns me. Is there any reason that
> client software should have full access to the SQL master database? We
> have many other production databases in use on this server. I'm
> considering installing a separate instance of SQL 2005 (their newest
> version uses SQL 2005, the version we're using now uses SQL 2000) so that
> they can have full ownership access of the master database without having
> to worry about this affecting other existing databases. Thanks for any
> advice.
> Ryan
>|||> This is concerns me.
That seems like an unreasonable response on the part of a DBA.
Concerned is far too mild. I think terrified would be reasonable.
This sounds like a quick fix that avoided having to actually figure
out what the real problem is. It is not something that I would allow
even on a development server, and on production any auditor (if they
knew the first thing about SQL Server) would have a field day.
Perhaps if someone does the analysis to identify the actual
requirement a more reasonable solution can be found. Otherwise I
would say that running on a separate instance is probably the only
answer.
Roy Harvey
Beacon Falls, CT
On Mon, 7 Aug 2006 07:43:38 -0500, "Ryan" <Tyveil@.newsgroups.nospam>
wrote:
>We have some client software developed by 3rd party that is used internally
>and requires use of our SQL server. We've had some problems with this
>software in the past and the developers solution was to add the dbclient
>login (used by the client software) to the dbo (owner) group of the SQL
>master database. This is concerns me. Is there any reason that client
>software should have full access to the SQL master database? We have many
>other production databases in use on this server. I'm considering
>installing a separate instance of SQL 2005 (their newest version uses SQL
>2005, the version we're using now uses SQL 2000) so that they can have full
>ownership access of the master database without having to worry about this
>affecting other existing databases. Thanks for any advice.
>Ryan
>|||Roy Harvey wrote:
>> This is concerns me.
> That seems like an unreasonable response on the part of a DBA.
> Concerned is far too mild. I think terrified would be reasonable.
> This sounds like a quick fix that avoided having to actually figure
> out what the real problem is. It is not something that I would allow
> even on a development server, and on production any auditor (if they
> knew the first thing about SQL Server) would have a field day.
> Perhaps if someone does the analysis to identify the actual
> requirement a more reasonable solution can be found. Otherwise I
> would say that running on a separate instance is probably the only
> answer.
When in doubt, make everybody an admin, right? ;-)
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Db-library network communications layer not loaded

I have an application that needs to to talk to MS SQL Server 2000.
When I connect from a client machine, I am getting db-library network
communications layer not loaded.
What component is it missing?
--
Cathy BIs the file Ntwdblib.dll in the system32 directory?
Ntwdblib is used for db-lib communications usually found in
older applications. It's not installed with MDAC.
-Sue
On Fri, 28 Jul 2006 07:43:02 -0700, Cathy Boehm
<CathyBoehm@.discussions.microsoft.com> wrote:

>I have an application that needs to to talk to MS SQL Server 2000.
>When I connect from a client machine, I am getting db-library network
>communications layer not loaded.
>What component is it missing?