<< Back To All Blogs
SharePoint Error Craziness: Volume 1
Sunday, February 1st, 2009
SharePoint is well-known for not handling errors well, specifically not describing what actually occurred, but it often also returns an error that seems to be descriptive but is really the side effect of another issue.
The error I am speaking about in particular, is:
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
This error can be received in a number of different situations, namely the situation that you pass an invalid GUID, or an incorrectly-formatted GUID. You will also receive this while trying to delete a list or document library if the list does not exist, which is something that was stumping me for quite some time. Some of the other calls will properly return an error that the item does not exist, but in this case it does not.
I hope Microsoft fired whoever worked on their SharePoint web services team, because a monkey with a typewriter could have done better.
That's all for now, I have more lovely errors to explain in the near future, but that's all for the night.
Sharepointin' Tom Out.
SharePoint STSADM AddSolution Object Reference not set to an Instance of the Object error
Resolving "Tracing Service lost trace events" in MOSS 2007
Fixing Access Denied While creating a new page in MOSS/WSS
Fixing "Error in loading DLL" in SharePoint
Currently no comments.
Add A Comment
Email Address: (not public, used to send notifications on further comments)
Enter the text above, except for the 1st and last character: