bleujaegel
asked on
SQLBrowser event ID 3
I am running Windows SBS 2003 with SQL Server 2005 (installed with Backup Exec 11d) and I am getting the following error in my event logs:
SQLBrowser event ID 3
The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid.
I found a post that said this is the issue:
This message appears because the TCP/IP Protocol for the instance is disabled. If desired, you can enable the TCP/IP Protocol for the instance and then configure the IP addresses you want the instance to listen on.
I looked in SQL Server Manager for a way to configure the IP addresses for the instance, but couldn't find a way to do it. I then looked into the registry and found the TCP/IP settings of 192.168.1.2 and 127.0.0.1 for IP1 and IP2 respectively under the key:
HKEY_LOCAL_MACHINE\SOFTWAR
I have no idea what they should be, but I would imagine that they are correct since they are both valid IP's.
Has anyone had this problem or know how to resolve this?
SQLBrowser event ID 3
The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid.
I found a post that said this is the issue:
This message appears because the TCP/IP Protocol for the instance is disabled. If desired, you can enable the TCP/IP Protocol for the instance and then configure the IP addresses you want the instance to listen on.
I looked in SQL Server Manager for a way to configure the IP addresses for the instance, but couldn't find a way to do it. I then looked into the registry and found the TCP/IP settings of 192.168.1.2 and 127.0.0.1 for IP1 and IP2 respectively under the key:
HKEY_LOCAL_MACHINE\SOFTWAR
I have no idea what they should be, but I would imagine that they are correct since they are both valid IP's.
Has anyone had this problem or know how to resolve this?
Nightman
To enable TCP for the instance, go to the SQL Server Configuration Manager, open the details for the BKUPEXEC instance and enable TCPIP from there.
ASKER
It say it's enabled, and listen all say yes as well. There is 1 adapter called via that says disabled and it's default port shows 0:1433. I do have 4 adapters, and three were disabled before installing BackupExec. Could this be the problem?
Not likely, if they were disabled before installing. However, in my experience SBS has subtle differences to many other windows servers, and it is entirely possible that something I would suggest for SQL Server could break SBS. I would suggest that you post a pointer question in the https://www.experts-exchange.com/Operating_Systems/SBS_Small_Business_Server Topic Area as well.
Is it causing any problems, or is this just an annoyance?
Is it causing any problems, or is this just an annoyance?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
According to the last link, it appears to be a non-issue. That's all I needed to hear. Nice work!
I posted the followup comment as a new question