Short version – This was fixed with the following procedure:

1. Go into List Settings for the list in question
2. Under columns I clicked the Column Ordering link
3. Changed Title’s position from Top to be 1 (It was 2 from the top in my case)

For a list of common MSDN HRESULT values, see Common HRESULT Values on MSDN. Locating HRESULTs HRESULTs are returned in an eight-digit hexadecimal form (80004005) or a 10-digit decimal form (–). The list below describes the HRESULTS that may be returned by the COM object of a local Magic xpa engine. The following HRESULT values are the most common. More values are contained in the header file Winerror.h. Assume you have a SharePoint list item which is storing data in two rows and row ordinal. So first few columns will be stored in Row 1 and next set will be stored in Row 2. But when you change the order of the items which is already stored it may be false to two different row ordinals and might cause the issue. This document provides the common usage details of the HRESULTs; individual protocol specifications provide expanded or modified definitions. Most values also have a default message defined, which can be used to map the value to a human-readable text message; when this is done, the HRESULT value is also known as a message identifier.

Kentucky Derby 2020 Results List

Explanation – This list had a lot of columns (60 to be exact). After further research there’s something unique that happens when you have 16 columns in a list. Any time someone creates 16 columns in a list and then sets any column that was created in position 16+ to position 1 (It doesn’t matter the type of column) in the list you will receive that error.

2017 Nfl Draft Results List All Rounds

Technical Explanation: The problem here is because SharePoint utilizes SQL server row wrapping to allow a maximum number of columns in a SharePoint list where SharePoint Server will create several rows in the database when data will not fit on a single row. This is controlled via the property RowOrdinal, which identifies which row a certain field should be stored. When RowOrdinal = 0, the field is stored in the first row of the row set for that list item and when RowOrdinal = 1, the field is stored in the second row of the row set for that list item.

Lets take a look at this in action:

Hresult Values List

1. Save list as template, open Manifest.xml
2. Find the <Fields> Section (Notice The RowOrdinal values??)<FieldName=”Test_Task” Version=”2″ DisplayName=”Test Task” Type=”Choice” RowOrdinal=”1″ ColName=”nvarchar35″ StaticName=”Test_x0020_Task” SourceID=”{f62365c4-32fa-4f67-a714-963aa49a3f8a}” ID=”{402b7fff-701c-45b4-bc06-ffaf51dd3fe8}” FillInChoice=”FALSE” Format=”Dropdown” Indexed=”FALSE” EnforceUniqueValues=”FALSE” Required=”TRUE”><FieldName=”Title” Version=”2″ DisplayName=”$Resources:core,Title;” Type=”Text” RowOrdinal=”0″ MaxLength=”255″ Indexed=”FALSE” EnforceUniqueValues=”FALSE” ColName=”nvarchar1″ FromBaseType=”TRUE” StaticName=”Title” SourceID=”http://schemas.microsoft.com/sharepoint/v3” Required=”FALSE” ID=”{fa564e0f-0c70-4ab9-b863-0177e6ddd247}”/>

Errors in ULS Logs:

System.Data.SqlClient.SqlException: Cannot insert the value NULL into column ‘tp_DocId’, table ‘SP2010_Content_10030.dbo.AllUserData’; column does not allow nulls. INSERT fails. The statement has been terminated.

This issue is similar to http://blogs.msdn.com/b/allenwang/archive/2012/05/21/sp2010-survey-list-error-and-event-id-5586.aspx