Setting Up the Subscription Settings Service Application in SharePoint 2013
Here’s a little tip that’s not particularly brilliant, but just useful, as you start working with the new application model in SharePoint 2013. You always need a subscription settings service application, but it’s one of those things that you cannot create in the UI. So just keep a bookmark to this post and come back as needed for a little copy and paste. This brief PowerShell snippet will create service application and proxy in one fell swoop:
New-SPSubscriptionSettingsServiceApplication -ApplicationPool "SharePoint Web Services Default" -Name "Subscription Settings Service Application" -DatabaseName "SubscriptionSettingsDB" | New-SPSubscriptionSettingsServiceApplicationProxy
Once you’ve created the Subscription Settings service application, you can go configure your application domain in Central Admin.
Comments
Anonymous
January 01, 2003
I am running into same question. In 2010 this server is only started for Multi-tenant environments (pertechnet.microsoft.com/.../ff627854(v=office.14).aspx ). If I am reading this correct, this is no longer the case and must be started for user with Apps form the app store? Is this correct?Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Eric, you are absolutely rightAnonymous
November 18, 2012
So you need one of these even if you are not doing multitenancy?Anonymous
January 16, 2014
hiAnonymous
January 16, 2014
hiAnonymous
April 07, 2014
Hi, am new to sharepoint.can anybody tell the role that Subscription Settings Service Application plays in creating apps.Anonymous
June 19, 2014
Hi Luca - you asked "So you need one of these even if you are not doing multitenancy?" the answer is yes.Anonymous
September 18, 2014
The comment has been removedAnonymous
January 26, 2015
Hello... what if by running this command you get an error... which I'm getting though, that states: New-SPSubscriptionSettingsServiceApplication : CREATE DATABASE permission
denied in database 'master'.
I haven't been able to address this issue as I already made my managed account an owner to master database.
Do you have any ideas?Anonymous
February 02, 2015
@jose: check the account you're using to run powershell