Tell me about the issue and I’ll help you find the solution you need.
You cannot open a public folder item when the server that holds the public folder database is stopped in an Exchange Server 2010 environment
Content provided by Microsoft
Applies to: Microsoft Exchange Server 2010 Service Pack 1Exchange Server 2010 EnterpriseExchange Server 2010 Standard
Consider the following scenario:
You have several public folder databases that are installed on several Microsoft Exchange Server 2010 servers.
You configure public folder replication between the public folder databases.
You configure the database of a mailbox to point to a public folder database on another server.
The public folder database that is specified cannot be accessed.
You connect to the mailbox by using a MAPI client application, and you try to open a public folder item.
In this scenario, you cannot open the public folder item. Additionally, the user interface of the MAPI client application may be corrupted.
This problem occurs because Exchange Server 2010 does not support that the MAPI client application calls that look for an alternative public folder when the default public folder database is unavailable. Therefore, the MAPI client application keeps trying to connect to the default public folder database instead of trying to connect to other public folder databases in the referral list.
To resolve this issue, install the following update rollup:
2425179 Description of Update Rollup 2 for Exchange Server 2010 Service Pack 1
Note Client redirection occurs only if the server that hosts the specified public folder database is not available. When the server that hosts the public folder is available, client redirection does not occur if a public folder database is dismounted. In this scenario, the client cannot open a public folder even when the update is installed.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
ERROR: at System.Diagnostics.Process.Kill()
at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)New URL: about:blank