Bug?: rsMultiReportItemsInPageSectionExpression when one report item, but referenced twice

When I reference the same report item twice in my footer expression I get an
error saying that I've refereced two items. My motivation is the database
field on each page footer. I have a custom assembly instance that stores
the value from the first page, then returns it when I am passing in empty
values. I tried the page number from the globals collection but ran into
#Error...anyway, getting off base. My issue is that the report expression
references a single item twice. Should I be able to do this? If not,
should the error message be more specific?
Expression:
=IIf(IsNothing(ReportItems!txtSchoolNameHidden.Value)=False,
Code.loc.SchoolName(ReportItems!txtSchoolNameHidden.Value),
Code.loc.SchoolName(""))
Error:
[rsMultiReportItemsInPageSectionExpression] The Value expression for the
textbox 'txtSchoolName' refers to more than one report item. An expression
in a page header or footer can refer to only one report item.Submitted bug to Microsoft via Product Feedback
"Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
news:%23RtLLbKNGHA.3728@.tk2msftngp13.phx.gbl...
> When I reference the same report item twice in my footer expression I get
> an error saying that I've refereced two items. My motivation is the
> database field on each page footer. I have a custom assembly instance
> that stores the value from the first page, then returns it when I am
> passing in empty values. I tried the page number from the globals
> collection but ran into #Error...anyway, getting off base. My issue is
> that the report expression references a single item twice. Should I be
> able to do this? If not, should the error message be more specific?
> Expression:
> =IIf(IsNothing(ReportItems!txtSchoolNameHidden.Value)=False,
> Code.loc.SchoolName(ReportItems!txtSchoolNameHidden.Value),
> Code.loc.SchoolName(""))
> Error:
> [rsMultiReportItemsInPageSectionExpression] The Value expression for the
> textbox 'txtSchoolName' refers to more than one report item. An
> expression in a page header or footer can refer to only one report item.
>

BSOD blamed on nlemsql.sys

We have Server 2003 crashing every day or so, saying:
*** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x0000
0000
*** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
There are only two references to nlemsql on Google, neither of which are
related to a crash.
We're trying to narrow down what happens just before this, but haven't
managed to get any useful information yet.
It's a stab in the dark, but: anyone seen this before?
Rikthat's the good ole KERNEL_MODE_EXCEPTION_NOT_HANDLED, an error which the os
did not know how to handle. These are almost always hardware compatibility
issues, you need a firmware or driver update. The question is which one, it
looks like the driver for nlemsql.sys. That driver is not part of SQL
Server. Search your system looking for it and when you find it right click
on it and look at properties, and then the version tab. There should be a
clue as to what this driver is for, or who made it somewhere here. You can
also open it in text pad looking for clues. Another thing you can do is to
check the directory it is in which occasionally well tell you something.
this file is not part of SQL 2000 or SQl 2005.
I would also contact your vendor of the server.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rik Hemsley" <rik@.rikkus.info> wrote in message
news:uy$h8OSZGHA.3972@.TK2MSFTNGP04.phx.gbl...
> We have Server 2003 crashing every day or so, saying:
> *** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x0000
0000
> *** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
> There are only two references to nlemsql on Google, neither of which are
> related to a crash.
> We're trying to narrow down what happens just before this, but haven't
> managed to get any useful information yet.
> It's a stab in the dark, but: anyone seen this before?
> Rik

BSOD blamed on nlemsql.sys

We have Server 2003 crashing every day or so, saying:
*** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x00000000
*** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
There are only two references to nlemsql on Google, neither of which are
related to a crash.
We're trying to narrow down what happens just before this, but haven't
managed to get any useful information yet.
It's a stab in the dark, but: anyone seen this before?
Rikthat's the good ole KERNEL_MODE_EXCEPTION_NOT_HANDLED, an error which the os
did not know how to handle. These are almost always hardware compatibility
issues, you need a firmware or driver update. The question is which one, it
looks like the driver for nlemsql.sys. That driver is not part of SQL
Server. Search your system looking for it and when you find it right click
on it and look at properties, and then the version tab. There should be a
clue as to what this driver is for, or who made it somewhere here. You can
also open it in text pad looking for clues. Another thing you can do is to
check the directory it is in which occasionally well tell you something.
this file is not part of SQL 2000 or SQl 2005.
I would also contact your vendor of the server.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rik Hemsley" <rik@.rikkus.info> wrote in message
news:uy$h8OSZGHA.3972@.TK2MSFTNGP04.phx.gbl...
> We have Server 2003 crashing every day or so, saying:
> *** STOP: 0x0000008E 0xC00000005,0xF74FB472,0xB8681AEC,0x00000000
> *** nlemsql.sys - Address F74FB472 base at F74F7000, DateStamp 3eca40a0
> There are only two references to nlemsql on Google, neither of which are
> related to a crash.
> We're trying to narrow down what happens just before this, but haven't
> managed to get any useful information yet.
> It's a stab in the dark, but: anyone seen this before?
> Rik