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

    Question

  •  

    Hi,

     

    I'm not able to start reporting services after applying the last SQL Server 2005 hotfix (9.0.3068), I'm getting the followwing  error 1053: The service did not respond to the start or control request in a timely fashion.

     

    Any clues ?

     

    Regards

     

    Dejan

     

     

     

     

     

     

     

    Friday, July 11, 2008 9:17 PM

Answers

  • Hi folks,

     

    As I said before I have this problem with DPM, so I oppened a call to PSSE.

     

    We managed to circumvent the problem with this instrucions:

     

                    My name is xxxxx and I am the Support Engineer that will be helping you with this case.  After looking over the case logs, I think I might have some information that will help.  Below is a process that might correct the timeout issue. 

     

     

     

    1.

     

    Click Start, click Run, type regedit, and then click OK.

    2.

    Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

    3.

    In the right pane, locate the ServicesPipeTimeout entry.

    Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:

    a.

    On the Edit menu, point to New, and then click DWORD Value.

    b.

    Type ServicesPipeTimeout, and then press ENTER.

    4.

    Right-click ServicesPipeTimeout, and then click Modify.

    5.

    Click Decimal, type 60000, and then click OK.

    This value represents the time in milliseconds before a service times out.

    6.

    Restart the computer.

     

    Now it's working. But they didn't agree that this is a bug, so they charged me the call. I do not agree with this because everything was working well and after I applyied a Security Hot Fix the service failed to start. If I understood correctly they said it's not a bug because it's not documented. They said that it would be a bug it the only solution were to unistall the hotfix.

     

    What do you think about this?

     

    Luck with this hot fix,

     

    Paulo

    Monday, July 21, 2008 3:51 PM
  • Hi,

    When this KB is installing, the services of SQL will be terminated automatically. So please check the SQL Server Configuration Manager, make sure that the service has started.

    Hopefully this helps.

     

    Monday, July 14, 2008 10:28 AM

