Exchange 2003 to 2010 Public folder Migration issue

I have successfully replicated our Exchange 2003 public folders to our exchange 2010 public folders using the addreplica script in exchange 2010 PS. I have moved all mailboxes to use the public folders on Exchange 2010.  A couple of days ago I ran the
"moveallreplicas.ps1", and the command successfully ran and has removed all replica pointers in the exchange 2010 PF database pointing to the exchange 2003 database. In Exchange 2003 ESM, I still have the replication to all the PF databases, and
the 2k3 has not been removed, nor has the public folder instances folder count changed at all. In searching through the logs I am getting this error on the exchange 2003 event viewer for applications about every minute or less. 
This is an SMTP protocol log for virtual server ID 1, connection #58254. The client at "xxx.xxx.xxx.xxx" sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first  ". The full command
sent was "xexch50 1076 2".  This will probably cause the connection to fail. 
The client IP indicated in the error is a Exchange 2010 server with the HUB/CAS roles loaded onto it. I am not sure if this is related or not.
I see some people have ran the move all replicas from the Exchange 2003 ESM, should I do that now? Is this even something to worry about since all my mailboxes are using the PF on 2010?
Thanks for any assistance!

I have looked at KB http://support.microsoft.com/?id=843106 and
it did not resolve the issue on the Exchange 2003 server or 2010. 
Last night I put in the fix for the Event ID 36885, method three of this article http://support.microsoft.com/kb/933430/en-us,
and the errors on both servers seemed to go away, but then have started back up this morning after about seven hours of no errors. I thought the registry entry would fix the issue, and it appears it did, but not sure why it would come back like this. I may
try restarting the servers tonight, but kind of confused how this could still be an issue with the registry entry in place. 

