Fixing SharePoint

It took almost my two days to search a way for hiding the "Discussion Board" area from a blank site. Main target was to not allow the users to create a Discussion Board in the site. I tried few ways but did not work as required. So the final thing that worked was the Powershell Scrip. I used the below script (found by one of my colleague) and it worked perfectly fine. Hope it will save someone's day. Regards, Before: After: Add-PSSnapin microsoft.sharepoint.powershell $web = Get-SPWeb "http://yoursitename/fullURL" $web.Features | ForEach-Object {   Write-Host $_.Definition.Id "---" $_.Definition.DisplayName   IF ($_.Definition.DisplayName -eq "DiscussionsList")   {     Disable-SPFeature -Identity $_ -URL "http://yoursitename/fullURL"     Write-Host "Disabled feature DiscussionsList"   } } Write-Host "------------------------------" Read-Host "Press any button"  Ho...

Error: I have encountered this issue after splitting up my content sources. However there could be many other reasons for this issue. This issue occurs when your SharePoint Search Index got corrupt and does not respond to your search query in a proper fashion. Resolution: Resetting the Search Index and running the full crawl again fixed the issue. You should also shrink Search Database in DB Server to free up the consumed space by the Search DB after resetting the Index. It should be in below order. 1. Reset Search Index ( Read More )  2. Shrink the Search DB ( Read More ) 3. Run full Crawl ( Read More )

Depending on farm size and topology, it will require you ~2 or more hours to change password and test the SharePoint farm and services after password rotation. Once the passwords has been changed in AD, you'll need to update passwords in farm ASAP to minimize the downtime. Mentioning few places in SharePoint where you must update service account with a new password after password rotation.   Browse your web applications one by one to ensure that all are up and running. Run User Profile Service and Start Incremental Crawl to make sure it works fine. Depending on your farm needs, test the other rest of applications and services. Expected Error Details Workaround Central Administration or Sites Down. Error: Cannot connect to the configuration database. Change passwords for SQL Server (MSSQLSERVER) and SQL Server Agent (MSSQLSERVER) services in DB Server Services Console Services down in Services Console...

Recently i encountered that one of  SharePoint resource is in 2nd highest accessed item from one of my Site Collection. It was _layouts/clientbin/mediaplayer.xap file and it was very new to me that where MediaPlayer.xap file is actually being used. Never seen this before in any of my SharePoint farm. Thanks to Microsoft's Savoeurn Va for replying to a user here . Its actually get called for SilverLight calls. Some of your page in your farm might be using some SilverLight plugin and that's calling _layouts/clientbin/mediaplayer.xap file. For confirmation, go to that target page, disable SilverLight in your IE browser, refresh the page and test it. If it threw an error or warning then your page is using some sort of  SilverLight plugins. Note: In my case it was Content Query Webpart which was calling Silverlight. I found this very nice article below on how to disable this Silverlight call. http://toddbaginski.com/blog/controlling-the-silverlight-media-player-in-a-c...

Using below code, you can set "Request Access" Email ID in SharePoint. It worked for SharePoint 2010 (could be working for SharePoint 2013). $path = "C:\Logs.txt" $contentWebAppServices = (Get-SPFarm).services | ? {$_.typename -eq "Microsoft SharePoint Foundation Web Application"} # Get All Web Application foreach($webApp in $contentWebAppServices.WebApplications) { add-content -Path $path -Value $webApp.name -Force if($webApp.name -ne "") {     foreach ($SPsite in $webApp.Sites)     {     add-content -Path $path -Value $SPsite.URL -Force        # get the collection of webs        foreach($SPweb in $SPsite.AllWebs)         {     add-content -Path $path -Value    $SPweb.URL -Force               # if a site inherits permissions, then the Access request ma...

Hi There, Using below code, you can disable or hide or remove "Request Access" option from SharePoint. It worked for SharePoint 2010 (could be working for SharePoint 2013). $contentWebAppServices = (Get-SPFarm).services | ? {$_.typename -eq "Microsoft SharePoint Foundation Web Application"} # Get All Web Application foreach($webApp in $contentWebAppServices.WebApplications) { Write-Host $webApp.name      foreach ($SPsite in $webApp.Sites)     {        # get the collection of webs        foreach($SPweb in $SPsite.AllWebs)         {               # if a site inherits permissions, then the Access request mail setting also will be inherited              if (!$SPweb.HasUniquePerm)          ...

Recently i faced this issue that "Readers" (people with read permissions on site) were unable to see "Site Actions" button on site but it was working fine for Contributors and above levels. Readers were able to see the ribbon on other sites even any subsite in the problematic site. I checked for Master Pages, Page Layouts or any custom code like CSS or JS made by any champion in my team which can hide it from Readers but everything looked fine to me. So i decided to nail it. No "Site Action" Visible Following the basic rule "Divide a problem into sub-problems and then solve one by one" i started checking for permissions and finally found the issue. The reason was ,my business users (who were not SP professionals) played with site settings and permissions configurations that resulted in "Site Actions" visibility lost for readers. I followed the below steps and issue resolved for me. Click on "Site Actions -> Site...