Skip to main content
8 events
when toggle format what by license comment
Aug 29, 2016 at 11:13 vote accept Magier
Apr 25, 2016 at 18:47 comment added Magier @Max Vernon yes I have gone through this article, TY. But the instance definitely continued to work. Only DBMail stopped. I still wonder why. Does it make a difference that the TCP Port is a dynamic port? -Because that is the case here.
Apr 21, 2016 at 20:03 comment added Hannah Vernon See msdn.microsoft.com/en-us/library/ms165724.aspx#Anchor_2 for details about the effects of turning off the SQL Server Browser service.
Apr 21, 2016 at 19:51 comment added Hannah Vernon @Magier - Cody is correct - SQL Server Browser is required to allow translation of instance names to port numbers when SQL Server is using a non-standard port, or SQL Server was installed using an instance name. Whether there is 1 or 100 instances on the machine makes no difference.
Apr 21, 2016 at 14:02 comment added Magier I thought the browser is necessary only in case there are running more than one instances on a server?
Apr 21, 2016 at 12:48 comment added Cody Konior If your apps use an instance name on a non-1433 port and Browser isn't running then it's impossible to connect. The only explanation is SQL Client aliases. Yes the config doesn't exist; I don't know where it gets that when it doesn't exist, but I read you can create it to override it.
Apr 21, 2016 at 10:00 comment added Magier The application's connection defenitely does not include a port, it just uses servername\instancename. Also, that specific node just held one single instance at the time the error occurred. So I wonder why this is a problem at all to stop the browser. The DatabaseMail.exe.config file does not exist.
Apr 21, 2016 at 9:27 history answered Cody Konior CC BY-SA 3.0