Sunday, March 11, 2012

Error: 1203 - attempting to unlock unowned resource

I have located several references to this issue, most refer to SQL 2000 -
KBs 814654, 828090 (n/a), 331885, etc. Ken Henderson at Tech-Ed 2005
suggested this likely indicates a SQL Server BUG.
Is a more recent SQL 7.0 build available that corrects for this issue?
----
DESCRIPTION: Error: 1203, Severity: 20, State: 1
Process ID 19 attempting to unlock unowned resource PAG: 14:1:20715.
----
SQL Server will hang and crash when this occurs. We have correlated this
with concurrent <Log backups plus OLTP users from an ASP application plus MS
Access analytic/query users>.
Can we realistically use PROFILER to trace for this occasional condition and
detect the SPID/Login/Workstation that is implicated in the error? Would
that provide us any useful information? For example, start a TRACE
immediately prior to our hourly Log Backups and stop the trace after they
complete? The occurrence of this issue is capricious.
SQL Server 7.00.1094, NT Server 4.0 with latest SPs and Hotfixes.
Issues began after applying build 1094. I have turned off lightwegtht
pooling (inherited from a prior DBA), applied NPFS patch to NT 4.0, had
developer use MAXDOP Query Hint,. reconfigured the Server to MAXDOP = 1, and
am ready to perform invasive monitoring to detect the root cause and a cure.
Thanks in advance for any suggestions on this very annoying problem.Hi,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter the error message
"Process ID <number> attempting to unlock unowned resource PAG". If I have
misunderstood your concern, please feel free to point it out.
As you have found KB 828090 said "When you run the xp_sendmail stored
procedure on a computer that is running SQL Server 7.0 versions 7.00.1085
to 7.00.1098, error 1203 is reported in the SQL Server error log.
Subsequently, a fatal exception might occur, causing the computer that is
running SQL Server to shut down"
The hotfix for KB 828090 is available now, but it is only intended to
correct the problem that this article describes. Apply it only to systems
that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to
obtain the hotfix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/defaul...scid=fh;[LN];CNTACTMS
NOTE that ONLY asking for hotfix by contacting PSS will be a FREE service.
Please apply the hotfix and then let me know whether it works for you.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

No comments:

Post a Comment