Similar Messages

  • 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.

  • Public Folder Migration issues

    Hello,
    I am at the last stages of migrating from exchange 2007 SP3 to 2010 SP3. Both versions have a CAS, HT, and MBX server. I've moved all the databases across and also replicated the public folder contents using: 
    AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\" 
    -ServerToAdd 2010MBX
    After resolving all the public folder item errors that popped up, I decided to move the public folders
    across. I ran the \moveallreplicas.ps1 script.
    On the Exchange 2007 MBX server, I got some EXCDO errors :
    Event ID 8237: Calendaring agent failed with error 0x80040219 while attempting to open the
    status message. If the user is a delegate, the access rights to the mailbox might not be set up correctly.  Otherwise, the calendar for this mailbox could be corrupted. This could be fixed by moving the mailbox to another Exchange server, or exporting
    the calendar to a Personal Folder File (.PST), and re-importing this into a new calendar. 
    Followed by 
    Event ID 8207: Calendaring agent failed with
    error code 0x80040219 while deleting appointment.
    and then event ID 8200: Calendaring agent failed in message delete notification with error 0x80040219 on : /Example folder/Staff/Room1/tom jones-280257926.EML.
    There were a few instances of these but the script ran succesfully. After the script ran, I checked the replication settings on the public folders and system public folders and on both servers every folder was set to replicate to only the new Exchange 2010
    MBX.
    On the Exchange 2007 MBX, if I run : getpublicfolderstatistics -server ex2007mbx  I get :
    Name                                     ItemCount               LastAccessTime
    exchangeV1                               401                25/03/2015 21:33:24
    If I run getpublicfolderstatistics -server ex2010mbx I get : 
    The operation cannot be executed because there is no available public folder da
    tabase on the server 'EX2010'. 
    If I run the same commands on the EX2010 MBX, I get :
    getpublicfolderstatistics -server ex2007mbx  I get :
    Name                                     ItemCount               LastAccessTime
    exchangeV1                               401                25/03/2015 21:33:24
    getpublicfolderstatistics -server ex2010mbx :
    The entire list of public folders including the exchangev1 folder with 401 items.
    I have checked the permissions on the exchangev1 folder which is in system public folders>schema+root>Microsoft.
    I have dismounted the public folder database on the EX2007MBX and I can access public folders ok. There are no errors and in the folders I have tried, I can add/ delete items.
    Would anyone please be able to advise on the following:
    1) What do I do about the EXCDO errors? They have not recurred since I ran the script and did not occur before I ran the script. What are the implications of the errors?
    2)Running getpublicfolderstatistics -server ex2010mbx  on the Exchange 2007 MBX gives me: 
    The operation cannot be executed because there is no available public folder da
    tabase on the server 'EX2010'. 
    However, the public folders do seem to appear on the EX2010MBX. Is this because EX2007 cannot see the 2010 database?
    3)How do I move the last folder on EX2007MBX: Exchangev1?
    Thanks very much,
    HA.

    Hi,
    From your description, I would like to clarify the following thing:
    Lower version (Exchange 2007) cannot get the database information of higher version (Exchange 2010), it is the expected behavior. Your understanding will be appreciated.
    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]
    Amy Wang
    TechNet Community Support

  • Exchange 2010 public folder not showing on exchange 20003 mailbox

    Hi,
    I have public folder on exchange 2003 and separate public folder on exchange 2010. On exchange 2010 user mailbox, I can see both 2003 and 2010 public folders. On exchange 2003 user mailbox, I can only see 2003 public folders. It is not the permission issue
    as I have given the user "owner" right and see not able 2010 public folder inless i move 2003 user mailbox to 2010 exchange.
    Appreciate if anyone could help me if to point me to directions or any hotfix I can run?
    Thank you very much.
    Pwint

    Are you using OWA or Outlook to view the public folders?
    If you're using OWA, the reason you can't see the folders is that OWA in Exchange 2003 uses WebDAV, which is no longer present in Exchange 2010.
    If you're using Outlook, you'll need to use the troubleshooting logs to determine the cause of the problems.
    It could be related to Outlook trying to connect directly to 2010 mailbox server instead of CAS. Because normally the mailbox server is installed without the CAS role, it does not allow a direct Outlook connection. Or it could be something else,
    like authentication.

  • 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 2003 to 2010 migration move public folder

    Hello.
    I'm on the road to Exchange 2010 migration and stuck at on question
    All tutorial says then you want to replicate system PF and Public Folders you need to add PF 2010 in ESM and set replication to Urgent,that's all
    But then  i view my system PF replication on Exchange 2010 i see checkbox Use public folder is checked and replication shedule on Exchange 2010 is set to Never run(greyed out)
    Is this right? Or i need to uncheck it and then shedule is set to Always run automaticly? 
    Do i need to do it for all PF? (system and non-system)?

    Hi stevemaystr,
    Don’t worry about the replication of PF, we can use the MoveAllReplicas.ps1 and ReplaceReplicaOnPFRecursive.ps1 script to move all public folder and all replicas to another database, please refer to:
    http://technet.microsoft.com/en-us/library/bb331970(v=exchg.141).aspx
    Additional,  I find an similar thread about Migrate PF from Exchange 2003 to Exchange 2010, for your reference:
    https://social.technet.microsoft.com/Forums/exchange/en-US/2dc27efa-d19c-4929-a2f1-54523c847d2a/moving-public-folders-from-exchange-2003-to-2010?forum=exchange2010
    Best Regards,
    Allen Wang

  • Exchange 2010 to 2013 Public Folder Migration -- Token Serialization

    Here is the log entry,Failed to save admin audit log for this cmdlet invocation. Organization: First Organization Log content:Cmdlet Name: New-PublicFolderMigrationRequestObject Modified: f0daff33-6a93-4367-b609-662cfa0b92de\71fc0595-b5d7-4f15-8b7c-bffcefbd810fParameter: SourceDatabase = Public Folder Database Parameter: CSVData = VGFyZ2V0TWFpbGJveCxGb2xkZXJQYXRoDQpDb2JvY28gUEYsXA0KQ29ib2NvIFBGLFxJUE1fU1VCVFJFRVxBcg==...Caller: ExternalAccess: FalseSucceeded: TrueRun Date: 2015-07-07T12:41:45OriginatingServer: (15.00.0995.012)Error:Microsoft.Exchange.Data.ApplicationLogic.AuditLogAccessDeniedException: The requesting account doesn't have permission to access the audit log. --- System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. at...

    Hey Guys!
    I'm in the process of testing a Public Folder migration from Exchange 2010 to 2013, I've been following the recommened migration scenario from Microsoft but have ran into this issue when running New-PublicFolderMigrationRequest. I let the request sit at a queued status for over 6 hours and then decided to look at the event logs. I'm receiving an access denied, requesting account does not have permission to serialize tokens.
    Luckily this is just a test and not in a production environment :-)
    Any suggestion or help to point me in the right direction would be appreciated
    Thanks Guys
    This topic first appeared in the Spiceworks Community

  • Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

    Dear All,
    I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
    For example: in exchange 2010 PF:   
    In exchange 2013
               \Public Folder\sales\A1_calendar
              --->
               \ Public Folder\sales\A2_calendar 
    ---> ?
                \Public Folder\sales\A3_calendar 
    --->  ?
                \Public Folder\sales\A4_calendar 
    ---> ?
    Thanks in advance.
    Regards,
    Willis Wong

    Hi Willis,
    This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Steve Fan
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    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]

  • Exchange 2010 - 2013 Public Folder Migration target database gets much bigger than source database

    Hi,
    i have a question about the pf migration from Exchange 2010 to Exchange 2013. The source database ist about 370 GB. The migration process is still running. At the moment the target database is already 491GB big. Is that a normal behaviour during the migration
    process.
    Thanks

    Hi,
    After you have finished the public folder migration process, you can compare the item count of public folders to make sure all public folders have been moved to Exchange 2013.
    You can check this by comparing the snapshots before and after the migration. You can refer to the "How do I know this worked?" section in the following article.
    Migrate Public Folders to Exchange 2013 From Previous Versions
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2003 to 2010 migration issues

    Hello,
    I have installed exchange 2010 in my legacy 2003 environment six months ago.
    i have moved all the mailboxes, Public folders to exchange 2010 and created routing group connectors between 2003 -2010.
    now unfortunately the legacy server got crashed. now the problem is we are unable to receive emails.
    Can somebody help on this.
    Thanks,
    Sanjay.

    you need to verify that mail flow is configured for exchange 2001
    Verify that Internet mail flow is configured to route through your Exchange 2010 transport servers. For more information, see the following topics:
    Configure Internet Mail Flow Directly Through a Hub Transport Server - https://technet.microsoft.com/en-us/library/bb738138(v=exchg.141).aspx
    Configure Internet Mail Flow Through a Subscribed Edge Transport
    Server - https://technet.microsoft.com/en-us/library/bb738158(v=exchg.141).asp
    To verify that all inbound protocol services (Microsoft Exchange ActiveSync, Microsoft Office Outlook Web App, Outlook Anywhere, POP3, IMAP4, Autodiscover service, and any other Exchange
    Web service) are configured for Exchange 2010, see Managing Client Access Servers. - https://technet.microsoft.com/en-us/library/aa997850(v=exchg.141).aspx
    For other steps follow the article: https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
    Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful&quot; if it really helps and &quot;Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
    question. ~~ This Information is provided is &quot;AS IS&quot; and confers NO Rights!!

  • Public folders are not in sync after settting up Replicas between Exchange 2003 and 2010

    I have setup Public Folder replicas between the 2 Exchange servers and I can see all the top and sub level folders.
    For those mailboxes that were migrated over to Exchange 2010,  I have noticied  a lower number of item contents in these fodders when views from an Outlook client whose mailbox had been migrated over to Exchange 2010.
    On Exchange 2003 System Manager, if I properties one of the Public Folders, under the Replicataion tab, I can see the old and new server there. On the Exchange server 2003 box, I can see the last update reviced was a few weeks ago.
    I did see an option to synchronize content but I am not sure which server to run this one from. The Exchange 2003 or 2010 server.
    There is also a Resend Changes... option. Should I use this instead?
    Can anyone advise?

    Hi,
    The "Resend changes" and "Synchronize content" options in Exchange 2003 ESM are used to initiate hierarchy and content replication.
    To update public folder hierarchy and content from Exchange 2010 side, you can use the following commands.
    Update-PublicFolderHierarchy
    Update-PublicFolder
    Please run the Get-publicfolderstatistics cmdlet to get public folder details such as item count, this information will help you compare content replicated between the source and destination servers.
    Besides, here is a blog about public folder replication troubleshooting for your reference.
    http://blogs.technet.com/b/exchange/archive/2006/01/17/417611.aspx
    Hope this is helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • 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

  • Issues with Public folder migration

    Hi,
    I'm at the end of an Exchange 2007 to 2010 migration. 99.9% of mailboxes have been moved to the 2010 Mailbox server. The environment is : 2007 SP3(1 X CAS, HT and MBX), 2010 SP3 (1 X CAS, HT, and MBX). I'd really appreciate some help on some Public folder
    replication issues:
    I have replicated the default public folders across using: 
    AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\" 
    -ServerToAdd 2010MBX
    1) When I get public folder statistics from each Exchange mailbox, there are a few public folders where there are 1 or 2 items on the old server that are not on the new one.  There is one public folder on the new server that is not on the old one. I've
    updated the hierarchy but that hasn't helped. Is it possible this is because of the folder being created on the new server later on? Is there any way to easily find the folder location in a complex hierarchy?
    2) When I try to get public folder statisctics on the 2007 MBX server, I get the following:
    [PS] C:\Documents and Settings\ha>Get-PublicFolderStatistics >d:\test\test2
    .txt
    WARNING: Object
    000000001A447390AA6611CD9BC800AA002FC45A030002640DAF3EE76D4783F6C0C0CD5AD03F015
    6AA8A1ECE0000 has been corrupted and it is in an inconsistent state. The
    following validation errors have occurred:
    WARNING: The Name property contains leading or trailing whitespace, which must
    be removed.
    WARNING: Object
    000000001A447390AA6611CD9BC800AA002FC45A030002640DAF3EE76D4783F6C0C0CD5AD03F015
    6AA8A1EDA0000 has been corrupted and it is in an inconsistent state. The
    following validation errors have occurred:
    WARNING: The Name property contains leading or trailing whitespace, which must
    be removed.
    WARNING: Object
    000000001A447390AA6611CD9BC800AA002FC45A0300789C48D2424955459FDBE1D59E103FF6000
    0000652320000 has been corrupted and it is in an inconsistent state. The
    following validation errors have occurred:
    WARNING: The Name property contains leading or trailing whitespace, which must
    be removed.
    How do I find the object referenced by the series of numbers (for example, 000000001A447390AA....)?
    I'm also  seeing some backfill events (even ID 1020) on the 2010 Hub transport.
    3) Which System Public Folders should be replicated from 2007 to 2010 prior to moving them using the moveallreplicas script? At the moment, the following are replicated between both servers: 
    StoreEvents (Old server), Schema-root, Schedule + Free Busy (and sub folders), OWA Scratchpad (Old Server), Event's Root, Offline address Book (/o=Exchange2003/cn=addrlists/cn=oabs/cn=Default Offline Address List & EX:/o=Exchange2003/ou=Exchange
    Administrative Group (FYDIBOHF23SPDLT) )
    Other system public folders are not replicated.
    Thanks,
    HA

    Hi,
    1) You can use the Get-Publicfolder -Recurse | Format-List Name, *path cmdlet to check the parent path of public folder.
    2) You can use the Get-PublicFolderStatistics  | fl name, *identity command to get the identity of public folder. View the list of identity you get, and check if you can find the following object.
    000000001A447390AA6611CD9BC800AA002FC45A030002640DAF3EE76D4783F6C0C0CD5AD03F015
    6AA8A1ECE0000
    3) When you migrate public folder from Exchange 2007 to Exchange 2010, you need to replicate the following system public folders, you can remove the others.
    SCHEDULE+ FREE BUSY, OFFLINE ADDRESS BOOK and EFORMS REGISTRY(if you use Organizational Forms)
    Here is a related thread for you reference.
    https://social.technet.microsoft.com/Forums/exchange/en-US/236fbd47-6907-4bb7-8f44-aec8acfa5cac/public-folders-system-folder-replication-from-exchange-2007-to-2010?forum=exchange2010
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Public Folder Migration from Exchange 2007 to 2013 fails RelinquishedWlmStall budget limitations

    I have been trying to migrate approx 50 public folders from Exchange 2007 to Exchange 2013 for several months.  I have followed every link I can find on how to do the migration properly.  It will stay in a queued state for hours until the MRS is
    restarted.  It will then start copying messages.  After reaching 28% I get RelinquishedWlmStall as Status Detail.  Running the Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl command I get the following: (truncated)
    Status                           : InProgress
    FailureTimestamp                 :
    IsValid                          : True
    ValidationMessage                :
    OrganizationId                   :
    RequestGuid                      : ff4af794-f31e-4334-959f-7d6c4ccbe310
    RequestQueue                     : PublicFolders
    ExchangeGuid                     : b12c1f83-c4ae-46bb-a26a-0422d90800e4
    Identity                         : eddf983d-5827-4a2a-98ef-820321ebebd0\ff4af794-f31e-4334-959f-7d6c4ccbe310
    DiagnosticInfo                   :
    Report                           
                                       4/23/2015 8:49:37 AM [pionexxxx] Request processing started.
                                       4/23/2015 8:49:37 AM [pionexxxxx] Cleared sync state for request
                                       00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                       4/23/2015 8:49:38 AM [pionexxxxxx] Stage: CreatingFolderHierarchy. Percent complete:
                                       10.
                                       4/23/2015 8:49:38 AM [pionexxxxxx] Initializing folder hierarchy from mailbox '': 50
                                       folders total.
                                       4/23/2015 8:49:38 AM [pionexxxx] Folder creation progress: 0 folders created in
                                       mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                       4/23/2015 8:49:38 AM [pionexxxxx] Warning: Failed to find or link recipient object
                                       'FF-D5-EF-1A-0A-95-D7-4B-89-02-A6-9E-DA-4D-23-4B' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes' with EntryId '00-00
                                       00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E
                                       98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-4C-00-00'. This folder can be linked
                                       manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       'D8-46-09-BE-0B-3D-6E-4A-95-10-8F-C5-AA-0B-88-50' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Inventory'
                                       with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                       3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-12-6A-F5-00-00'. This folder
                                       can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                       migration completes.
                                       4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       'A6-12-DA-05-7D-21-DE-44-90-61-64-23-8C-62-41-F4' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Ulysses'
                                       with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                       3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-7C-00-00'. This folder
                                       can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                       migration completes.
                                       4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       '96-76-90-F1-A5-B7-DB-41-A7-A3-D6-8D-86-AE-45-A5' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/CSR Schedule' with EntryId '00-00-00
                                       00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E-98
                                       03-B9-14-4F-B4-12-C1-00-00-00-0E-34-FF-00-00'. This folder can be linked manually
                                       by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                       '82-72-47-AA-D7-68-85-4C-91-92-41-45-8A-20-EA-6D' in active directory for mail
                                       enabled public folder 'Public Root/IPM_SUBTREE/DC 24 Hr Schedule' with EntryId '00-
                                       0-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-85-62-89-2A-52-C3-92-
                                       5-93-F8-5A-6F-56-5D-D1-D4-00-00-00-00-27-37-00-00'. This folder can be linked
                                       manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                       4/23/2015 8:49:41 AM [pionexxxx] Folder hierarchy initialized for mailbox
                                       'b12c1f83-c4ae-46bb-a26a-0422d90800e4': 46 folders created.
                                       4/23/2015 8:49:41 AM [pionexxxx] Stage: CreatingInitialSyncCheckpoint. Percent
                                       complete: 15.
                                       4/23/2015 8:49:41 AM [pionexxxx] Initial sync checkpoint progress: 0/50 folders
                                       processed. Currently processing mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                       4/23/2015 8:49:42 AM [pionexxxx] Initial sync checkpoint completed: 46 folders
                                       processed.
                                       4/23/2015 8:49:42 AM [pionexxxx] Stage: LoadingMessages. Percent complete: 20.
                                       4/23/2015 8:49:43 AM [pionexxxx] Messages have been enumerated successfully. 40607
                                       items loaded. Total size: 149 MB (156,253,810 bytes).
                                       4/23/2015 8:49:43 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 25.
                                       4/23/2015 8:49:43 AM [pionexxxx] Copy progress: 0/40607 messages, 0 B (0
                                       bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                       4/23/2015 9:04:37 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 28.
                                       4/23/2015 9:04:37 AM [pionexxxxx] Copy progress: 3660/40607 messages, 7.015 MB
                                       (7,355,409 bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                       4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
                                       unfavorable server health or budget limitations.
    ItemsTransferred                 : 3660
    PercentComplete                  : 25
    4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
    unfavorable server health or budget limitations.
    It never tries to restart.  Can anyone please help?  The server checks for health all come back ok.   I will be more than glad to include further information.  

    Hi,
    Basic on the error message, I notice that public folder migrate slow and display that “Relinquishing job because of large delays due to unfavorable server health or budget limitations” .
    If I misunderstand your concern, please do not hesitate to let me know.
    Since it is just slow and not failing, please do not stop the batch, it might connect to another server for sync.
    Meanwhile, please refer to below link so that get details about Exchange Online migration performance and best practices:
    https://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
    If the issue persists, please collect the relevant migration report for further troubleshooting.
    Thanks
    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]
    Allen Wang
    TechNet Community Support

Maybe you are looking for

  • Issue with Audit Log report in SharePoint 2010

    I have enabled REPORTING feature at site collection level and configured the site collection audit settings. I tried to generated Audit log reports, most of the time it keeps on processing as shown in fig.It keeps on processing, never comes to report

  • HP LaserJet 2600n poor print quality/streaking

    I am the original owner of an HP LJ 2600n with a poor print quality/streaking issue. The poor print quality occurs with any and all paper that I use (currently Hammerhill 20# stock) and occurred with Windows XP and Windows 7. The print cartidges are

  • Need of a Javascript

    For the site I am working on i have been asked to do something thats a little more complex that all the CSS and DIV problems I have been posting about recently. That said it is something which probibly hasent change since I first learnt web design ba

  • File to File interface Count

    HI ALL, I have a file to file scenario used to move 100 PDF files from System A to B . i give wildcard * in the sender communication and used ASMA to name the file in the receiver side. the requirment is client is asking to send a e-mail aftre sendin

  • Plugin install problem - Sorry, an error has occured

    Hi, We are having problem's with our QuickTime plugin code. We are using the object and embeded tag and are using the following url http://www.apple.com/qtactivex/qtplugin.cab for the codebase attribute. We are redirected to this url, http://wsidecar