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 |
|
monty
Posting Yak Master
130 Posts |
 Posted - 2006-11-26 : 09:40:59
|
| Hi All,iam seeing some errors related to buffer latch for sometime now the error is something like below"Waiting for type 0x4, current count 0xa, current owning EC 0x70EAC0C0. WARNING: EC abc040c0, 7 waited 300 sec. on latch 70bee3c4, class MISC. Not a BUF latch"is this something to worry and how to get rid of this?any help wld be appricieatedits me monty |
|
|
harsh_athalye
Master Smack Fu Yak Hacker
5581 Posts |
Posted - 2006-11-26 : 12:22:17
|
| You need to update your SQL Server with latest service pack.Check below articles:[url]http://support.microsoft.com/?kbid=898541[/url][url]http://support.microsoft.com/default.aspx?scid=kb;en-us;309093[/url]Harsh AthalyeIndia."Nothing is Impossible" |
 |
|
|
monty
Posting Yak Master
130 Posts |
Posted - 2006-11-29 : 02:04:00
|
Hi Harsh,i have sql server2000+sp4+cumulative hotfix installed do u think stilli need to go for hotfix install? becoz in the article i suppose it reffers to sp3, if iam not wrong..and the secondlinkis not opening up.. thanks for your prompt response i was away from work so wasnt able to reply earlier..thanks very much..its me monty |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2006-11-29 : 02:10:13
|
this is the second link:http://support.microsoft.com/kb/309093/en-us
SqlSpec: a fast and comprehensive data dictionary generator for
SQL Server 2000/2005, Analysis Server 2005, Access 97/2000/XP/2003
http://www.elsasoft.org |
|
|
|
monty
Posting Yak Master
130 Posts |
Posted - 2006-12-07 : 22:54:32
|
| Hi All,its been really a hide n seek game with the errors iam receiving on this same server, i have managed to get SAN admins, network admins to see wheather there is prob with SAN or hba's, but it seems there isnt any, when i raised a ticket with MS earlier they said it cld be because of disk. The other errors which came up are:1)IO to block (b25a4400) Failed on HardDisk(5) through Path(0) irp(fe135008).2)An Io Request to the device \Device\HarddiskDmVolumes\PhysicalDmVolumes\B did not complete or canceled within the specific timeout. this can occur if the device driver does not set a cancel routine for a given IO request packet.any help wld be apprieciatedits me monty |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2006-12-08 : 00:22:58
|
| These are definitely IO path errors and nothing to do with SQL Server. I can't help you if you've exhausted all avenues of investigation with your hardware diagnostics.Paul RandalLead Program Manager, Microsoft SQL Server Core Storage Engine (Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
|
|
|
|
|
Memory Error