Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
bulloo
Starting Member
1 Post |
Posted - 2008-02-12 : 04:45:40
|
Hi there,My SQL 2000 has totally crashed my server (no rpc, no network connections, etc) and required a reboot.The only errors I could locate were from the SQL Server Errorlog (see below):2008-02-12 00:16:27.61 spid143 WARNING: EC a8be8098, 1 waited 900 sec. on latch b63beb48. Not a BUF latch.2008-02-12 00:16:27.61 spid143 Waiting for type 0x4, current count 0xa, current owning EC 0xA8BF4098.2008-02-12 00:16:27.61 spid143 WARNING: EC a8bf0098, 3 waited 900 sec. on latch b63beb48. Not a BUF latch.2008-02-12 00:16:27.61 spid143 Waiting for type 0x4, current count 0xa, current owning EC 0xA8BF4098.2008-02-12 00:16:27.69 spid63 Time out occurred while waiting for buffer latch type 2,bp 0x217d5c0, page 1:94), stat 0x40d, object ID 1:0:0, EC 0x3B5935B0 : 0, waittime 600. Continuing to wait.2008-02-12 00:16:27.69 spid63 Waiting for type 0x2, current count 0x10000a, current owning EC 0x3B5935B0.These continued on throughout the night and left the system unusable!Has anyone else encountered these?My memory configuration on the server is 8 Gb RAM, using:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /PAE /3GBMy AWE settings are set as:Dynamic memory (min: 1024, max: 6079). I've left enough for AWE and the O/S itself! Funnily enough the same thing occured exactly one week ago and the same time (however profiler and logs have not picked out anything suspicious)?!?Many thanks |
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-02-12 : 18:32:19
|
Do you have some scheduled task operating at same time? E 12°55'05.25"N 56°04'39.16" |
 |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-12 : 23:21:19
|
Found anything in windows evevt logs? |
 |
|
|
|
|
|
|