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.
Showing posts with label couple. Show all posts
Showing posts with label couple. Show all posts
Sunday, March 25, 2012
Saturday, February 25, 2012
DBs not appearing in query analyer dropdown
A couple of databases on one of our SQL Servers is missing in the db
dropdown in query analyzer.
dropdown in query analyzer.
Does anyone know what I need to update to sync this with the actual
databases?
Thanks,
BurtThe user you are logged in with does not have access to those
databases. There is no "syncing" necessary.
Friday, February 24, 2012
DBPROCESS is dead or not enabled
We started getting this error a couple of weeks ago:
"Database error code: 10005
Database error message: DBPROCESS is dead or not enabled."
No changes were made prior to receiving this error. So far we have replaced
the network interface card and applied the latest SQL and Windows Server
service packs, but we're still getting this error.
Any ideas?
Jim
Hi
What version of SQL, Windows and SP's?
What does the SQL Server error log show?
That error is generally a DBlib error so speak to the vendor of your
product. DBLib is a very old way of accessing a database server.
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/
"KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> We started getting this error a couple of weeks ago:
> "Database error code: 10005
> Database error message: DBPROCESS is dead or not enabled."
> No changes were made prior to receiving this error. So far we have
> replaced
> the network interface card and applied the latest SQL and Windows Server
> service packs, but we're still getting this error.
> Any ideas?
> Jim
|||SQL 2000 SP4
Windows 2003 Server Enterprise SP1
SQL Server error log shows no errors as well as the Windows Event Viewer.
What can I do to change the DBlib connection? We are the vendors of the
application.
What are the alternatives.
Thanks,
Jim
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What version of SQL, Windows and SP's?
> What does the SQL Server error log show?
> That error is generally a DBlib error so speak to the vendor of your
> product. DBLib is a very old way of accessing a database server.
> 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/
> "KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
> message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
>
>
"Database error code: 10005
Database error message: DBPROCESS is dead or not enabled."
No changes were made prior to receiving this error. So far we have replaced
the network interface card and applied the latest SQL and Windows Server
service packs, but we're still getting this error.
Any ideas?
Jim
Hi
What version of SQL, Windows and SP's?
What does the SQL Server error log show?
That error is generally a DBlib error so speak to the vendor of your
product. DBLib is a very old way of accessing a database server.
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/
"KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> We started getting this error a couple of weeks ago:
> "Database error code: 10005
> Database error message: DBPROCESS is dead or not enabled."
> No changes were made prior to receiving this error. So far we have
> replaced
> the network interface card and applied the latest SQL and Windows Server
> service packs, but we're still getting this error.
> Any ideas?
> Jim
|||SQL 2000 SP4
Windows 2003 Server Enterprise SP1
SQL Server error log shows no errors as well as the Windows Event Viewer.
What can I do to change the DBlib connection? We are the vendors of the
application.
What are the alternatives.
Thanks,
Jim
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What version of SQL, Windows and SP's?
> What does the SQL Server error log show?
> That error is generally a DBlib error so speak to the vendor of your
> product. DBLib is a very old way of accessing a database server.
> 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/
> "KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
> message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
>
>
DBPROCESS is dead or not enabled
We started getting this error a couple of weeks ago:
"Database error code: 10005
Database error message: DBPROCESS is dead or not enabled."
No changes were made prior to receiving this error. So far we have replaced
the network interface card and applied the latest SQL and Windows Server
service packs, but we're still getting this error.
Any ideas?
JimHi
What version of SQL, Windows and SP's?
What does the SQL Server error log show?
That error is generally a DBlib error so speak to the vendor of your
product. DBLib is a very old way of accessing a database server.
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/
"KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> We started getting this error a couple of weeks ago:
> "Database error code: 10005
> Database error message: DBPROCESS is dead or not enabled."
> No changes were made prior to receiving this error. So far we have
> replaced
> the network interface card and applied the latest SQL and Windows Server
> service packs, but we're still getting this error.
> Any ideas?
> Jim|||SQL 2000 SP4
Windows 2003 Server Enterprise SP1
SQL Server error log shows no errors as well as the Windows Event Viewer.
What can I do to change the DBlib connection? We are the vendors of the
application.
What are the alternatives.
Thanks,
Jim
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What version of SQL, Windows and SP's?
> What does the SQL Server error log show?
> That error is generally a DBlib error so speak to the vendor of your
> product. DBLib is a very old way of accessing a database server.
> 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/
> "KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
> message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> > We started getting this error a couple of weeks ago:
> > "Database error code: 10005
> > Database error message: DBPROCESS is dead or not enabled."
> > No changes were made prior to receiving this error. So far we have
> > replaced
> > the network interface card and applied the latest SQL and Windows Server
> > service packs, but we're still getting this error.
> >
> > Any ideas?
> >
> > Jim
>
>
"Database error code: 10005
Database error message: DBPROCESS is dead or not enabled."
No changes were made prior to receiving this error. So far we have replaced
the network interface card and applied the latest SQL and Windows Server
service packs, but we're still getting this error.
Any ideas?
JimHi
What version of SQL, Windows and SP's?
What does the SQL Server error log show?
That error is generally a DBlib error so speak to the vendor of your
product. DBLib is a very old way of accessing a database server.
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/
"KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> We started getting this error a couple of weeks ago:
> "Database error code: 10005
> Database error message: DBPROCESS is dead or not enabled."
> No changes were made prior to receiving this error. So far we have
> replaced
> the network interface card and applied the latest SQL and Windows Server
> service packs, but we're still getting this error.
> Any ideas?
> Jim|||SQL 2000 SP4
Windows 2003 Server Enterprise SP1
SQL Server error log shows no errors as well as the Windows Event Viewer.
What can I do to change the DBlib connection? We are the vendors of the
application.
What are the alternatives.
Thanks,
Jim
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What version of SQL, Windows and SP's?
> What does the SQL Server error log show?
> That error is generally a DBlib error so speak to the vendor of your
> product. DBLib is a very old way of accessing a database server.
> 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/
> "KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
> message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> > We started getting this error a couple of weeks ago:
> > "Database error code: 10005
> > Database error message: DBPROCESS is dead or not enabled."
> > No changes were made prior to receiving this error. So far we have
> > replaced
> > the network interface card and applied the latest SQL and Windows Server
> > service packs, but we're still getting this error.
> >
> > Any ideas?
> >
> > Jim
>
>
DBPROCESS is dead or not enabled
We started getting this error a couple of weeks ago:
"Database error code: 10005
Database error message: DBPROCESS is dead or not enabled."
No changes were made prior to receiving this error. So far we have replaced
the network interface card and applied the latest SQL and Windows Server
service packs, but we're still getting this error.
Any ideas?
JimSQL 2000 SP4
Windows 2003 Server Enterprise SP1
SQL Server error log shows no errors as well as the Windows Event Viewer.
What can I do to change the DBlib connection? We are the vendors of the
application.
What are the alternatives.
Thanks,
Jim
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What version of SQL, Windows and SP's?
> What does the SQL Server error log show?
> That error is generally a DBlib error so speak to the vendor of your
> product. DBLib is a very old way of accessing a database server.
> 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/
> "KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
> message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
>
>|||Hi
What version of SQL, Windows and SP's?
What does the SQL Server error log show?
That error is generally a DBlib error so speak to the vendor of your
product. DBLib is a very old way of accessing a database server.
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/
"KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> We started getting this error a couple of weeks ago:
> "Database error code: 10005
> Database error message: DBPROCESS is dead or not enabled."
> No changes were made prior to receiving this error. So far we have
> replaced
> the network interface card and applied the latest SQL and Windows Server
> service packs, but we're still getting this error.
> Any ideas?
> Jim
"Database error code: 10005
Database error message: DBPROCESS is dead or not enabled."
No changes were made prior to receiving this error. So far we have replaced
the network interface card and applied the latest SQL and Windows Server
service packs, but we're still getting this error.
Any ideas?
JimSQL 2000 SP4
Windows 2003 Server Enterprise SP1
SQL Server error log shows no errors as well as the Windows Event Viewer.
What can I do to change the DBlib connection? We are the vendors of the
application.
What are the alternatives.
Thanks,
Jim
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What version of SQL, Windows and SP's?
> What does the SQL Server error log show?
> That error is generally a DBlib error so speak to the vendor of your
> product. DBLib is a very old way of accessing a database server.
> 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/
> "KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
> message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
>
>|||Hi
What version of SQL, Windows and SP's?
What does the SQL Server error log show?
That error is generally a DBlib error so speak to the vendor of your
product. DBLib is a very old way of accessing a database server.
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/
"KAI Network Admin" <KAINetworkAdmin@.discussions.microsoft.com> wrote in
message news:63761100-A438-4B80-9DCF-A7D1DD7B931D@.microsoft.com...
> We started getting this error a couple of weeks ago:
> "Database error code: 10005
> Database error message: DBPROCESS is dead or not enabled."
> No changes were made prior to receiving this error. So far we have
> replaced
> the network interface card and applied the latest SQL and Windows Server
> service packs, but we're still getting this error.
> Any ideas?
> Jim
Subscribe to:
Comments (Atom)