Skip to content

ColName attribute causes HRESULT: 0x80040E14 and other misterious errors

March 1, 2011

We are using a SharePoint list that is created from a custom list definition. This list contains 12 columns that are all of Numeric type.

When adding a new item to the list programmatically we encountered the following issues:

  1. When we assign value to all the 12 Numeric fields, the following exception is thrown:

    Exception from HRESULT: 0x80040E14
    at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean
    bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish)….

  2. When assigning value to all but one particular Numeric field, the update runs without error, but the values of the listitem fields are mixed up. The field that was not assigned a value gets the value of an other field of the list.

After troubleshooting for several hours it turned out that something is wrong with the list definition. Some fields of the list contained the same ColName attribute. The SharePoint Work Acceleration Toolkit (SWAT) was a great help finding this out, as these attributes got into the list definition when reverse engineering a list and had already been deleted.

The resolution of the problem was not straightforward. Redeploying the list definition without the ColName attributes didn’t help. The same issue was present in the list that were created by the new list definition.

The solution that finally worked was to

  1. remove all affected fields from the list definition
  2. redeploly the stripped list definition
  3. add the fields back to the list definition
  4. replace the IDs of the fields with new GUIDs
  5. redeploy the list definition

After this procedure the list was working fine.

Advertisements

From → MOSS 2007, WSS 3.0

One Comment
  1. Nagaraj permalink

    HI
    i am also getting the same error i have done application pages coding in wss 3.0 for creating new list item i am getting this error and even for updating the list item also and if run the cmd as mentioned above for Windows SharePoint Services 3.0 it says
    “you must specify either the inplace parameter or by sidebyside parameter in the command prompt”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: