Wednesday, January 29, 2014
SharePoint 2013: Set-SPEnterpriseSearchTopology : Could not connect to the HostController
Description
After configuring all of the Enterprise Search components for a new Search Topology, the activation of the Search Topology fails.
Error Message
PS C:\> Set-SPEnterpriseSearchTopology -Identity $SearchTopologyName
Set-SPEnterpriseSearchTopology : Could not connect to the HostController
service on server SERVERNAME Topology Activation could not be started.
At line:1 char:1
+ Set-SPEnterpriseSearchTopology -Identity $SearchTopologyName
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Offic...tSearchTopology:
SetSearchTopology) [Set-SPEnterpriseSearchTopology], InvalidTopologyExcept
ion
+ FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchT
opology
Troubleshooting Steps
In Services.msc and in Central Administration, verified the Search Host Controller Service is "Started" on all SharePoint servers in the Topology.
Restarted the Search Host Controller Service
Solution
The Search Host Controller Service was running under the identity of an Application Pool Account, which did not have the required permissions to establish the connection.
In Central Administration, Security, Configure Service Accounts, changed the Service Account assigned to the Search Host Controller Service, to the SharePoint Farm Account. Ran the activation again, and it was successful.
References
Microsoft TechNet (2013). Change the default search topology in SharePoint Server 2013. Retrieved January 29, 2014 from http://technet.microsoft.com/en-us/library/jj862356.aspx
SharePoint 2013: How to Rename the Search Service Application Using PowerShell
Description
This post explains how to change the name of the Enterprise Search Service Application using PowerShell.
Key Words
PowerShell, Enterprise Search Service Application.
Solution
1. Set a variable
$SvcAppSearch = Get-SPEnterpriseSearchServiceApplication
2. Verify the current name
$SvcAppSearch.name
3. Change the name
$SvcAppSearch.name = "SPEnterpriseSearchServiceApplicationNewName"
4. Update
$SvcAppSearch.Update()
5. Verify the new name in PowerShell
Get-SPEnterpriseSearchServiceApplication
6. Run IIS Reset on the Web server which is hosting Central Administration
7. Verify the new name in Central Administration
Central Administration, Application Management, Manage Service Applications
References
Microsoft TechNet (2013). Get-SPEnterpriseSearchServiceApplication. Retrieved January 29, 2014 from http://technet.microsoft.com/en-us/library/ff608050.aspx
SharePoint 2013: How to Configure the Search Service Application using PowerShell
Description
This post describes how to configure the SharePoint Server 2013 Search Service Application using PowerShell.
In this example, there is one Database Server (SERVER01), one Web Server (SERVER03), and one Application Server (SERVER04).
Solution
This solution is for a small farm environment that has one Database Server, one Web Server, and one Application Server. The steps below will result in a complete Search Topology.
The steps provided do not represent an automated script that you would copy and paste into a window and run all at once. Instead, the steps are intended to be run manually, one at a time, in the PowerShell window. The post is written this way on purpose and provides a way to step through each cmdlet one at a time.
If you have a different server topology or if you would prefer a fully automated script to provision the Search Service Application, then I recommend that you look at the References section and possibly utilize one of the more sophisticated examples that exist in the community knowledge base.
Before Starting...
Ensure that the Service Account to be used for the Service Application Pool exists and has been registered in Central Administration as a Managed Account
Ensure that the Host Controller Service in Central Administration is registered under a Service Account that has adequate permissions to activate the Search Topology (e.g. Farm Account)
1. Prepare the PowerShell Session
Open the PowerShell window as Administrator.
Clear-Host
Set-ExecutionPolicy unrestricted
Respond Y to confirm
Get-PSSnapin -name Microsoft.SharePoint.PowerShell -EA SilentlyContinue
2. Determine Naming Convention and Set Initial Variables
Set the Variables
$Svr01 = "SERVER01"
$Svr03 = "SERVER03"
$Svr04 = "SERVER04"
$SvcAppPl03 = "SvcApp_SPServiceApplicationPool_03"
$SvcAppSrch = "SvcApp_SPEnterpriseSearchServiceApplication_01"
$SvcAppSrchPrxy = "SvcApp_SPEnterpriseSearchServiceApplication_01_Proxy_01"
$SvcAppDBSvr = "SERVER01"
$SvcAppDB = "SvcApp_SPEnterpriseSearchServiceApplication_01_DB_01"
$SvcAppSrchAdmnCmp = $SvcAppSrch | Get-SPEnterpriseSearchAdministrationComponent
$ESSI03 = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER03"
$ESSI04 = Get-SPEnterpriseSearchServiceInstance -Identity "SERVER04"
$QSSN03 = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity "SERVERN03"
$QSSN04 = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity "SERVERN04"
$IndexLocP = "I:\IndexPrimary"
$IndexLocR = "I:\IndexReplica"
3. Start the Search Service Instances
Start-SPEnterpriseSearchServiceInstance -Identity $Svr03
Start-SPEnterpriseSearchServiceInstance -Identity $Svr04
4. Start the Query and Site Settings Service Instances
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -identity $QSSN03
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -identity $QSSN04
5. Create the Search Service Application
New-SPEnterpriseSearchServiceApplication -Name $SvcAppSrch -ApplicationPool $SvcAppPl03 -AdminApplicationPool $SvcAppPl03 -DatabaseName $SvcAppDB -DatabaseServer $SvcAppDBSvr
6. Set the Search Admin Component
Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance $Svr04
7. Create and Configure Search Topology 02
$SrchTop01 = Get-SPEnterpriseSearchTopology -SearchApplication $SvcAppSrch
$SrchTop02 = New-SPEnterpriseSearchTopology -SearchApplication $SvcAppSrch -Clone -SearchTopology $SrchTop01
8. Create the Search Admin Component
New-SPEnterpriseSearchAdminComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr04
9. Create Search Content Processing Components
New-SPEnterpriseSearchContentProcessingComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr04
New-SPEnterpriseSearchContentProcessingComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr03
10. Create Analytics Processing Components
New-SPEnterpriseSearchAnalyticsProcessingComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr04
New-SPEnterpriseSearchAnalyticsProcessingComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr03
11. Create Search Crawl Components
New-SPEnterpriseSearchCrawlComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr04
New-SPEnterpriseSearchCrawlComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr03
12. Create Search Query Processing Components
New-SPEnterpriseSearchQueryProcessingComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr04
New-SPEnterpriseSearchQueryProcessingComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr03
13. Create and Assign Index Partitions
New-SPEnterpriseSearchIndexComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr04 -RootDirectory $IndexLocP -IndexPartition 0
New-SPEnterpriseSearchIndexComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr03 -RootDirectory $IndexLocR -IndexPartition 0
New-SPEnterpriseSearchIndexComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr03 -RootDirectory $IndexLocP -IndexPartition 1
New-SPEnterpriseSearchIndexComponent –SearchTopology $SrchTop02 -SearchServiceInstance $Svr04 -RootDirectory $IndexLocR -IndexPartition 1
14. Activate Search Topology 02
Set-SPEnterpriseSearchTopology -Identity $SrchTop02
15. Remove Search Topology 01
$SrchTop01 = Get-SPEnterpriseSearchTopology -SearchApplication $SvcAppSrch | where {($_.State) -eq "Inactive"}
Remove-SPEnterpriseSearchTopology -Identity $SrchTop01 -Confirm:$false
16. Create Search Service Application Proxy
$SvcAppSrchPrxy = New-SPEnterpriseSearchServiceApplicationProxy -Name "SvcApp_SPEnterpriseSearchServiceApplication_01_Proxy_01" -SearchApplication $SvcAppSrch
Key Words
Search Service, Search Service Application, Search Topology.
References
ChandrasekarN (February, 2013). SharePoint 2013 - Configuring Search Service Application and Topology using PowerShell. Retrieved January 29, 2014 from http://blogs.msdn.com/b/chandru/archive/2013/02/19/sharepoint-2013-configuring-search-service-application-and-topology-using-powershell.aspx
Earp, S. (September, 2013). Configuring SharePoint 2013 Search with PowerShell. Retrieved January 27, 2014 from http://blogs.technet.com/b/ptsblog/archive/2013/09/19/configuring-sharepoint-2013-search-with-powershell.aspx
Harbar, S. (July, 2012). Multi Tenancy with SharePoint 2013: What’s new and changed. Retrieved January 29, 2014 from http://www.harbar.net/articles/sp2013mt.aspx
Klindt, T. (December, 2012). Create SharePoint 2013 Search service application with PowerShell. Retrieved January 29, 2014 from http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=378
Microsoft TechNet (2013). Create and configure a Search service application in SharePoint Server 2013. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/gg502597.aspx
Microsoft TechNet (2013). Get-SPSearchService. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ee620539(v=office.14).aspx
Microsoft TechNet (2013). Get-SPEnterpriseSearchServiceApplication. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff608050.aspx
Microsoft TechNet (2013). Get-SPEnterpriseSearchServiceInstance. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff607740.aspx
Microsoft TechNet (2013). Get-SPEnterpriseSearchTopology. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/jj219578.aspx
Microsoft TechNet (2013). Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff608115.aspx
Microsoft TechNet (2013). New-SPEnterpriseSearchServiceApplication. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff607751.aspx
Microsoft TechNet (2013). New-SPEnterpriseSearchServiceApplicationProxy. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff607722.aspx
Microsoft TechNet (2013). Set-SPEnterpriseSearchServiceApplication. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff607974.aspx
Microsoft TechNet (2013). Set-SPEnterpriseSearchTopology. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/jj219653.aspx
Microsoft TechNet (2013). Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff607759.aspx
Microsoft TechNet (2013). Start-SPEnterpriseSearchServiceInstance. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/ff607852.aspx
Microsoft TechNet (2013). Remove-SPEnterpriseSearchTopology. Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/jj219505.aspx
Ravikanth (April, 2013). Creating and configuring a SharePoint 2013 search service application. Retrieved January 29, 2014 from http://www.powershellmagazine.com/2013/04/29/creating-and-configuring-a-sharepoint-2013-search-service-application/
Monday, January 27, 2014
Solution for Site Collection Lock, Missing Site Settings Menu in SharePoint 2007
Description
Logged into a SharePoint 2007 Site Collection as a Site Collection Administrator with Full Control permission level, the Site Actions, Site Collection Settings menu is not present. The reason for this is that the Site Collection has a lock on it and is in a "Read-Only" state. In a case observed, this lock occured because a disk partition lacked adequate free space to complete a backup when new Site Collection backup process began.
Once the disk space and backup issues are corrected, an STSADM.exe command can be run from the Command Line that will put the Site Collection in a "Not Locked" state. This will make the Site Collection Settings menu appear.
As explained below, the desired state is "Not Locked" but problem state is "Read-only":
- Read-only - Blocks additions, updates, and deletions to the site collection.
- Not Locked - Sets the site collection to an unlock status. This is the default setting.
Solution
1) Open the CMD line (Start, Run, CMD)
2) Change Directory to Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin directory
3) Run this command to unlock the Site Collection:
stsadm -o setsitelock -url http://hostname.domainname.com -lock none
4) Run this command to verify the Site Collection is Not Locked (None):
stsadm -o getsitelock -url http://hostname.domainname.com
(Aquino, 2009)
Key Words
Site Settings missing, Site Collection Settings menu missing, Site Collection lock, Backup ran out of space.
References
Aquino, F. (November, 2009). Moss 2007 Site Action -> Site Settings have disappeared. Retrieved January, 2014 from http://stackoverflow.com/questions/1809512/moss-2007-site-action-site-settings-have-disappeared
Microsoft TechNet (May, 2008). Lock site collections (Office SharePoint Server). Retrieved January 27, 2014 from http://technet.microsoft.com/en-us/library/cc508855(v=office.12).aspx
Labels:
SharePoint,
SharePoint 2007,
stsadm.exe,
Support
Thursday, January 23, 2014
SharePoint 2013: How to Configure the Machine Translation Service Application using PowerShell
Description
This post describes how to configure the SharePoint Server 2013 Machine Translation Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Service Application components. Document the naming convention.
Application Pool: SvcApp_SPServiceApplicationPool_01
Application Pool Service Account: Domain\SvcAccount
Application: SvcApp_SPPerformancePointServiceApplication_01
2) Prepare the Application Pool / Service Account
Example: Subscription Settings Application Pool: SvcApp_SPServiceApplicationPool_01 Application Pool Service Account: Domain\SvcAccount
A) If you are using an existing application pool:
You do not need to create a Service Account nor an Application Pool. Note the names of each.
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
B) If you are creating a new application pool:
Determine which service account you will use to run the application pool that will be assigned to the. If you need to, create and register a service account to run the Subscription Settings Service Application.
Create the Service Application Pool and register it to the Service Account.
$SvcAppPool = New-SPServiceApplicationPool -Name "SvcApp_SPServiceApplicationPool_01"$AppPool = New-SPServiceApplicationPool -Account (Get-SPManagedAccount Domain\SvcAccount)
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
3) Open the SharePoint 2013 Management Shell as Administrator.
4) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPTranslationServiceApplication –ApplicationPool $SvcAppPool -Name "SvcApp_SPTranslationServiceApplication_01" -DatabaseName "SvcApp_SPTranslationServiceApplication_01_DB_01" -DatabaseServer "SQL Alias Name"
Verify Service Application.
Get-SPServiceApplication | Select Name
5) Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPTranslationServiceApplicationProxy -Name "SvcApp_SPTranslationServiceApplication_01_Proxy_01" -ServiceApplication $SvcApp
Verify Service Application Proxy
Get-SPServiceApplicationProxy | Select Name
Notes
This Service Application does have a database associated with it.
These steps will result in a redundant Proxy for the Service Application. One can be deleted.
References
Microsoft TechNet (2012). New-SPTranslationServiceApplication. Retrieved January 23, 2014 from http://technet.microsoft.com/en-us/library/jj219712.aspx.
Microsoft TechNet (2012). New-SPTranslationServiceApplicationProxy. Retrieved January 23, 2014 from http://technet.microsoft.com/en-us/library/jj219763.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
SharePoint 2013: How to Configure the PerformancePoint Service Application using PowerShell
Description
This post describes how to configure the SharePoint Server 2013 PerformancePoint Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Service Application components. Document the naming convention.
Application Pool: SvcApp_SPServiceApplicationPool_01
Application Pool Service Account: Domain\SvcAccount
Application: SvcApp_SPPerformancePointServiceApplication_01
2) Prepare the Application Pool / Service Account
Example: Subscription Settings Application Pool: SvcApp_SPServiceApplicationPool_01 Application Pool Service Account: Domain\SvcAccount
A) If you are using an existing application pool:
You do not need to create a Service Account nor an Application Pool. Note the names of each.
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
B) If you are creating a new application pool:
Determine which service account you will use to run the application pool that will be assigned to the. If you need to, create and register a service account to run the Subscription Settings Service Application.
Create the Service Application Pool and register it to the Service Account.
$SvcAppPool = New-SPServiceApplicationPool -Name "SvcApp_SPServiceApplicationPool_01"$AppPool = New-SPServiceApplicationPool -Account (Get-SPManagedAccount Domain\SvcAccount)
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
3) Open the SharePoint 2013 Management Shell as Administrator.
4) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPPerformancePointServiceApplication –ApplicationPool $SvcAppPool -Name "SvcApp_SPPerformancePointServiceApplication_01" -DatabaseName "SvcApp_SPPerformancePointServiceApplication_01_DB_01" -DatabaseServer "SQL Alias Name"
Verify Service Application.
Get-SPServiceApplication | Select Name
5) Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPPerformancePointServiceApplicationProxy -Name "SvcApp_SPPerformancePointServiceApplication_01_Proxy_01" -ServiceApplication $SvcApp
Verify Service Application Proxy
Get-SPServiceApplicationProxy | Select Name
Notes
This Service Application does have a database associated with it.
References
Microsoft TechNet (2012). New-SPPerformancePointServiceApplication. Retrieved January 23, 2014 from http://technet.microsoft.com/en-us/library/ff608122.aspx.
Microsoft TechNet (2012). New-SPPerformancePointServiceApplicationProxy. Retrieved January 23, 2014 from http://technet.microsoft.com/en-us/library/ff608135.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
SharePoint 2013: How to Configure the Word Automation Service Application using PowerShell
Last Updated March 28, 2014
Description
This post describes how to configure the SharePoint Server 2013 Word Automation Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Word Automation Service Application components. Document the naming convention.
Example:
Application Pool Service Account: Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPWordConversionServiceApplication_01
Service Application Proxy: SvcApp_SPWordConversionServiceApplication_01_Proxy_01
2) Open the SharePoint 2013 Management Shell as Administrator.
3) Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name
4) Get the existing Application Pool.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"
5) Open the SharePoint 2013 Management Shell as Administrator.
6) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPWordConversionServiceApplication –ApplicationPool $SvcAppPool02 -Name "SvcApp_SPWordConversionServiceApplication_01" -DatabaseName "SvcApp_SPWordConversionServiceApplication_01_DB_01" -DatabaseServer "SQL Alias Name"
The Proxy is created when the New Service Application cmdlet is run. It does not appear that the name of the Proxy may be set or changed independently for this Service Application.
7) Verify Service Application.
Get-SPServiceApplication | Select Name
8) Verify Service Application Proxy
Get-SPServiceApplicationProxy | Select Name
References
Microsoft TechNet (2012). New-SPWordConversionServiceApplication. Retrieved January 23, 2014 from http://technet.microsoft.com/en-us/library/ff608091.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
SharePoint 2013: How to Configure the Excel Service Application using PowerShell
Description
This post describes how to configure the SharePoint Server 2013 Excel Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Service Application components. Document the naming convention.
Application Pool: SvcApp_SPServiceApplicationPool_01
Application Pool Service Account: Domain\SvcAccount
Application: SvcApp_SPExcelServiceApplication_01
2) Prepare the Application Pool / Service Account
Example: Subscription Settings Application Pool: SvcApp_SPServiceApplicationPool_01 Application Pool Service Account: Domain\SvcAccount
A) If you are using an existing application pool:
You do not need to create a Service Account nor an Application Pool. Note the names of each.
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
B) If you are creating a new application pool:
Determine which service account you will use to run the application pool that will be assigned to the. If you need to, create and register a service account to run the Subscription Settings Service Application.
Create the Service Application Pool and register it to the Service Account.
$SvcAppPool = New-SPServiceApplicationPool -Name "SvcApp_SPServiceApplicationPool_01"$AppPool = New-SPServiceApplicationPool -Account (Get-SPManagedAccount Domain\SvcAccount)
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
3) Open the SharePoint 2013 Management Shell as Administrator.
4) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPExcelServiceApplication –ApplicationPool $SvcAppPool -Name "SvcApp_New-SPExcelServiceApplication_01"
Verify Service Application.
Get-SPServiceApplication | Select Name
Verify Service Application Proxy
Get-SPServiceApplicationProxy | Select Name
Notes
The Proxy is created when the New Service Application cmdlet is run. It does not appear that the name of the Proxy may be set or changed independently for this Service Application.
References
Microsoft TechNet (2012). New-SPExcelServiceApplication. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607809.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
Wednesday, January 22, 2014
SharePoint 2013: How to Configure the Access Service Application using PowerShell
Description
This post describes how to configure the SharePoint Server 2013 Access Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Service Application components. Document the naming convention.
Application Pool: SvcApp_SPServiceApplicationPool_01
Application Pool Service Account: Domain\SvcAccount
Application: SvcApp_SPAccessServiceApplication_01
2) Prepare the Application Pool / Service Account
Example: Subscription Settings Application Pool: SvcApp_SPServiceApplicationPool_01 Application Pool Service Account: Domain\SvcAccount
A) If you are using an existing application pool:
You do not need to create a Service Account nor an Application Pool. Note the names of each.
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
B) If you are creating a new application pool:
Determine which service account you will use to run the application pool that will be assigned to the. If you need to, create and register a service account to run the Subscription Settings Service Application.
Create the Service Application Pool and register it to the Service Account.
$SvcAppPool = New-SPServiceApplicationPool -Name "SvcApp_SPServiceApplicationPool_01"$AppPool = New-SPServiceApplicationPool -Account (Get-SPManagedAccount Domain\SvcAccount)
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
3) Open the SharePoint 2013 Management Shell as Administrator.
4) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPAccessServiceApplication –ApplicationPool $SvcAppPool -Name "SvcApp_SPAccessServiceApplication_01"
Verify Service Application.
Get-SPServiceApplication | Select Name
Verify Service Application Proxy
Get-SPServiceApplicationProxy | Select Name
Notes
The Proxy is created when the New Service Application cmdlet is run. It does not appear that the name of the Proxy may be set or changed independently for this Service Application.
References
Microsoft TechNet (2012). New-SPAccessServiceApplication. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607785.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
SharePoint 2013: How to Configure the Metadata Service Application using PowerShell
Description
This post describes how to configure the SharePoint Server 2013 Metadata Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Service Application components. Document the naming convention.
Application Pool: SvcApp_SPServiceApplicationPool_01
Application Pool Service Account: Domain\SvcAccount
Application: SvcApp_SPMetadataServiceApplication_01
Proxy: SvcApp_SPMetadataServiceApplication_01_Proxy_01
Database: SvcApp_SPMetadataServiceApplication_01_DB_01
2) Prepare the Application Pool / Service Account
Example: Subscription Settings Application Pool: SvcApp_SPServiceApplicationPool_01 Application Pool Service Account: Domain\SvcAccount
A) If you are using an existing application pool:
You do not need to create a Service Account nor an Application Pool. Note the names of each.
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
B) If you are creating a new application pool:
Determine which service account you will use to run the application pool that will be assigned to the. If you need to, create and register a service account to run the Subscription Settings Service Application.
Create the Service Application Pool and register it to the Service Account.
$SvcAppPool = New-SPServiceApplicationPool -Name "SvcApp_SPServiceApplicationPool_01"$AppPool = New-SPServiceApplicationPool -Account (Get-SPManagedAccount Domain\SvcAccount)
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
3) Open the SharePoint 2013 Management Shell as Administrator.
4) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPMetadataServiceApplication –ApplicationPool $SvcAppPool -Name "SvcApp_SPMetadataServiceApplication_01" -DatabaseName "SvcApp_SPMetadataServiceApplication_01_DB_01"
Verify Service Application.
Get-SPServiceApplication | Select Name
5) Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPMetadataServiceApplicationProxy -Name "SvcApp_SPMetadataServiceApplication_01_Proxy_01" -ServiceApplication $SvcApp
Verify Service Application Proxy
Get-SPServiceApplicationProxy | Select Name
References
Microsoft TechNet (2012). New-SPMetadataServiceApplication. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607557.aspx.
Microsoft TechNet (2012). New-SPMetadataServiceApplicationProxy. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff608097.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
SharePoint 2013: How to Configure the Business Data Catalog Service Application using PowerShell
Description
This post describes how to configure the SharePoint Server 2013 Business Data Catalog Service Application using PowerShell.
Solution
1) Document the Naming Convention
Determine a naming convention for each of the Service Application components. Document the naming convention.
Application Pool: SvcApp_SPServiceApplicationPool_01
Application Pool Service Account: Domain\SvcAccount
Application: SvcApp_SPBusinessDataCatalogServiceApplication_01
Proxy: SvcApp_SPBusinessDataCatalogServiceApplication_01_Proxy_01
Database: SvcApp_SPBusinessDataCatalogServiceApplication_01_DB_01
2) Prepare the Application Pool / Service Account
Example: Subscription Settings Application Pool: SvcApp_SPServiceApplicationPool_01 Application Pool Service Account: Domain\SvcAccount
A) If you are using an existing application pool:
You do not need to create a Service Account nor an Application Pool. Note the names of each.
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
B) If you are creating a new application pool:
Determine which service account you will use to run the application pool that will be assigned to the. If you need to, create and register a service account to run the Subscription Settings Service Application.
Create the Service Application Pool and register it to the Service Account.
$SvcAppPool = New-SPServiceApplicationPool -Name "SvcApp_SPServiceApplicationPool_01"$AppPool = New-SPServiceApplicationPool -Account (Get-SPManagedAccount Domain\SvcAccount)
Verify Application Pool.
Get-SPServiceApplicationPool | Select Name
Get the existing Application Pool.
$SvcAppPool = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_01"
3) Open the SharePoint 2013 Management Shell as Administrator.
4) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPBusinessDataCatalogServiceApplication –ApplicationPool $SvcAppPool -Name "SvcApp_ SPBusinessDataCatalogServiceApplication _01" -DatabaseName "SvcApp_ SPBusinessDataCatalogServiceApplication _01_DB_01"
Verify Service Application.
Get-SPServiceApplication | Select Name
5) Create the Service Application Proxy and assign it to the Service Application.
$SvcAppProxy = New-SPBusinessDataCatalogServiceApplicationProxy -Name "SvcApp_SPBusinessDataCatalogServiceApplication_01_Proxy_01" -ServiceApplication $SvcApp
Verify Service Application Proxy.
PS C:\ Get-SPServiceApplicationProxy | Select Name
References
Microsoft TechNet (2012). New-SPBusinessDataCatalogServiceApplication. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607899.aspx.
Microsoft TechNet (2012). New-SPBusinessDataCatalogServiceApplicationProxy. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607952.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
SharePoint 2013: How to Configure the Usage Service Application using PowerShell
Last Updated March 28, 2014
Description
This post describes how to configure the SharePoint Server 2013 Usage Service Application using PowerShell.
Solution
1) Plan and Document the Naming Convention.
Document a naming convention for each of the Service Application components.
Example:
Application Pool Service Account: Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPUsageApplication_01
Service Application Database: SvcApp_SPUsageApplication_01_DB_01
Service Application Proxy: SvcApp_SPUsageApplication_01_Proxy_01
2) Open the SharePoint 2013 Management Shell.
3) Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name
4) Get the existing Application Pool.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"
5) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPUsageApplication –Name “SvcApp_SPUsageApplication_01” -DatabaseName "SvcApp_SPUsageApplication_01_DB_01" –DatabaseServer “SQL Alias Name”
The Proxy is created automatically when the New Service Application cmdlet is run. It does not appear that the name of the Proxy may be set or changed independently for this Service Application at the time of creation.
6) Verify Service Application.
Get-SPServiceApplication | Select Name
7) Verify Service Application Proxy.
Get-SPServiceApplicationProxy | Select Name
8) Get the Usage and Health Data Collection Proxy.
$SvcAppProxy = Get-SPServiceApplicationProxy | Where {$_.TypeName -like “Usage and Health*”}
9) Start the Usage and Health Data Collection Proxy.
$SvcAppProxy.Provision()
References
Microsoft TechNet (2012). New-SPUsageApplication. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607699.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
Description
This post describes how to configure the SharePoint Server 2013 Usage Service Application using PowerShell.
Solution
1) Plan and Document the Naming Convention.
Document a naming convention for each of the Service Application components.
Example:
Application Pool Service Account: Domain\SvcAccount (this should already be created)
Application Pool: SvcApp_SPServiceApplicationPool_02 (this should already be created)
Service Application: SvcApp_SPUsageApplication_01
Service Application Database: SvcApp_SPUsageApplication_01_DB_01
Service Application Proxy: SvcApp_SPUsageApplication_01_Proxy_01
2) Open the SharePoint 2013 Management Shell.
3) Verify the Name of the Application Pool.
Get-SPServiceApplicationPool | Select Name
4) Get the existing Application Pool.
$SvcAppPool02 = Get-SPServiceApplicationPool "SvcApp_SPServiceApplicationPool_02"
5) Create the Service Application and assign it to the Application Pool.
$SvcApp = New-SPUsageApplication –Name “SvcApp_SPUsageApplication_01” -DatabaseName "SvcApp_SPUsageApplication_01_DB_01" –DatabaseServer “SQL Alias Name”
The Proxy is created automatically when the New Service Application cmdlet is run. It does not appear that the name of the Proxy may be set or changed independently for this Service Application at the time of creation.
6) Verify Service Application.
Get-SPServiceApplication | Select Name
7) Verify Service Application Proxy.
Get-SPServiceApplicationProxy | Select Name
8) Get the Usage and Health Data Collection Proxy.
$SvcAppProxy = Get-SPServiceApplicationProxy | Where {$_.TypeName -like “Usage and Health*”}
9) Start the Usage and Health Data Collection Proxy.
$SvcAppProxy.Provision()
Microsoft TechNet (2012). New-SPUsageApplication. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ff607699.aspx.
Microsoft TechNet (2012). Service application cmdlets in SharePoint 2013. Retrieved January 22, 2014 from http://technet.microsoft.com/en-us/library/ee906561.aspx.
Microsoft TechNet (2012). SharePoint 2013 - Service Applications. Retrieved January 22, 2014 from http://social.technet.microsoft.com/wiki/contents/articles/12512.sharepoint-2013-service-applications.aspx.
Subscribe to:
Posts (Atom)
Blog Archive
-
▼
2014
(24)
-
▼
January
(15)
- SharePoint 2013: Set-SPEnterpriseSearchTopology : ...
- SharePoint 2013: How to Rename the Search Service ...
- SharePoint 2013: How to Configure the Search Servi...
- Solution for Site Collection Lock, Missing Site Se...
- SharePoint 2013: How to Configure the Machine Tran...
- SharePoint 2013: How to Configure the PerformanceP...
- SharePoint 2013: How to Configure the Word Automat...
- SharePoint 2013: How to Configure the Excel Servic...
- SharePoint 2013: How to Configure the Access Servi...
- SharePoint 2013: How to Configure the Metadata Ser...
- SharePoint 2013: How to Configure the Business Dat...
- SharePoint 2013: How to Configure the Usage Servic...
- SharePoint 2013: How to Configure Secure Store Ser...
- SQL Server 2012: SELECT Machine Name, Server Name...
- How to Associate SQL Server Login with Existing Da...
-
▼
January
(15)
Events / Conferences / User Groups
- AIIM Conference
- Boston Area SharePoint User Group
- Boston Azure User Group
- Collaborate
- DevConnections
- DevIntersection
- Enterprise Search Summit
- Microsoft Build
- Microsoft SharePoint Conference
- Microsoft TechEd
- New England ASP.NET Professionals User Group
- New England Oracle Applications User Group
- Oracle Applications User Group (OAUG)
- Oracle OpenWorld
- PeopleSoft Government Contractor Special Interest Group
- PeopleSoft Southern New England Users Group
- Quest International Users Group
- SharePoint Saturday
- SPTechCon
- SQL PASS
- SQL Saturday
- Startup Weekend