Indexing Service causes MMC error: Failed to create empty document

I get the error Microsoft Management Console "Failed to create empty document" when trying to access the Exchange System Manager from our Exchange Server. I found this solution to the problem on EE, but it didn't resolve my issue: 
I went into task manager and noticed cisvc.exe (the indexing service) was utilizing over 60% of my CPU, and had been for over 8 hours, so I stopped the service. Then tada, anything that uses MMC started working properly. For kicks, I restarted the service, and it is hardly registering any cpu usage. My question is, is there any reason the Indexing Service needs to run on Exchange 2003? If so, how can I get it to stop utilizing that much CPU and prevent the error from showing up? What could be triggering the service to shoot up like that?
The OS is Windows Server 2003 R2 SP1 with 3Gb of RAM, Dual Intel XEON 3.00 GHz. There is consistantly over 3Gb available on the C partition.
Let me know if there is any more information needed to assist with this question.
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

jrstxConnect With a Mentor Author Commented:
Yes,  I have had the indexing service turned off on the server since Monday 02/04, and have not had any negative consequences. I appreciate you trying to help out on this.
Many MMC console issues can be resolved by upgrading from 2.0 to 3.0 MMC console.

I have been watching this post and found that you can't create temp files by using mmc console. Do you have something, like AV software, that prevents the creation of .tmp files?
jrstxAuthor Commented:
I checked the version of MMC on the server, and it was already v3.0. Do you know if I need to have the indexing service running on Exchange?
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

ChiefITConnect With a Mentor Commented:
I did a little research. Looks like a known problem with MMC. See if this may help you out. Sorry for the delayed response.

jrstxAuthor Commented:
I appreciate the advice, however, I already found that article and no luck there. I have plenty of space available on C: and the TEMP environment variable does exist.  Last night I turned off the Indexing Service on the server, and so far, I haven't noticed any negative effects on Exchange. I will continue to monitor. If you come across and thing else I can try I'd appreciate it.

Did the indexing service do the trick?
All Courses

From novice to tech pro — start learning today.