App Management Service Application Stopped

I've just provisioned the App Management Service Application in my SP 2013 on-prem dev farm. However, the status says "Stopped" when I view the list of Service Applications. enter image description here The service instance is started, however. enter image description here When I check the service application in Powershell, it says "Disabled". enter image description here How can I get the service app and associated proxy to a "Started" status? Thanks in advance!

45.3k 9 9 gold badges 54 54 silver badges 96 96 bronze badges asked Oct 12, 2018 at 21:01 Drew Paxton Drew Paxton 514 3 3 silver badges 10 10 bronze badges

2 Answers 2

The Disable status means the App service is not provisioned correctly, so try to provision it using PowerShell

$srv = Get-SPServiceInstance | where-object $srv.Provision() Get-SPServiceInstance | $srv #check its status

This issue might also occur if you have started the App Managment Service in Services on Server before creating the App Managment Service Application Service .

So in your case,

answered Oct 12, 2018 at 21:40 Mohamed El-Qassas MVP ♦ Mohamed El-Qassas MVP 45.3k 9 9 gold badges 54 54 silver badges 96 96 bronze badges

Thanks, Mohamed. Unfortunately, when I attempt to stop the service, it gets stuck in a 'stopping' status. I've tried restarting the timer service and rebooting the server, but its still stubbornly stuck.

Commented Oct 12, 2018 at 22:42

I was able to get this fixed by provisioning the App Management Service Application and App Management Service Application Proxy separately in PowerShell.

enter image description here

enter image description here

answered Oct 12, 2018 at 23:14 Drew Paxton Drew Paxton 514 3 3 silver badges 10 10 bronze badges

Hello @drew, this is what exactly said to you in my answer for the first suggestion! "The Disable status means the App service is not provisioned correctly, so try to provision it using PowerShell

Commented Oct 13, 2018 at 7:48

@MohamedEl-QassasMVP, I didn't mean to slight your answer at all. When I first tried your initial answer (and what ended up working for me), the service was still stuck in a 'Stopping' state. That also made me unable to try your second answer because I couldn't fully stop the service.

Commented Oct 15, 2018 at 15:48

Once I deleted the timer job instance that was attempting to stop the service, I was able to restart it. Once the service was in a 'Started' state again, I was able to use a variation of your answer. But if you look at mine, I'm reprovisioning the Service Application and associated Proxy. Not the Service Instance itself. In any case, you definitely pointed me in the right direction, so I've marked your post as the answer. Cheers, -Drew

Commented Oct 15, 2018 at 15:51

@Drex No problem bro, glad to hear you have solved your issue! Thanks for your appreciation, Have a nice day!