Error 1203

I am finding Error 1203 Severity 20 periodically in my trace.
This seems to correlate with intermittent failed insert statements performed
by a stored procedure. The stored procedure is executed shortly before this
error is recorded.
Nothing is written to the SQL Server log.
The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
running on W2K server.
The same error occurs in a test database on SQL Server 2000 Standard, no
service packs, build 3790.
I found one reference to it in response to a question on winnetmag.com:
What is error msg 1203, "attempting to unlock unowned resource "?
Answered: This error indicates a bug in SQL Server. Several bugs that caused
this error were fixed in SQL Server 2000, service pack 1. If you can create
a script that will allow anyone to reproduce this problem, you should send
it in to Microsoft SQL Server support.
I can't reproduce this except in our database. dbcc checkdb indicates no
errors.
I am concerned about data loss without any error to detect it. Can anyone
help me with this?
Thanks
BillHi
Error 1203 is bad. Process ID %d attempting to unlock unowned resource %.*ls.
There are a number of KB articles indicating that it occurs up to version
8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
Server sp3a and see if the error still occurs. Plus, if you are not on SQL
Server 2000 sp3a, you are exposed to the Slammer virus.
Regards
Mike
"bill" wrote:
> I am finding Error 1203 Severity 20 periodically in my trace.
> This seems to correlate with intermittent failed insert statements performed
> by a stored procedure. The stored procedure is executed shortly before this
> error is recorded.
> Nothing is written to the SQL Server log.
> The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
> running on W2K server.
> The same error occurs in a test database on SQL Server 2000 Standard, no
> service packs, build 3790.
> I found one reference to it in response to a question on winnetmag.com:
> What is error msg 1203, "attempting to unlock unowned resource "?
> Answered: This error indicates a bug in SQL Server. Several bugs that caused
> this error were fixed in SQL Server 2000, service pack 1. If you can create
> a script that will allow anyone to reproduce this problem, you should send
> it in to Microsoft SQL Server support.
> I can't reproduce this except in our database. dbcc checkdb indicates no
> errors.
> I am concerned about data loss without any error to detect it. Can anyone
> help me with this?
> Thanks
> Bill
>
>|||Mike:
SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
MS03-031. This was originally launched as build 817 but caused a but in the
DtsGui.dll. This fix replaced the previous edition to build 818. This
release caused a password issue when using SEM. This fix is build 819.
SP3a is build 760.
The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
release code. If one uses this, then only SP3a need to be applied.
Build 818:
http://support.microsoft.com/?scid=kb;en-us;821277&spid=2852&sid=global
Build 819:
http://support.microsoft.com/kb/826161
Release A:
http://support.microsoft.com/default.aspx?scid=kb;en-us;826818
Sincerely,
Anthony Thomas
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:94447A54-2C1F-483F-8D71-1584645C4BCA@.microsoft.com...
> Hi
> Error 1203 is bad. Process ID %d attempting to unlock unowned resource
%.*ls.
> There are a number of KB articles indicating that it occurs up to version
> 8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
> Server sp3a and see if the error still occurs. Plus, if you are not on SQL
> Server 2000 sp3a, you are exposed to the Slammer virus.
> Regards
> Mike
>
> "bill" wrote:
> > I am finding Error 1203 Severity 20 periodically in my trace.
> >
> > This seems to correlate with intermittent failed insert statements
performed
> > by a stored procedure. The stored procedure is executed shortly before
this
> > error is recorded.
> >
> > Nothing is written to the SQL Server log.
> >
> > The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
> > running on W2K server.
> >
> > The same error occurs in a test database on SQL Server 2000 Standard, no
> > service packs, build 3790.
> >
> > I found one reference to it in response to a question on winnetmag.com:
> >
> > What is error msg 1203, "attempting to unlock unowned resource "?
> > Answered: This error indicates a bug in SQL Server. Several bugs that
caused
> > this error were fixed in SQL Server 2000, service pack 1. If you can
create
> > a script that will allow anyone to reproduce this problem, you should
send
> > it in to Microsoft SQL Server support.
> >
> > I can't reproduce this except in our database. dbcc checkdb indicates
no
> > errors.
> >
> > I am concerned about data loss without any error to detect it. Can
anyone
> > help me with this?
> >
> > Thanks
> > Bill
> >
> >
> >
> >|||Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/details.aspx?FamilyID=90dcd52c-0488-4e46-afbf-acace5369fa3&displaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer) virus."
It will not remove Slammer if it is present, and the page says "SQL 2000
Servers infected by the "Slammer" worm virus should follow instructions
on the Microsoft TechNet Web site before installing SP3a."
According to
http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&DisplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with SP3
or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
AnthonyThomas wrote:
>Mike:
>SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
>MS03-031. This was originally launched as build 817 but caused a but in the
>DtsGui.dll. This fix replaced the previous edition to build 818. This
>release caused a password issue when using SEM. This fix is build 819.
>SP3a is build 760.
>The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
>release code. If one uses this, then only SP3a need to be applied.
>Build 818:
>http://support.microsoft.com/?scid=kb;en-us;821277&spid=2852&sid=global
>
>Build 819:
>http://support.microsoft.com/kb/826161
>
>Release A:
>http://support.microsoft.com/default.aspx?scid=kb;en-us;826818
>
>Sincerely,
>
>Anthony Thomas
>
>|||I don't understand your question at all. Here's what I said:
Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/details.aspx?FamilyID=90dcd52c-0488-4e46-afbf-acace5369fa3&displaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer)
virus." It will not remove Slammer if it is present, and the page
says "SQL 2000 Servers infected by the "Slammer" worm virus should
follow instructions on the Microsoft TechNet Web site before
installing SP3a."
According to
http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&DisplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with
SP3 or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
You had incorrectly stated "SQL Server SP3a DOES NOT contain the fix for
the "Slammer Worm" virus MS03-031," and I corrected your misstatement.
It does. SQL Server build 818 appeared after Service Pack 3 (Service
Pack 3/3a is build 760), and build 818 corrected three post-Slammer
security vulnerabilities identified in MS03-031.
Slammer appeared after sp3 had been released, and it did not affect
anyone who had already installed sp3, or who had installed the even
early post-sp2 fix correcting the vulnerability ultimately exploited by
Slammer (pre-Slammer, pre-sp2 bulletin MS02-039). Everything to do with
Slammer (recognition of the vulnerability, the security bulletin, the
patch, the service pack that contained the patch, and finally the
exploit) happened well before the later and unrelated bulletin MS03-031
(build 818, which was post-sp3, not pre-sp3).
SK
AnthonyThomas wrote:
>Then why the need for MS03-031 for post SP3 or SP3a, both of which are only the 760 builds, while the MS03-031 was originally 817, then 818, closely followed by 819? Since the hot fixes and service packs are cumulative, why didn't the post SP2 hot fixes make it into the SP3(a) releases? Again, if they did, then why the need for the 817 through 819 builds?
>Sincerely,
>
>Anthony Thomas
>
>