Boot.ini file: current

Showing posts with label current. Show all posts

Tuesday, March 20, 2012

BUG: Severe error occurred on the current command...

select top 10 count(*) peerTotal, B.peerCountryCode, B.peerCountry,
(select top 1 peerCity from Peers where peerCity != 'Determining' AND peerCountry != 'NULL' and peerCountryCode = B.peerCountryCode group by peerCity order by count(peerCity) desc) peerTopCity
from Peers B where peerCountryCode != 'NULL' and peerCountry != 'NULL' group by peerCountryCode, peerCountry order by peerTotal desc

This causes the error

but if you take the order by at teh end out, it works. The table is partitioned acrosss 3 bladesBy the way, I am using SP2 CTP|||Source,Severity,Message
01/09/2007 09:06:09,Server,Unknown,A user request from the session with SPID 59 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
01/09/2007 09:06:09,Server,Unknown,Error: 17310<c/> Severity: 20<c/> State: 1.
01/09/2007 09:06:09,spid59,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
01/09/2007 09:06:09,spid59,Unknown,Stack Signature for the dump is 0x0684EA45
01/09/2007 09:06:09,spid59,Unknown,78132A36 Module(MSVCR80+00002A36)
01/09/2007 09:06:09,spid59,Unknown,781329AA Module(MSVCR80+000029AA)
01/09/2007 09:06:09,spid59,Unknown,0126872D Module(sqlservr+0026872D)
01/09/2007 09:06:09,spid59,Unknown,01268590 Module(sqlservr+00268590)
01/09/2007 09:06:09,spid59,Unknown,01268AE0 Module(sqlservr+00268AE0)
01/09/2007 09:06:09,spid59,Unknown,01267AEF Module(sqlservr+00267AEF)
01/09/2007 09:06:09,spid59,Unknown,0100B1D5 Module(sqlservr+0000B1D5)
01/09/2007 09:06:09,spid59,Unknown,0100B4C5 Module(sqlservr+0000B4C5)
01/09/2007 09:06:09,spid59,Unknown,0100B39F Module(sqlservr+0000B39F)
01/09/2007 09:06:09,spid59,Unknown,0102F3DB Module(sqlservr+0002F3DB)
01/09/2007 09:06:09,spid59,Unknown,01030CC2 Module(sqlservr+00030CC2)
01/09/2007 09:06:09,spid59,Unknown,0102CDE6 Module(sqlservr+0002CDE6)
01/09/2007 09:06:09,spid59,Unknown,012DC2DD Module(sqlservr+002DC2DD)
01/09/2007 09:06:09,spid59,Unknown,013ADAA5 Module(sqlservr+003ADAA5)
01/09/2007 09:06:09,spid59,Unknown,012DB9B7 Module(sqlservr+002DB9B7)
01/09/2007 09:06:09,spid59,Unknown,012DC028 Module(sqlservr+002DC028)
01/09/2007 09:06:09,spid59,Unknown,012DD905 Module(sqlservr+002DD905)
01/09/2007 09:06:09,spid59,Unknown,012DD7A0 Module(sqlservr+002DD7A0)
01/09/2007 09:06:09,spid59,Unknown,012DCEA7 Module(sqlservr+002DCEA7)
01/09/2007 09:06:09,spid59,Unknown,012DDBA3 Module(sqlservr+002DDBA3)
01/09/2007 09:06:09,spid59,Unknown,012E13A8 Module(sqlservr+002E13A8)
01/09/2007 09:06:09,spid59,Unknown,013C92D9 Module(sqlservr+003C92D9)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,01415594 Module(sqlservr+00415594)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,01454E39 Module(sqlservr+00454E39)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,0141A804 Module(sqlservr+0041A804)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,01418E23 Module(sqlservr+00418E23)
01/09/2007 09:06:09,spid59,Unknown,013C9B43 Module(sqlservr+003C9B43)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,0141B6BE Module(sqlservr+0041B6BE)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,01415594 Module(sqlservr+00415594)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,01415E6E Module(sqlservr+00415E6E)
01/09/2007 09:06:09,spid59,Unknown,013C9B43 Module(sqlservr+003C9B43)
01/09/2007 09:06:09,spid59,Unknown,013C8AE9 Module(sqlservr+003C8AE9)
01/09/2007 09:06:09,spid59,Unknown,01EBFF7D Module(sqlservr+00EBFF7D)
01/09/2007 09:06:09,spid59,Unknown,0151F41F Module(sqlservr+0051F41F)
01/09/2007 09:06:09,spid59,Unknown,013B6A49 Module(sqlservr+003B6A49)
01/09/2007 09:06:09,spid59,Unknown,013B6891 Module(sqlservr+003B6891)
01/09/2007 09:06:09,spid59,Unknown,* Short Stack Dump
01/09/2007 09:06:09,spid59,Unknown,* -
01/09/2007 09:06:09,spid59,Unknown,* *******************************************************************************
01/09/2007 09:06:09,spid59,Unknown,* SegSs: 00000023:
01/09/2007 09:06:09,spid59,Unknown,* Esp: 63CCB9FC: 63CC1102 21E257A8 21E7D930 21C9E3E8 63CCBA40 02490881
01/09/2007 09:06:09,spid59,Unknown,* EFlags: 00010246: 006F0064 00730077 004E005F 00000054 00610050 00680074
01/09/2007 09:06:09,spid59,Unknown,* SegCs: 0000001B:
01/09/2007 09:06:09,spid59,Unknown,* Ebp: 63CCBA18: 63CCBA4C 013B6A49 21E7D930 00000000 21E257A8 63CC1156
01/09/2007 09:06:09,spid59,Unknown,* Eip: 013B6891: 5BD9A5F3 3843893C C7404389 FFFFFC45 C38BFFFF 64F44D8B
01/09/2007 09:06:09,spid59,Unknown,* Edx: 00000000:
01/09/2007 09:06:09,spid59,Unknown,* Ecx: 00000008:
01/09/2007 09:06:09,spid59,Unknown,* Ebx: 21E7D930: 013B68C0 00000000 0000006D 21E257A8 00000000 00000000
01/09/2007 09:06:09,spid59,Unknown,* Eax: 00000000:
01/09/2007 09:06:09,spid59,Unknown,* Esi: 00000000:
01/09/2007 09:06:09,spid59,Unknown,* Edi: 21E7D948: 00000000 00000000 00000000 00000000 00000000 00000000
01/09/2007 09:06:09,spid59,Unknown,*
01/09/2007 09:06:09,spid59,Unknown,* dbghelp 64330000 64444FFF 00115000
01/09/2007 09:06:09,spid59,Unknown,* xplog70 63B30000 63B32FFF 00003000
01/09/2007 09:06:09,spid59,Unknown,* xplog70 63B10000 63B1BFFF 0000c000
01/09/2007 09:06:09,spid59,Unknown,* xpstar90 63AE0000 63B05FFF 00026000
01/09/2007 09:06:09,spid59,Unknown,* odbcint 63AC0000 63AD6FFF 00017000
01/09/2007 09:06:09,spid59,Unknown,* ATL80 7C630000 7C64AFFF 0001b000
01/09/2007 09:06:09,spid59,Unknown,* BatchParser90 63990000 639AEFFF 0001f000
01/09/2007 09:06:09,spid59,Unknown,* ODBC32 63950000 6398CFFF 0003d000
01/09/2007 09:06:09,spid59,Unknown,* SQLSCM90 63930000 63938FFF 00009000
01/09/2007 09:06:09,spid59,Unknown,* xpstar90 638D0000 63918FFF 00049000
01/09/2007 09:06:09,spid59,Unknown,* xpsqlbot 638B0000 638B5FFF 00006000
01/09/2007 09:06:09,spid59,Unknown,* msftepxy 633C0000 633D4FFF 00015000
01/09/2007 09:06:09,spid59,Unknown,* SQLNCLIR 00770000 007A2FFF 00033000
01/09/2007 09:06:09,spid59,Unknown,* comdlg32 762B0000 762F9FFF 0004a000
01/09/2007 09:06:09,spid59,Unknown,* COMCTL32 77530000 775C6FFF 00097000
01/09/2007 09:06:09,spid59,Unknown,* sqlncli 63010000 63233FFF 00224000
01/09/2007 09:06:09,spid59,Unknown,* CLBCatQ 777B0000 77832FFF 00083000
01/09/2007 09:06:09,spid59,Unknown,* xpsp2res 62D40000 63004FFF 002c5000
01/09/2007 09:06:09,spid59,Unknown,* ntdsapi 766F0000 76704FFF 00015000
01/09/2007 09:06:09,spid59,Unknown,* SAMLIB 62D30000 62D3EFFF 0000f000
01/09/2007 09:06:09,spid59,Unknown,* NTMARTA 77E00000 77E21FFF 00022000
01/09/2007 09:06:09,spid59,Unknown,* wshtcpip 71AE0000 71AE7FFF 00008000
01/09/2007 09:06:09,spid59,Unknown,* hnetcfg 62CD0000 62D28FFF 00059000
01/09/2007 09:06:09,spid59,Unknown,* dssenh 68100000 68123FFF 00024000
01/09/2007 09:06:09,spid59,Unknown,* imagehlp 76C10000 76C38FFF 00029000
01/09/2007 09:06:09,spid59,Unknown,* WINTRUST 76BB0000 76BDAFFF 0002b000
01/09/2007 09:06:09,spid59,Unknown,* dbghelp 62950000 62A64FFF 00115000
01/09/2007 09:06:09,spid59,Unknown,* msfte 626F0000 62948FFF 00259000
01/09/2007 09:06:09,spid59,Unknown,* security 61F50000 61F53FFF 00004000
01/09/2007 09:06:09,spid59,Unknown,* rasadhlp 76F80000 76F84FFF 00005000
01/09/2007 09:06:09,spid59,Unknown,* WLDAP32 76F10000 76F3DFFF 0002e000
01/09/2007 09:06:09,spid59,Unknown,* winrnr 76F70000 76F76FFF 00007000
01/09/2007 09:06:09,spid59,Unknown,* DNSAPI 76ED0000 76EF8FFF 00029000
01/09/2007 09:06:09,spid59,Unknown,* RESUTILS 344B0000 344C2FFF 00013000
01/09/2007 09:06:09,spid59,Unknown,* CLUSAPI 34490000 344A1FFF 00012000
01/09/2007 09:06:09,spid59,Unknown,* OLEAUT32 77D00000 77D8BFFF 0008c000
01/09/2007 09:06:09,spid59,Unknown,* WSOCK32 71BB0000 71BB8FFF 00009000
01/09/2007 09:06:09,spid59,Unknown,* VERSION 77B90000 77B97FFF 00008000
01/09/2007 09:06:09,spid59,Unknown,* MTXCLU 34470000 34488FFF 00019000
01/09/2007 09:06:09,spid59,Unknown,* msvcp60 780C0000 78120FFF 00061000
01/09/2007 09:06:09,spid59,Unknown,* MSDTCPRX 343F0000 34467FFF 00078000
01/09/2007 09:06:09,spid59,Unknown,* XOLEHLP 343E0000 343E5FFF 00006000
01/09/2007 09:06:09,spid59,Unknown,* COMRES 77010000 770D5FFF 000c6000
01/09/2007 09:06:09,spid59,Unknown,* schannel 76750000 76776FFF 00027000
01/09/2007 09:06:09,spid59,Unknown,* cryptdll 766E0000 766EBFFF 0000c000
01/09/2007 09:06:09,spid59,Unknown,* kerberos 34320000 34377FFF 00058000
01/09/2007 09:06:09,spid59,Unknown,* iphlpapi 76CF0000 76D09FFF 0001a000
01/09/2007 09:06:09,spid59,Unknown,* msv1_0 76C90000 76CB6FFF 00027000
01/09/2007 09:06:09,spid59,Unknown,* ole32 77670000 777A3FFF 00134000
01/09/2007 09:06:09,spid59,Unknown,* MSCOREE 340C0000 34104FFF 00045000
01/09/2007 09:06:09,spid59,Unknown,* AUTHZ 76C40000 76C53FFF 00014000
01/09/2007 09:06:09,spid59,Unknown,* rsaenh 68000000 6802EFFF 0002f000
01/09/2007 09:06:09,spid59,Unknown,* SQLOS 344D0000 344D4FFF 00005000
01/09/2007 09:06:09,spid59,Unknown,* sqlevn70 4F610000 4F7B8FFF 001a9000
01/09/2007 09:06:09,spid59,Unknown,* instapi 48060000 48069FFF 0000a000
01/09/2007 09:06:09,spid59,Unknown,* psapi 76B70000 76B7AFFF 0000b000
01/09/2007 09:06:09,spid59,Unknown,* comctl32 77420000 77522FFF 00103000
01/09/2007 09:06:09,spid59,Unknown,* SHLWAPI 77DA0000 77DF1FFF 00052000
01/09/2007 09:06:09,spid59,Unknown,* SHELL32 7C8D0000 7D0D2FFF 00803000
01/09/2007 09:06:09,spid59,Unknown,* NETAPI32 71C40000 71C97FFF 00058000
01/09/2007 09:06:09,spid59,Unknown,* opends60 333E0000 333E6FFF 00007000
01/09/2007 09:06:09,spid59,Unknown,* USERENV 76920000 769E3FFF 000c4000
01/09/2007 09:06:09,spid59,Unknown,* WS2HELP 71BF0000 71BF7FFF 00008000
01/09/2007 09:06:09,spid59,Unknown,* WS2_32 71C00000 71C16FFF 00017000
01/09/2007 09:06:09,spid59,Unknown,* MSWSOCK 71B20000 71B60FFF 00041000
01/09/2007 09:06:09,spid59,Unknown,* Secur32 76F50000 76F62FFF 00013000
01/09/2007 09:06:09,spid59,Unknown,* MSASN1 76190000 761A1FFF 00012000
01/09/2007 09:06:09,spid59,Unknown,* CRYPT32 761B0000 76242FFF 00093000
01/09/2007 09:06:09,spid59,Unknown,* GDI32 77C00000 77C47FFF 00048000
01/09/2007 09:06:09,spid59,Unknown,* USER32 77380000 77411FFF 00092000
01/09/2007 09:06:09,spid59,Unknown,* RPCRT4 77C50000 77CEEFFF 0009f000
01/09/2007 09:06:09,spid59,Unknown,* ADVAPI32 77F50000 77FEBFFF 0009c000
01/09/2007 09:06:09,spid59,Unknown,* MSVCP80 7C420000 7C4A6FFF 00087000
01/09/2007 09:06:09,spid59,Unknown,* msvcrt 77BA0000 77BF9FFF 0005a000
01/09/2007 09:06:09,spid59,Unknown,* MSVCR80 78130000 781CAFFF 0009b000
01/09/2007 09:06:09,spid59,Unknown,* kernel32 77E40000 77F41FFF 00102000
01/09/2007 09:06:09,spid59,Unknown,* ntdll 7C800000 7C8BFFFF 000c0000
01/09/2007 09:06:09,spid59,Unknown,* sqlservr 01000000 02C09FFF 01c0a000
01/09/2007 09:06:09,spid59,Unknown,* MODULE BASE END SIZE
01/09/2007 09:06:09,spid59,Unknown,*
01/09/2007 09:06:09,spid59,Unknown,*
01/09/2007 09:06:09,spid59,Unknown,* ry order by peerTotal desc
01/09/2007 09:06:09,spid59,Unknown,* != 'NULL' and peerCountry != 'NULL' group by peerCountryCode<c/> peerCount
01/09/2007 09:06:09,spid59,Unknown,* y) desc) peerTopCity from divinityTorrentPeers B where peerCountryCode
01/09/2007 09:06:09,spid59,Unknown,* CountryCode = B.peerCountryCode group by peerCity order by count(peerCit
01/09/2007 09:06:09,spid59,Unknown,* Peers where peerCity != 'Determining' AND peerCountry != 'NULL' and peer
01/09/2007 09:06:09,spid59,Unknown,* ountryCode<c/> B.peerCountry<c/> (select top 1 peerCity from Torrent
01/09/2007 09:06:09,spid59,Unknown,* SET XACT_ABORT ON; select top 10 count(*) peerTotal<c/> B.peerC
01/09/2007 09:06:09,spid59,Unknown,* Input Buffer 510 bytes -
01/09/2007 09:06:09,spid59,Unknown,* Access Violation occurred reading address 00000000
01/09/2007 09:06:09,spid59,Unknown,* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
01/09/2007 09:06:09,spid59,Unknown,* Exception Address = 013B6891 Module(sqlservr+003B6891)
01/09/2007 09:06:09,spid59,Unknown,*
01/09/2007 09:06:09,spid59,Unknown,*
01/09/2007 09:06:09,spid59,Unknown,* Private server build.
01/09/2007 09:06:09,spid59,Unknown,* 01/09/07 09:06:09 spid 59
01/09/2007 09:06:09,spid59,Unknown,* BEGIN STACK DUMP:
01/09/2007 09:06:09,spid59,Unknown,*
01/09/2007 09:06:09,spid59,Unknown,* *******************************************************************************|||Hmm.. I am also getting this error, even after installing the new Sp2 CTP patch.... this is bad that no one has even responded to this yet..

Sunday, March 11, 2012

Bug Listing?

Is there anywhere on your website that lists the current bugs/problems
identified post SP1 that will be fixed in future SP releases? I think it
would be very useful for a lot of RS developers to have a definitive list,
rather than scouring around newsgroups to find that the problem we've got is
actually a bug?If you have some bugs you know of, please post them here.
http://www.reportingservicesfaq.com/ow.asp?SP1Bugs
Help build the Wiki!
--
Reporting Services Articles, Forums, Blogs and Wiki Community
www.ReportingServicesFAQ.com
Simon wrote:
> Is there anywhere on your website that lists the current bugs/problems
> identified post SP1 that will be fixed in future SP releases? I think it
> would be very useful for a lot of RS developers to have a definitive list,
> rather than scouring around newsgroups to find that the problem we've got is
> actually a bug?

Wednesday, March 7, 2012

buflatch error

Under what circumstances do we get this message?
Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec. on
latch 8130f2c0. Not a BUF latch.My first port of call will be to check H/W(controller, disk drives for bad
sectors)
switch on perfmon(current disk read/write queue length) see under what
circumstances this is happening(heavy read/write)
HTH
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
on
> latch 8130f2c0. Not a BUF latch.|||The output of sysprocesses might give some more information.
Here is an article that might be useful for you:
http://support.microsoft.com/?kbid=822101
A latch is a short-term lightweight synchronization object. The following
list describes the different types of latches:
? Non-buffer (Non-BUF) latch: The non-buffer latches provide
synchronization services to in-memory data structures or provide re-entrancy
protection for concurrency-sensitive code lines. These latches can be used
for a variety of things, but they are not used to synchronize access to
buffer pages.
This message indicates longer than expected thread wait in the system. If
you see a drop of performance due to this, please consider contact microsoft
support. The problem might have been fixed by existing hotfix or QFE
http://support.microsoft.com/kb/309093/EN-US/
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> on
> latch 8130f2c0. Not a BUF latch.|||Thanks Wei. It helps
"wei xiao" wrote:
> The output of sysprocesses might give some more information.
> Here is an article that might be useful for you:
> http://support.microsoft.com/?kbid=822101
> A latch is a short-term lightweight synchronization object. The following
> list describes the different types of latches:
> ? Non-buffer (Non-BUF) latch: The non-buffer latches provide
> synchronization services to in-memory data structures or provide re-entrancy
> protection for concurrency-sensitive code lines. These latches can be used
> for a variety of things, but they are not used to synchronize access to
> buffer pages.
>
> This message indicates longer than expected thread wait in the system. If
> you see a drop of performance due to this, please consider contact microsoft
> support. The problem might have been fixed by existing hotfix or QFE
> http://support.microsoft.com/kb/309093/EN-US/
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> > Under what circumstances do we get this message?
> >
> > Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> > 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> > on
> > latch 8130f2c0. Not a BUF latch.
>
>

buflatch error

Under what circumstances do we get this message?
Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec. on
latch 8130f2c0. Not a BUF latch.
My first port of call will be to check H/W(controller, disk drives for bad
sectors)
switch on perfmon(current disk read/write queue length) see under what
circumstances this is happening(heavy read/write)
HTH
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
on
> latch 8130f2c0. Not a BUF latch.
|||The output of sysprocesses might give some more information.
Here is an article that might be useful for you:
http://support.microsoft.com/?kbid=822101
A latch is a short-term lightweight synchronization object. The following
list describes the different types of latches:
? Non-buffer (Non-BUF) latch: The non-buffer latches provide
synchronization services to in-memory data structures or provide re-entrancy
protection for concurrency-sensitive code lines. These latches can be used
for a variety of things, but they are not used to synchronize access to
buffer pages.
This message indicates longer than expected thread wait in the system. If
you see a drop of performance due to this, please consider contact microsoft
support. The problem might have been fixed by existing hotfix or QFE
http://support.microsoft.com/kb/309093/EN-US/
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> on
> latch 8130f2c0. Not a BUF latch.
|||Thanks Wei. It helps
"wei xiao" wrote:

> The output of sysprocesses might give some more information.
> Here is an article that might be useful for you:
> http://support.microsoft.com/?kbid=822101
> A latch is a short-term lightweight synchronization object. The following
> list describes the different types of latches:
> ? Non-buffer (Non-BUF) latch: The non-buffer latches provide
> synchronization services to in-memory data structures or provide re-entrancy
> protection for concurrency-sensitive code lines. These latches can be used
> for a variety of things, but they are not used to synchronize access to
> buffer pages.
>
> This message indicates longer than expected thread wait in the system. If
> you see a drop of performance due to this, please consider contact microsoft
> support. The problem might have been fixed by existing hotfix or QFE
> http://support.microsoft.com/kb/309093/EN-US/
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
>
>

buflatch error

Under what circumstances do we get this message?
Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec. on
latch 8130f2c0. Not a BUF latch.My first port of call will be to check H/W(controller, disk drives for bad
sectors)
switch on perfmon(current disk read/write queue length) see under what
circumstances this is happening(heavy read/write)
HTH
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
on
> latch 8130f2c0. Not a BUF latch.|||The output of sysprocesses might give some more information.
Here is an article that might be useful for you:
http://support.microsoft.com/?kbid=822101
A latch is a short-term lightweight synchronization object. The following
list describes the different types of latches:
? Non-buffer (Non-BUF) latch: The non-buffer latches provide
synchronization services to in-memory data structures or provide re-entrancy
protection for concurrency-sensitive code lines. These latches can be used
for a variety of things, but they are not used to synchronize access to
buffer pages.
This message indicates longer than expected thread wait in the system. If
you see a drop of performance due to this, please consider contact microsoft
support. The problem might have been fixed by existing hotfix or QFE
http://support.microsoft.com/kb/309093/EN-US/
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
> Under what circumstances do we get this message?
> Waiting for type 0x2, current count 0x508, current owning EC 0x00000000.
> 2005-03-08 02:49:26.52 spid189 WARNING: EC 6e4d3560, 0 waited 4800 sec.
> on
> latch 8130f2c0. Not a BUF latch.|||Thanks Wei. It helps
"wei xiao" wrote:

> The output of sysprocesses might give some more information.
> Here is an article that might be useful for you:
> http://support.microsoft.com/?kbid=822101
> A latch is a short-term lightweight synchronization object. The following
> list describes the different types of latches:
> ? Non-buffer (Non-BUF) latch: The non-buffer latches provide
> synchronization services to in-memory data structures or provide re-entran
cy
> protection for concurrency-sensitive code lines. These latches can be used
> for a variety of things, but they are not used to synchronize access to
> buffer pages.
>
> This message indicates longer than expected thread wait in the system. If
> you see a drop of performance due to this, please consider contact microso
ft
> support. The problem might have been fixed by existing hotfix or QFE
> http://support.microsoft.com/kb/309093/EN-US/
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://weblogs.asp.net/weix
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Bharath" <Bharath@.discussions.microsoft.com> wrote in message
> news:DFA6BE50-896C-408C-9C6B-16A1EA59645A@.microsoft.com...
>
>

Saturday, February 25, 2012

Buffer Latch error

quote:

> I have been having the following time out error message on
> my production server for a while now.
> Waiting for type 0x4, current count 0xa, current owning EC
> 0x5E0B63C8.
> Time out occurred while waiting for buffer latch type 4,bp
> 0x1473080, page 1:23), stat 0xb, object ID 7:3:0, EC
> 0x6ACBB9E0 : 0, waittime 600. Continuing to wait.
>
> The is an sms server that runs SQL2000 sp3 on Windows 2000
> sp4. The microsoft suggestion is to apply sp3 - which I
> already did when the server was built. Has anyone come
> accross this problem and if so, how did you fix? Is
> reapplying service pack a good thing to do? Thanks:
>
>

|||The server runs SMS and every so often during the day it
would run querries to find out what new computers are out
there. The application and server don't seem to have any
problem except for the fact that it generates this error
message. The timeout occurs sometimes during a backup and
that causes the job to fail. What more information can I
give you? How can an IO problem be resolved or how can we
determine if it is a query, memory or hardware?
June

quote:

>--Original Message--
>I've seen this.
>MS will probably disagree. But personally I feel that

this is a horribly

quote:

>handled error and perhaps a bug. You don't provide the

specific error number

quote:

>but assuming it's the same thing I've seen on numerous

occaisions...

quote:

>this error often points to a) a server with inadequte IO

