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

Labels:

Popular posts from this blog

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 
Read more

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
1 comment
Read more

Ports that need to be open on Firewall for Edge Transport servers

Ports that need to be open on firewall for Edge Server subscription with Hub Server to function properly: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server) Since Edge server needs to communicate with Hub server it is important that it can resolve Hub transport servers by FQDN and Hub transport servers must be able to resolve Edge servers by its FQDNs. To accomplish this you need to either open 53 (DNS) port and configure internal network adapter to use internal DNS but as a security precaution I would suggest to enter DNS records for Edge servers on local DNS manually and to fill hosts file on Edge servers with FQDNs for Hub transport servers.
2 comments
Read more