Process ID 65 attempting to unlock unowned resource

Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
I am getting the above error in the event log for my website.
Can someone help me and tell me what this means?
thansk in Advance. KimHi
See if this applies:
http://support.microsoft.com/?kbid=814654
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
> Process ID 65 attempting to unlock unowned resource PAG: 7:1:166448.
> I am getting the above error in the event log for my website.
> Can someone help me and tell me what this means?
> thansk in Advance. Kim
>|||Hi,
It looks to be the exact problem - except we are running with service pak 4
here's the version info
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Developer
Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
> Hi
> See if this applies:
> http://support.microsoft.com/?kbid=814654
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:ZW_he.25101$0i3.23178@.bignews3.bellsouth.net...
>|||Hi
You are running Windows SP4, but SQL Server SP3 (8.00.760)
The problem was fixed in build 765 which was after SP3.
You can do one of the following:
Download the Security Hotfix Rollup that will take you build to 818
(http://www.microsoft.com/downloads/...&displaylang=en)
Download build 878,
http://support.microsoft.com/defaul...kb;en-us;838166
Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
your server is not using AWE or PAE as there is a known issue with it and
SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
http://msmvps.com/epprecht/archive/...5/14/46940.aspx
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Kim" <kim@.xxx.com> wrote in message
news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net...
> Hi,
> It looks to be the exact problem - except we are running with service pak
> 4
> here's the version info
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Developer
> Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23px3ddhWFHA.2960@.TK2MSFTNGP15.phx.gbl...
>|||Hi,
Thanks for your help.
I will pass this on to the guy who will do the updates.
Kim
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:eoxzWthWFHA.2976@.TK2MSFTNGP10.phx.gbl...
> Hi
> You are running Windows SP4, but SQL Server SP3 (8.00.760)
> The problem was fixed in build 765 which was after SP3.
> You can do one of the following:
> Download the Security Hotfix Rollup that will take you build to 818
>
(http://www.microsoft.com/downloads/...4ae9d-bd44-40c5
-add3-b8c99618e68d&displaylang=en)
> Download build 878,
> http://support.microsoft.com/defaul...kb;en-us;838166
> Or apply SP4 for SQL Server. If you are going to apply SP4, make sure that
> your server is not using AWE or PAE as there is a known issue with it and
> SP4. http://www.microsoft.com/sql/downloads/2000/sp4.asp and
> http://msmvps.com/epprecht/archive/...5/14/46940.aspx
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Kim" <kim@.xxx.com> wrote in message
> news:LY0ie.14211$7A2.2550@.bignews6.bellsouth.net...
pak[vbcol=seagreen]
>