Error: 644, Severity: 21, State: 6

Hi All

Ignore the error below, It's got to do with isolation levels (nolock in this case): refer http://support.microsoft.com/?kbid=834290 for details.

Error: 644, Severity: 21, State: 6
Could not find the index entry for RID '1631393920202020202020202020202033392020202020202 020202020202019bcd3113230303037333120202020202020' in index page (1:420134), index ID 0, database 'DBName'..

What I'd like to know is how to get the table name that was affected out of this error message. Do I query sysindexes, sysobjects, use a function or something else?

Thanks in advance.

GrahamNo need to answer the question:

dbcc traceon(3604)
dbcc page ('DBName', 1, 420134, 0)
select name from sysobjects where id =1141579105--m_objId from page header
dbcc traceon(3604)
dbcc page ('DBName', 1, 305272,0)
select name from sysobjects where id =1141579105--m_objId from page header
dbcc traceon(3604)
dbcc page ('DBName', 1, 369029, 0)
select name from sysobjects where id =2021582240--m_objId from page header

/*
TABLE A: DBCC PAGE Parameters
Parameter Description
dbid ID of the database containing the page
dbname Name of the database containing the page
filenum File number containing the page
pagenum Page number within the file
printopt Optional print option; takes one of these values:
0 Default; print the buffer header and page header
1 Print the buffer header, page header, each row separately, and the row offset table
2 Print the buffer and page headers, page as a whole, and the offset table

*/

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/default.aspx?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.

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/default.aspx?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.

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.

Error: "expression can only refer to field w/ data scope"

