Deadlock bug in MoveItem or CreateReport

Reporting services is throwing deadlock exceptions which if retried (up to 10 times) sometimes succeed. When those exceptions happen Reporting Services is coming to a halt waiting for the deadlock to resolve. Performance is unacceptably degraded then.
In my test I am trying to run multiple concurrent SOAP sessions with a single admin level user account and in each session my process moves old report definitions into historical folders (saves with unique names) and then creates new report definition (again the report names are not overlapping) and finally creates a snapshot of the new report.
1. Is there a way to avoid those deadlocks?
2. From the SQL Server log files it looks like there is some level of pessimistic locking happening on some tables. Is that really necessary? It seems like the operations that are being performed deal with independent data elements that should not require any synchronization/serialization.
3. What level of parallelism is allowed when making concurrent calls to the server on the same user id but within separate sessions? Are there any restrictions?
4. Is there a place (maybe at MSDN) to report this as a real bug?
I can also provide sql server trace log file with information about the deadlock. No way to attach it here.
***********************************************************************
SOAP Exception message when the deadlock occurs is as follows:
***********************************************************************
Reason: An internal error occurred on the report server. See the error log for m
ore details. --> An internal error occurred on the report server. See the error
log for more details. --> Transaction (Process ID 55) was deadlocked on lock res
ources with another process and has been chosen as the deadlock victim. Rerun th
e transaction.
12:32:41,836 ERROR [STDERR] AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: An internal error occurred on the report server. See the error log
for more details. --> An internal error occurred on the report server. See t
he error log for more details. --> Transaction (Process ID 55) was deadlocked
on lock resources with another process and has been chosen as the deadlock vict
im. Rerun the transaction.
faultActor: http://engw03dmrs1/ReportServer/ReportService.asmx
faultNode:
faultDetail:
{http://www.microsoft.com/sql/reportingservices}ErrorCode: rsInternalErr
or
{http://www.microsoft.com/sql/reportingservices}HttpStatus: 400
{http://www.microsoft.com/sql/reportingservices}Message: An internal err
or occurred on the report server. See the error log for more details.
{http://www.microsoft.com/sql/reportingservices}HelpLink: http://go.micr
osoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostic
s.Utilities.ErrorStrings.resources.Strings&EvtID=rsInternalError&ProdNam
e=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=8.00
{http://www.microsoft.com/sql/reportingservices}ProductName: Microsoft S
QL Server Reporting Services
{http://www.microsoft.com/sql/reportingservices}ProductVersion: 8.00.878
.00
{http://www.microsoft.com/sql/reportingservices}ProductLocaleId: 127
{http://www.microsoft.com/sql/reportingservices}OperatingSystem: OsIndep
endent
{http://www.microsoft.com/sql/reportingservices}CountryLocaleId: 1033
{http://www.microsoft.com/sql/reportingservices}MoreInformation:
<Source>ReportingServicesLibrary</Source>
<Message msrs:ErrorCode="rsInternalError" msrs:HelpLink="http://go.mic
rosoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnosti
cs.Utilities.ErrorStrings.resources.Strings&EvtID=rsInternalError&ProdNa
me=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=8.00" xmlns:msrs= "http://www.microsoft.com/sql/reportingservices">An internal error occurred on t
he report server. See the error log for more details.</Message>
<MoreInformation>
<Source>.Net SqlClient Data Provider</Source>
<Message>Transaction (Process ID 55) was deadlocked on lock resource
s with another process and has been chosen as the deadlock victim. Rerun the tra
nsaction.</Message>
</MoreInformation>
{http://www.microsoft.com/sql/reportingservices}Warnings: nullCan you contact me offline? Replace ms with microsoft.
Thanks
Tudor
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tomasz" <Tomasz@.discussions.microsoft.com> wrote in message
news:B85F6392-B1B9-4FE0-B69B-D51E47C2EB4B@.microsoft.com...
> Reporting services is throwing deadlock exceptions which if retried (up to
10 times) sometimes succeed. When those exceptions happen Reporting Services
is coming to a halt waiting for the deadlock to resolve. Performance is
unacceptably degraded then.
> In my test I am trying to run multiple concurrent SOAP sessions with a
single admin level user account and in each session my process moves old
report definitions into historical folders (saves with unique names) and
then creates new report definition (again the report names are not
overlapping) and finally creates a snapshot of the new report.
> 1. Is there a way to avoid those deadlocks?
> 2. From the SQL Server log files it looks like there is some level of
pessimistic locking happening on some tables. Is that really necessary? It
seems like the operations that are being performed deal with independent
data elements that should not require any synchronization/serialization.
> 3. What level of parallelism is allowed when making concurrent calls to
the server on the same user id but within separate sessions? Are there any
restrictions?
> 4. Is there a place (maybe at MSDN) to report this as a real bug?
> I can also provide sql server trace log file with information about the
deadlock. No way to attach it here.
> ***********************************************************************
> SOAP Exception message when the deadlock occurs is as follows:
> ***********************************************************************
> Reason: An internal error occurred on the report server. See the error log
for m
> ore details. --> An internal error occurred on the report server. See the
error
> log for more details. --> Transaction (Process ID 55) was deadlocked on
lock res
> ources with another process and has been chosen as the deadlock victim.
Rerun th
> e transaction.
> 12:32:41,836 ERROR [STDERR] AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
> faultSubcode:
> faultString: An internal error occurred on the report server. See the
error log
> for more details. --> An internal error occurred on the report server.
See t
> he error log for more details. --> Transaction (Process ID 55) was
deadlocked
> on lock resources with another process and has been chosen as the
deadlock vict
> im. Rerun the transaction.
> faultActor: http://engw03dmrs1/ReportServer/ReportService.asmx
> faultNode:
> faultDetail:
> {http://www.microsoft.com/sql/reportingservices}ErrorCode:
rsInternalErr
> or
> {http://www.microsoft.com/sql/reportingservices}HttpStatus: 400
> {http://www.microsoft.com/sql/reportingservices}Message: An
internal err
> or occurred on the report server. See the error log for more details.
> {http://www.microsoft.com/sql/reportingservices}HelpLink:
http://go.micr
>
osoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostic
> s.Utilities.ErrorStrings.resources.Strings&EvtID=rsInternalError&ProdNam
> e=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=8.00
> {http://www.microsoft.com/sql/reportingservices}ProductName:
Microsoft S
> QL Server Reporting Services
> {http://www.microsoft.com/sql/reportingservices}ProductVersion:
8.00.878
> .00
> {http://www.microsoft.com/sql/reportingservices}ProductLocaleId:
127
> {http://www.microsoft.com/sql/reportingservices}OperatingSystem:
OsIndep
> endent
> {http://www.microsoft.com/sql/reportingservices}CountryLocaleId:
1033
> {http://www.microsoft.com/sql/reportingservices}MoreInformation:
> <Source>ReportingServicesLibrary</Source>
> <Message msrs:ErrorCode="rsInternalError"
msrs:HelpLink="http://go.mic
>
rosoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnosti
> cs.Utilities.ErrorStrings.resources.Strings&EvtID=rsInternalError&ProdNa
> me=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=8.00"
xmlns:msrs=> "An">http://www.microsoft.com/sql/reportingservices">An internal error
occurred on t
> he report server. See the error log for more details.</Message>
> <MoreInformation>
> <Source>.Net SqlClient Data Provider</Source>
> <Message>Transaction (Process ID 55) was deadlocked on lock
resource
> s with another process and has been chosen as the deadlock victim. Rerun
the tra
> nsaction.</Message>
> </MoreInformation>
> {http://www.microsoft.com/sql/reportingservices}Warnings: null
>

DDS Sends multiple emails. Bug?

Hi,
can anyone tell me what's going on here.
I BCC myself on all data driven subscriptions to ensure people are receiving
their subscriptions and there is no funny business going on.
In one case, the query for my data driven subscription returns one record.
So I should only get one email sent out. However, 2 emails are being
posted.
In other cases however, the correct emails are sent.
Is this a bug? Or is something happening that is causing RS to
occaisionally pick up duplicates?
thanks
MattDDS should not send out duplicate emails. The log files should give you
some hint if the same notification is being processed twice.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:#HDHciTlEHA.896@.TK2MSFTNGP12.phx.gbl...
> Hi,
> can anyone tell me what's going on here.
> I BCC myself on all data driven subscriptions to ensure people are
receiving
> their subscriptions and there is no funny business going on.
> In one case, the query for my data driven subscription returns one record.
> So I should only get one email sent out. However, 2 emails are being
> posted.
> In other cases however, the correct emails are sent.
> Is this a bug? Or is something happening that is causing RS to
> occaisionally pick up duplicates?
> thanks
> Matt
>|||I have this same issue, although mine isn't a DDS. Just a standard
subscription. I had one that sent to multiple people, but they were
getting two emails every morning so I disabled it to test out the
issue. I created a new subscription last night and when I came in this
morning, I had THREE emails waiting for me. All had the exact same
time stamp down to the second. I have no idea why it would deliver to
me three times, but this is obviously a big issue.
Does anyone have any insights into what causes this? Most of my
subscriptions work just fine. But there's just something off with a
few of these.
Alison
On Wed, 8 Sep 2004 08:14:43 +0800, "Matt"
<NoSpam:Matthew.Moran@.Computercorp.com.au> wrote:
>Hi,
>can anyone tell me what's going on here.
>I BCC myself on all data driven subscriptions to ensure people are receiving
>their subscriptions and there is no funny business going on.
>In one case, the query for my data driven subscription returns one record.
>So I should only get one email sent out. However, 2 emails are being
>posted.
>In other cases however, the correct emails are sent.
>Is this a bug? Or is something happening that is causing RS to
>occaisionally pick up duplicates?
>thanks
>Matt
>

DBNULL

I found a bug, if a textbox of a record row has dbnull value, all of following rows will hide the textbox, even they have non dbnull value. My current workaround is use ISNULL(col,'') AS col in query.

Is this by design or a bug?

If this is reproducible, it is a bug. I have not seen it, though. Which version and build of Reporting Services are you using?|||I am using the reportviewer in vs2005 beta2 to view local report.|||

We are not seeing this in current builds. I believe that it is resolved.

dbmssocn bug?

sometimes, if I connect DNS name for localhost running sql2000, (go to the
router and back) at a simple "SELECT * FROM table" statament I get a long
delay (application hangs for 10-20 second), and drops the connection.
When I change the datasource to "netbios" name, the same statament works
without trouble.
where is the bug? In dbmssocn? in ADO events (I use them...)?
cursorlocations? Why only sometimes?
What did you mean use DNS name and NetBIOS name ?
Are you connecting from a client PC? Does it work with Query Analyser ? Does
it timeout all the time.
"SRINGER Zoltn" <kecskemetisrac@.free-mail.hu> wrote in message
news:O7hVZOiBFHA.3840@.tk2msftngp13.phx.gbl...
> sometimes, if I connect DNS name for localhost running sql2000, (go to the
> router and back) at a simple "SELECT * FROM table" statament I get a long
> delay (application hangs for 10-20 second), and drops the connection.
> When I change the datasource to "netbios" name, the same statament works
> without trouble.
> where is the bug? In dbmssocn? in ADO events (I use them...)?
> cursorlocations? Why only sometimes?
>
|||another relevant information:
if I change cursorlocation to adUseClient, works...
... but I need serverside cursor especially via internet!
|||From the earlier posts, it sounds like you are could just
have some DNS issues in your network. Have you checked the
event logs for such? Have you tried an alias using the IP
address?
-Sue
On Mon, 31 Jan 2005 16:13:33 +0100, "SRINGER Zoltn"
<kecskemetisrac@.free-mail.hu> wrote:

>another relevant information:
>if I change cursorlocation to adUseClient, works...
>
>... but I need serverside cursor especially via internet!
>

dbmssocn bug?

sometimes, if I connect DNS name for localhost running sql2000, (go to the
router and back) at a simple "SELECT * FROM table" statament I get a long
delay (application hangs for 10-20 second), and drops the connection.
When I change the datasource to "netbios" name, the same statament works
without trouble.
where is the bug? In dbmssocn? in ADO events (I use them...)?
cursorlocations? Why only sometimes?What did you mean use DNS name and NetBIOS name ?
Are you connecting from a client PC? Does it work with Query Analyser ? Does
it timeout all the time.
"SRINGER Zoltn" <kecskemetisrac@.free-mail.hu> wrote in message
news:O7hVZOiBFHA.3840@.tk2msftngp13.phx.gbl...
> sometimes, if I connect DNS name for localhost running sql2000, (go to the
> router and back) at a simple "SELECT * FROM table" statament I get a long
> delay (application hangs for 10-20 second), and drops the connection.
> When I change the datasource to "netbios" name, the same statament works
> without trouble.
> where is the bug? In dbmssocn? in ADO events (I use them...)?
> cursorlocations? Why only sometimes?
>|||another relevant information:
if I change cursorlocation to adUseClient, works...
... but I need serverside cursor especially via internet!|||From the earlier posts, it sounds like you are could just
have some DNS issues in your network. Have you checked the
event logs for such? Have you tried an alias using the IP
address?
-Sue
On Mon, 31 Jan 2005 16:13:33 +0100, "SRINGER Zoltn"
<kecskemetisrac@.free-mail.hu> wrote:

>another relevant information:
>if I change cursorlocation to adUseClient, works...
>
>... but I need serverside cursor especially via internet!
>