Start service automatically

Question

Is there a way to configure velocity to start automatically once windows has started up? It seems like a pain to have to open PS and start it manually each time. I tried changing the service startup type to automatic but it never finishes "starting". Anyone know how to do this?

Answer 1

Hi, currently the admin operations (cluster start, stop, etc.) are supposed to be done by admin tool only. However, if you really need your service (or services on multiple nodes, i.e. you want your cluster to start automatically) to start automatically, you can change the start type to ‘automatic’ (as you have done). In this case service(s) may take some time to come up (which would be reflected by ‘starting’ status) as we need to make sure that there is no other cluster running before starting a new one. Eventually, the service(s) would come up.

---

Amit. (Velocity Dev, MSFT)

Answer 2

Its not working. I get this error



Then it just stays in the "Starting" state forever until I open up the task manager and kill the process. Are there supposed to be any start parameters? The box is greyed out and uneditable.

Answer 3

In this scenario, the service can take upto 15 minutes to start (maximum limit). Since this start time can be greater than the Service Control Manager's start command, you'd receive that error (1053) but the service would be able to come up eventually.

No start parameters are required. The box is grayed out since the status is 'starting'. It won't be uneditable when the status is 'stopped'.

---

Amit. (Velocity Dev, MSFT)

Answer 4

honestly this is pretty dumb. it takes 2 seconds to start when i do it manually but 15 minutes to start when the service is started automatically. im just going to create my own service that runs automatically and runs the command to get rid of this annoyance.

Answer 5

As I said, we need to make sure that the cluster isn't running before starting a new one. Moreover, starting service automatically is not supported. Cluster operations are supposed to be done by admin tool only.
Having said that, I think your scenario of having services that start automatically makes sense. We would definitely take a look at it, thanks.

---

Amit. (Velocity Dev, MSFT)

Answer 6

Could someone from MSFT provide guidance on what the supported options would be for getting the service started again after it goes down?

Scenario:

Cluster of 3 Velocity servers set as highly available
One server goes down for some reason (for example, applying Windows Updates and restart required)
Server gets restarted

Would an administrator need to log in and somehow manually get the server to "rejoin" the cluster? 

Being new to this product, I have many questions about high availability considerations.  If some of this is covered in another link or in some samples somewhere, please advise.

Answer 7

Hi wimpy1

After the server machine is restarted, you would need to go to the powershell administration tool and issue the 'start-cachehost ...' command to make it re-join the cluster.

Thanks,
Ankur.

---

Ankur

Answer 8

Wow, this is the dumbest thing I've ever heard of. If your service takes 15 minutes to start, it's a bug. I don't care if it's by design -- something is obviously terribly wrong. Saying there's a manual step to login and manually run a script is totally broken. I know it's only CTP3 so I shouldn't be to harsh, but this is totally invalid behaviour. Please fix this in the next release. We should be able to have our servers reboot at any time and not have to worry about it.

Answer 9

Reviving this thread - wondering if this has changed at all in the beta 2 bits.  By the look of the documentation (http://msdn.microsoft.com/en-us/library/ee790886.aspx#cachehost) it has not.

 

Scott

Answer 10

I completly agree with MichaelGG on this one. We need to have option to reboot our servers and not to worry about manually starting some services. Creating start up scripts for services seems just silly, that is just Band-Aid solution. The whole idea of Windows services is to run services with out user interaction.

Can we get update on this? 

Cheers

---

Ivan Bondy - MCPD, MCDBA, MCSA, MCTS - Sharepoint consultant