Exchange 2013 Public Folder Accessability Issues

After migrating from Exchange 2010 to Exchange 2013 we are experiencing random issues accessing Public Folders.  Issues range from a hung server requests to on-screen errors like this one:
“Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”
We are using groups to manage permissions, verified that they are mail enabled, and have used the following PS command to re-propagate permissions:
./AddUsersToPFRecursive.ps1 -TopPublicFolder "%folder%" -User "%groupname" -Permissions %permissionlevel"
The odd thing is that if the user bounces between on of their Inbox folders then back to one of the Public folders or restarts Outlook it seems to resolve itself.
Ideas?

Hi Niko,
Firstly, apologies for the delayed update...
We are still experiencing random loss of access to Public Folders, I would think it would be so much easier if I could replicate the problem quickly and easily however that is not the case as I ran into this issue again this morning.
I am really at a loss for explanation, what I can offer is when we had migrated from Exchange 2000 to Exchange 2010 I had to export the PF out to a pst file prior to importing them on the new server installation.  While migrating from Exchange 2010
to Exchange 2013 we did follow the migration process.
Here is what our current settings from Get-OutlookAnywhere -Server %Server%
RunspaceId                         : e2e4f324…
ServerName                        
: %server%
SSLOffloading                     
: True
ExternalHostname                  
: <set>
InternalHostname                   : <set>
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods          
: {Basic, Ntlm, Negotiate}
XropUrl                           
ExternalClientsRequireSsl         
: True
InternalClientsRequireSsl         
: True
MetabasePath              
        : IIS://%server%/W3SVC/1/ROOT/Rpc
Path                              
: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags           
ExtendedProtectionSPNList         
AdminDisplayVersion               
: Version 15.0 (Build 775.38)
Server                             : %server%
AdminDisplayName             
ExchangeVersion                   
: 0.20 (15.0.0.0)
Name                              
: Rpc (Default Web Site)
DistinguishedName                 
: CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=%server%,CN=Servers,CN=Exchange
                    Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=%company%
