Monday, January 26, 2009
Thursday, January 15, 2009
How did it happen?
I tried to edit an existing SPListItem through the Web UI.
I reach for my search bar and find blah blah Violation of PRIMARY KEY constraint blah Backup blah Restore.
Shouldn't the API gracefully handle such an error?
Time to dig through the logs.
Event logs say nada but I found the following in SharePoint logs.
Normally I wouldn't be so worried but in this case it now happens a lot with separate items in this list.
Thinking maybe something has become corrupted I've tried a stsadm -o backup and restore into a fresh site collection in a fresh web application using a fresh content database, but hey the issue has been restored into the new site collection.Any help and or suggestion would be greatly appreciated, what a way to start the new year at work.
On a great note my holiday was "O" for awesome! Chur Chur.