SBS 2k3 and Microsoft Search 4.0

I installed Microsoft Search 4.0 on a SBS 2k3 Premium server (Pre R2). Ever
since then, I have been getting the following error in the Application log
whenever the Microsoft Search service starts:

Microsoft Search, event ID 3006

"Performance monitoring for the Gatherer service cannot be initialized,
because the counters are not loaded or the shared memory object cannot be
opened. This only affects availability of the perfmon counters. Rebooting the
system may fix the problem."


Rebooting the system did not correct the problem. I also cleared and
reloaded all counters associated with the MSSearch, MSSGatherer, MSSGTHRSVC,
and UGatherer (and rebooted again). This also did not work.

I suppose I could add a "Disable Performance Counters" entry to the registry
for the service, but I would rather fix the problem. Does anybody have any
ideas? Also, do you know which of the 4 aforementioned services would need
the "Disable Performance Counters" key if I decide to go the route of
disabling the Microsoft Search performance counters.

Thanks,

Joe Welna
.

Relevant Pages

  • Re: Process Performance Counter is Disabled
    ... It should also work with XP Home but I am not 100% sure, when you use the lodctr command you might hit a snag and get a message saying that a certain registry key or value is missing, if you get the message take note of the *exact* registry key or value and try manually crating it and then try the command again. ... Removed the registry entry "Disable Performance Counters" ...
    (microsoft.public.windowsxp.general)
  • Re: Error running program
    ... application I am getting an error "Process performance counter is ... so the request operation cannot be preformed". ... and set the value of the DWORD "Disable Performance Counters" to '0'. ...
    (microsoft.public.windowsxp.general)
  • Process Performance Counter is Disabled
    ... "Process Performance Counter is Disabled, ... Removed the registry entry "Disable Performance Counters" ...
    (microsoft.public.windowsxp.general)
  • Re: Process Performance Counter is Disabled
    ... "John John " wrote: ... Removed the registry entry "Disable Performance Counters" ...
    (microsoft.public.windowsxp.general)
  • RE: Process.GetProcessByName throws InvalidOperationException
    ... You can find documentation on "Disable Performance Counters" in the following knowledge base articles: ... delete "Disable Performance Counters" registry value. ...
    (microsoft.public.dotnet.framework)