This is an English speaking site. It really helps to posted your question in English if you expect an answer.
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
I'm trying connect sql server 2000 in windows service with other system on same network.
there are 4 system connected without any problem. But on other 4 system, it is giving error
on connection open while starting windows service. The error is: "the service on local computer started and then stopped some services stop automatically" etc. Same Connection string working in web service
without any error. But giving problem in Window Service. Is there any Configuration setting of that server or sql server 2000. Any help will be highly appreciated.........
Could be that, could be a firewall, could be something else.
Before trying to fix it though I'd introduce a minimum of logging in the service so in future you don't have to stare blindly at that nearly information-free message: "the service started, and then stopped unexpectedly".
It's also nice to have the ability to debug service initialization. To do this, introduce a config setting and put a method like this into your service class:
string s = ConfigurationManager.AppSettings["debug"];
if (s == null || s.ToLower() != "true") return;
DateTime until = DateTime.Now.AddSeconds(30);
while (DateTime.Now < until && !Debugger.IsAttached)
Now in the service main thread, just insert a call to this method before doing anything else. (Not in the start method that probably simply starts the main thread; you want this method to return immediately as before. But in the thread it starts, you want to wait for a debugger to attach if so configured.) Build, deploy, and debug!