All replies

  • Hi,

    When this KB is installing, the services of SQL will be terminated automatically. So please check the SQL Server Configuration Manager, make sure that the service has started.

    Hopefully this helps.

     

    Monday, July 14, 2008 10:28 AM
  • Hi,

    We are getting the same error message on one of our SQL servers.
    The problem might have been that the service Reporting Services was NOT running during the installation of the patch.
    We had a scheduled restart of the service go in and stop it just as the WSUS update was running.

    Now we're stuck and cannot repair the installation of Reporting Services or run the service.
    How do we do then?

    Thanks,

    Monday, July 14, 2008 11:45 AM
  • We're also having the same problem.

     

    I cannot confirm if Reporting Services was running or not. It is set to automatically start, and there are no indications that it failed beforehand, but the same result as above is what I get now every time it tries to start, manually or otherwise.

     

    Thanks
    Tuesday, July 15, 2008 6:12 PM
  • Hi all,

    Have same Problem, after installing KB 948109 and rebooting the server Report Server Service did not start anymore...

    Any help is highly appreciated !

     

    TIA

    acki

     

    P.S. Deinstalling the Hotfix and Report Services runns again...

    Wednesday, July 16, 2008 8:39 AM
  • I had exactly the same problem! In thelog I can see the update for reporting services failed. Alle the others were good. Does anyone have a solution.?

     

    Frank

    Wednesday, July 16, 2008 2:10 PM
  • I had the same problem on our server.  I called PSS and they ackowledged that others have had the same issue.  They gave me 2 choices:
    1.  Uninstall the hotfix
    2.  Add a registry key to allow a longer wait time for the services to start and reboot (similar to: http://support.microsoft.com/?kbid=884495)

    I opted for #2 and it worked for me. 
    Hope this helps others,
    Tom
    Wednesday, July 16, 2008 10:00 PM
  •  

    We uninstalled the hotfix to solve the problem for the time being.

    Maybe we'll try the registry hack later.

     

    Cheers,

    Michael

    Thursday, July 17, 2008 6:01 PM
  • Hi,

    I'm currently having the same problem - are there any news available?

    Regards,

     Sparky222

     

     

    Friday, July 18, 2008 10:55 AM
  • I've the same problem after applying KB948109, but the message that appears in event viewer is:

    Event ID 7000

    The SQL Server Reporting Services (MS$DPM2007$) service failed to start due to the following error:

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

     

     

    Event ID 7009

     

    Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (MS$DPM2007$) service to connect.

     

    Unisntalling the hotfix the service is OK.

     

     

    Just for the records: this have happened in 2 servers, but in my notebook it's OK. Perhaps in my notebook all went all right because sql 2005 is the default instance. On the server it's a named instance.

     

     

     

    Sunday, July 20, 2008 2:54 AM
  • I don't think that the problem is dependent using instance names or not.

     

    I've tested it at six environments - all with the default instance name - and I've got the problems in every SSRS.

     

    But now I've some more problems - The un- installation routine doesn't work on two of my machines. One is based on a Windows Server 2008 x64 and the other is a Windows Vista Business x64. It was necessary to uninstall the complete Sql Server and fixing entrees in the registry.

    Monday, July 21, 2008 6:19 AM
  • Hi folks,

     

    As I said before I have this problem with DPM, so I oppened a call to PSSE.

     

    We managed to circumvent the problem with this instrucions:

     

                    My name is xxxxx and I am the Support Engineer that will be helping you with this case.  After looking over the case logs, I think I might have some information that will help.  Below is a process that might correct the timeout issue. 

     

     

     

    1.

     

    Click Start, click Run, type regedit, and then click OK.

    2.

    Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

    3.

    In the right pane, locate the ServicesPipeTimeout entry.

    Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:

    a.

    On the Edit menu, point to New, and then click DWORD Value.

    b.

    Type ServicesPipeTimeout, and then press ENTER.

    4.

    Right-click ServicesPipeTimeout, and then click Modify.

    5.

    Click Decimal, type 60000, and then click OK.

    This value represents the time in milliseconds before a service times out.

    6.

    Restart the computer.

     

    Now it's working. But they didn't agree that this is a bug, so they charged me the call. I do not agree with this because everything was working well and after I applyied a Security Hot Fix the service failed to start. If I understood correctly they said it's not a bug because it's not documented. They said that it would be a bug it the only solution were to unistall the hotfix.

     

    What do you think about this?

     

    Luck with this hot fix,

     

    Paulo

    Monday, July 21, 2008 3:51 PM
  • Hi,

     

    I also did the reghack above with positive result.

    Although I would call it a bug, since you actually have to do something to get around the problem.

    Wednesday, July 30, 2008 1:48 PM

  • I have a pc with Windows XP SP 2

    Sql Server 2000 and Sql Server 2005 Express Edition.  Both Worked right but not now...

    Now I'm having a message error when I try to start sql server in both cases.

    The error 1053...

    Some users here said that changing some registry values they managed to solve the problem

    What registry keys and what values are the corrects??

    Thanks a lot in advance.









    Saturday, October 18, 2008 10:52 PM
  •  

    I had the same exact problem after updating our server through Microsoft Update and it killed DPM2007, after much time thinking there was something wrong with SQL it was actually .Net Framework 2.0 where is had become corrupt.
    Monday, November 03, 2008 4:04 AM
  • The solution of PES sure worked for us (although we always are very careful and reluctant in changing the registry).

    Thank you very much Paulo for sharing this solution!

    Kind regards,

    Peter


    Peter Elzinga
    Wednesday, January 21, 2009 9:37 AM
  • Please refer the below link

    http://support.microsoft.com/kb/954835

    Saturday, August 27, 2011 12:48 PM
  • Hi folks,

    As I said before I have this problem with DPM, so I oppened a call to PSSE.

    We managed to circumvent the problem with this instrucions:

                    My name is xxxxx and I am the Support Engineer that will be helping you with this case.  After looking over the case logs, I think I might have some information that will help.  Below is a process that might correct the timeout issue. 

    1.

    Click Start, click Run, type regedit, and then click OK.

    2.

    Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

    3.

    In the right pane, locate the ServicesPipeTimeout entry.

    Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:

    a.

    On the Edit menu, point to New, and then click DWORD Value.

    b.

    Type ServicesPipeTimeout, and then press ENTER.

    4.

    Right-click ServicesPipeTimeout, and then click Modify.

    5.

    Click Decimal, type 60000, and then click OK.

    This value represents the time in milliseconds before a service times out.

    6.

    Restart the computer.

    Now it's working. But they didn't agree that this is a bug, so they charged me the call. I do not agree with this because everything was working well and after I applyied a Security Hot Fix the service failed to start. If I understood correctly they said it's not a bug because it's not documented. They said that it would be a bug it the only solution were to unistall the hotfix.

    What do you think about this?

    Luck with this hot fix,

    Paulo

    Thanks PES for the solution. Update service of WSUS starts again !!!

    (Server W2008 SP2 64bits without kb954835)

    • Edited by furax033 Wednesday, August 01, 2012 12:52 PM
    Wednesday, August 01, 2012 12:42 PM
  • I just installed SQL Server 2008 R2 SP2 (on a Windows Server 2008 R2 SP1 OS).

    Same symptoms, SSRS was working before, and after would not start with a, "...the service did not respond to the start or control request in a timely fashion"

    Used the fix Paulo described and bingo, it is now working fine.  Thanks for the post.

    Tuesday, August 14, 2012 7:07 PM
  • Worked fine for me but I Increased the value to 100000.
    Wednesday, September 12, 2012 5:37 PM
  • Thanks very much! It worked for me! :)

    Vijay Ramshetty

    • Proposed as answer by Vijay Ramshetty Thursday, December 05, 2013 7:13 AM
    Thursday, December 05, 2013 7:12 AM
  • Yes I had the same problemmmmm. Thanks for the post.
    Tuesday, January 28, 2014 5:38 PM
  • I was with a problem in my Reporting Services installation exactly like this and with this issue it was solved.

    Tuesday, February 04, 2014 5:31 PM
  • Worked fine for me but I also had to Increase the value to 100000.

    SQL Server DBA

    Wednesday, March 05, 2014 4:13 PM