Fixing SharePoint

Hi There, Microsoft don't want our lives easy with simple configurations. :P I found error "Microsoft.SharePoint.SPException: Unable to properly communicate with the workflow service." in my ULS logs and tried to fix it. However, i noticed few Exceptions on top of this unexpected error which was the main cause of this error. Main Unexpected Error in ULS: I looked a bit top of it and found the Exception  "Microsoft.Workflow.Client.ScopeNotFoundException: Scope '/SharePoint/default/afb6b02c-a3e5-4dff-8e13-4930f4f3c76b' was not found.  HTTP headers received from the server - ActivityId: 7d0657c4-8ce0-4aaa-94b6-01a49312d14f. NodeId: PROD-SPAPP01. Scope: /SharePoint/default/afb6b02c-a3e5-4dff-8e13-4930f4f3c76b/711fc309-214c-4ae3-a36b-c055470a499e. Client ActivityId : dcbb459d-140f-60b2-3171-32aaaaec3a44. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.     at Microsoft.Workflow.Common.AsyncResult.End

Hi Mates, Here i am with another post. It took me almost 6 hours to install, troubleshoot and configure the Workflow Manager for Workflow Service Application in SharePoint 2013 properly. There are many blogs to configure it and most of them just cover the major steps not the errors that could occur. Update: Before you move ahead with installation, you must check this post otherwise you could get in trouble after installing it in your farm. I would really like you to visit this  blog . It helped me a lot to configure Workflow Manager. Thanks man. So, lets begin...! First thing to consider is, where to install the Workflow Manager in SharePoint 2013 Farm? So now I have 2 WFE, 2 APP Servers and 1 DB server. You should install it on APP servers only. In case you have less resources, you can install on WFE servers too but not on DB server. Lets keep that server away from hosting any services. Like SharePoint, Workflow Manager also makes itself a farm. For example,

Hi Mates, Although Microsoft provides enough information about the service applications from their configuration to their usage but still it will take time to summarize the functionalities of each service application.  Below table will give you a generic idea about the service application and its usage. I have compiled this list from Microsoft itself.  Tip: If you cannot copy the below table. Use the below file link to view or download from Google Drive. File:  SharePoint 2013 Service Applications and their responsibilities Service Application Usage [MSFT] Access Services 2010 Web Service Application Access Services 2010 is a service application that allows users to modify and publish in SharePoint Server 2013 an Access web database that was previously created in SharePoint Server 2010. App Management Service Application The App Management Service is responsible for storing and providin

Hi Mates, I'll try to cover the service accounts and permissions required to each service account for a setup in SharePoint. Microsoft recommends many different service accounts for different purposes like configuration, setup and service applications but it totally depends on your needs what you need to configure. Here are few of service accounts with their permissions required in AD, OS, SQL and their usage for a medium level architecture.  Tip: To fit this table on my blog page, i am decreasing the font size. If can't copy it from here, download or view the below Excel file that contains the same data. File: Planning Service Accounts And Permissions For SharePoint 2010 and SharePoint 2013 Installation Account Name Usage SQL Permissions AD Permissions OS Permissions AD Policy YourDomain\ SPSVCSetup Installation, Configuration Wizard and Remote Server Access, SharePoint Management Shell Domain u

Hi Mates, You set the Failover server to Web Applications easily while creation and most of the time for few Service Applications too. But how you'll set the Failover database server for the service applications that do not give you the option to set while their creation or configuration? This issue happened with me while establishing a SharePoint 2013 Farm. I think the same thing would happen with SharePoint 2010 so this article may be helpful for you. You can set the Failover SQL server for SharePoint service application databases or any other configuration pr content database by using PowerShell commands. Important: Before moving ahead, make sure the service accounts you are using for different services or SharePoint configuration must have the same permissions role in DB2 server as they have in DB1 server for a successful redirect of SharePoint in case of failure. They must have login permissions granted in DB2 server. Example below. DB1 Server: D

<<  Back to main post on Search Service Application Before After Step 1 : Clone the Active Search Topology # Clone $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step 2 : Get the ID of the Index Component to Remove # Get the Index Search Component ID To Remove $indexComponentID = ( Get-SPEnterpriseSearchComponent -SearchTopology $clone -Identity IndexComponent1).componentID Note : Use Get-SPEnterpriseSearchStatus -SearchApplication $ssa to see which components you have. Or use Get-SPEnterpriseSearchComponent -SearchTopology $clone Step 3 : Remove the original Index Component # Remove Search Component Remove-SPEnterpriseSearchComponent -Identity $indexComponentID .GUID -SearchTopology $clone -confirm : $false Step 4 : Activate Search Topology Again # Activate Search

<< Back to main post on Search Service Application Before After Script Step #1 - Clone the Search Topology $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step #2 - Get the ComponentID to Move # Get the Search Component ID To Move $queryComponentID = ( Get-SPEnterpriseSearchComponent -SearchTopology $clone -Identity QueryProcessingComponent1).componentID Note : If you don ' t know the query component name, use this command to find. Get-SPEnterpriseSearchComponent -SearchTopology $clone Step #3 - Remove the Search Component from the Original Server # Remove Search Component Remove-SPEnterpriseSearchComponent -Identity $queryComponentID .GUID -SearchTopology $clone -confirm : $false Step #4 - Activate the Search Topology Again # Activate Search Topology Again Se

<<  Back to main post on Search Service Application Before After Script Step #1 - Clone the Active Search Topology # Clone the active search topology $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step #2 - Add the New Search Component on the WFE # Add New Search Component $wfe = Get-SPEnterpriseSearchServiceInstance -Identity "PROD-SPWFE02" New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $wfe Note : If you see any error running the above command, run the below command first. Start-SPEnterpriseSearchServiceInstance -Identity $wfe Step #4 - Activate the Cloned Search Topology # Activate Search Topology Set-SPEnterpriseSearchTopology -Identity $clone You are Done...!

<< Back to main post on Search Service Application Before After Script !...Add a new Index Partition Server...! If you have not already started the Search Service Instance on the server, use this to start. $ssi = Get-SPEnterpriseSearchServiceInstance -Identity "PROD-SPAPP02" Start-SPEnterpriseSearchServiceInstance -Identity $ssi Get-SPEnterpriseSearchServiceInstance -Identity $ssi ---------------------------------------------------------------------------------------------------- Step 1 : Clone the Active Search Topology #Clone Active Search Topology $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step 2 : Create the New Index Component on the WFE #Create New Index Component for Index Partition 0 New-SPEnterpriseSearchIndexComponent – SearchTopology $clone -Se

<<  Back to main post on Search Service Application Before After !...Add a new Analytics Processing Component...! Step 1 : Get Search Service Instance and Start on New Index Server $ssi = Get-SPEnterpriseSearchServiceInstance -Identity "PROD-SPAPP02" Start-SPEnterpriseSearchServiceInstance -Identity $ssi In case your Search Service Instance is not Online, run below commands and wait Start-SPEnterpriseSearchServiceInstance -Identity $ssi Get-SPEnterpriseSearchServiceInstance -Identity $ssi Step 2 : Clone Active Search Topology $ssa = Get-SPEnterpriseSearchServiceApplication $active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa -Active $clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone – SearchTopology $active Step 3 : Add New Analytics Processing Component New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance $ssi Step 4 : Activate the Cloned Search Top