If you attempt to set an Alert on a specific Discussion Post, like this: You will end up a yellow screen of death, like this: [crayon-529245f16fca6929960484/] This bug appears to be ‘long standing’, and still exists as of the October 2013 Cumulative Update for SharePoint Server. On the process of setting up the Alert, a process gets the Content Type ID of the Folder. We start in the Microsoft.SharePoint.SPViewContext.FolderContentTypeId method, executing: [crayon-529245f16fcc3501228304/] From there, entering GetValueFromUrlOrViewState, we enter: [crayon-529245f16fccd942837811/] Within this method, here are the key variable values: [crayon-529245f16fcd8389896544/] From there, we come back to the Microsoft.SharePoint.SPViewContext.FolderContentTypeId method and further on down, execute: [crayon-529245f16fce2638082976/] Where valueFromUrlOrViewState equals the variable “str”. So you want to generate a new SPContentTypeID object with a hex string and a URL. This is where things “go wrong”. [crayon-529245f16fcea112715408/] We’re calling SPUtility.Hex where chArray has invalid characters (values outside of 0 – 9 and A – F) in it. The first one that gets hit is the “,” (comma) character. SPUtility.Hex has no return statement, so it throws a System.ArgumentException. This particular bug will require Microsoft to resolve it. I’ve opened a PSS case on it.
↧