Just got a forum error

[Shawn]

Server Error in '/' Application.
Could not continue scan with NOLOCK due to data movement.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Could not continue scan with NOLOCK due to data movement.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[SqlException: Could not continue scan with NOLOCK due to data movement.]
System.Data.SqlClient.SqlDataReader.Read() +176
FuseTalk.API.GetThreads(Int32 CategoryID, DateTime DateAgo, Int32 MaxRows, Int32 UserID, Int32 ForumID, Boolean PrivateTopic) +1924
_ASP.categories_ascx.__Render__control1(HtmlTextWriter __output, Control parameterContainer) +2154
System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +27
System.Web.UI.Control.Render(HtmlTextWriter writer) +7
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +72
System.Web.UI.Control.Render(HtmlTextWriter writer) +7
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
System.Web.UI.Page.ProcessRequestMain() +1926


Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032

 

[imported_Lucifer]

Hmm, no issues here.

 

[SynthDude2001]

I get those from time to time when clicking on threads (or the main forum listings). Seems very random though.

 

[Jason Clark]

This is a very random error, and its generated when SQL has an issue with a row level lock.

 

[allisolm]

Originally posted by: Jason Clark
This is a very random error, and its generated when SQL has an issue with a row level lock.

I for one feel so much better now that Jason's explanation has been provided. :shocked: (Allison backs slowly out of this thread and settles down with her copy of Computers for Dummies hoping that someday she will understand his sentence.) :brokenheart:

 

[Shawn]

Originally posted by: Jason Clark
This is a very random error, and its generated when SQL has an issue with a row level lock.

Which means? 😛

 

[Mark R]

Which means?

It means that fusetalk uses an optimisation that sometimes doesn't work.

Normally, if a thread is being updated (e.g. a new post is being saved) then any loads of that thread will be stalled until the save has completed. Because of all the stalling, this can slow things down.

Fuse talk uses an optimisation that disables the stalling, and allows a thread to be loaded even while it is being updated. This isn't actually a major problem, all that usually will happen is that the post being saved doesn't get displayed. But, very occasionally, the save will need to do something complicated (like get a bit more disk space, alter an index). In these exceptional circumstances, the load will crash with this error.