Re: Problem after 49.71 Days
From: Steve Kass (skass_at_drew.edu)
Date: 02/28/05
- Next message: David: "Re: Drastic slowdown on SQL Server"
- Previous message: David Gugick: "Re: Home Network w/ 2 SQLServers: 1-way problem"
- In reply to: Lockdesign Ltd: "Problem after 49.71 Days"
- Next in thread: Lockdesign Ltd: "Re: Problem after 49.71 Days"
- Reply: Lockdesign Ltd: "Re: Problem after 49.71 Days"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 28 Feb 2005 18:06:00 -0500
Geoff,
When you brought this up in November, I suggested you see about
getting the hotfix
mentioned in http://support.microsoft.com/default.aspx?scid=kb;en-us;823273.
You answered that your rpcrt4.dll file on the 2000 Server box was later
than the one in
the KB article, and I'm guessing you didn't request the hotfix. Is it
possible you compared
your 2000 Server file date with the information for the NT Server 4.0 hotfix
accidentally? While the NT 4.0 hotfix file info just lists Rpcrt4.dll,
the file information
for the Windows 2000 Server hotfix mentions 3 files.
Date Time Version Size File name
--------------------------------------------------------------
07-Jan-2004 00:21 5.0.2195.6878 953,104 Ole32.dll
07-Jan-2004 00:21 5.0.2195.6888 435,472 Rpcrt4.dll
07-Jan-2004 00:21 5.0.2195.6878 211,216 Rpcss.dll
Can you double-check? Maybe the 2000 Server hotfix will take care of
the problem.
Steve Kass
Drew University
Geoff Kell (Lockdesign Ltd) wrote:
>I have raised this question previously but now have additional information.
>
>We have a SQL Server 7 machine running under Windows 2000 on a HP Compaq
>Proliant ML370/G2.
>
>The system runs fine until 49.71 days (the time it takes for the
>GetTickCount API to wrap back to 0. i.e. max no milliseconds in 32 bit
>quantity).
>
>After this we start to get timeouts when reading and writing to the
>database. The timeouts start immediately after the 49.71 days (within a
>couple of seconds) and continue until we reboot the database machine.
>Rebooting all the clients does not stop the problem occuring once the clients
>restart and reconnect; we **MUST** reboot the actual SQL Server machine.
>
>We considered the possibility that the problem could be caused by clients
>holding connections open to the database for the 49.71 days but have taken
>steps to ensure that connections are not held open this long. We also noticed
>that we had 'dangling connections' (connections shown as open but where the
>owner had been rebooted, etc). We have taken steps to clear these connections
>down.
>
>Now just over 50 days ago we went through the 49.71 days without any
>problems. However, our plant was not running at this point and therefore
>there were very few database transactions in progress. On Friday night we hit
>the next 49.71 days (99.42), the plant was running and sure enough, 2 seconds
>after the 99.42 days passed we started getting timeouts. I noticed that there
>were 100% spikes in CPU utilisation on the database machine that corresponded
>to the timeouts. The SQLServer process was the one taking up the 100% CPU.
>These spikes were not evident before the 99.42 days. A reboot of the SQL
>Server machine was carried out and the countdown to the next 49.71 days began
>:(
>
>One thought that we have is that the problem could be caused by an open
>transaction over the 49.71 day period, i.e. Starting before but ending after.
>Having said this I have no explanation as to why this should cause the
>problem from that point on.
>
>At the moment it looks like we are going to go back to the scheduled reboot
>before the problem hits us again; but in our 24/7 environment this is
>somewhat inconvenient.
>
>Any thoughts, ideas or suggestions are more than welcome. Not only to fix
>the problem but also things to investigate.
>
>TIA
>Geoff
>
>
>
- Next message: David: "Re: Drastic slowdown on SQL Server"
- Previous message: David Gugick: "Re: Home Network w/ 2 SQLServers: 1-way problem"
- In reply to: Lockdesign Ltd: "Problem after 49.71 Days"
- Next in thread: Lockdesign Ltd: "Re: Problem after 49.71 Days"
- Reply: Lockdesign Ltd: "Re: Problem after 49.71 Days"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
