Three SQLBrowser Event Viewer messages generated on a server running Backup Exec

I'm seeing three errors in the Application event logs of a Backup Exec server, all with the source of 'SQLBrowser'.  The OS is Windows Server 2003 and the Backup Exec version is 12.0.  

The events are back to back with oddly sequential Event Ids: 1, 2, and 3:

Event 1, Source: SQLBrowser - The SQL Configuration for SQL is inaccessible or invalid
Event 2, Source: SQLBrowser - The configuration of the SQL instance MSSQLServer is not valid
Event 3, Source: SQLBrowser - The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid

Can anyone help me understand these three errors and offer ways to correct them?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rodney BarnhardtServer AdministratorCommented:
This really seems nothing to worry about per BE.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
james_axtonAuthor Commented:
I saw that, but it only addresses one of the three messages.
Rodney BarnhardtServer AdministratorCommented:
I looked and there could be various reason. Here is some information:
One had two different version of SQL on the server and uninstalled the other version.
Here was another solution:
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.
You can try changing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\AdminConnection\Tcp\TcpDynamicPorts
The default value is 0 change it to 1434. Restart the SQL service and the error from the SQL Browser stop being recorded at every startup.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Rodney BarnhardtServer AdministratorCommented:
This MSDN has more information, and also mentions #2 possible being caused by SQL 2000 being on the same box as 2005.
james_axtonAuthor Commented:
rbarnhardt, if I missed multiple installations of SQL Server I'm going to be embarrassed.  I'll check tomorrow morning and report back.  Thanks!
james_axtonAuthor Commented:
This gets slightly complicated.  Under Installed Applications there is only one instance of SQL Server, version 2005.  I was also able to verify that there has only been one SQL Server installation on this server - again, version 2005.    However, there are SQL Server files sitting on another partition that belonged to SQL Server 2000.  This is not an "official" installation, mind you, but rather a back up of sorts that someone made using this spare partition (it's not the C drive, where SQL Server 2005 is).  Do you think those files might be causing the issue?  I personally don't, but I'm also not very well versed in this area.  Do you still think it's safe to ignore these messages?  
Rodney BarnhardtServer AdministratorCommented:
Here is an idea. If you are backing up the other drive, exclude the SQL 2000 files and folders if the are not needed. This may rid your error messages. The errors that you gave do not seem to specify a drive letter, so unless it is showing that in more detail that you did not include AND you are backing up that other partition, then they could be related.
james_axtonAuthor Commented:
I got rid of Event Id 3 by changing the TCPDynamicPorts key from 0 to 1433.  Events 1 and 2 are still present.  I'm inclined at this point to just ignore the messages.  They are only happening when the server is rebooted, and the SQLBrowser service is starting okay.  Here are a few more notes:

- TCP/IP for the BKUPEXEC instance is enabled
- Only one instance of SQL Server is installed
- The SQL server has been patched to SP2
- The only SQL-related files that are being backed up by Backup Exec are SQL Server 2005 databases located on a separate SQL Server 2005 server.  

If this backup server is otherwise healthy, the SQLBrowser service is starting, and backups are being marked as "Complete", do you think there's any reason for concern over events 1 and 2?  Internet searches reveal many frustrated requests for assistance with this very issue, but relatively few successful fixes.
Rodney BarnhardtServer AdministratorCommented:
No. I think it is fine. I was just throwing out the suggestion to try to narrow down the problem. Anything I read seemed to indicate that these messages were no real issue.
james_axtonAuthor Commented:
Thanks for staying with it rbarnhardt!  It's very much appreciated!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.