I get the following error when i try to add a new field being returned in a
dataset:
"Report item expressions can only refer to fields within the current data
set scope or, if inside an aggregate, the specified data set scope".
I have no idea what this means, and i can reference just fine every other
field i'm returning in the dataset.
I found an earlier person who had this problem, and the response was "you
can only bind one dataset to a report item". This can't be my problem,
though, as i've only GOT one dataset.
TIA,
--
BrianSide note (may not be the solution to your problem):
You can bind more than one dataset to a report! I've done this
successfully, and it's actually pretty easy.
"G" <brian.grant@.si-intl-kc.com> wrote in message
news:#jeQ0rwfEHA.3148@.TK2MSFTNGP10.phx.gbl...
> I get the following error when i try to add a new field being returned in
a
> dataset:
> "Report item expressions can only refer to fields within the current data
> set scope or, if inside an aggregate, the specified data set scope".
> I have no idea what this means, and i can reference just fine every other
> field i'm returning in the dataset.
> I found an earlier person who had this problem, and the response was "you
> can only bind one dataset to a report item". This can't be my problem,
> though, as i've only GOT one dataset.
> TIA,
> --
> Brian
>|||Both comments below are true: You can have several datasets in a **report**
but only bind one dataset to a **report item**.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"SQL" <nospam@.adfadfadf.com> wrote in message
news:ufCl4HxfEHA.2812@.tk2msftngp13.phx.gbl...
> Side note (may not be the solution to your problem):
> You can bind more than one dataset to a report! I've done this
> successfully, and it's actually pretty easy.
>
> "G" <brian.grant@.si-intl-kc.com> wrote in message
> news:#jeQ0rwfEHA.3148@.TK2MSFTNGP10.phx.gbl...
> > I get the following error when i try to add a new field being returned
in
> a
> > dataset:
> >
> > "Report item expressions can only refer to fields within the current
data
> > set scope or, if inside an aggregate, the specified data set scope".
> >
> > I have no idea what this means, and i can reference just fine every
other
> > field i'm returning in the dataset.
> >
> > I found an earlier person who had this problem, and the response was
"you
> > can only bind one dataset to a report item". This can't be my problem,
> > though, as i've only GOT one dataset.
> >
> > TIA,
> >
> > --
> > Brian
> >
> >
>|||That's all well and good, but none of these apply to my situation! I have
only one dataset, period, yet i'm getting this error.
Is there another problem that could cause this sort of error?
"Ravi Mumulla (Microsoft)" <ravimu@.online.microsoft.com> wrote in message
news:Ot5fX7xfEHA.1048@.tk2msftngp13.phx.gbl...
> Both comments below are true: You can have several datasets in a
**report**
> but only bind one dataset to a **report item**.
> --
> Ravi Mumulla (Microsoft)
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "SQL" <nospam@.adfadfadf.com> wrote in message
> news:ufCl4HxfEHA.2812@.tk2msftngp13.phx.gbl...
> > Side note (may not be the solution to your problem):
> >
> > You can bind more than one dataset to a report! I've done this
> > successfully, and it's actually pretty easy.
> >
> >
> > "G" <brian.grant@.si-intl-kc.com> wrote in message
> > news:#jeQ0rwfEHA.3148@.TK2MSFTNGP10.phx.gbl...
> > > I get the following error when i try to add a new field being returned
> in
> > a
> > > dataset:
> > >
> > > "Report item expressions can only refer to fields within the current
> data
> > > set scope or, if inside an aggregate, the specified data set scope".
> > >
> > > I have no idea what this means, and i can reference just fine every
> other
> > > field i'm returning in the dataset.
> > >
> > > I found an earlier person who had this problem, and the response was
> "you
> > > can only bind one dataset to a report item". This can't be my problem,
> > > though, as i've only GOT one dataset.
> > >
> > > TIA,
> > >
> > > --
> > > Brian
> > >
> > >
> >
> >
>|||Found it!!!!
Dunno if this is a bug or expected behavior or what but....
I was using the custom query designer because i had a rather dynamic query
to write. When i added a new field in the return set, that field was NOT
automatically added to the field list in the dataset returned fields window.
I had to manually add that field. Solved the problem.
Brian
"G" <brian.grant@.si-intl-kc.com> wrote in message
news:OIUd%23Y6fEHA.236@.tk2msftngp13.phx.gbl...
> That's all well and good, but none of these apply to my situation! I have
> only one dataset, period, yet i'm getting this error.
> Is there another problem that could cause this sort of error?
>
> "Ravi Mumulla (Microsoft)" <ravimu@.online.microsoft.com> wrote in message
> news:Ot5fX7xfEHA.1048@.tk2msftngp13.phx.gbl...
> > Both comments below are true: You can have several datasets in a
> **report**
> > but only bind one dataset to a **report item**.
> >
> > --
> > Ravi Mumulla (Microsoft)
> > SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > "SQL" <nospam@.adfadfadf.com> wrote in message
> > news:ufCl4HxfEHA.2812@.tk2msftngp13.phx.gbl...
> > > Side note (may not be the solution to your problem):
> > >
> > > You can bind more than one dataset to a report! I've done this
> > > successfully, and it's actually pretty easy.
> > >
> > >
> > > "G" <brian.grant@.si-intl-kc.com> wrote in message
> > > news:#jeQ0rwfEHA.3148@.TK2MSFTNGP10.phx.gbl...
> > > > I get the following error when i try to add a new field being
returned
> > in
> > > a
> > > > dataset:
> > > >
> > > > "Report item expressions can only refer to fields within the current
> > data
> > > > set scope or, if inside an aggregate, the specified data set scope".
> > > >
> > > > I have no idea what this means, and i can reference just fine every
> > other
> > > > field i'm returning in the dataset.
> > > >
> > > > I found an earlier person who had this problem, and the response was
> > "you
> > > > can only bind one dataset to a report item". This can't be my
problem,
> > > > though, as i've only GOT one dataset.
> > > >
> > > > TIA,
> > > >
> > > > --
> > > > Brian
> > > >
> > > >
> > >
> > >
> >
> >
>|||Either that or you can use the static version of the query first, which will
populate the fields list for you, and then replace it with the the
corresponding query expression.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"G" <brian.grant@.si-intl-kc.com> wrote in message
news:up0IDI7fEHA.2020@.TK2MSFTNGP10.phx.gbl...
> Found it!!!!
> Dunno if this is a bug or expected behavior or what but....
> I was using the custom query designer because i had a rather dynamic query
> to write. When i added a new field in the return set, that field was NOT
> automatically added to the field list in the dataset returned fields
window.
> I had to manually add that field. Solved the problem.
> Brian
> "G" <brian.grant@.si-intl-kc.com> wrote in message
> news:OIUd%23Y6fEHA.236@.tk2msftngp13.phx.gbl...
> > That's all well and good, but none of these apply to my situation! I
have
> > only one dataset, period, yet i'm getting this error.
> >
> > Is there another problem that could cause this sort of error?
> >
> >
> > "Ravi Mumulla (Microsoft)" <ravimu@.online.microsoft.com> wrote in
message
> > news:Ot5fX7xfEHA.1048@.tk2msftngp13.phx.gbl...
> > > Both comments below are true: You can have several datasets in a
> > **report**
> > > but only bind one dataset to a **report item**.
> > >
> > > --
> > > Ravi Mumulla (Microsoft)
> > > SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > "SQL" <nospam@.adfadfadf.com> wrote in message
> > > news:ufCl4HxfEHA.2812@.tk2msftngp13.phx.gbl...
> > > > Side note (may not be the solution to your problem):
> > > >
> > > > You can bind more than one dataset to a report! I've done this
> > > > successfully, and it's actually pretty easy.
> > > >
> > > >
> > > > "G" <brian.grant@.si-intl-kc.com> wrote in message
> > > > news:#jeQ0rwfEHA.3148@.TK2MSFTNGP10.phx.gbl...
> > > > > I get the following error when i try to add a new field being
> returned
> > > in
> > > > a
> > > > > dataset:
> > > > >
> > > > > "Report item expressions can only refer to fields within the
current
> > > data
> > > > > set scope or, if inside an aggregate, the specified data set
scope".
> > > > >
> > > > > I have no idea what this means, and i can reference just fine
every
> > > other
> > > > > field i'm returning in the dataset.
> > > > >
> > > > > I found an earlier person who had this problem, and the response
was
> > > "you
> > > > > can only bind one dataset to a report item". This can't be my
> problem,
> > > > > though, as i've only GOT one dataset.
> > > > >
> > > > > TIA,
> > > > >
> > > > > --
> > > > > Brian
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

Error with ole db

I created a view refer to a visual foxpro with ole db for visual foxpro which was working fine before. But now, I received an error while select the view

Msg 7302, Level 16, State 1, Line 1
Cannot create an instance of OLE DB provider "VFPOLEDB" for linked server "ORST3".

Please advise. Thanks in advance

Can you provide us with sample repro code for this issue?

Thanks