August 19, 2011 at 1:55 am
Does anyone konw of a reason why the SQL Server Browser would terminate unexpectedly ?
This is a newly built server, SQL 2008 R2 + SP1, named instance and a non standard port). When the broswer service isnt running we cannot connect to Analysis Services. This box is due to go into produciton but I'm currently thinking of rebuilding it if I cannot resolve this issue. We will be running a number of large cubes on this server which take in excess of 12 hours to process. If the browser restarts during processing the cube/SQL Agent job fails. I have tried using different services account to start the process but with the same outcome. The error is...
The SQL Server Browser service terminated unexpectedly. It has done this 11 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Does anyone have any ideas ??
Thanks
bg
August 19, 2011 at 2:20 am
Does the event viewer post any other error messages than the one above?
Anything in the SQL Server log directory?
You can start the service from the command line with a -c switch, and I think this will then post errors when it crashes, so would be worth giving a go - instructions here:
http://msdn.microsoft.com/en-us/library/ms181087.aspx
The things I'd be looking at would be a port conflict (UDP 1434) or some sort of firewall/security software issue
August 19, 2011 at 2:35 am
Hi, there are no other errors in any of the SQL error logs or event logs. Only other software that has been installed is Proclarity and we use this across our SQL servers and never have had a port issue. I will try starting from the command line and see if that produces any errors. Thanks
August 22, 2011 at 2:54 am
OK the C: drive on this server has been reimaged. So I ma in the process on manually installing SQL 2008 r2. The installation hangs when its get to "SQLBrowserConfigASAction_install_startup_cpu64" then eventually times out with.
The following error has occured
Server "SQL Browser" start request time out.
Click retry to retry the failed operation or click cancel to cancel this operation and continue.
Appication event log show the following....
1. The SQLBrowser is enabling SQL instance and connectivity discovery support.
2. The SQLBrowser is enabling Analysis Services discovery support.
3. The SQLBrowser service has started.
4. The SQLBrowser service has shutdown.
5. The SQLBrowser is closing Analysis Services discovery support. There are no SQL Server Analysis Services instances or the discovery service encountered an error.
6. The SQLBrowser is enabling SQL instance and connectivity discovery support.
August 22, 2011 at 3:15 am
There's a link here about the remnants of a 32-bit install of SQL Server that was causing issues:
Although if you've re-imaged and are still having issues, I'd say it's time to log a case with MS Support
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply