All About SharePoint and Other Technologies

Came across this error recently while creating a sub site using a custom template. "This web template requires that certain features be installed, activated, and licensed. The following problems are blocking application of the template: Feature Description Feature Scope Feature ID Problem ViewFormPagesLockDown Feature Site collection 7******3-0**4-4**d-9**a-7c175******4 Not activated" Solution: ViewFormPagesLockdown  is referring to the  Limited Access User Permissions Lockdown mode  feature. Please try to navigate to the site collection where you want to use the template to create a sub-site, then go to Site Settings>Site Collection Administration>Site Collection features to activate the  Limited Access User Permissions Lockdown mode  feature to see the result.

Get list of all solutions installed on the farm: [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") $farm=[Microsoft.SharePoint.Administration.SPFarm]::Local foreach ($solution in $farm.Solutions)         {             if ($solution.Deployed){                Write-Host($solution.DisplayName)                $solution.DisplayName >> c:\temp\test.txt             }                  } Get list of all features installed on the farm: [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") $farm=[Microsoft.SharePoint.Administration.SPFarm]::Local foreach ($feature in $farm.FeatureDefinitions)          {             if ($feature.Scope -eq "Farm" -and...

Thought of sharing my experience on an issue which took an entire day to resolve! Here it goes, Users unable to access the SharePoint site! Page keeps prompting for credentials thrice and returns a blank page. BUT site collection admin as well as farm account were able to access without any issue. Troubleshooting steps: 1. Checked for the event logs - Found nothing related 2. Restarted the security token service app pool. 3. Restarted IIS. 4. Cleared space in the drives. Nothing worked! 5. Performed Server reboot!  (1.App Server, 2.WFE, 3. DB Server) 6. Checked for the logs in all the servers. Error log in WFE server: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specif...

Issue:  Unable to upload files to SharePoint document library irrespective of the document size. Solution: When you delete items from a SharePoint site, they're sent to the site Recycle Bin. When you delete items from a site Recycle Bin, they're sent to the site collection Recycle Bin.  A SharePoint site collection administrator can view and restore deleted items from the site collection Recycle Bin to their original locations. If an item is deleted from the site collection Recycle Bin, or it exceeds the retention time, it is permanently deleted. 1. Click the gear icon and go to the "Site Settings" page. 2. Under the Site Collection Administration, click on "Recycle bin". 3. Delete the unwanted files.

SharePoint provides a feature to the users to "Share" the site or the content to other users or groups and grant permissions to the same. But sometimes an error is thrown "Only a limited set of people are allowed to share this content" while a share attempt is made in spite of the user having the desired permissions. Solution: Enable "Allow access requests" under the Access Requests Settings. Access Requests Settings could be found under Site Settings->Site permissions.

When you try to publish the SharePoint 2010 reusable or list workflow using SharePoint designer 2013 you will get following exception in UI. This could be because during the workflow publishing phase, SharePoint will create few temporary files under the temp folder. As part of the clean-up process the w3wp process will delete these temporary files at a later stage. Sometimes the process deletes the folder itself instead of deleting the files alone due to which the workflow may fail to publish. Solution: 1. Navigate to C:\Users\<service-acct>\AppData\Local\Temp on both the server (WFE1 and WFE2) 2. Create a text file inside the temp folder and in the properties check read-only option. 3. Reset iis /noforce 4. Publish the workflow. If the temp folder is not available, please create one and add the file inside it. 

Central Administration in SharePoint Server is where you go to perform administration tasks from a central location.  Sometime we encounter the "Service Unavailable" error message while trying to access the central admin.  Please follow the steps below to resolve the issue. 1. Open the IIS.  2. Expand the server name. 3. Click on Application Pools. 4. Please check whether the Central Admin application pool is started. If not, please start. 5. Also check whether the Central Admin site is started by expanding the "Sites". Sometimes the issue persists even after starting the application pool and the site. In that case, please go to the application pool. Click on advanced settings-> Identity->Please enter the credentials in the App Pool Identity and save.