Software,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%domain%,DC=net
Identity                           : %server%\Rpc (Default Web Site)
Guid                              
: 0bf08d0e…
ObjectCategory                    
: %domain%/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                       
: {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                       
: 5/5/2014 3:08:31 PM
WhenCreated                       
: 2/20/2014 2:13:17 PM
WhenChangedUTC                    
: 5/5/2014 8:08:31 PM
WhenCreatedUTC                    
: 2/20/2014 8:13:17 PM
OrganizationId                    
OriginatingServer                 
: %server%
IsValid                           
: True
ObjectState                       
: Changed

Similar Messages

  • Exchange 2013 - Public Folder Mailbox and Single Item Recovery

    Hello,
    I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
    "Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
    is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
    looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

    So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder. 
    Check out this article
    http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
    I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB  but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward.  That said this will also increase the
    DB size so consider all the options before implementing
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Exchange 2013 user cann't access exchange 2013 public folder

    Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
    problem, thanks.
    belows are information about outlook anywhere in our exchange.
    exchange 2007:(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
    exchange 2013:(primary site)shcas01,shcas02; (DR site)wxcas01
    Identity                           : SHCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHCAS02\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : WXCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL04\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}

    Hi,
    I have found an article said that we need to set the external host name the same. See more details in the following link:
    http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
    To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
    Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
    The following configuration is set on each Exchange 2007 server:
    The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
    Sent By
    Silver

  • Exchange 2013 Public Folders external issues

    Hello,
    I am having some issues with gaining access to my public folders externally.
    OS: Windows Server 2012 Datacenter
    Exchange: 2013 with SP1
    Domain: i.client.local
    External & internal hostname: ex01.client.dk
    I have tried from Windows 7 with Outlook 2010, and Windows 8 with Outlook 2013. (I have also tried to apply patch from: http://support.microsoft.com/kb/2839517)
    If I try to access public folders, I get this error:
    Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange.
    If I try to access public folders with cache enabled, I get this error: http://support.microsoft.com/kb/2788136
    I have tried deleting all public folders, public folder databases, and the related mailbox database. And creating all again, however
    with same result. 
    [PS] C:\Windows\system32>Get-PublicFolder | fl
    RunspaceId : a90240df-5376-4397-8c2a-4291a924e911
    Identity : \
    Name : IPM_SUBTREE
    MailEnabled : False
    MailRecipientGuid :
    ParentPath :
    ContentMailboxName : Public
    ContentMailboxGuid : d97cbc5c-4c39-47c7-8b56-764396dc32ca
    EformsLocaleId :
    PerUserReadStateEnabled : True
    EntryId : 00000000134872D0905F3849B78B9128A8B0CBE30100DF9CA23E198A714AB68A74F2C09F11020000000000020000
    DumpsterEntryId : 00000000134872D0905F3849B78B9128A8B0CBE30100DF9CA23E198A714AB68A74F2C09F110200000000000A0000
    ParentFolder : 00000000134872D0905F3849B78B9128A8B0CBE30100DF9CA23E198A714AB68A74F2C09F11020000000000010000
    OrganizationId :
    AgeLimit :
    RetainDeletedItemsFor :
    ProhibitPostQuota : Unlimited
    IssueWarningQuota : Unlimited
    MaxItemSize : Unlimited
    LastMovedTime :
    FolderSize : 0
    HasSubfolders : True
    FolderClass :
    FolderPath : {}
    DefaultFolderType : None
    ExtendedFolderFlags : SharedViaExchange
    MailboxOwnerId : i.client.local/Public
    IsValid : True
    ObjectState : Unchanged
    [PS] C:\Windows\system32>Get-PublicFolder \ -GetChildren
    Name Parent Path
    Mira \
    [PS] C:\Windows\system32>Get-OrganizationConfig | FL RootPublicFolderMailbox
    RootPublicFolderMailbox : d97cbc5c-4c39-47c7-8b56-764396dc32ca
    [PS] C:\Windows\system32>Get-Mailbox -PublicFolder | FL Name,ExchangeGuid
    Name : Public
    ExchangeGuid : d97cbc5c-4c39-47c7-8b56-764396dc32ca
    I can easily access the Exchange-server internally and externally. 
    XML from Outlook "Test autoconfiguration" tool.
    <?xml version="1.0" encoding="utf-8"?>
    <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
    <User>
    <DisplayName>Alex Mathiasen</DisplayName>
    <LegacyDN>/o=client/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=8cfd63e296ee4d6d99fa842a78584d43-Alex Mathiasen34410</LegacyDN>
    <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
    <DeploymentId>823f5581-e9a1-4b8c-a79e-afcbe9900267</DeploymentId>
    </User>
    <Account>
    <AccountType>email</AccountType>
    <Action>settings</Action>
    <MicrosoftOnline>False</MicrosoftOnline>
    <Protocol>
    <Type>EXCH</Type>
    <Server>[email protected]</Server>
    <ServerDN>/o=client/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
    <ServerVersion>73C0834F</ServerVersion>
    <MdbDN>/o=client/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
    <PublicFolderServer>ex01.client.dk</PublicFolderServer>
    <AD>ex01.i.client.local</AD>
    <ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
    <EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=i.client.local</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=i.client.local</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-photo>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-extinstall>
    <OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
    <UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
    <OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
    <ServerExclusiveConnect>off</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXPR</Type>
    <Server>ex01.client.dk</Server>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
    <EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=i.client.local</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=i.client.local</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-photo>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-extinstall>
    <OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
    <UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
    <OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
    <ServerExclusiveConnect>on</ServerExclusiveConnect>
    <EwsPartnerUrl>https://ex01.client.dk/ews/exchange.asmx</EwsPartnerUrl>
    <GroupingInformation>Default-First-Site-Name</GroupingInformation>
    </Protocol>
    <Protocol>
    <Type>WEB</Type>
    <Internal>
    <OWAUrl AuthenticationMethod="Basic, Fba">https://ex01.client.dk/owa/</OWAUrl>
    <Protocol>
    <Type>EXCH</Type>
    <ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
    </Protocol>
    </Internal>
    <External>
    <OWAUrl AuthenticationMethod="Fba">https://ex01.client.dk/owa/</OWAUrl>
    <Protocol>
    <Type>EXPR</Type>
    <ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
    </Protocol>
    </External>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>ex01.client.dk</Server>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
    <EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=i.client.local</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=i.client.local</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-photo>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-extinstall>
    <OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
    <UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
    <OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    <Protocol>
    <Type>EXHTTP</Type>
    <Server>ex01.client.dk</Server>
    <SSL>On</SSL>
    <AuthPackage>Ntlm</AuthPackage>
    <ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
    <EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
    <EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
    <EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
    <EcpUrl-um>?rfr=olk&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=i.client.local</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=i.client.local</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-photo>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;realm=i.client.local</EcpUrl-extinstall>
    <OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
    <UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
    <OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
    <ServerExclusiveConnect>On</ServerExclusiveConnect>
    </Protocol>
    <PublicFolderInformation>
    <SmtpAddress>[email protected]</SmtpAddress>
    </PublicFolderInformation>
    </Account>
    </Response>
    </Autodiscover>

    I can't access the public folders at all. Trying to access the public folders, result in the error from the following page: http://support.microsoft.com/kb/2788136,
    or "Cannot expand the folder..."
    It is affecting all users using this Exchange-server. I am actually having this error on two different Exchange-serverens at two different companies at the moment. 
    And it is a fresh Exchange 2013 environment in both cases. 
    PS: I discovered that the public folders works inside the same domain as the Exchange-server, however users can't access the public folders externally. 
    I also tried to use the Exchange-server as DNS, in order to be able to resolve i.client.local:
    <PublicFolderInformation>
    <SmtpAddress>[email protected]</SmtpAddress>
    </PublicFolderInformation>
    however I am still unable to open the public folders, even after being able to resolve the DNS name i.client.local. 

  • Exchange 2013 public folder can not create folder

    hello,
    we have migrate public folders to20102013.
    we can not createfolders / files inpublic folders.Access Rights seems to be
    ok on the control panel
    in Outlook, we can not apply change permissions
    what can i do to fix that ?
    all the public folder have migrate on the secondary mailbox public folder like the technet KB
    Please, help us !
    thank you

    Could you please have a look at below mentioned links ? May be, it will help you to sort-out the issue which you are getting right now while moving public folder :
    http://redmondmag.com/articles/2013/07/15/exchange-2013-cu2.aspx
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-preview-public-folders-part1.html
    Carlo

  • Exchange 2013 - Public folder search not working

    Hi There,
    We have Exchange 2013 install on server 2012 and clients using Outlook 2010 on Windows 7.
    Since we have installed the system a search of the public folders always returns no results even if we know the email is there. Any suggestions?
    Thank you
    Dave

    Hi Triumphtech,
    Yes, if our Exchange 2003 environment is healthy, it will work.
    Please forgive me for the silly clarification. If we used Exchange 2003 and wanted to migrate to Exchange 2013. We must migrate to Exchange 2007/2010 first, then to Exchange 2013.
    So please make sure we have moved the public folder successfully first.
    And great information from Tarique Noorain.
    According to  the article, I found some points for your reference:
    1. Although a full text search of public folder content is available, public folder content isn't searchable across public folders and the content isn't indexed by Exchange Search.
    2. You must use Outlook 2007 or later to access public folders on Exchange 2013 servers.
    Feel free to contact me if there is any problem.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 Public folder permission issue

    When i select the public folder and click the permission tab to set the permission, below error message will be pop up. This error message only happen in few sub public folder, another folder without this problem. There are two replica
    in different mail store server.
    Microsoft Corporation
    Microsoft® Windows® Operating System
    6.1.7600.16385
    Exception has been thrown by the target of an invocation.
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.ConstraintException: Column 'Identity' is constrained to be unique.  Value 'gcr.geg.local/Managed OU/Galaxy Corporate/HR&A/Esther
    Chan (Corp HR&A)' is already present.
       at System.Data.UniqueConstraint.CheckConstraint(DataRow row, DataRowAction action)
       at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
       at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Int32 position, Boolean fireEvent, Exception& deferredException)
       at System.Data.DataTable.InsertRow(DataRow row, Int64 proposedID, Int32 pos, Boolean fireEvent)
       at System.Data.DataRowCollection.Add(DataRow row)
       at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.AddEntry(DataTable table, ADObjectId identity, String name, MultiValuedProperty`1 accessRights)
       at Microsoft.Exchange.Management.SystemManager.WinForms.PublicFolderClientPermissionHelper.GenerateClientPermissionDataSource(Object clientPermission)
       at lambda_method(ExecutionScope , String )
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Delegate.DynamicInvokeImpl(Object[] args)
       at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateLambdaExpression(ColumnExpression expression, Type dataType, DataRow dataRow, DataRow inputRow)
       at Microsoft.Exchange.Management.SystemManager.ExpressionCalculator.CalculateCore(DataRow dataRow, DataRow inputRow, IList`1 query)
       at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.FillColumnsBasedOnLambdaExpression(String changedColumn)
       at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandlerBase.UpdateTable(DataRow row, String targetConfigObject, Boolean isOnReading)
       at Microsoft.Exchange.Management.SystemManager.WinForms.AutomatedDataHandler.OnReadData(CommandInteractionHandler interactionHandler, String pageName)
       at Microsoft.Exchange.Management.SystemManager.WinForms.DataHandler.Read(CommandInteractionHandler interactionHandler, String pageName)
       at Microsoft.Exchange.Management.SystemManager.WinForms.DataContext.ReadData(CommandInteractionHandler interactionHandler, String pageName)
       at Microsoft.Exchange.Management.SystemManager.WinForms.ExchangePage.<OnSetActive>b__0(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Common, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.ActiveDS, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.UM.TroubleshootingTool.Shared, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.RightsManagementServices.Core, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Transport, Version=14.1.214.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Common.IL, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Sqm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Management.SnapIn.Esm, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    PresentationFramework, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    WindowsBase, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
    Microsoft.Exchange.Management.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35

    Hi,
    This issue appears to be related to
    data access from their ASp.Net application.
    To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft
    Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
    http://support.microsoft.com/contactus/?ws=support
    FIX: "Exception has been thrown by the target of an invocation"
    error message
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Exchange 2013 Public Folder Migration Problem

    Hi All,
    Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
    I have followed the guide for public folder migration here
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
    We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
    However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them
    fine from the ECP - just not from outlook.
    It also appears some users cannot see some folders that they have permissions to.
    Can anyone assist with some ideas to resolve ?
    Thanks.

    Question?
    Are you able to create the Folder in OWA?
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:
       LinkedIn:
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
    it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
    My Bad, that's what I was trying to say.
    Testing the same thing in the LAB, should have some update tomorrow morning.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 Public Folder Migration Not Listed

    I started a public folder migration from my 2010 SP3 Exchange server to my new 2013 SP1 Exchange server. Somewhere during the process I failed. Not sure where but I am now at the point where if I try to create a new public folder on teh 2013 box i get a
    warning like this.
    An existing Public Folder deployment has been detected. To migrate existing Public Folder data, create new Public Folder mailbox using -HoldForMigration switch.
    So I then run Get-PublicFoldermIgrationRequest to see what is still waiting... I get no migration listed in Exchange Management Shell.
    I would like to find the place in AD or in the Server that thinks there is still an active request out there and remove it so I can start again with a clean slate. How do I do that?
    Thanks!

    Hi Zulea,
    This is a known issue, I recommend you refer to the following article to resolve the issue:
    http://support.microsoft.com/kb/3004062/en-us
    Cause:
    This problem occurs when the Exchange organization coexists with an earlier version of Exchange Server, and one or more public folder databases from the earlier version of Exchange still exist.
    Resolution:
    To resolve this issue, use one of the following methods.
    Method 1: Create the mailbox by using the -HoldForMigration switch:
    This option lets an administrator create a public folder mailbox in order to begin a migration from the existing public folders:
    Open the Exchange Management Shell.
    Run the following cmdlet to create the public folder mailbox:
    New-Mailbox "Public Folder Mailbox" -PublicFolder -HoldForMigration
    Method 2: Remove all public folder databases from earlier versions of Exchange Server
    To remove existing public folder databases, see the following TechNet websites, as appropriate for the version of Exchange that an existing public folder resides on.
    Exchange 2010:
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
          (http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx)    
    Exchange 2007:
    http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx
          (http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx)    
    Create the public folder mailbox by using either the Exchange Admin Center (EAC) or the Exchange Management Shell (EMS). To do this, see the following TechNet website:
    http://technet.microsoft.com/en-us/library/jj552410(v=exchg.150).aspx
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Exchange 2010 to Exchange 2013 Public Folder Problem

    Dear Experts,
    I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
    1) Parent Domain in Site A (abc.com)
    2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
    3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
    I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
    Anyone help will be highly appreciated.
    Thanks & Regards,
    ZB

    so you want users to access the PF in site B.
    Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
    run this for Exchanger 2013 DA
    Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
    Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
    Where Technology Meets Talent

  • Exchange 2013 public folder showing as mail enable no, after migration

    I have migrated from 2010 to 2013 and now have a problem with some MailPublicFolders. They can receive mail, but show up in EAC as Mail Enabled "no". If I try to mail enable them they get an odd ball address i.e.
    subject?[email protected]
    I need them to show as mail enabled in EAC so I can give people SendAs etc.
    If I edit the email address, I get an error saying the address already exists.
    I think it is from 2003/2010 when alias was set to
    [email protected] and now that is not permitted.
    Thinking back to when we went from 2003 to 2010, we had to mail disable, then mail enable to get them working.
    How can I fix the properties and end up with a mail enabled mailpublicfolder?

    Hi,
    For this issue, I recommend you delete the public folder object under the Microsoft Exchange System Objects container. Before you delete the public folder object, please note the existing SMTP addresses.
    After that, please Mail-enable the
    public folder again to check result.
    Here is a similar thread for your reference.
    https://social.technet.microsoft.com/Forums/en-US/1cce206c-694b-4dc2-8052-39e988fe0dcf/public-folder-not-showing-up-as-mail-enabled-but-its-receiving-email?forum=exchange2010
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 Public Folder Calendars in OWA

    Hello,
    I have a Public Folder calendar that I need to publish via OWA in Exchange 2013.  I understand that you cannot view any public folder that is not mail enabled in OWA.  If I make this specific calendar mail enabled will I be able to view the calendar
    in OWA?  I think I still have to convert this to a shared mailbox.  If that is the case, what are the best steps to perform that?

    Hi,
    Yes I agree with Ed Crowley. In Exchange 2013 Cumulative Update 1, Microsoft have allowed to display public folders. However, two major restrictions exist. First, OWA can only display modern public folders. In other words, you have to complete your
    migration to Exchange 2013 and then execute a public folder migration before OWA can be used. No access is possible to legacy public folders. Second, OWA can only display “mail public folders”, or public folders that contain “mail and post items” (as they
    are referred to by Outlook). Other folders (calendars, contacts, tasks, notes, InfoPath, and journal items) are unsupported.
    Regards,
    Santhosh,
    www.jijitechnologies.com

  • EXCHANGE 2013 Public Folder Migration across Domain Forest

    Hi
    I am planning to migration public folder across the forest but unable find any documentation. can you guys share the step by step guide to move/migrate public folder. we have exchange 2013 in source and target forest.   
    Please help!

    Hi,
    Currently, there is no official document about Exchange 2013 cross-forest public folder migration. Maybe some third party software can help you to do cross forest public folder migration.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 Public Folder Missing in Outlook

    Hello,
    i have succesfully migrated from Exchange 2010 to Exchange 2013.
    Everything was running after i migrated the public folders they disappeared on the Clients after starting Outlook 2013.
    We are able to see the public Folders in OWA but not in Outlook.
    Anybody know this Problem and can help?
    regards
    René

    Hi,
    Based on the description, everything was running after you migrated from Exchange 2010 to Exchange 2013. When you upgraded from Outlook 2010 to Outlook 2013, you couldn't see public folders in Outlook 2013. However, you could see public folders in Outlook
    2010, but you couldn't expand it. OWA worked well.
    If I misunderstood your concern, please feel free to let me know.
    About "No we had migrated to Office 2013 before but tested it now with Outlook 2010.", was the Outlook 2010 client a remaining Outlook 2010 client?
    Did the issue affect all users or some of them?
    Could you please switch between online mode and cached mode to check the result?
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Outlook save/update error with Exchange 2013 public folder used as Contact Items

    Hello Everybody.
    This problem is driving me crazy.
    In Exchange 2013 i have created a public folder with several subfolders used as Contact Items.
    I've reviewed all settings several times and all is ok.
    Outlook 2010/2013 users several times receive the message:
    "The item cannot be saved to this folder. The folder was deleted or moved, or you do not have permission. Do you want to save a copy of it in the default folder for the item?"
    when try save an existing contact after modification.
    I can assure you that user permissions, server configurations are ok; please, help me.

    Did you make the subfolder the correct type, i.e., a contacts-type folder?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Maybe you are looking for

  • Macbook Pro -- sleep and wakeup problems

    If I fold the screen down when leaving my Macbook pro 8,1 (ML 8.1) and then open it again within a few minutes, it will not "wake up".  If I continuously open and close it, the small LED on the front goes bright when I close it and dim when I open it

  • Light Window not working in internet explorer

    For those of you familiar with lightwindow, This is one of the codes for a game on my site, when i use it for firefox it works great but when i try to use it with internet explorer i get Error: invalid argument TRY IT PLEASE I NEED HELP! html tester

  • Resource bundle is not refreshed from DB table as expected

    Does anybody implement this approach successfully http://technology.amis.nl/2012/08/14/refresh-resource-bundle-from-within-the-adf-application-to-absorb-changes-in-database-backed-bundles to refresh bundle text on BC level (for EOs, VOs, validation t

  • J2sdk1.4.1 installation in Solaris 2.6

    Hi, I've installed the "j2sdk-1_4_1-rc-solaris-i586.sh" (Solaris j2sdk1.4.1) and "J2SE_Solaris_2[3].6_x86_Recommended.tar.Z" (patch for solaris 2.6). And make the j2sdk1.4.1 de default java. When running java, the following message ocurrs: 18:03 eid@

  • Help ! Acrobat Pro 9

    Bonjour à tous, J'ai un souci pour imprimer des fichiers PDF à partir de l'application QUARX XPRESS 6.1 depuis mon MAX OS X 10.6.2 avec l'application ACROBAT PRO 9. Dans la liste d'impression il m'indique : "error: error drawing page 1" Est-ce que qu