I am now doing my third setup of my SP 2013 system, and I have been using Todd Klint's notes mostly, but when I get to creating the App Management Service App and starting the App Management Service (in this document), the service consistently stays in the Starting (if viewing Services in CA)/Provisioning (if checking in PowerShell) state, even after a reboot. I don't remember having this problem before. Is there some step I missed that is a requirement for this service to run?

Hi  cgtyoder,

The App Management Service depends on the following services in order to work:

SPSubscriptionSetingsServiceApplication

SPAppManagementServiceApplications

Make sure all of them are created correctly.

For your issue, you can delete the App Management Service Application and  Subscription Settings Service  Application , then recreate them.

Best Regards,

Eric

The App management does depend on the Subscription Settings Service for the SharePoint Store to work correctly, but this is NOT needed for the service (From Central Admin | System Settings | Manage Services on Server) to start up correctly. I would try stopping the service from PowerShell and then starting it again as maybe something got hosed up when you tried to start it originally:

Open SharePoint Management Shell as Admin

Run the following PowerShell Commands to stop the service (Afterward check services on server and see if it is in a stopping state or stopped and then start it again):

$appSvc = Get-SPServiceInstance | Where -Property TypeName -like "App*"
Stop-SPServiceInstance -Identity $appSvc

Note: After this service is stopped you could use the cmdlet to start the App Management Service (As an alternative of Central Admin)

 

Start-SPServiceInstance -Identity $appSvc

Even after carrying out above steps, "App management service" still remains in starting state.

I restarted IIS, no effect.

I ran the SharePoint products configuration wizard, still no effect.

What to do ?

Hi,

This is a old thread ..but I had the similar issue in my devbox last week, so to resolve this  I disconnected the server from farm using the following command:

psconfig -cmd configdb -disconnect,

note this will delete all the sites including CA from IIS, not recommended for production farm

then again reran the configuration wizard and to create a new farm and create a new configuration database. After that everything worked fine. This method avoid re-installation of SharePoint but reset all the services.

Thanks,

Pat