I am trying to run the windows service through services.msc. I am getting following error.

Question

0.00/5 (No votes)

See more:

C#

Services
---------------------------
Windows could not start the Window Service service on Local Computer.



Error 1053: The service did not respond to the start or control request in a timely fashion.

I am trying to compress the pdf. If the pdf size is greater than 30 mb i am getting above error.

What I have tried:

I had Done Following changes in registry

C#

Create the registry entry for the Services Pipe Timeout and give it higher than the default value:
Start the registry editor (regedit.exe)
navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Right-click on the above key and choose New, then DWORD Value
Type ServicesPipeTimeout as the name for it and press ENTER
Right-click on the ServicesPipeTimeout value and choose to Modify it
In the Base section click Decimal
In the Value data text box type for example 180000 as the value of timeout period and click OK
Restart the computer

Then also it is giving same error.

Posted 21-Nov-16 20:37pm

dattaprasaddhuri

Updated 21-Nov-16 21:57pm

Add a Solution

Comments

Richard MacCutchan 22-Nov-16 2:46am

The error is telling you what the problem is. You need to do some debugging to find out why.

Mehdi Gholam 22-Nov-16 2:47am

Show your code, the above explanation is not helpful.

Also why compress a pdf in a service on the service startup.

2 solutions

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)

Bernhard Hiller · Answer 1 · 2016-11-21T21:43:00

Solution 1

The startup of a Windows Service is just a start of that service including its configuration. It is not at all meant for doing the work the service was created for. That work has to be done after startup.

Posted 21-Nov-16 21:43pm

Bernhard Hiller

23741 · Answer 2 · 2016-11-21T21:57:00

Use a timer in your OnStart to perform the action you want so as not to block the OnStart from returning on time.

Don't do your action (compressing etc..) for a few seconds after the OnStart has been called thereby not blocking and causing a timeout.

If you think about it - it's good that it does time out - can you imagine having quite a few services blocking the service manager for extended periods of time?