Melick's Blog

“This view cannot be displayed because it exceeds the list view threshold (5000 items) enforced by the administrator. To view items, try selecting another view or creating a new view. If you do not have sufficient permissions to create views for this list, ask your administrator to modify the view so that it conforms to the list view threshold.” And if you are more dig in to it, the error will be occur in your Web Parts Custom Scripts SharePoint Apps CAML Queries Which is related to that list. First we have a look why this is happening. The Live View Threshold is item count which is limited by SharePoint Administrator to process by SharePoint server at a time. Further elaborating when you are viewing or query (CAML, ODATA, and REST) against the list SharePoint will process the entire set of items to get the required results even though you have mentioned limits or filters unless it is not indexed. Thus when it is exceeding threshold limit (5000 default) SharePoint will throw ...

This article breaks into three sections. Identify and Cause Add Exception to Strict Name Checking Disable Loopback Identify and Cause There are many reasons to happen this but most of the time it will happen when you change the Access mapping to match your domain. For an example you might have webwfe01 as your web application in your default zone. And if you change that to www.sampleweb.com this may be occurred for Windows Users. This is because by not having Fully Qualified Domain name specified is not matching with the local machine. For an Example, Your local machine can be in a domain myorg.com and the specified Mapping is sampleweb.com Thus this will cause LoopBack check which it true by design for security reasons. Microsoft specifies two methods to resolve the issue. Disable Strict Name Checking Disable Loopback Check REF: https://support.microsoft.com/en-us/help/896861/you-receive-error-401.1-when-you-browse-a-web-site-that-uses-integrated-authentication-and-is-...

  Quick Tip : I have configured the membership provider to work with ASP.NET application which is going to deploy in to the SharePoint. But when I used FormsAuthentication.SetAuthCookie() to set the Authentication Token it doesn’t work for me. I have tried disabling anonymous authentication but still didn’t work. Then I changed the FormsAuthentication.SetAuthCookie() method to following set of lines and ultimately worked. FormsAuthenticationTicket ticket = new FormsAuthenticationTicket(txtUserName.Value, false , 60); string encTicket = FormsAuthentication.Encrypt(ticket); Response.Cookies.Add( new HttpCookie(FormsAuthentication.FormsCookieName, encTicket));