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

22 comments:

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

    ReplyDelete
  2. Thanx a lot, this a good solution

    ReplyDelete
  3. 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...

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

    ReplyDelete
  5. 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.

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

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

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

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

    Regards
    Minal

    ReplyDelete
  10. 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.

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

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

    ReplyDelete
  13. Thanks a lot, it worked in my case!

    ReplyDelete
  14. Thannnkkk Youuuuuu !!!!!!!!!!

    ReplyDelete
  15. Eres Grande Brotherr!!

    Me Salvaste el Diaa!!!

    Exitosss!!

    y Thanks

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

    ReplyDelete
  17. 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

    ReplyDelete

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

    ReplyDelete
  19. Thanx a lot, this a good solution

    ReplyDelete
  20. Thanx a lot, this a good solution

    ReplyDelete