2 Exchange MMC Error

Can you let us know the error messages in the Event Viewer.

Is the error with just that Public Folder. if you have multiple replicas, make sure its upto date

For the ADUC error, refer to the link below
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3721529&SiteID=17

The error below corresponds to the 2nd picture error.  The top error does not generate anything in the event logs.

The description for the Event ID (1000) in Source (Microsoft Exchange Server) cannot be round.  The local computer may not have the necessary registry information or message DLL files to display the message from a remote computer.  You may be able to use /AUXSOURCE-flag to retrieve this discription.  The following information is part of the event: maildsmx.dll 6.57638.1, 430e738e,rtdll.dll,52.3790.3959,45d70ad8,0,0002a0d0.

the mmc seems to error out after selecting a user a couple of times, similar to a memory leak.  no idea how to fix it.

Did you ever fix this issue I am having the same issue now.
Windows it wonderful this is really frustrating I have had this problem for a few months now it goes and comes. If someone knows how to fix please update.

ERR Microsoft for the win!!

I never fixed this.  From what I could tell it started after I brought a 2008 DC into my domain and updated the forest schema  to 2k8.  Did you do the same?

This is nothing but MMC files are damaged. You will have to reconfigure them.

how?  I'm open for any suggestions

I just found the fix its a IE7 update issue Ha go figure worked great for me!

http://support.microsoft.com/kb/932513

Just did what they said and fixed my issue.

Also stopped the following first

Use the command net stop MSExchangeSA /y to stop System Attendant and all its dependent services.

Use the command net stop IISAdmin /y to stop all IIS engines.

Then did they following for some reason would not start right.

http://technet.microsoft.com/en-us/library/aa998163(EXCHG.65).aspx

This sounds right cause The problem didn't start till i updated the IE. So I have had this problem since then.

Oh well I hope you have luck with the above comment.

Thanks
Vonsean!

Wow...this fixed it for me.  Nice job.  How did you find that KB?

You wouldn't believe it, but that didn't solve the problem in the end.  The MMC still generates the same error above after a few queries.

Well Just as in your issue my server is still doing this. After a day or two it comes back. I have been dealing with this for a while. I am tempted to contact microsoft on this. Will let you know if i am able to correct it.

Thanks!
Vonsean

I have 1 free open ticket with MS as well, but I'd hate to use it on this MMC error.  Please let me know if you get it figured out. :)

Update: I haven't called M$ yet, but I've noticed things that might be useful information.  I can now get errors in the application log regarding this event.

Event Type:      Error
Event Source:      Microsoft Management Console
Event Category:      None
Event ID:      1000
Date:            3/20/2009
Time:            8:16:58 AM
User:            N/A
Computer:      EXCHANGE
Description:
The description for Event ID ( 1000 ) in Source ( Microsoft Management Console ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: mmc.exe, 5.2.3790.3959, ntdll.dll, 5.2.3790.3959, 0002a0d0.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6d 6d 63   ure  mmc
0018: 2e 65 78 65 20 35 2e 32   .exe 5.2
0020: 2e 33 37 39 30 2e 33 39   .3790.39
0028: 35 39 20 69 6e 20 6e 74   59 in nt
0030: 64 6c 6c 2e 64 6c 6c 20   dll.dll
0038: 35 2e 32 2e 33 37 39 30   5.2.3790
0040: 2e 33 39 35 39 20 61 74   .3959 at
0048: 20 6f 66 66 73 65 74 20    offset
0050: 30 30 30 32 61 30 64 30   0002a0d0
0058: 0d 0a                     ..      

I am having an almost identical issue, with the exception that my offset (last octet in the support info) is 0001bd02.  I am not having much luck finding a root cause.  Did either of you find a fix yet?

Scott

No.  I am probably going to upgrade my exchange server to 2k7 soon so I haven't bothered calling M$ about this.

I have that on my plate as well, but am a bit nervous about attempting an update with a 'broken' system, no matter how trivial it may be... I will post back if I find a fix.

Scott

There are 2 hotfixes out for this error, but they both pertain to 2003 and not running from XP-32bit.  The 2 for 2003 are...

http://support.microsoft.com/kb/936345

http://support.microsoft.com/kb/946459

The 2nd seems to have worked for my 2003 boxes, but no love for XP.