capacity and/or b)

quote:

>queries that are inneffecient for one reason or another

that are

quote:

>exacerrbating the IO issue.
>Now... I'll accept that a hardware platform and/or query

might be slow...

quote:

>but I do NOT like the fact that the query simply times

out. I'd rather let

quote:

>it run and have warning messages written to the log that

indicate a problem

quote:

>is happening on this spid. Just my two cents...
>but anyway... you should probably be looking at IO issues

at the server and

quote:

>query level.
>Of course it could be something completely different.

There's not enough

quote:

>info in your mail to know for sure...
>--
>Brian Moran
>Principal Mentor
>Solid Quality Learning
>SQL Server MVP
>http://www.solidqualitylearning.com
>
>"June Spearman" <anonymous@.discussions.microsoft.com>

wrote in message

quote:

>news:0b2a01c3db7c$f0f4d270$a501280a@.phx.gbl...
on[QUOTE]
EC[QUOTE]
4,bp[QUOTE]
2000[QUOTE]
>
>.
>

Buffer Latch error

I have been having the following time out error message on
my production server for a while now.
Waiting for type 0x4, current count 0xa, current owning EC
0x5E0B63C8.
Time out occurred while waiting for buffer latch type 4,bp
0x1473080, page 1:23), stat 0xb, object ID 7:3:0, EC
0x6ACBB9E0 : 0, waittime 600. Continuing to wait.
The is an sms server that runs SQL2000 sp3 on Windows 2000
sp4. The microsoft suggestion is to apply sp3 - which I
already did when the server was built. Has anyone come
accross this problem and if so, how did you fix? Is
reapplying service pack a good thing to do? Thanks:I've seen this.
MS will probably disagree. But personally I feel that this is a horribly
handled error and perhaps a bug. You don't provide the specific error number
but assuming it's the same thing I've seen on numerous occaisions...
this error often points to a) a server with inadequte IO capacity and/or b)
queries that are inneffecient for one reason or another that are
exacerrbating the IO issue.
Now... I'll accept that a hardware platform and/or query might be slow...
but I do NOT like the fact that the query simply times out. I'd rather let
it run and have warning messages written to the log that indicate a problem
is happening on this spid. Just my two cents...
but anyway... you should probably be looking at IO issues at the server and
query level.
Of course it could be something completely different. There's not enough
info in your mail to know for sure...
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"June Spearman" <anonymous@.discussions.microsoft.com> wrote in message
news:0b2a01c3db7c$f0f4d270$a501280a@.phx.gbl...
> I have been having the following time out error message on
> my production server for a while now.
> Waiting for type 0x4, current count 0xa, current owning EC
> 0x5E0B63C8.
> Time out occurred while waiting for buffer latch type 4,bp
> 0x1473080, page 1:23), stat 0xb, object ID 7:3:0, EC
> 0x6ACBB9E0 : 0, waittime 600. Continuing to wait.
>
> The is an sms server that runs SQL2000 sp3 on Windows 2000
> sp4. The microsoft suggestion is to apply sp3 - which I
> already did when the server was built. Has anyone come
> accross this problem and if so, how did you fix? Is
> reapplying service pack a good thing to do? Thanks:
>
>|||The server runs SMS and every so often during the day it
would run querries to find out what new computers are out
there. The application and server don't seem to have any
problem except for the fact that it generates this error
message. The timeout occurs sometimes during a backup and
that causes the job to fail. What more information can I
give you? How can an IO problem be resolved or how can we
determine if it is a query, memory or hardware?
June
>--Original Message--
>I've seen this.
>MS will probably disagree. But personally I feel that
this is a horribly
>handled error and perhaps a bug. You don't provide the
specific error number
>but assuming it's the same thing I've seen on numerous
occaisions...
>this error often points to a) a server with inadequte IO
capacity and/or b)
>queries that are inneffecient for one reason or another
that are
>exacerrbating the IO issue.
>Now... I'll accept that a hardware platform and/or query
might be slow...
>but I do NOT like the fact that the query simply times
out. I'd rather let
>it run and have warning messages written to the log that
indicate a problem
>is happening on this spid. Just my two cents...
>but anyway... you should probably be looking at IO issues
at the server and
>query level.
>Of course it could be something completely different.
There's not enough
>info in your mail to know for sure...
>--
>Brian Moran
>Principal Mentor
>Solid Quality Learning
>SQL Server MVP
>http://www.solidqualitylearning.com
>
>"June Spearman" <anonymous@.discussions.microsoft.com>
wrote in message
>news:0b2a01c3db7c$f0f4d270$a501280a@.phx.gbl...
>> I have been having the following time out error message
on
>> my production server for a while now.
>> Waiting for type 0x4, current count 0xa, current owning
EC
>> 0x5E0B63C8.
>> Time out occurred while waiting for buffer latch type
4,bp
>> 0x1473080, page 1:23), stat 0xb, object ID 7:3:0, EC
>> 0x6ACBB9E0 : 0, waittime 600. Continuing to wait.
>>
>> The is an sms server that runs SQL2000 sp3 on Windows
2000
>> sp4. The microsoft suggestion is to apply sp3 - which I
>> already did when the server was built. Has anyone come
>> accross this problem and if so, how did you fix? Is
>> reapplying service pack a good thing to do? Thanks:
>>
>
>.
>

Tuesday, March 20, 2012

BUG: Severe error occurred on the current command...

Sunday, March 11, 2012

Bug Listing?

Wednesday, March 7, 2012

buflatch error

buflatch error

buflatch error

Saturday, February 25, 2012

Buffer Latch error

Buffer Latch error

Boot.ini file

Blog Archive

About Me