A search through TechNet only revealed a single entry, and this particular KB article referenced a different error code. It went on to explain how to re-register the Exchange namespace with WMI. The error code above, 0x80080005, translates to server execution failed which sounds quite bad at first.

As it turns out, recycling the WMI service should be enough to sort out this problem. For some reason, the System Attendant had become detached from the WMI service. In this case, the server was restarted, which obviously cured the problem.

I've blogged this in the hope that someone searching for '9097 0x80080005' will get a hit. :-)

Comments

What do you mean recycle the WMI? I ran WBEM util and a recursive search for classes returns only 57 out of an expected 600 classes so I'm a tad worried !

How can I reinstall WMI on a win2k server?

Posted by: Damian Barrow at Jan 23, 2004 3:25:12 AM

We get this error on some of our Exchange 2003 servers at a 5 minute interval, as described in the KB article. But the solution suggested by Microsoft is not good, apparently!
This error is poorly documented by MS.
Konan Houphoue

Posted by: Konan at Apr 7, 2004 9:20:17 AM

We had this same problem. To easily fix this go to the following article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;288590&sd=ee

It is as simple as running a utility from the system32 directory against a file on the Exchange CD.

Posted by: nathan at Jul 14, 2004 11:15:51 PM

I was getting a similar error when trying to install Exchange 2003 on a new and prep'd WIN2003, the actually errors in the logs varied but the main jist was 'Error code 0X80080005 (5): Server execution failed'

The main problem was the same, WMI had hung and a kill and start did the trick.

Posted by: Nathan at Sep 13, 2004 2:16:49 AM

Hi,

On our Exchange 2000 Server, the error code 80080005 appears in the EventSystem error ID 4097. The description reads, "The COM+ Event System detected a bad return code during its internal processing. HRESULT was 80080005 from line 42 of .\eventsystemobj.cpp." Regardless of what event error the error code 80080005 appears in, does 80080005 always allude to the same problem?