Outlook clients repeatedly disconnect from and reconnect to Exchange Server 2013
You experience one or more of the following symptoms in Microsoft Exchange Server 2013.
The Microsoft Outlook 2013 client, Microsoft Outlook 2010 client, or Microsoft Outlook 2007 client disconnects from the server that is running Microsoft Exchange Server 2013. Shortly after the disconnection, the client reconnects to the Exchange server. This behavior continues repeatedly.
The MSExchangeRpcProxyAppPool is continually recycled. In Event Viewer under “Application and Services Logs \ Microsoft \ Exchange \ ActiveMonitoring” in the ProbeResult log, you see probe result errors for the “Outlook” service for different 2013 databases that indicate the following value:
In the Details view in the log entry, you see the following line:
Microsoft.Exchange.Data.Storage.DatabaseNotFoundException: The database with ID <GUID> couldn't be found
To resolve this problem, use one of the following methods, as appropriate.
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
If you are not using legacy public folder databases, or if you are working in a pure Exchange 2013 environment, remove the default public folder database setting on each Exchange 2013 Mailbox database that points to the deleted public folder database object.
To do this, connect to CN=Configuration in ADSI Edit, and then navigate to the following location:
Domain.com/Configuration/Services/Microsoft Exchange/Org/Administrative Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Databases
Clear the msExchHomePublicMDB value so that it reads as <not set>.
If you are in an Exchange co-existence environment that includes Exchange 2013, and you are still connecting to legacy public folder databases (that do not use Exchange 2013 public folders), you can set the default public folder database to a valid Exchange 2010 or Exchange 2007 legacy public folder database. To do this, run the following command in Exchange Management Shell:
Set-MailboxDatabase <Exchange MDB> -PublicFolderDatabase <Legacy Public Folder DB to use>
YOU ARE HERE: HOME / SOLUTIONS / HOW TO REMOVE THE DEFAULT PUBLIC FOLDER DATABASE FOR AN EXCHANGE MAILBOX DATABASE
How to Remove the Default Public Folder Database for an Exchange Mailbox Database
FEBRUARY 29, 2012 BY PAUL CUNNINGHAM 25 COMMENTS
Microsoft has made it pretty clear in recent years that public folders will be going away at some stage in the future of Exchange Server.
If you’ve been using public folders in your Exchange organization and decided to get rid of them completely then you may run into this particular issue.
In this scenario I have gone ahead and prepared to remove the public folder database by:
- Removing all of the public folder content
- Ensured OAB distribution is set to web only
- Ensured all my clients are Outlook 2007 and above
When I attempt to remove the public folder database I receive this error.
The public folder database cannot be deleted
The public folder database ‘PF-BR-01’ cannot be deleted.
Public folder database “PF-BR-01” is the default public folder database for the following mailbox database(s):
. Before deleting the public folder database, assign a new default public folder database to the mailbox database(s).
The solution seems logical. All I need to do is modify that mailbox database so it no longer uses the public folder database.
It is simple enough to change the public folder database configured for a mailbox database to some other public folder database, but in this situation I’m trying to get rid of public folders entirely. So instead I want to set the mailbox database to have no default public folder database.
Here is what happens if I try to use Set-MailboxDatabase to set the value to $null.
[PS] C:\>Set-MailboxDatabase MB-BR-01 -PublicFolderDatabase $null
Cannot validate argument on parameter 'PublicFolderDatabase'. The argument is null or empty. Supply an argument that is
not null or empty and then try the command again.
+ CategoryInfo : InvalidData: (:) [Set-MailboxDatabase], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Set-MailboxDatabase
It doesn’t work. However all is not lost, there is another way, using ADSIEdit.msc.
Open ADSIEdit.msc and connect to the Configuration naming context.
Connect to the Configuration naming context with ADSIEdit
Navigate to the container that holds the Exchange databases. For Exchange 2010 you’ll find this in CN=Services -> CN=Microsoft Exchange -> CN=(your organization name) -> CN=Administrative Groups -> CN=Exchange Administrative Group (FYDIBOHF23SPDLT) -> CN=Databases.
Right-click the mailbox database you want to remove the default public folder database from and choose Properties.
Scroll down until you find the msExchHomePublicMDB attribute. Highlight it and then clickEdit.
Click the Clear button so that the value changes to “not set”.
Click OK, and OK again to commit the change.