Fatal error 682 - what is it and how do you fix it?

Question

User592324952 posted

When trying to improve my app, I actually broke it (as you do) and came up with the error message reproduced herein. Any help in understanding the nature of the error and how to go about resolving it would be more than handy [:'(] 

Server Error in '/' Application.

---

Warning: Fatal error 682 occurred at Feb  3 2006  9:26PM. Note the error and time, and contact your system administrator.

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: Warning: Fatal error 682 occurred at Feb  3 2006  9:26PM. Note the error and time, and contact your system administrator.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): Warning: Fatal error 682 occurred at Feb 3 2006 9:26PM. Note the error and time, and contact your system administrator.] System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857242 System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734854 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838 System.Data.SqlClient.SqlDataReader.HasMoreRows() +150 System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout) +214 System.Data.SqlClient.SqlDataReader.Read() +9 System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping) +156 System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue) +153 System.Data.Common.DataAdapter.Fill(DataSet dataSet, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) +172 System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +175 System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +137 System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +83 System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1770 System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +17 System.Web.UI.WebControls.DataBoundControl.PerformSelect() +149 System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +70 System.Web.UI.WebControls.GridView.DataBind() +4 System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82 System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls() +69 System.Web.UI.Control.EnsureChildControls() +87 System.Web.UI.Control.PreRenderRecursiveInternal() +41 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360

Thank you in advance.

Answer 1

User592324952 posted

---

Warning: Fatal error 682 occurred at Feb  3 2006  9:26PM. Note the error and time, and contact your system administrator.

I have been digging deeper and found out that the error message number is for ERROR_LONGJUMP of course doing a Google on that turned up zip and MSDN only tell you its name, nothing about it or how to fix it.

Any 'code athletes' out there who know how to '_LONGJUMP'

Tia

Answer 2

User-1225738063 posted
Sounds like there is something SERIOUSLY wrong with your SQL Server.  Check the system event logs, and the SQL Logs, and see what it has to say happened at the time.  I'm guessing there was one or more events listed in one or both of those places.

Answer 3

User592324952 posted

Good thinking [:D] the server is remotely hosted and I have written to the support guys, who are always helpful.

Cheers.

Answer 4

User592324952 posted

Warning: Fatal error 682 occurred at Feb  3 2006  9:26PM. Note the error and time, and contact your system administrator.

Okay, by way of feedback, here is an update on Fatal error 682. Seeing there is Zero information on it on Google or MSDN other than to give it a name of LONGJUMP, which also turns up nothing, I decided to resolve the issue myself.

Essentially (I thought), okay the remote server is telling me it is broken, so I simply deleted the offending table, imported a new one, and that fixed the problem.

Of course, its nice to have it fixed, but why the crummy error message that really says nothing, and how is it that there is no information on this type of error? I feel that there was corruption in one record, which occurred for whatever reason and from that time onwards, that table was cactus and non-responsive. Strangely however I could access other records from within the same table, just not specific records...anyway, the moral to the story is almost the same as fixing broken hardware.

Reboot the computer - Golden Rule #1

Taking this analogy further with databases, the #1 rule seems to be:

Delete and reinstall from a backup [:P]