Q
Problem solve Get help with specific problems with your technologies, process and projects.

Unable to manage public folder node in Exchange Manager

I am running Exchange 2000 enterprise version, and for some reason I am not able to manage the public folder node in the Exchange Manager. Another problem that I am facing is that if I enable SSL on OWA, it takes ages to load up. (I have created my own certificate, so I am not using a purchased one.) Any ideas?
You didn't say what happens when you try to manage them, so I'm going to guess that you're getting a common error -- 0x80004005. Error 80004005 is a generic error message that translates to MAPI_E_FAIL or in some contexts MAPI_E_CALL_FAILED (a.k.a. 'the operation failed').

Viewing, expanding or modifying permissions on a PF in ESM can cause this error to appear. There are a variety of possible causes for this:

  • The default Web site on the server doesn't contain a blank Host header.
    (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q282076)

  • The default Web site on this server is using the wrong network adapter IP address.
    (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q285643)

  • The Exadmin virtual directory is configured to require SSL.
    (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q279863)

  • You apply the folder traversal vulnerability patch (MS Security Bulletin MS00-078) but don't have Windows 2000 SP2 installed.
    (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q280806)

    For general troubleshooting of this error, see http://support.microsoft.com/default.aspx?scid=kb;en-us;Q289492 and http://www.microsoft.com/exchange/using/tips/Svr_80004005.asp.

    As for the slowness with SSL, that's not much of a surprise. SSL adds a lot of overhead to the system, especially processor overhead. Have you looked at the Process and Processor performance objects to see if you're spiking the CPU during the request? I would have a look at the disk, network, memory and CPU performance counters and see what resources are being consumed during the logon and mailbox access process. It might also be worth your while to take a network trace, as well. This will help you locate network-related errors (if any).

    Editor's Note: For more information, check out our extensive collection of Exchange Best Web Links.

    *Sign up for our free weekly Exchange tips to have expert technical advice about managing Exchange delivered right to your inbox.


  • This was last published in March 2002

    Dig Deeper on Exchange Server setup and troubleshooting

    Have a question for an expert?

    Please add a title for your question

    Get answers from a TechTarget expert on whatever's puzzling you.

    You will be able to add details on the next page.

    Start the conversation

    Send me notifications when other members comment.

    Please create a username to comment.

    -ADS BY GOOGLE

    SearchServerVirtualization

    SearchCloudComputing

    SearchSQLServer

    SearchEnterpriseDesktop

    SearchVirtualDesktop

    Close