Entourage cannot see tasks in public folders in exchange 2003

Hi,
I have a bunch of users using entourage on their macs and they cannot see a public folder task list from an exchange 2003 server. They can see their mail, contacts, calendar, etc...
Has anyone ever seen this?? The rights on the public folder have them as owners of the folder so they should be able to see it. When the users click on the folder it says it is empty... but is isn't. Any help would be appreciated

Hi,
Please refer to the following article:
http://support.microsoft.com/kb/2249852/en-us
The issue occurs when the Internet Information Services (IIS) website that hosts the Exchange Web Services (EWS) virtual directory contains a site binding that binds to an IPv6 address.
Note It is a known issue that this configuration may cause an exception .
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

  • Moving public folders from exchange 2003 to exchange 2010 error while moving replicas

    Dear All,
    i am in the process of migrating from Microsoft Exchange 2003 to Exchange 2010,
    i am done with moving all the mailboxes 300 mailbox almost with a 1.5 TB DB with no issues 
    when i tried all the processes, procedures, instructions and forums to move the public folder or 
    to use move all replicas from Exchange 2003 to Exchange 2010 i always get errors , now when i try 
    to open PF Management console from the exchange 2010 server i get it but it is disconnected
    then i can choose to coneect to the new server name EXCHANGE2010 with no issues
    when i try to expand the default folder and system folder i get the following error.
    OAB is set on the new server as default.
    when i try to add replica using power shell i get this error:
    WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an inst
     of an object.
    Object reference not set to an instance of an object.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], NullReferenceException
        + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    following error when trying to expand PF on EXCHANGE 2010
    Microsoft Corporation
    Microsoft® Windows® Operating System
    6.0.6000.16386
    Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''.
    Microsoft.Exchange.Configuration.MonadDataProvider.CommandExecutionException: Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''. ---> System.NullReferenceException: Object
    reference not set to an instance of an object.
       at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.GetMapiPublicFolderDatabasesIdentities(ADSystemConfigurationSession configurationSession, ADObjectId serverId, TaskErrorLoggingDelegate errorHandler)
       at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ValidateServerContainsPFDatabase(Server server, ADSystemConfigurationSession scSession, TaskErrorLoggingDelegate errorHandler)
       at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ResolvePublicFolderServerAndUserLegacyDNs(ADSystemConfigurationSession scSession, ServerIdParameter serverIdParameter, String& serverLegacyDN, String& userLegacyDN, Fqdn& serverFQDN,
    TaskErrorLoggingDelegate errorHandler)
       at Microsoft.Exchange.Configuration.Tasks.GetMapiObjectTask`2.CreateSession()
       at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.InternalStateReset()
       at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalStateReset()
       at Microsoft.Exchange.Management.MapiTasks.GetPublicFolder.InternalStateReset()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.InternalEndInvoke(IAsyncResult results)
       at Microsoft.PowerShell.HostingTools.PipelineProxyBase.EndInvoke(IAsyncResult results)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Close()
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Dispose(Boolean disposing)
       at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
       at Microsoft.Exchange.Management.SystemManager.DataTableLoader.Fill(RefreshRequestEventArgs e)
       at Microsoft.Exchange.Management.SystemManager.DataTableLoader.OnDoRefreshWork(RefreshRequestEventArgs e)
       at Microsoft.Exchange.Management.SystemManager.RefreshableComponent.worker_DoWork(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
    Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Common, Version=14.0.631.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.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Transport, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.PowerShell.HostingTools, 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.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.Common, 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.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.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Search.ExSearch, 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.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.UM.UmDiagnostics.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Rtc.Collaboration, Version=3.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Rtc.Media, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Management.Automation, Version=1.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.HelpProvider, Version=14.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
    System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    MMCEx, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
    Microsoft.Exchange.Data.Directory.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.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    i will be thankful for any assistant.
    PF DB is arounf 90 GB with alot of public folders and sub-folders. around 60 mail PF and too many subfolders.

    First and the most important thing you need to do is, upgrade exchange 2010 to SP2 and RU5.
    Exchange 2010 RTM support is long gone.
    http://www.microsoft.com/en-us/download/details.aspx?id=36768
    http://www.microsoft.com/en-us/download/details.aspx?id=41480
    Your exchange 2010 is still in stogeage ;)
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://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.

  • Can no longer see messages in public folders in Outlook (2010) conversation view

    (originally posted this under MS Community outlook discussion and it was suggested I post it here):
    Hello:
    I believe this may be related to a recent update, but previously I could see messages from public folders in my conversation view.  Now, I am only able to see messages in private folders (including sent items).
    I have the cached exchange mode on.
    I loved the conversation view because I could move e-mails out of my inbox to public folders (on our company server) to keep my inbox under required size limits, but still have easy access to e-mails within the conversation string.  That view in my
    opinion was the best upgrade to Outlook when it first came out.  Now it's virtually useless for me again.
    If there's something i can change to get those messages re-appearing again I'd really love to know what I can do, it was really useful for me.
    Thanks in advance to any who reply!

    Hi,
    Based on the descrtiption, I know that there is no emails exist in public folder when using conversation view in Outlook after installing update.
    1. I suggest use OWA to check whether emails exist in public folder when using Conversation View. If it works well, it seems an issue on the Outlook client side.
    2. Please check the connectivity between Outlook and Public Folder.
    3. I suggest disable conversation view for test to verify whether emails appear in public folder. If the emails appear, it seems an issue on Outlook Conversation View.
    4. I also suggest run Outlook under safe mode to avoid some AVs and add-ins. Try to re-create profile to refresh the caches.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Move mailboxes and public folders from exchange 2007 to Exchange 2013

    1. How do i move mailboxes from exchange 2007 to exchange 2013. I have more than 1000 mailboxes.
    What is the correct way to migrate. do i need to move a single mailbox. During migration do the mailboxes get corrupted
    2. I want to move public folders from Exchange 2007 to Exchange 2013.
    I ran powershell commands and got these results please do guide me how to move to exchange 2013.and what are the shell commands
    Get-publicfolder
    Name Parent Path
    IPM_SUBTREE
    Get-publicfolder | select AdminDisplayName,FolderPath
    AdminDisplayName FolderPath
    Get-PublicFolderStatistics | select AdminDisplayName,FolderPath
    AdminDisplayName FolderPath
    exchangeV1 schema-root\microsoft\exchangeV1
    Internet Newsgroups Internet Newsgroups
    Get-PublicFolder -Recurse | fl name,replicas > c:\publicfolder.txt
    Name : IPM_SUBTREE
    Replicas : {}
    Name : Internet Newsgroups
    Replicas : {MAIL\Public Folder Storage\Public Folder Database}

    I have started moving mailboxes , i have tried moving few individual mailboxes to see how things go
    MAIL is my exchange 2007 and MAIL1 is my exchange 2013, please do refer the below result
    PS] C:\Windows\system32>Get-MailboxDatabase -server mail
    Name                           Server          Recovery       
    ReplicationType
    Mailbox Database               MAIL            False           None
    [PS] C:\Windows\system32>Get-MailboxDatabase -server mail1
    Name                           Server          Recovery       
    ReplicationType
    Mailbox Database 1460777952    MAIL1           False           None
    [PS] C:\Windows\system32>New-MoveRequest -Identity '[email protected]' -TargetDatabase "Mailbox Database 1460777952"
    DisplayName               StatusDetail              TotalMailboxSize         
    TotalArchiveSize         PercentComplete
    [email protected]          Queued                    363.6 MB (381,217,115 ...                         
    0

  • Public folders from exchange 2007 to exchange 2013

    HI I am new to exchange, i am planning to do the migration of Exchange 2007SP3 UR10 to Exchange 2013 CU7, I want to move public folders from exchange 2007 to exchange 2013. wht is the procedure to move and wht are the commands to know how many public folders
    i have.I just want to be aware before the installation so that later i can avoid issues.please do guide me

    Hi Quiett,
    please find  how to move public folders on ttp://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html 
    You can replace your servers names and follow exactly the proedure that is shown there. I strongly suggest to read also the 2nd page (replication) before you start. Please be aware of
    Set-OrganizationConfig –PublicFoldersLockedForMigration $True , so you cannot change the source side whle migrating.
    Regards,
    Martin

  • Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

    Hi
    I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
    not available. either there are network problems or the exchange server is down for maintenance."
    Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
    The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

    Hi northerly,
    I recommend you follow the steps below for troubleshooting:
    1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
    2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
    3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
    What's more, here is a helpful KB for your reference.
    Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
    http://support.microsoft.com/kb/2834139/en-us
    Hope my clarification is helpful.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Manually Move Public Folders from Exchange 2010 to 2013

    Hi all,
    I have a issue to finishing my migration from Exchange 2010 to Exchange 2013, I have been trying to migrate my Public folders but always after a couple hours, the migration state is failed.
    The final error is the following:
    FailureCode                      : -2146233088
    FailureType                      : SourceMailboxAlreadyBeingMovedPermanentException
    FailureSide                      :
    Message                          : Error: Couldn't switch the mailbox into Sync Source mode.
                                       This could be because of one of the following reasons:
                                         Another administrator is currently moving
    the mailbox.
                                         The mailbox is locked.
                                         The Microsoft Exchange Mailbox Replication
    service (MRS) doesn't have the correct
                                       permissions.
                                         Network errors are preventing MRS from cleanly
    closing its session with the
                                       Mailbox server. If this is the case, MRS may continue
    to encounter this error for
                                       up to 2 hours - this duration is controlled by the TCP
    KeepAlive settings on the
                                       Mailbox server.
                                       Wait for the mailbox to be released before attempting
    to move this mailbox again.
    So, after seeing this I started to monitoring all process and I realized that after creating hierarchy the process start to fail and keep in StalledDueMailboxlock status, and the error is:
    FailureCode                      :
    FailureType                      :
    FailureSide                      :
    Message                          : Informational: The request has been temporarily postponed because the mailbox is
                                       locked. The Microsoft Exchange Mailbox Replication service
    will attempt to continue
                                       processing the request after 2/14/2015 12:38:20 PM.
    Finally, digging more into reports of migration I  found this:
    MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to open entry ID. (hr=0x80040115, ec=6)_x000A_Diagnostic context:_x000A_ Lid: 40487 EMSMDBMT.EcDoRpcExt2 called [length=73]_x000A_ Lid: 44583 EMSMDBMT.EcDoRpcExt2
    exception [rpc_status=0x6][latency=0]_x000A_ Lid: 62184 _x000A_ Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a_x000A_ Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 51452_x000A_ Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-02-14T14:25:40.9210000Z_x000A_
    Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2_x000A_ Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 6_x000A_ Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1741_x000A_ Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0_x000A_ Lid: 11672 dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 0_x000A_ Lid: 23260 Win32Error: 0x6_x000A_ Lid: 61553 StoreEc: 0x80040115_x000A_ Lid: 52176 ClientVersion: 15.0.1044.25_x000A_ Lid: 50032 ServerVersion: 14.3.181.6_x000A_ Lid: 50128 _x000A_ Lid: 50288 _x000A_ Lid: 23354
    StoreEc: 0x80040115_x000A_ Lid: 25913 _x000A_ Lid: 21817 ROP Failure: 0x80040115_x000A_ Lid: 22894 _x000A_ Lid: 24942 StoreEc: 0x80040115
    So, would like to know if exist any procedure to migrate/move my Public Folders from Exchange 2010 to 2013 manually, something like Export/Import.
    Regards!

    What script and process you are running to migrate the Public Folders?
    And what do you mean by Manually?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.comTwitter:
    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.

  • Migrating Public Folders on Exchange Server 2007 SP1 to Exchange Online\Office 365

    Hello,
    Our company is looking to migrate from Exchange 2007 on premises to Exchange Online/Office 365. We have a number of public folders on our exchange server that function similarly to how the new shared mailboxes work in Exchange Online. That is to say that
    we have many outside users (customers and wholesale dealers) emailing this public folder ([email protected]) and our end users are given permission to view and respond as themselves ([email protected]). I've been looking all over but haven't found a clean
    way to migrate the current public folders directly into shared mailboxes. I'd just start from scratch, but we want to keep the records of the emails we've received at these public folders for customer support reasons. Can anyone help?

    Hi psh8989,
    According to your description, I know that you want to migrate public folder from Exchange 2007 to Office 365.
    Since Office 365 is different from Exchange On-Premises, I suggest ask Office 365 Forum for help so that you can get more professional suggestions. For your convenience:
    http://community.office365.com/en-us/default.aspx
    However, I can also share some information for your reference : )
    Based on my knowledge, Exchange supports moving your public folders to Office 365 and Exchange Online from Exchange 2007 SP3 RU10 or later. I notice that your Exchange server version is SP1, please upgrade to SP3 RU10 first and perform migration.
    More detailed information to see:
    Migrate legacy public folders to Office 365 and Exchange Online 
    http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx
    Thanks
    Mavis Huang
    TechNet Community Support

  • Migrating public folders to exchange 2013 hebrew issue

    I am migrating public folders to exchange 2013. half of them a named in hebrew.
    The migration fails, the error is character  related. 
    Is it possible at all to migrate hebrew named public folders?

    Hi,
    Did you got the error message mentioned in the following thread?
    http://social.technet.microsoft.com/Forums/exchange/en-US/8b383a46-b710-4fc0-aa0b-e52f288cf93d/e2010-to-e2013-public-folders-migration-failed?forum=exchangesvrdeploy
    If so, please check if they are mail-enabled public folders. If they are mail-enabled public folders, please make sure there are no invalid characters in alias.
    Based on the description, you couldn't migrate public folders named in Hebrew, other public folders could be moved successfully. If I misunderstood your concern, please let me know.
    If the issue persists, I'm afraid you need to rename these public folders in English.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Having issues seeing public folders in Exchange 2013.

    We have an multi-tenant Exchange 2013 environment and are currently trying to set up up Public Folders for use with one of our tenants.  
    I have created the primary public folder mailbox and then created a public folder for the Tenant and assigned the necessary permissions to user account I would like to access the folder from (in this case "owner" permissions).  However I cannot
    see the public folder from Outlook.  This is the case with both Outlook 2007 and Outlook 2013.  I have made sure I am in the folder view (Cntrl + 6) but I see no public folders to speak of.  I am able to log into OWA and add the public folder
    to the favourite list by right clicking and selecting "add public folder", I am also able to access the public folders using a third party mobile app for iPhone called "Public Folders".  I've also tried creating completely new profiles
    in both versions of Outlook but I cannot see the public folders that way either.
    We are currently using a third party wildcard certificate with our multi-tenant environment, not sure if that would have an impact on what we are doing here but thought I'd throw that in just in case. 

    Hi,
    Do you mean the public folder still cannot be seen even you logged the Outlook 2007 good user on an Outlook 2013 machine?
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Other Mac users cannot see my shared public folder

    Other users on my network cannot see my Public shared folder. I can see their public folders no problem. I can connect to my computer from another Mac and "connect as" myself and see folders.
    I have File Sharing turned on. Permissions look copacetic. It says I'm the owner of the shared folder.
    IT's has a profile on this same machine – its Public folder shows up for other users. When I set up a new account profile, its shared folder shows up no problem.
    It may, just may, have to do with me changing my short login name after migrating to this machine. Problem is, I have no idea how to confirm that. Finder shows proper ownership and permissions in the info windows. I think there's something deeper down in the account system level that is wrong, but I don't know where to look.

    squareman wrote:
    It may, just may, have to do with me changing my short login name after migrating to this machine. Problem is, I have no idea how to confirm that. Finder shows proper ownership and permissions in the info windows. I think there's something deeper down in the account system level that is wrong, but I don't know where to look.
    If you have admin rights, you can create a new account in System Preferences and see if that shared folder shows up on the network. If it does, then it could be related to changing short name (which I have heard you aren't suppose to do). If not, it may be something in the system. Give that a try and post back what happens.

  • Exchange 2013 users cannot open public folders on exchange 2010

    Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
    client version is outlook 2013
    outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
    outlook any where external host name field is blank (we need to keep outlook any where disable for external)
    outlook anywhere internal authentication is set to NTLM and Client require SSL to false   
    I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggest  

    Hello,
    Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
    If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
    If the user has no permission to see the public folder, please check the permission.
     =============================================================
    1. Open ADSIEDIT.
    2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
    Administrative Group ->CN=Databases ->CN= PF Database.
    3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
    Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
    Additional article for your reference.
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Project Lite user cannot see tasks assigned ...

    Hi
    I have assigned tasks to a user Project 2013 and linked the project to Project Online.
    As the administrator, I see all my tasks in the Timesheet view in PWA but the users that use Project Lite canot view their tasks and cannot see them in their Timesheet.
    I am quessing it is a permissions issue but cannot find where to set the right permissions.
    Any solutions out there?
    Thanks.

    Hi,
    Have you correctly published the assignment of the user from the project (either PWA or MS Project Pro)?
    Is the user looking at the right period?
    Is the publish job successful?
    Is the booking type committed and not proposed?
    Is the resource the assignment owner of the assignment?
    Have you assigned an enterprise resource and not a local resource? When you go to the resource center, select the resource, can you see the assignment?
    Hope this helps,
    Guillaume Rouyre, MBA, MCP, MCTS |

  • Why am I seeing other peoples public folders that I don't know under recent files

    Under "Recent Items" and "Servers" I am seeing Public Folders of people I do not know. I am not able to access or open their servers. Have they been able to access my computer? My settings are set to "File Sharing Off"

    run this script in terminal. It will reset to the default (it funtions like the reset homepage layout funtion in IOS)
    rm ~/Library/Application\ Support/Dock/*.db

  • Cannot delete mails in public folders using OWA after applying SP3 RU5

    Hello,
    we recently applied service pack 3 rollup 5 to our Exchange 2010 server (before it was running rollup 4).
    Ever since, when we try to delete a mail in a public folder using OWA we get the message "An unexpected error occurred and your request couldn't be handled". Each attempt also causes error 108 in the application log (Outlook Web App couldn't
    connect Exchange Web Services due to a configuration error. Response code = "500".) which is not accompanied by any other errors.
    Neither uninstalling the rollup nor restoring the server's system state to a point before installation of RU4 could fix the error. Deleting mails in a mailbox still works fine, it's only within public folders and only in OWA.
    Any ideas?

    Hi,
    Please refer to the following article:
    http://support.microsoft.com/kb/2249852/en-us
    The issue occurs when the Internet Information Services (IIS) website that hosts the Exchange Web Services (EWS) virtual directory contains a site binding that binds to an IPv6 address.
    Note It is a known issue that this configuration may cause an exception .
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

Maybe you are looking for

  • View Doc (pdf, image, .doc) imported as BLOB files in UIImageView within a UIScrollView.

    Hi, I am new to IOS programming and after researching on topic i found post saying it is possible to view BLOB file in uiimageView. I have already done sucessfully for BLOB file of Image. but i can not view pdf file, even if i got NSData. /****** fro

  • New iPad (3rd gen) keyboard doesn't slide back in

    My new iPad keyboard (i.e. the default virtual keyboard of iOS) when it comes up (slides up) it doesn't slide back in when the typing mode is no longer needed. E.g. when I swipe all the way to the left and reach the search screen, the keyboard pops u

  • Dreamweaver to CF Builder Transition Guide. Please!

    It would be extremely helpful if someone would release some sort of documentation to help us long-time Dreamweaver users transition to CF Builder.  From what I've been reading there are LOTS of coders/developers who claim to hate CF Builder already. 

  • Technical system  in XI

    Dear All When i am trying to create a technical system in Web As ABAP in my XI server, i do not get any software component version. Please guide with the process for creating a ABAP technical system in XI server Sandeep

  • Anyconnect 3.1 and user certificate-based authentication

    Hi experts, I'm trying to test a basic full tunnel VPN connection from Anyconnect 3.1 installed on a Windows 7 machine to a Cisco ASA, using only certificate authentication. Steps i took: 1) I've created a Windows 2008 certificate authority for testi