This service application is not new for us as we have learned about this in previous versions of SharePoint 2010/2013. This service supports site subscriptions. It has some characteristics in common with IIS Web Services as it is a WCF Web service and the object that represents it at runtime is an SPIisWebService-derived object. However, it does not implement the Service Application Framework.

In SharePoint 2010, SharePoint uses this service application for Multi-tenant Mode or sites that use site subscriptions. In a multi-tenant environment, this service application stores the subscriptions settings and configuration data.

In SharePoint 2013, the introduction of App Management Service Application and Subscription Settings Service Application is one of the prerequisites of it. The App Management Service is inherently subscription aware and does NOT need to be provisioned in Partitioned Mode.

Same case with SharePoint 2016.

Known facts about this

  • There is no GUI to provision this Service Application
  • Provisioned via PowerShell only
  • This Service Application has it's own Content Database

We will walk through the steps of provisioning a Microsoft SharePoint Foundation Subscription Settings Service Application. Let’s start!

Configure the Subscription Settings Service Application using PowerShell

You can start the Microsoft SharePoint Foundation Subscription Settings Service Application from Central Admin first and then provision it via PowerShell or simply run PowerShell and it will start and provision the service application.

  1. If you go Central Admin > System Settings > Manager Service on the farm. You will see this:2016-04-13_23h19_36
  2. Please make sure of following things:
    1. Log in with a Domain Account which should be Local Admin on the server
    2. security admin fixed server role on the SQL Server instance
    3. db_owner fixed database role on all databases that are to be updated
  3. Now start the SharePoint PowerShell Window (Run as Administrator)
  4. Run the following script
    1. # Gets the name of the managed account
      $manaccount = Get-SPManagedAccount Krossfarm\kfadmin
    2. # Creates an application pool for the Subscription Settings Service Application using the Managed Account in step 1.
      $appPoolService = New-SPServiceApplicationPool -Name "SS-AppPool" -Account $manaccount
    3. # Creates the Subscription Settings Service Application, using the variable to associate it with the application pool that was created earlier.
      $appService = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPoolService -Name SettingsServiceApp -DatabaseName "SS-ContentDB"
    4. # Creates a proxy for the Subscription Settings Service Application and supplies the SS service variable use at step 3.
      $proxyService = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $appService 2016-04-13_23h20_03
    5. Once it successfully completes, go to the Central Admin and you will see it has started:2016-04-13_23h20_35
    6. If you go Manager Service Application and you will see it is provisioned here:2016-04-13_23h42_54

See Also: