Search:

giblitz();

little nuggets of insider knowledge from Fusion Powered

service-specific error 10049

When working with sql server recently, I changed the initial configuration so that I could use it via a VPN IP address that was used and I also told sql server NOT to listen on all IP addresses also. I found that a website I was working on had stopped working, turns out that the sql server process had restarted and failed to start!

I checked the event log and found an event with this string inside “service-specific error 10049“, it’s a little bit cryptic but the error stopped sql server 2008 from starting up properly.

I found that the problems were firstly, I told the sql server to NOT bind on all available IP addresses, so changed that back, and that secondly, one of the IP addresses I did tell it to bind to, wasn’t available when sql server restarted (a server vpn ip address – connection hadn’t been established). Binding to all IP address and removing the VPN address entry seemed to do the trick!


  1. Do you have any experiences you'd like to share? Tell me about them!

Leave a Reply