SharePoint Service Applications

You shouldn't start the first two unless you need them.

Reboot is the quick answer.

I rebooted several times, nothing.

Im trying to run PerformanPoint Services, SQL Reporting Services Server, and Reporting Services Add-in all on the same box. This box is added to the farm.

What services should be enabled besides PerformancePoint Services?

I was having trouble getting the Secure Store Services service started on the box so I tested out some other services and now I cant get them out of either "STOPPING" or "STARTING"

How much memory do you have on this server?  

4GB ... 3GHz

is there a way to manually stop or start a service that is controlled via central admin that is stuck in either "Stopping" or "Starting" mode?

You may need to bump the memory up.  I've seen strange issues happen when many services are running on a box with only 4 GB.

The box is actually a VM.

Thanks for the link to manually restart some services... however I can find the service name for those three services listed above.

This has turned to a 500 pt question bro.

has it?  :-)

Im trying to run PerformanPoint Services, SQL Reporting Services Server, and Reporting Services Add-in all on the same box. This box is added to the farm.  What services should be enabled besides PerformancePoint Services?

To manually restart some services, I cant find the service name for those three services listed above.

Yes, thanks however I already tried that beforehand.  I couldnt find the actual service name for those three services listed above.

If you run get-spserviceinstance and don't see PerformancePoint or Claims or Workflow Timer, you have other issues.

Was SharePoint installed as a farm, or did you do a stand alone?

I just want to stop all services running on this machine that was added to the farm as a WFE. then start the services that are needed to run:  PerformanPoint Services, SQL Reporting Services Server, and Reporting Services Add-in all on the same box, properly.

The ones that I tried to stop are stuck at "STOPPING"

Thanks much!  

SharePoint was installed as a FARM and connected as a WFE. Central Admin is shared between all WFEs.

Please provide a screenshot of your Powershell command and the returned list.

I was doing the commands in CMD window using:  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\stsadm Get-SPServiceInstance

Im not too familiar with Powershell ...

You know ... I should have know that one.  I will get the info up soon.

Since you were running commands the wrong way, you should probably follow the stuff in the URL i posted earlier.

The last image of course gave the instances for all the WFEs attached to farm.

Perf Point is started, so that is good.  You don't need to worry about Claims to Windows.  BDC is already started.

So your question was how do I manually stop and start services.  The answer is via PowerShell, going off the Technet article I provided.

PerformancePoint needs to be started on the WFE that is running SQL Reporting Services, etc. only.

This is what is running on the WFE that Im in question about.

Have you manually tried to stop and start them using PowerShell, like I've noted multiple times?

Yes I have and Im getting an error when doing so.  Im trying to find that instance to delete but cant. UGH!

Either reboot your box, or go into Job Definitions under the Monitoring section in Central Admin and try to find this job, and delete it.

OK, I rebooted the box.  Now 6 services are stuck on "Stopping" and the rest are all "Stopped." I cant get these services to be all "Stopped"   I just want to start PerformancePoint Service but that is stuck at "Stopping" for some reason.

If you look in services.msc (not in central admin).......is the SHarePoint Timer service running?  Sounds like a bunch of jobs are stuck and not correctly processing.  This is because the timer service isn't running, or the jobs are corrupt and need to be manually deleted.

Yes it is running ... automatically ... with a service account.  So the jobs is more than likely corrupt.  Where can I find and delete ... I went through all the jobs in Job Definitions under the Monitoring section in Central Admin and deleted what was possible to delete.

I know have three services that are stuck in "Starting" mode...

Claims to Windows Token Service
Microsoft SharePoint Foundation Web Application
Microsoft SharePoint Foundation Workflow Timer Service

and you started them through PowerShell?

I tried to stop them through PowerShell and all I was seeing was "Stopping", some stopped but some still said that so I tried to start them instead.   I just cant seem to get them to Start/Stop via Central Admin

Something is seriously messed up. When I try to start a service via central admin, the service just sits there saying "Starting..."

Mind boggling but I got it to work.  I can start/stop services via Central Admin just fine.  I detached the WFE from the farm and reattached it and all seems to work well now.

I however would like to know what services are actually needed to be started to have the following function properly all on one box on this farm:

PerformanPoint Services, SQL Reporting Services Server, and Reporting Services Add-in.

I currently have this started:
PerformancePoint Service
Microsoft SharePoint Foundation Workflow Timer Service
Secure Store Service
Excel Calculation Services
Microsoft SharePoint Foundation Incoming E-Mail

PerfPoint just needs secure store and PerformancePoint services.  But that doesn't mean you should disable everything else.

Understood.

I have majority of the other services running on an existing WFE. I just created a new WFE to host: PerformanPoint Services, SQL Reporting Services Server, and Reporting Services Add-in.

I dont think I need the other services running on both WFEs.  

Being that we are discussing PerformancePoint and Secure Store Service ... I have an issue!

When Im setting up secure store service, I want to locate the content db to another database server other than SharePoints database. When I do this I get the following error:  The timer job completed, but failed on one or more machines in the farm.

Would you know a work around?  Thanks

Honestly this should be another question in the forum.  

Will do.  I broke it up into two.  Thanks!

Do you still need this ticket open?  If not, please award points.

Being that this question was about how to start/stop services manually and I ended up detaching WFE from farm and re-attaching WFE to fix the issue ... I guess we can close it out.

I ended up detaching the WFE from the farm and reattaching it. The starting/stopping all seems to work well now.  The selected questions from Expert are some that helped me better understand Powershell.