Skip to main content

No existing PublicFolder matches the identity '\'

When you open the Public Folders management console on the mailbox server you get following error:

No existing 'PublicFolder' matches the following Identity: '\'. Make sure that you specified the correct 'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'.

In my case the problem was in missing homeMDB attribute value on mailbox server on which I got the error. To resolve the issue:

  1. Start ADSI Edit and connect to Configuration Naming Context
  2. Navigate to CN=Configuration, DC= , DC= , DC=/Services/Microsoft Exchange/Organization/Administrative Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Servers/YOURMBXSERVER*

    *Note: YOURMBXSERVER is mailbox server where you got the error
  3. Right-click CN=Microsoft System Attendant and then click Properties to display the Attributes list and find the homeMDB attribute.
    If the homeMDB attribute has a value, make sure  it points to a valid mailbox database, which is the database local to this server (in case you are using DAG)
  4. If the value of the homeMDB attribute is empty <not set> or not correct, you need to populate it or change to correct value.
  5. If the value is empty e.g. <not set> go to CN=Configuration, DC= , DC= , DC=/Services/Microsoft Exchange/Organization/Administrative Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Databases and find the database that is LOCAL to YOURMBXSERVER (if you are using DAG, you can set different home server for different databases)
  6. Right-click CN=DATABASENAME and find distinguishedName attribute under Attribute editor
  7. Click View and copy the complete value
  8. Now go back to CN=Microsoft System Attendant (as in STEP 2 and 3), right click on it, select Properties, select homeMDB attribute and paste the value you copied before.
  9. Wait 10-15 minutes

 

For another possible solution check http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/14ea8ee9-1f4c-4a0c-817b-dc7ead184e08

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.