It is not a question of one service being stopped manully, but when the system goes down ?!?!
Main Topics
Browse All TopicsI am trying to create multiple windows services (two at this moment) which will work in redundant manner. i.e. One Service is performing the Normal Routine of work, and the other one is being notified of its status. Whenever the ongoing service goes down, the other service(may be located on different computer) starts up the Normal Routine. Similarly there can be around four such services. But first I am concerned about making two only.
So how can I make sure that if one service goes down, the other one is automatically invoked, is there a workaround using Sockets?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>>So how can I make sure that if one service goes down, the other one is automatically invoked,
Establish communication between the two services (socket, namedpipes, whatever). When the "normal" one stops sending an "I'm alive" signal, then the failover should kick in.
Also, PHYL has a point. Win2K can be set to automatically restart a Service that has crashed. That may solve part of the problem... Look into it.
-- Dan
Thanks people.
Anyway, I eventually had to do it using Sockets, which I did not want to do, BECAUSE::
1:: .NET provides interim methods to handle Inter-Service communication using OnCustomCommand (receiver) and ExecuteCommand(sender) methods. But when I used this approach
2:: The service takes massive amount of memory (about 12M) without having the main functionality in which I'll make it communicate with http using HttpWebRequest.
Sumit Amar
Oracle9i DBA
Sun Certified Java Programmer
Brainbench Certified for 149 tests (world rank 3)
worldwide rankings >> www.ob-d.com/bb.asp
No comment has been added to this question in more than 21 days, so it is now classified as abandoned..
I will leave the following recommendation for this question in the Cleanup topic area:
Split PHYL, DanRollins
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
Greg
EE Cleanup Volunteer
Business Accounts
Answer for Membership
by: PHYLPosted on 2002-10-28 at 08:05:42ID: 7378915
Why don't you use the build-in Service Recovery functions of the Win2k OS?
bye, Günter Prossliner PHYL