Hi,
If you deployed SharePoint 2013 and your user logon name accounts have space characters, the users will receive "Sorry, something went wrong Correlation ID: 00000000-0000-0000-0000-000000000000" if they are accessing specific sections
of your sites.
I am describing a little bit how the problem can be reproduced. I have:
- SharePoint 2013 with CU August 13 2013 (15.0.4535.1000) – latest CU available for SharePoint 2013 (at this moment).
- User Profile Synchronization Service properly configured.
- One user account who has space characters in the value of sAMAccountName (e.g. Smith John)
- One user account who doesn’t have space characters in the value of sAMAccountName (e.g. Smith.John)
If you authenticate to SharePoint 2013 using "ITECH\Smith John" and go to "Newsfeed" -> "I'm following" section and click to get the sites / documents you are following, SharePoint will return "Sorry, something went
wrong Correlation ID: 00000000-0000-0000-0000-000000000000".
In the SharePoint logs you will get:
"Application error when access /personal/itech_smith%20john/Social/Sites.aspx, Error=A potentially dangerous Request.Path value was detected from the client (%).
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)"
"System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (%).
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)"
"Getting Error Message for Exception System.Web.HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (%).
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)"
If you look carefully, the URL address looks like "http://yourdomain/personal/itech_ smith%2520john/Social/Sites.aspx". The problem is the %2520 which
normally should be %20.
If you manually correct the URL (http://yourdomain/personal/itech_ smith%20john/Social/Sites.aspx) you will get to the correct page.
If you authenticate to SharePoint 2013 using "DOMAIN\Smith.John" you will not encounter the issue described above.
Is it possible Microsoft support to check and come with a patch for this issue?
Best regards,
Iftode Viorel