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

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

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi

The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed

The error you get: The attempt to connect to http://yourserver/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found If you removed Exchange server from the machine and installed it again, you can get following error when you open Exchange Management Console: The following error occurred while attempting to connect to the specified Exchange server 'yourserver.domain.com': The attempt to connect to http://yourserver.domain.com/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found. Possible causes are:   -The user name or password specified are invalid.   -Kerbero