Hi All,
I recently got a bug when I was navigating to "Site Actions" >> Manage Content and Structure and Boom! . An error was thrown:
BUG:
-------------------------------------------------------------------------------------------------------------
Exception from HRESULT: 0x81070215 at Microsoft.SharePoint.Library.SPRequestInternalClass.GetViewsSchemaXml(String bstrUrl, String bstrListName, Boolean bFullBlown, ISP2DSafeArrayWriter p2DWriter, Int32& plDefaultViewIndex) at Microsoft.SharePoint.Library.SPRequest.GetViewsSchemaXml(String bstrUrl, String bstrListName, Boolean bFullBlown, ISP2DSafeArrayWriter p2DWriter, Int32& plDefaultViewIndex)
-----------------------------------------------------------------------------------------------------------
A very nasty error. But the error code (HRESULT: 0x81070215) reminded of the error which I had seen before. Its was in my blog.
It happens when open a list, either the list is has not properly been deleted and is in a corrupted state. I have revisited my site and found that one of my custom list named "Annotations" was in corrupted state. Or may be I had deleted the solution but not deactivated on the site feature.
FIX:
Although the help message displays information about using the forcedeleteweb operation, you have to use forcedeletelist instead. The syntax is:
stsadm.exe -o forcedeletelist -url <url>For e.g. if the list called as "Annotations" has corrupted just fire up this command:
stsadm -o forcedeletelist -url http://server/apac/lists/annotations
For more info:
http://bloggingabout.net/
http://technet.microsoft.com/
Just fire the stsadm command and activate the feature.
Now, again go to "Site Actions" >> "Manage Content and Structure".
It will work fine.
Cheers,
--aaroh
3 comments:
Hey,
Thank you for the useful information!
Cheers from Portugal
You just saved me a LOT of time Aroh, thank you for this post! You prompted me to check all my list instances which were deployed from code in Visual Studio.
And, indeed, there was a list instance causing the issue. I redeployed the code, which meant I could then go and manually delete the list instance and list in the browser. Problem solved. Thanks again!
@Christine: good that it solved your issue ..
Post a Comment