December 21, 2009

Resolving the SQL Server Error “The request failed or the service did not respond in a timely fashion”




When you are unable to log into your SQL Server, one recommended solution is to see if the required services are running. To do so, you can go to Start > Microsoft SQL Server 2005/2008 > Configuration Tools > SQL Server Configuration Manager.

image

Select the ‘SQL Server Services’ node and you can see the services that are running. If you observe in the screenshot shown below, the SQL Server service (MSSQLSERVER) is not running

image

When you right click and attempt to start the service, you may encounter an error that says “The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details”

image

One of the solutions to resolve this error is to see if the default port of SQL Server i.e: 1433 is not being used by a different service. Click on the ‘Protocols for MSSQLServer’ node

image

On investigating, I found that the VIA protocol was using up port 1433.

image

I disabled the protocol by right clicking on it and the problem got solved


Did you like this post?
kick it on DotNetKicks.com
subscribe via rss subscribe via e-mail
print this post follow me on twitter


About The Author

Suprotim Agarwal, ASP.NET Architecture MVP works as an Architect Consultant and provides consultancy on how to design and develop Web applications.

Suprotim is also the founder and primary contributor to DevCurry, DotNetCurry and SQLServerCurry. He has also written an EBook 51 Recipes using jQuery with ASP.NET Controls.

Follow him on twitter @suprotimagarwal

 
  Feedback:

comments

20 Responses to "Resolving the SQL Server Error “The request failed or the service did not respond in a timely fashion”"
  1. Anonymous said...
    June 18, 2010 at 8:42 AM

    The proposed solution by Suprotim Agarwal re disabling VIA worked perfectly.

  2. Anonymous said...
    July 6, 2010 at 5:07 PM

    Thanx a lot, this a good solution

  3. Anonymous said...
    August 10, 2010 at 4:01 AM

    THANX A LOT SIR..really very helfull...i nearly struggled for 3 days regarding this problem.. and finally solved with ur solution.. thnaq thanq thanq...

  4. Anonymous said...
    August 11, 2010 at 6:44 AM

    I looked at my settings and it was already disabled but I still have the problem.

  5. Anonymous said...
    August 11, 2010 at 7:09 AM

    If VIA is already disabled, the workaround is found here
    http://support.microsoft.com/kb/955494
    Try and Start the service from Services snap-in console. If it doesn't start under the id specified, start under the local system account.

  6. Anonymous said...
    August 28, 2010 at 3:17 PM

    thanks, it work!

  7. Anonymous said...
    October 25, 2010 at 6:16 AM

    Very thnks for your solution....
    No words to express this.......
    Thanks a Lot.

  8. Anonymous said...
    October 28, 2010 at 5:02 AM

    Thank you very much yaar.Once again thanks for your post .It solved my problem .

  9. Anonymous said...
    November 10, 2010 at 2:16 PM

    Agarwal ji, you are star....I struggled 2hrs before this...;-)

  10. Anonymous said...
    February 18, 2011 at 5:39 AM

    Thank you much.. It helps me alot... :)

    Regards
    Minal

  11. Spacemoses said...
    March 6, 2011 at 10:25 AM

    I had this same problem. I determined that the problem was actually due to changing my Windows password that the SQL Server account used. Once I updated the password in the Configuration Manager for the service, I was able to start it just fine.

  12. Anonymous said...
    March 31, 2011 at 11:34 AM

    Tnx Very Useful Solution. Well it serve to me changeing the 1433 port, by 1434. Anyway tnx a lot.

  13. Anonymous said...
    October 13, 2011 at 3:42 AM

    Excellent

  14. Anonymous said...
    November 18, 2011 at 5:28 AM

    That Was Really Awesome....
    I was Searching for Solutions Since Last 2 hrs..
    Great Work....
    Thanks .

  15. Simon said...
    November 21, 2011 at 3:01 AM

    Thanks a lot, it worked in my case!

  16. asif said...
    March 10, 2013 at 10:59 PM

    Thannnkkk Youuuuuu !!!!!!!!!!

  17. Anonymous said...
    April 17, 2013 at 2:11 PM

    Eres Grande Brotherr!!

    Me Salvaste el Diaa!!!

    Exitosss!!

    y Thanks

  18. DiegoS! said...
    May 6, 2013 at 4:56 AM

    Velho Muito obrigado por seu post estava com esse problema e com sua ajuda foi resolvido obrigado mesmo

  19. Harishankar Maurya said...
    August 31, 2013 at 6:46 AM

    The sevice failed and or the did not respond in a timely fashion.
    Consult the event log or other applicable error log for details.



    not working

  20. Zohair Ahmed said...
    November 21, 2013 at 10:53 PM


    its Really work .VIA disable,Its very useful for me ,Working Perfectly,Thanks for sharing

 

Copyright © 2009-2014 All Rights Reserved for SQLServerCurry.com by Suprotim Agarwal | Terms and Conditions