Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I can't seem to edit any list item in a particular list. The stack trace points to the AddOrUpdateItem() method (below). I can't think of any recent changes made to the content type of list definition that would cause it and this list was fine up until recently (no distinctive tasks performed, other than a few item edits, worth noting):

<nativehr>0x8000ffff</nativehr><nativestack></nativestack>

Stack Trace:

[COMException (0x8000ffff): <nativehr>0x8000ffff</nativehr><nativestack></nativestack>]
   Microsoft.SharePoint.Library.SPRequestInternalClass.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, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback) +0
   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, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback) +406

I'd like to give a bit more context but I honestly don't know what else to troubleshoot.

Note, this isn't item specific.

The logs don't reveal anything other than what the stack trace does.

Any pointers in the right direction greatly appreciated.

Please also note - this has happened before. Tearing down the list and rebuilding and repopulating it resolved it, but that isn't an issue now due to content.

share|improve this question
1  
does the list have any event receivers? –  TZHX Dec 6 '12 at 15:19
    
this might give you some insight social.msdn.microsoft.com/Forums/en/sharepointdevelopmentlegacy/… –  ali Sharepoint Dec 6 '12 at 15:56
    
No, no recent receivers. Thank you both for the feedback. –  DeeMac Dec 6 '12 at 16:13
    
This error CAN be a serious one and caused by a corruption in a DLL or Data. I would check your windows logs for warnings and errors just in-case and get a copy of something like hdtune pro and do a scan of your harddisk. Otherwise it may be a broken index on the list, or something a lot less serious, but never take a 0x8000FFFF lightly, it means corruption. –  Hugh Wood Dec 6 '12 at 16:13
2  
Oh I've seen this. Try an IISRESET, that helps clear stuff out. If not, I had to wipe the list. –  David Lozzi Dec 6 '12 at 18:31

2 Answers 2

up vote 1 down vote accepted

Same issue i faced recently, but resolved with lot of research.

The above mentioned issue will come duplicate columns exist in your List schema file. verify your List schema once.... Still the problem exist, follow the below trick

verify your "ColName" attribute for every Field, it should be UNIQUE for every Field. because Colname attribute defines the mapping of the field to the physical storage name for this field. This must be a valid name in the underlying database and must be identical to the name used in the database table.

For more details :

http://msdn.microsoft.com/en-us/library/ms437580.aspx

So please mention unique ColName for every Field in the List schema, but my suggestion is in the list schema file dont mention this Colname attribute for the List Fields, SP will take care of this.

Hope this helps... Happy Coding :)

share|improve this answer

Agreeing and summarising both Hugh and David above, this is corruption somewhere along the line, and sometimes an IISReset fixes it.

The corruption may be within the list itself or in a column defintion - so make sure you have a recent content database backup handy before you delete the list.

I'd recommend recreating the list and somehow get the items out of there and into the new one (try with Datasheet view to copy/paste items across first).

Before you do wipe the list, save it as a template (with content, if it's not too big), and see if you can move it and replicate it on a different environment. This will absolutely prove that the list is at fault, and nothing else.

HRESULT exception codes like that are spat out back by the COM server underlying SharePoint, and normally we (developers) see them if we have a malformed CAML Query. 0x8000FFFF doesn't ALWAYS mean corruption, it's just a completely untrapped error (or 'catastrophic failure'). Causes for it when updating a list could be a wide range of things, including malformed Calculated Column formulas, malformed User fields, or someone somehow managing to inject some kind of code into a field that's not properly escaped before being fed to the database.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.