<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>WSS/MOSS - Common Issue - SQL Deadlocks during STSADM import operations </title><link>http://blogs.technet.com/stefan_gossner/archive/2008/11/26/wss-moss-common-issue-sql-deadlocks-during-stsadm-import-operations-or-when.aspx</link><description>In the last couple of weeks I have seen several cases where STSADM import operations failed with random exceptions. With other words: performing the same import into an empty site collection multiple times the import operation failed at different points</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: WSS/MOSS - Common Issue - SQL Deadlocks during STSADM import operations </title><link>http://blogs.technet.com/stefan_gossner/archive/2008/11/26/wss-moss-common-issue-sql-deadlocks-during-stsadm-import-operations-or-when.aspx#3162788</link><pubDate>Tue, 02 Dec 2008 13:22:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3162788</guid><dc:creator>Yaron ben shalom</dc:creator><description>&lt;p&gt;We have a similar problem only no Import is taking place- just our EmailRecieved event handler. We have SP1 and Infrastructure update installed. We are trying to create and change item permissions (not inherited) when a mail message is recieved and sometimes get deadlocks on stored procedures implementing security operations. The list already has several thousand items and probably a very large amount of specific permissions (dbo.RoleAssignment has about 4 million records). Do you have any ideas perhaps?&lt;/p&gt;</description></item><item><title>re: WSS/MOSS - Common Issue - SQL Deadlocks during STSADM import operations </title><link>http://blogs.technet.com/stefan_gossner/archive/2008/11/26/wss-moss-common-issue-sql-deadlocks-during-stsadm-import-operations-or-when.aspx#3162792</link><pubDate>Tue, 02 Dec 2008 13:31:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3162792</guid><dc:creator>Stefan_Gossner</dc:creator><description>&lt;p&gt;Hi Shalom,&lt;/p&gt;
&lt;p&gt;sorry, this cannot be answered easily.&lt;/p&gt;
&lt;p&gt;It would be required to analyze the deadlock in more detail and verify the code of your event receiver to isolate the issue.&lt;/p&gt;
&lt;p&gt;If you need assistance for this I would recommend to raise a support call with Microsoft support.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Stefan&lt;/p&gt;
</description></item><item><title>re: WSS/MOSS - Common Issue - SQL Deadlocks during STSADM import operations </title><link>http://blogs.technet.com/stefan_gossner/archive/2008/11/26/wss-moss-common-issue-sql-deadlocks-during-stsadm-import-operations-or-when.aspx#3174356</link><pubDate>Mon, 29 Dec 2008 16:25:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3174356</guid><dc:creator>Leon Zandman</dc:creator><description>&lt;P&gt;This happened to us. We managed to solve it by doing IISRESET's and retrying the import. Eventually the import succeeded, so it probably was a timing issue.&lt;/P&gt;</description></item><item><title>re: WSS/MOSS - Common Issue - SQL Deadlocks during STSADM import operations </title><link>http://blogs.technet.com/stefan_gossner/archive/2008/11/26/wss-moss-common-issue-sql-deadlocks-during-stsadm-import-operations-or-when.aspx#3226890</link><pubDate>Wed, 15 Apr 2009 23:32:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3226890</guid><dc:creator>Flo</dc:creator><description>&lt;p&gt;Hi Stefan,&lt;/p&gt;
&lt;p&gt;great article!&lt;/p&gt;
&lt;p&gt;What debugger did you use to set the breakpoint and where did you attached it? - directly to the process of the sql instance?&lt;/p&gt;
&lt;p&gt;I am actually not to familiar with debuggers - but want to give it a try.&lt;/p&gt;
&lt;p&gt;As far as I know you usually set a breakpoint in your application at a pice of code or datastructure where you want to stop the execution - but how do you know where this will be? I mean wouldn't you need to know when the deadlock occurs?&lt;/p&gt;
&lt;p&gt;Or do you set the breakpoint before the routine which will kill the deadlock starts its execution?&lt;/p&gt;
&lt;p&gt;And is this possible for a user without having in-depth information about the code and symbols of the process?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Flo&lt;/p&gt;</description></item><item><title>re: WSS/MOSS - Common Issue - SQL Deadlocks during STSADM import operations </title><link>http://blogs.technet.com/stefan_gossner/archive/2008/11/26/wss-moss-common-issue-sql-deadlocks-during-stsadm-import-operations-or-when.aspx#3226892</link><pubDate>Wed, 15 Apr 2009 23:37:49 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3226892</guid><dc:creator>Stefan_Gossner</dc:creator><description>&lt;p&gt;Hi Flo,&lt;/p&gt;
&lt;p&gt;I used WinDBG and set the breakpoint as follows:&lt;/p&gt;
&lt;p&gt;bp sqlservr!RaiseDeadlockError&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Stefan&lt;/p&gt;
</description></item></channel></rss>