The browser was unable to update the service

April 4, 2011 at 04:35:12
Specs: Windows 2003 Server Standard Edition SP1, Intel Xeon 2.33 GHZ and 4 GB of RAM
Hi all.
Since two months ago, we are having in a regulary way of time, the following error message:

Event Type: Error
Event Source: BROWSER
Event Category: None
Event ID: 8007
Date: 4/2/2011
Time: 6:29:23 PM
User: N/A
Computer: OPM1MJD
The browser was unable to update the service status bits. The data is the error.

For more information, see Help and Support Center at
0000: bb 06 00 00 ยป...

When this error appears, DC begin to not answer and all APPs which use it begin to fail.

Any idea? We have W2003 SP1 server.

Thanks in advance.


Gabriel Matas

See More: The browser was unable to update the service

Report •

April 4, 2011 at 07:47:30
What Anti-Virus are you running?
What version of I.E. are you running?

Report •

April 4, 2011 at 08:09:06
First of all, thanks for your answer.

We have Trend Micro OfficeScan V10 and the IE version is 6.0.3790

The problem is that no chenges was done when this problem appear.



Report •

April 4, 2011 at 09:01:34
Well Anti-Viruses are constantly updating them selves so a change could have happened without you knowing. There was a known issue with McAfee that caused this kind of problem so hence the reason I asked the question. I use Trend Micro my self and have not run into this so there is a problem somewhere else. This error is unfortunatly one of Microsoft's "Failed but I do not know why errors." Some questions and things to try...

Are you running a WSUS server or automatic updates of any kind?

People having this error usually find the problem with their Anti-Virus and/or Firewall. What firewall are you using or is t just Microsoft Windows Firewall?

Some people with this error have found issues in their TCP/IP stack. Try rebuilding the stack.

Good luck with this.

Report •

Related Solutions

April 4, 2011 at 09:18:30
Hi ace.

Windows update Service is off on the server, and we don't have any Firewall also. Maybe is a TCP/IP stack problem, as you told me, but I'm not quite sure if we will be able to do that in this production server. Do you know how to do it or when I can find some info about that?

Thanks again.


Report •

April 4, 2011 at 09:40:53
Yes, if you only have one NIC you would have to do it after hours.

Here is where I got the info on the TCP/IP stack causing the problem...

Hope it helps.

Report •

Ask Question