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
Showing posts with label dbprocess. Show all posts
Showing posts with label dbprocess. Show all posts
Friday, February 24, 2012
DBPROCESS is dead or not enabled
why the error message "DBPROCESS is dead or not enabled" appear frequently , but when i run the application again ,it can connect to the server.
What can i do to solve the problem?
SERVER 2000 enterprise edition (not sp4)
Hi,
this is a very generic one, indicating mainly that the communication between the server and the client failed, due to problems like a lost connection, problems in the used protocol, timeouts, or simply a SQL Server error which should be protocolled in the SQL Server log and/or event log (depending on the severity). In addition make sure that you enabled remote connections for named Pipes / TCP.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
But is there any problems, when i update the sql server to sq4, will the problem be resolve?
Is this sql server's bug or the network problems or client application's problem.
Anyone can help?|||Anybody has the same problem with me?|||
J'ai exactement le même problème au bout d'un certain temps d'inactivit. Je cherche à le rsoudre. J'ai ce problème depuis que je suis pass à SQL Server 2005. J'accède à SQL Server par l'intermdiaire d'un accès natif dans mes applications Windev. A bient?t avec la solution, j'espère
|||also check whether the Auto close property of the database is on ... if it is on .. set it OFF and try
select DATABASEPROPERTY ('somedatabase' , 'isAutoClose' ) run this statement and if it returns 1 set this property off and see
Madhu
|||Je rencontre galement ce problème seulement sur un ordinateur client parmi une dizaine sous Windev en accs natif ( l'ancien ) : j'attends le nouveau avec impatience mais si quelqu'un a une solution ?.
Idem : somedy has solved this problem ?
DBPROCESS is dead or not enabled
why the error message "DBPROCESS is dead or not enabled" appear frequently , but when i run the application again ,it can connect to the server.
What can i do to solve the problem?
SERVER 2000 enterprise edition (not sp4)
Hi,
this is a very generic one, indicating mainly that the communication between the server and the client failed, due to problems like a lost connection, problems in the used protocol, timeouts, or simply a SQL Server error which should be protocolled in the SQL Server log and/or event log (depending on the severity). In addition make sure that you enabled remote connections for named Pipes / TCP.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
But is there any problems, when i update the sql server to sq4, will the problem be resolve?
Is this sql server's bug or the network problems or client application's problem.
Anyone can help?|||Anybody has the same problem with me?|||
J'ai exactement le même problème au bout d'un certain temps d'inactivit. Je cherche à le rsoudre. J'ai ce problème depuis que je suis pass à SQL Server 2005. J'accède à SQL Server par l'intermdiaire d'un accès natif dans mes applications Windev. A bient?t avec la solution, j'espère
|||also check whether the Auto close property of the database is on ... if it is on .. set it OFF and try
select DATABASEPROPERTY ('somedatabase' , 'isAutoClose' ) run this statement and if it returns 1 set this property off and see
Madhu
|||Je rencontre galement ce problème seulement sur un ordinateur client parmi une dizaine sous Windev en accs natif ( l'ancien ) : j'attends le nouveau avec impatience mais si quelqu'un a une solution ?.
Idem : somedy has solved this problem ?
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
why the error message "DBPROCESS is dead or not enabled" appear frequently , but when i run the application again ,it can connect to the server.
What can i do to solve the problem?
SERVER 2000 enterprise edition (not sp4)
Hi,
this is a very generic one, indicating mainly that the communication between the server and the client failed, due to problems like a lost connection, problems in the used protocol, timeouts, or simply a SQL Server error which should be protocolled in the SQL Server log and/or event log (depending on the severity). In addition make sure that you enabled remote connections for named Pipes / TCP.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
But is there any problems, when i update the sql server to sq4, will the problem be resolve?
Is this sql server's bug or the network problems or client application's problem.
Anyone can help?|||Anybody has the same problem with me?|||
J'ai exactement le même problème au bout d'un certain temps d'inactivit. Je cherche à le rsoudre. J'ai ce problème depuis que je suis pass à SQL Server 2005. J'accède à SQL Server par l'intermdiaire d'un accès natif dans mes applications Windev. A bient?t avec la solution, j'espère
|||also check whether the Auto close property of the database is on ... if it is on .. set it OFF and try
select DATABASEPROPERTY ('somedatabase' , 'isAutoClose' ) run this statement and if it returns 1 set this property off and see
Madhu
|||Je rencontre galement ce problème seulement sur un ordinateur client parmi une dizaine sous Windev en accs natif ( l'ancien ) : j'attends le nouveau avec impatience mais si quelqu'un a une solution ?.
Idem : somedy has solved this problem ?
DBPROCESS is dead or not enabled
why the error message "DBPROCESS is dead or not enabled" appear frequently , but when i run the application again ,it can connect to the server.
What can i do to solve the problem?
SERVER 2000 enterprise edition (not sp4)
Hi,
this is a very generic one, indicating mainly that the communication between the server and the client failed, due to problems like a lost connection, problems in the used protocol, timeouts, or simply a SQL Server error which should be protocolled in the SQL Server log and/or event log (depending on the severity). In addition make sure that you enabled remote connections for named Pipes / TCP.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
But is there any problems, when i update the sql server to sq4, will the problem be resolve?
Is this sql server's bug or the network problems or client application's problem.
Anyone can help?|||Anybody has the same problem with me?|||
J'ai exactement le même problème au bout d'un certain temps d'inactivit. Je cherche à le rsoudre. J'ai ce problème depuis que je suis pass à SQL Server 2005. J'accède à SQL Server par l'intermdiaire d'un accès natif dans mes applications Windev. A bient?t avec la solution, j'espère
|||also check whether the Auto close property of the database is on ... if it is on .. set it OFF and try
select DATABASEPROPERTY ('somedatabase' , 'isAutoClose' ) run this statement and if it returns 1 set this property off and see
Madhu
|||Je rencontre galement ce problème seulement sur un ordinateur client parmi une dizaine sous Windev en accs natif ( l'ancien ) : j'attends le nouveau avec impatience mais si quelqu'un a une solution ?.
Idem : somedy has solved this problem ?
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
DBPROCESS is dead - still
I have posted recently regarding one workstation that
receives the error message:
DBPROCESS is dead or not enabled. A database error has
occurred.
Database error code 10025.
Database error message: Select error: Possible network
error: Write to server failed. General network error.
Check your documentation.
This error isn't happening on any other workstations
running the same application. I have even moved the pc to
the same location where it's running successfully and it
still receives the same message. I have reinstalled the
client application and have re-installed Connectivity
only as the application uses DB-Library. Still the same
error. Anyone have any other ways of troubleshooting this
problem, or possible resolution?
Thanks,
HillaireHave you tried the dbsetavail command ?
J
>--Original Message--
>I have posted recently regarding one workstation that
>receives the error message:
>DBPROCESS is dead or not enabled. A database error has
>occurred.
>Database error code 10025.
>Database error message: Select error: Possible network
>error: Write to server failed. General network error.
>Check your documentation.
>This error isn't happening on any other workstations
>running the same application. I have even moved the pc to
>the same location where it's running successfully and it
>still receives the same message. I have reinstalled the
>client application and have re-installed Connectivity
>only as the application uses DB-Library. Still the same
>error. Anyone have any other ways of troubleshooting this
>problem, or possible resolution?
>Thanks,
>Hillaire
>.
>|||No I haven't. I'm wondering why would I need to, as the
application works correctly on all other pc's. Any idea
how it would solve the problem?
Thanks!!!
>--Original Message--
>Have you tried the dbsetavail command ?
>J
>>--Original Message--
>>I have posted recently regarding one workstation that
>>receives the error message:
>>DBPROCESS is dead or not enabled. A database error has
>>occurred.
>>Database error code 10025.
>>Database error message: Select error: Possible network
>>error: Write to server failed. General network error.
>>Check your documentation.
>>This error isn't happening on any other workstations
>>running the same application. I have even moved the pc
to
>>the same location where it's running successfully and
it
>>still receives the same message. I have reinstalled the
>>client application and have re-installed Connectivity
>>only as the application uses DB-Library. Still the same
>>error. Anyone have any other ways of troubleshooting
this
>>problem, or possible resolution?
>>Thanks,
>>Hillaire
>>.
>.
>|||To be perfectly honest, I have no idea why it would fail
on one but work on others.
The only thing I can think of is there is something on
that particular machine thats disabling it, i.e firewalls
and the like.
J
>--Original Message--
>No I haven't. I'm wondering why would I need to, as the
>application works correctly on all other pc's. Any idea
>how it would solve the problem?
>Thanks!!!
>>--Original Message--
>>Have you tried the dbsetavail command ?
>>J
>>--Original Message--
>>I have posted recently regarding one workstation that
>>receives the error message:
>>DBPROCESS is dead or not enabled. A database error has
>>occurred.
>>Database error code 10025.
>>Database error message: Select error: Possible network
>>error: Write to server failed. General network error.
>>Check your documentation.
>>This error isn't happening on any other workstations
>>running the same application. I have even moved the pc
>to
>>the same location where it's running successfully and
>it
>>still receives the same message. I have reinstalled the
>>client application and have re-installed Connectivity
>>only as the application uses DB-Library. Still the same
>>error. Anyone have any other ways of troubleshooting
>this
>>problem, or possible resolution?
>>Thanks,
>>Hillaire
>>.
>>.
>.
>
receives the error message:
DBPROCESS is dead or not enabled. A database error has
occurred.
Database error code 10025.
Database error message: Select error: Possible network
error: Write to server failed. General network error.
Check your documentation.
This error isn't happening on any other workstations
running the same application. I have even moved the pc to
the same location where it's running successfully and it
still receives the same message. I have reinstalled the
client application and have re-installed Connectivity
only as the application uses DB-Library. Still the same
error. Anyone have any other ways of troubleshooting this
problem, or possible resolution?
Thanks,
HillaireHave you tried the dbsetavail command ?
J
>--Original Message--
>I have posted recently regarding one workstation that
>receives the error message:
>DBPROCESS is dead or not enabled. A database error has
>occurred.
>Database error code 10025.
>Database error message: Select error: Possible network
>error: Write to server failed. General network error.
>Check your documentation.
>This error isn't happening on any other workstations
>running the same application. I have even moved the pc to
>the same location where it's running successfully and it
>still receives the same message. I have reinstalled the
>client application and have re-installed Connectivity
>only as the application uses DB-Library. Still the same
>error. Anyone have any other ways of troubleshooting this
>problem, or possible resolution?
>Thanks,
>Hillaire
>.
>|||No I haven't. I'm wondering why would I need to, as the
application works correctly on all other pc's. Any idea
how it would solve the problem?
Thanks!!!
>--Original Message--
>Have you tried the dbsetavail command ?
>J
>>--Original Message--
>>I have posted recently regarding one workstation that
>>receives the error message:
>>DBPROCESS is dead or not enabled. A database error has
>>occurred.
>>Database error code 10025.
>>Database error message: Select error: Possible network
>>error: Write to server failed. General network error.
>>Check your documentation.
>>This error isn't happening on any other workstations
>>running the same application. I have even moved the pc
to
>>the same location where it's running successfully and
it
>>still receives the same message. I have reinstalled the
>>client application and have re-installed Connectivity
>>only as the application uses DB-Library. Still the same
>>error. Anyone have any other ways of troubleshooting
this
>>problem, or possible resolution?
>>Thanks,
>>Hillaire
>>.
>.
>|||To be perfectly honest, I have no idea why it would fail
on one but work on others.
The only thing I can think of is there is something on
that particular machine thats disabling it, i.e firewalls
and the like.
J
>--Original Message--
>No I haven't. I'm wondering why would I need to, as the
>application works correctly on all other pc's. Any idea
>how it would solve the problem?
>Thanks!!!
>>--Original Message--
>>Have you tried the dbsetavail command ?
>>J
>>--Original Message--
>>I have posted recently regarding one workstation that
>>receives the error message:
>>DBPROCESS is dead or not enabled. A database error has
>>occurred.
>>Database error code 10025.
>>Database error message: Select error: Possible network
>>error: Write to server failed. General network error.
>>Check your documentation.
>>This error isn't happening on any other workstations
>>running the same application. I have even moved the pc
>to
>>the same location where it's running successfully and
>it
>>still receives the same message. I have reinstalled the
>>client application and have re-installed Connectivity
>>only as the application uses DB-Library. Still the same
>>error. Anyone have any other ways of troubleshooting
>this
>>problem, or possible resolution?
>>Thanks,
>>Hillaire
>>.
>>.
>.
>
DBPROCESS is dead
I have a user that is losing his database connection
after about 6 minutes or so with error:
Database error code: 10025
Database error message: Select error: Possible network
error: Write to SQL server failed. General network error.
The same user access another application on the same
server, different database, with no problems and the same
application used by another user who is having no
problems.
Any ideas what could be going on?
Thanks,
Angelina
Hi,
Execute the SQL Profiler for that user (set the filter) and
check what is happening.
This can be because of slow network as well (in his PC ).
Thanks
Hari
MCDBA
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on?
> Thanks,
> Angelina
|||Could be a firewall or VPN setting that automatically closes the connection
when it is idle. 300 seconds is a common default setting. I know that is
five minutes, but 1 minute of activity and 5 minutes of inactivity = 1 dead
connection.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on?
> Thanks,
> Angelina
after about 6 minutes or so with error:
Database error code: 10025
Database error message: Select error: Possible network
error: Write to SQL server failed. General network error.
The same user access another application on the same
server, different database, with no problems and the same
application used by another user who is having no
problems.
Any ideas what could be going on?
Thanks,
Angelina
Hi,
Execute the SQL Profiler for that user (set the filter) and
check what is happening.
This can be because of slow network as well (in his PC ).
Thanks
Hari
MCDBA
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on?
> Thanks,
> Angelina
|||Could be a firewall or VPN setting that automatically closes the connection
when it is idle. 300 seconds is a common default setting. I know that is
five minutes, but 1 minute of activity and 5 minutes of inactivity = 1 dead
connection.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on?
> Thanks,
> Angelina
DBPROCESS is dead
I have a user that is losing his database connection
after about 6 minutes or so with error:
Database error code: 10025
Database error message: Select error: Possible network
error: Write to SQL server failed. General network error.
The same user access another application on the same
server, different database, with no problems and the same
application used by another user who is having no
problems.
Any ideas what could be going on'
Thanks,
AngelinaHi,
Execute the SQL Profiler for that user (set the filter) and
check what is happening.
This can be because of slow network as well (in his PC ).
Thanks
Hari
MCDBA
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina|||Could be a firewall or VPN setting that automatically closes the connection
when it is idle. 300 seconds is a common default setting. I know that is
five minutes, but 1 minute of activity and 5 minutes of inactivity = 1 dead
connection.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina
after about 6 minutes or so with error:
Database error code: 10025
Database error message: Select error: Possible network
error: Write to SQL server failed. General network error.
The same user access another application on the same
server, different database, with no problems and the same
application used by another user who is having no
problems.
Any ideas what could be going on'
Thanks,
AngelinaHi,
Execute the SQL Profiler for that user (set the filter) and
check what is happening.
This can be because of slow network as well (in his PC ).
Thanks
Hari
MCDBA
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina|||Could be a firewall or VPN setting that automatically closes the connection
when it is idle. 300 seconds is a common default setting. I know that is
five minutes, but 1 minute of activity and 5 minutes of inactivity = 1 dead
connection.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina
DBPROCESS is dead
I have a user that is losing his database connection
after about 6 minutes or so with error:
Database error code: 10025
Database error message: Select error: Possible network
error: Write to SQL server failed. General network error.
The same user access another application on the same
server, different database, with no problems and the same
application used by another user who is having no
problems.
Any ideas what could be going on'
Thanks,
AngelinaHi,
Execute the SQL Profiler for that user (set the filter) and
check what is happening.
This can be because of slow network as well (in his PC ).
Thanks
Hari
MCDBA
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx
.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina|||Could be a firewall or VPN setting that automatically closes the connection
when it is idle. 300 seconds is a common default setting. I know that is
five minutes, but 1 minute of activity and 5 minutes of inactivity = 1 dead
connection.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx
.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina
after about 6 minutes or so with error:
Database error code: 10025
Database error message: Select error: Possible network
error: Write to SQL server failed. General network error.
The same user access another application on the same
server, different database, with no problems and the same
application used by another user who is having no
problems.
Any ideas what could be going on'
Thanks,
AngelinaHi,
Execute the SQL Profiler for that user (set the filter) and
check what is happening.
This can be because of slow network as well (in his PC ).
Thanks
Hari
MCDBA
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx
.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina|||Could be a firewall or VPN setting that automatically closes the connection
when it is idle. 300 seconds is a common default setting. I know that is
five minutes, but 1 minute of activity and 5 minutes of inactivity = 1 dead
connection.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Angelina" <anonymous@.discussions.microsoft.com> wrote in message
news:16d5701c448ab$4f0ee440$a601280a@.phx
.gbl...
> I have a user that is losing his database connection
> after about 6 minutes or so with error:
> Database error code: 10025
> Database error message: Select error: Possible network
> error: Write to SQL server failed. General network error.
> The same user access another application on the same
> server, different database, with no problems and the same
> application used by another user who is having no
> problems.
> Any ideas what could be going on'
> Thanks,
> Angelina
Subscribe to:
Comments (Atom)