Month: October 2014

Throttle, Throttle, disable the Throttle

We’ve been working through some issue’s on one of our SP2013 Farms related to List Throttling on a library in a particular site. Mark Rackley posted a very good blog yesterday about this issue and some ways to work around it. This is a great read for Admins, Dev, and End Users who may run into this issue. I just wanted to add that one of our SharePoint Admins here also found some powershell that will allow you to completely disable the throttle on a single SharePoint List. I don’t recommend this option as a fix for all, but maybe you have a list that is in the process of getting “fixed” or cleaned up, but you’ve gotta leave your throttle up for functionalities sake until it’s resolved. Our concern was the list throttle is a Web Application Level setting, so ANY list/library in ANY site in ANY Site Collection in your web app is affected and you don’t know what other lists have now creeped over the limit and  will break once you reduce the threshold back down to the recommended limit of 5000. So what was found is a powershell script that will disable the throttle for just 1 list, that way all of the lists can continue to adheed to the throttle limit while this 1 particular list can continue to function around it. Disable throttle for particular...

Read More

System.ServiceModel.EndpointNotFoundException was thrown while running PSCONFIG

I’ve been seeing a common issue while patching Project Server 2013 as of late. PSCONFIG will run but I’ll get this error before it all blows up. (Well not literally but you admins know what I’m talking about). An exception of type System.ServiceModel.EndpointNotFoundException was thrown. Additional exception information: There was no endpoint listening at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. I spent about 2hrs trying to figure out what was going on, then realized it can’t find a listening endpoint if WWW isn’t running… Yeah, it was that simple. So when you start psconfig make sure www is running. I just opened another powershell window and ran “net start w3svc” which will start the WWW service.  Seems to be happy after that and completes without and issue after that. (or at least without that endpoint listening error) I’ve only seen this on Project Server 2013 farms as of late, although I vaguely remember something similar while patching a SharePoint 2013 farm without Project Server on it. One thing to note: I wasn’t seeing this error in my cmd window when I was running this psconfig as such:  psconfig -cmd upgrade -inplace b2b -force, I had to add the -wait parameter and then it started showing up. Anyways hope that saves my...

Read More

Twitter Posts

Marrell Sanders @ MSIgnite