New answers tagged

1

Over time, the content database can accumulate objects that are corrupted. An object that should have a parent object might be orphaned; an object that should have a child object might not have one. These things can happen due to a variety of misfortunes: power failures, lost connectivity, application timeouts, software faults, or just plain bad luck. To ...


1

The command as you have it shown will list the items that would be repaired by the command, but will not perform any repair action. Change the $false to $true to actually go ahead with the repair operations once you've analysed the output from the original command. Andy


1

The SharePoint Feature Administration and Clean Up Tool available at http://featureadmin.codeplex.com/ usually does a good job of cleaning these up. I usually use the script at http://etienne-sharepoint.blogspot.co.uk/2011/10/solving-missingsetupfile-errors-from.html to deal with missing setup file issues (just remember to add the $file.delete() line when ...


1

please check your IIS Server Security token service .If it is stopped click start option or try to restart the service. I have faced same issue long back and this option worked me. if it is not working for your scenario let me know.


1

I've had this problem before. You probably need to run the PowerShell command Get-SPProduct -Local Also I would try to run the PSConfig on all servers. More here: http://thesharepointfarm.com/2013/12/the-magic-of-get-spproduct-local/


0

I had the same symptoms on a SharePoint 2013 On Premise SP1 and October 2015 CU problem was I ensured the user using the windows login name: domain\username e.g: var user = clientContext.Web.EnsureUser("dev\administrator"); with this user, IsSiteAdmin returned False (he was definitely directly added to site collection admins) also with this user I did ...


1

Instead of using the server name as the domain name of your incoming email, use an Internet one. Let's say your company domain name is company.com: Register sharepoint.company.com (or anything else) as an MX entry in DNS. Make it point to your company mail server On the mail server (let's assume Exchange), create a connector to route all emails sent to ...



Top 50 recent answers are included