Error in starting windows service

Question

3.00/5 (1 vote)

See more:

Hi,
I want to execute some codes in my windows service.i have tested these codes in a winform application and its worked successfully.but now when i install my windows service and i want to start it a message appears and tell me that my service starts and then stops because it has nothing to do!!!?

what is my mistake?
Note: I have a System.Timers.Timer in my service to execute some codes every 15 minutes.and i have installed my windows service application as an administrator.

Posted 6-Sep-11 17:59pm

M_Mogharrabi

Add a Solution

Comments

Sergey Alexandrovich Kryukov 7-Sep-11 0:12am

No way to figure this out without looking at your code. But I gave you general recommendation which will help you to detect a problem by yourself.
--SA

3 solutions

Solution 2

To identify the problem, could you put try.. catch block

C#

try
{
....
}
catch (Exception ex)
{
... ex.Message....
}

It will catch the root cause for this service issue. From that, you can fix the problem which stops the service. My gut feeling is that there may be few setting/configuration issue in windows service definition.

Posted 6-Sep-11 18:12pm

Ganesan Senthilvel

Comments

Sergey Alexandrovich Kryukov 7-Sep-11 0:25am

OP should to it on top of stack of each thread and log the full exception dump. My 5.
--SA

Solution 3

Hello friend this is same question like this..

please see this question and it will be solved if it is help full to you...

work with windows service[^]

Posted 6-Sep-11 18:25pm

Tejas Vaishnav

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-09-06T18:09:00

First, avoid timers by all means. Use a separate thread instead with System.Threading.Thread.Sleep. This is much more reliable and more straightforward to program.

Secondly, it's hard to see you problem without looking at your code. Services are harder to debug. Use System.Diagnostics.EventLog and log to the system event log you can open and view via the command:

%SystemRoot%\system32\eventvwr.msc /s

See http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx[^].

Another way is implementing most of you code in a separate assembly which you can use in you Windows Service and also in a regular interactive application, such as console application. However, remember that Windows Service is a very unusual host for running code: many aspects will look different. Create a very simple skeleton of the Windows Service first and make sure it works first, add some "meat" later step by step. Perform debug in both modes (interactive and Service) on regular basis.

Don't forget an important flag to use: the static property System.Environment.UserInteractive, see http://msdn.microsoft.com/en-us/library/system.environment.userinteractive.aspx[^]. Very useful.

—SA