I've programmed a small service running as Windows Service. On most computers this works well, but there are a few computers, where the service sometimes does not start when the computer is rebootet.
It is no problem to start the service after the boot. Just the automatic start right on boot does not work.
I already tried to put the service into delayed start, but this didn't Change anything. The service still sometimes not starts on reboot.
The service is running on a local service account and does just open a few WFC services and wait for connections.
Related
I'm attempting to use Suricata IDS for monitoring the network events in a specific interface.
I have been able to install the service and I am able to execute it.
Everything seems to be working fine, except for the fact that the service might fail to start at computer startup.
The service in fact necessarily needs to have the connection ready and available (assigned IP, etc.) when Windows starts it.
So, the service is working correctly at startup ONLY when the network is up and running for that interface.
If for some reason the network connection comes up later than usual, the service fails to start, and Windows seems to not try again to start it.
I've been looking at other stackoverflow questions in order to correctly set the dependencies for the network connection and for what I'm trying to do, but they seem to not be working.
So, what are the correct dependencies to add to my service for instructing Windows to wait for the network connection to be up and running (IP already assigned, DNS already set, etc.) before starting it?
If you have an alternative idea on how to solve the problem you're welcome to post a reply.
Any suggestion is appreciated.
I'm running an application that is a web app and the backend for an ios app as well as a database in an ec2 instance. Will these processes resume if I stop, resize, and restart my instance? Will I need to go in and run startup scripts?
Any help is appreciated, I'm confused by the AWS documentation as to exactly what happens.
It's just like turning your laptop off and then back on. If you have configured the services to start automatically on boot then they will restart, if you haven't configured them to start automatically on boot then they won't.
This is a function of the software you have installed and configured on the EC2 instances, and whatever Operating System your EC2 instance is running. You won't find much about this in the AWS documentation because it isn't really Amazon specific.
I have a WCF service hosted as a windows service.
The WCF service reads from an MSMQ and does some processing.
It is running fine when installed locally on my windows 7 machine and reads properly from a public queue on my machine and does some action.
However when the service and the public queue is set up on a Windows 2008 server, the public queue has entries, but the WCF service is not picking it up.
Made sure all features are turned on the server machine as it is on my windows 7 machine and still no luck.
Not sure if there are any settings that I need to enable on the server machine for the WCF service to read from the queue.
Is it possible to change the order of windows services or run one service after another?
The reason i want this: I have IIS configuration located on a shared drive. And when i reboot server, it first run IIS (w3wp) service and couldn't start it. because at that point, shared network drive is not available. So i want to first finishing the network service to map all network drives and then run IIS service. so i don't need to restart IIS service every-time i reboot the server. is there any other way to achieve this?
Thanks!
By default, some Windows services are configured with "dependencies" to ensure that the prerequisite services are started first... so you can just add to them.
Here's how to set dependencies with Registry edits , from the command-line (sc config ServiceName depend=servicetoDependOn), and from .NET.
If you're running Server 2008 / Vista / 7 you can set the IIS service for delayed start.
There are sort of two tiers: first all the "automatic" stuff, then the "automatic (delayed start)" stuff.
I have developed a windows service using C#.net. The purpose of this service is block an application. When ever serrvice starts the application will be blocked. Can I operate this service from server to start or stop in client system?
Try 'sc' command from the command prompt. As servers IP and services name use your own.
Starting service:
sc \\192.168.1.100 start MySQL
Stopping service:
sc \\192.168.1.100 start MySQL
More information here.