SBS 2008, Event ID 8: The SQLBrowser service was unable to process a client request. errors

The application eventlog of your SBS 2008 server is flooding with the following error more than once a minute.

Event ID: 8
Source: SQLBrowser
Description: “The SQLBrowser service was unable to process a client request.”

I have seen this on multiple servers and it looks like the issue occurs when you install an additional SQL instance and enables the SQL Browser service. This does not occur on a standard SBS 2008 server, because the SQL browser service is disabled by default.

Solution: After some research and found all kind of possible solutions, in my cases the problem was solved by enabling Named Pipes on the protocols for SBSMONITORING within SQL Server Configuration manager. If you have more SQL instance enable Named Pipes for all instances.

To change this go to, Start, All Programs, Microsoft SQL Server 2005, Configuration Tools, SQL Server Configuration Manager. Browse to SQL Server 2005 Network Configuration (32bit) select Protocols for SBSMONITORING and rightclick Named Pipes and select Enable. Repeat this for every Instance you have additional created.

Also checked this only occurs to SBS 2008 servers with SBS 2011 never seen this problem.

Posted in Blog, SBS 2008, SQL 2005 at December 9th, 2011. 5 Comments.

SQL Server (dbname) service won’t start after promoting the server to a domain controller

When you promote your windows member server to a domain controller the SQL Server (dbname) service won’t start anymore.

The system event log notes error even id: 7024 “The SQL Server (dbname) service terminated with service-specific error 17113 (0x42D9).”

Solution: This is because the SQL Server (dbname) service is started under the local system account, this doesn’t work on a domain controller. Start the service under a user account with enough rights.

Posted in Blog, SQL 2005, SQL 2008 at October 22nd, 2010. 2 Comments.

Sharing Buttons by Linksku