DB PROCESS IS DEAD

Dear Friends,

Please help me in below unexpected error.

Server Details:

HP Proliant DL385 G1, 142*6 GB

AMD Opteron ? Processor 280, 2.40 GHz

4.00 GB RAM, DVD ROM

Win2K3 R2, SP1 64bit

SQL Server Details:

SQL Server 2000 Enterprise Edition 32bit

Service Pack4

Network Details:

Clients can access the server by Terminal Server and also by Direct Connectivity.

The connectivity is provided by RF network Provider.

Application Details:

Application was designed by Power Builder 6.5.

Error Details:

If I divide my clients connectivity to the server then it is divided into 3 types

TYPE A >> Users inside my LAN using a DNS server they give the server name in their Parameter file to connect to the Database Server.

TYPE B >> Users who are in WAN connect to the server by Terminal Servers for Data Input.

Terminal Servers are inside my LAN.

TYPE C >> Users who are in WAN connect to the Server by Direct Connection for Reports and Print Out they give the IP address of the Database server directly in their Parameter files.

After every 6 to 7 days the ERROR DB Processes Dead comes to the TYPE C.

The error Numbers are 100025 and 100005.

At the same time TYPE A AND TYPE B are not getting any errors.

For further diagnosis I have taken a client machine to Net Meeting and taken his desktop in control. I have connected the client machine to the database server by ISQL in command prompt.

From Backend I can see that the SQL server has allocated a SPID to the client machine. After I have executed

1>SELECT * FROM SYSDATABASES

2>GO

It will return me all data but it will not show me how many rows selected or EOF.

After some time it will give me the prompt (3>) but without EOF and after that if I give another query then it will give the below error

DB-Library: Attempt to initiate a new SQL Server Operation with results pending.

DB-Library: Unexpected EOF from SQL Server. General Network Error. Check Your Documentation.

Net-Library error 10054: ConnectionCheckForData(CheckForData())

DB-Library: DBPROCESSES is dead or not enabled.

DB-Library: DBPROCESSES is dead or not enabled.

DB-Library: DBPROCESSES is dead or not enabled.

DB-Library: DBPROCESSES is dead or not enabled.

At the same time if I give IP address of another server then it works and TYPE A and TYPE B don’t get any problem.

To stop this error I have to restart the server after that for again seven days it works and again the same problem.

I cant find anything I have checked tempdb, cache size but it is normal no abnormal activities.

No virus Issues.

Please advice.

Regards,

James

You might want to try posting this in the "SQL Server Data Access" forum which deals with network issues.

One consideration is that your output indicates DB-Library which has been obsoleted in newer versions of SQL. You might consider using an ODBC or OLEDB client to see if you get the same result.

|||

Hello Guys the solution of the above problem is Installing the latest Service Pack 8.0.2187.

My problem is solved.... Till Now I couldn't findout what was the problem.

Thanks to ALL,

James

DB Maintenance & Single-User Mode

SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
quad-Xeon 2.2 GHz with 4 GB of RAM.
The SQL Server instance has 4 non-system databases, including the SharePoint
Services content database. We've been running, at 2:00 AM, weekly complete
backups and nightly transaction log backups--with integrity checks and
optimizations.
Every morning, we find that only the SharePoint database has been set to
"Single User" restricted access. Every time, the log shows:
"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
found 0 errors and repaired 0 errors."
The links below point to related information. This appears to have been a
bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
Thanks,
Jim
"FIX: SQLMaint.exe Sets Database Status Incorrectly"
http://support.microsoft.com/default...b;EN-US;276234
"a problem about repair damaged database and single user mode"
http://groups.google.com/groups?q=sq...t.c om&rnum=5
Yes but it's not necessarily a good idea to use that option
and you'd probably want to clear the Attempt to repair any
minor problems check box in the maintenance plan.
If you get DBCC errors, you'd want to manually intervene and
do some type of root cause analysis. Then proceed with
whatever action from there.
-Sue
On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
<jmoon()at()uab.edu> wrote:

>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>quad-Xeon 2.2 GHz with 4 GB of RAM.
>The SQL Server instance has 4 non-system databases, including the SharePoint
>Services content database. We've been running, at 2:00 AM, weekly complete
>backups and nightly transaction log backups--with integrity checks and
>optimizations.
>Every morning, we find that only the SharePoint database has been set to
>"Single User" restricted access. Every time, the log shows:
>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
>found 0 errors and repaired 0 errors."
>The links below point to related information. This appears to have been a
>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>Thanks,
>Jim
>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>http://support.microsoft.com/default...b;EN-US;276234
>
>"a problem about repair damaged database and single user mode"
>http://groups.google.com/groups?q=sq...t.c om&rnum=5
>
|||Thank you, Sue.
Jim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8gq7j0pemr387cd2csrsainr9v11a0npf6@.4ax.com...
> Yes but it's not necessarily a good idea to use that option
> and you'd probably want to clear the Attempt to repair any
> minor problems check box in the maintenance plan.
> If you get DBCC errors, you'd want to manually intervene and
> do some type of root cause analysis. Then proceed with
> whatever action from there.
> -Sue
> On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
> <jmoon()at()uab.edu> wrote:
>

DB Maintenance & Single-User Mode

SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
quad-Xeon 2.2 GHz with 4 GB of RAM.
The SQL Server instance has 4 non-system databases, including the SharePoint
Services content database. We've been running, at 2:00 AM, weekly complete
backups and nightly transaction log backups--with integrity checks and
optimizations.
Every morning, we find that only the SharePoint database has been set to
"Single User" restricted access. Every time, the log shows:
"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
found 0 errors and repaired 0 errors."
The links below point to related information. This appears to have been a
bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
Thanks,
Jim
"FIX: SQLMaint.exe Sets Database Status Incorrectly"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;276234
"a problem about repair damaged database and single user mode"
http://groups.google.com/groups?q=sql+server+dbcc+checkdb+single+user+mode&hl=en&lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5Yes but it's not necessarily a good idea to use that option
and you'd probably want to clear the Attempt to repair any
minor problems check box in the maintenance plan.
If you get DBCC errors, you'd want to manually intervene and
do some type of root cause analysis. Then proceed with
whatever action from there.
-Sue
On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
<jmoon()at()uab.edu> wrote:
>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>quad-Xeon 2.2 GHz with 4 GB of RAM.
>The SQL Server instance has 4 non-system databases, including the SharePoint
>Services content database. We've been running, at 2:00 AM, weekly complete
>backups and nightly transaction log backups--with integrity checks and
>optimizations.
>Every morning, we find that only the SharePoint database has been set to
>"Single User" restricted access. Every time, the log shows:
>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
>found 0 errors and repaired 0 errors."
>The links below point to related information. This appears to have been a
>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>Thanks,
>Jim
>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>http://support.microsoft.com/default.aspx?scid=kb;EN-US;276234
>
>"a problem about repair damaged database and single user mode"
>http://groups.google.com/groups?q=sql+server+dbcc+checkdb+single+user+mode&hl=en&lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5
>|||Thank you, Sue.
Jim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8gq7j0pemr387cd2csrsainr9v11a0npf6@.4ax.com...
> Yes but it's not necessarily a good idea to use that option
> and you'd probably want to clear the Attempt to repair any
> minor problems check box in the maintenance plan.
> If you get DBCC errors, you'd want to manually intervene and
> do some type of root cause analysis. Then proceed with
> whatever action from there.
> -Sue
> On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
> <jmoon()at()uab.edu> wrote:
>>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>>quad-Xeon 2.2 GHz with 4 GB of RAM.
>>The SQL Server instance has 4 non-system databases, including the
>>SharePoint
>>Services content database. We've been running, at 2:00 AM, weekly
>>complete
>>backups and nightly transaction log backups--with integrity checks and
>>optimizations.
>>Every morning, we find that only the SharePoint database has been set to
>>"Single User" restricted access. Every time, the log shows:
>>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT
>>AUTHORITY\SYSTEM
>>found 0 errors and repaired 0 errors."
>>The links below point to related information. This appears to have been a
>>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>>Thanks,
>>Jim
>>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>>http://support.microsoft.com/default.aspx?scid=kb;EN-US;276234
>>
>>"a problem about repair damaged database and single user mode"
>>http://groups.google.com/groups?q=sql+server+dbcc+checkdb+single+user+mode&hl=en&lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5
>

DB Maintenance & Single-User Mode

SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
quad-Xeon 2.2 GHz with 4 GB of RAM.
The SQL Server instance has 4 non-system databases, including the SharePoint
Services content database. We've been running, at 2:00 AM, weekly complete
backups and nightly transaction log backups--with integrity checks and
optimizations.
Every morning, we find that only the SharePoint database has been set to
"Single User" restricted access. Every time, the log shows:
"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
found 0 errors and repaired 0 errors."
The links below point to related information. This appears to have been a
bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
Thanks,
Jim
"FIX: SQLMaint.exe Sets Database Status Incorrectly"
http://support.microsoft.com/defaul...kb;EN-US;276234
"a problem about repair damaged database and single user mode"
de&hl=en&l
r=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5" target="_blank">http://groups.google.com/groups? q=...soft.com&rnum=5Yes but it's not necessarily a good idea to use that option
and you'd probably want to clear the Attempt to repair any
minor problems check box in the maintenance plan.
If you get DBCC errors, you'd want to manually intervene and
do some type of root cause analysis. Then proceed with
whatever action from there.
-Sue
On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
<jmoon()at()uab.edu> wrote:

>SQL Server 2000 SP3 running on Windows Server 2003. The machine is a
>quad-Xeon 2.2 GHz with 4 GB of RAM.
>The SQL Server instance has 4 non-system databases, including the SharePoin
t
>Services content database. We've been running, at 2:00 AM, weekly complet
e
>backups and nightly transaction log backups--with integrity checks and
>optimizations.
>Every morning, we find that only the SharePoint database has been set to
>"Single User" restricted access. Every time, the log shows:
>"DBCC CHECKDB (STS_1182080930, repair_fast) executed by NT AUTHORITY\SYSTEM
>found 0 errors and repaired 0 errors."
>The links below point to related information. This appears to have been a
>bug in SQL Server 7. Is it still a bug in SQL Server 2000 SP3?
>Thanks,
>Jim
>"FIX: SQLMaint.exe Sets Database Status Incorrectly"
>http://support.microsoft.com/defaul...kb;EN-US;276234
>
>"a problem about repair damaged database and single user mode"
>de&hl=en&
lr=&ie=UTF-8&selm=etEeJupv%24GA.176%40cppssbbsa01.microsoft.com&rnum=5" target="_blank">http://groups.google.com/groups? q=...soft.com&rnum=5
>|||Thank you, Sue.
Jim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8gq7j0pemr387cd2csrsainr9v11a0npf6@.
4ax.com...
> Yes but it's not necessarily a good idea to use that option
> and you'd probably want to clear the Attempt to repair any
> minor problems check box in the maintenance plan.
> If you get DBCC errors, you'd want to manually intervene and
> do some type of root cause analysis. Then proceed with
> whatever action from there.
> -Sue
> On Mon, 30 Aug 2004 16:29:38 -0500, "Jim Moon"
> <jmoon()at()uab.edu> wrote:
>
>