none
InterOrg Replication Tool (IORepl) Errors

    Question

  • Hi,

    I have successfully configured to replicate F/Bs and PFs between an Exchange 2003 SP2 organisation and an Exchange 2010 SP1 organisation.  What I am finding is that the jobs always run successfully the first time but on subsequent runs of the PF job I get the following errors in the log:

    >>>>>>>>>>>>>>>>>>>>>>>>>>> REPLICATION STARTED <<<<<<<<<<<<<<<<<<<<<<<<<<<
    @@START 13:04:46
    Session : Ex2003 to Ex2010 PFs
    Start Time : Friday, July 01, 2011  13:04:46
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    @@STATS 0 0 0 0 0 0 0 0
    Stop Time : Friday, July 01, 2011  13:06:36
    >>>>>>>>>>>>>>>>>>>>>>>>>>> REPLICATION STOPPED <<<<<<<<<<<<<<<<<<<<<<<<<<<
    @@STOP 13:06:36

    Has anyone seen this and know what it is referring to or what is wrong?  I have very carefully followed every step in the technet article and Exchange Team blog articles - http://technet.microsoft.com/en-us/library/ee307369(EXCHG.80).aspx.

    The symptom seems to be that some PF content is not now replicating.

    Thanks

    Mark

     

    Friday, July 01, 2011 12:12 PM

All replies

  • Hello Mark,

    Check this out...

     

    Cause:There was no Public folder database in the destination server 
    Resolution:Changed the end point of replication to point to a server that has public folder database

    Cheers,

     


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Friday, July 01, 2011 12:31 PM
  • Thanks for your response Gulab.

    However I deliberately set up a multi-role server running CAS, HUB, MBX and PF roles to use as the end-point for replication so I can't see how that will apply.  I have double-checked that the service account mailbox is on that servers mailbox database, that the mailbox database is set to use the local PF database and even set the RPCClientAccessParamater to be itself as well.

    Any other suggestions?

    I have just rebooted the subscriber server which had some updates to install and also stopped exssrv.exe, removed the exsync*.dat files and re-created the exssrv.exe job, so will monitor.  This job re-creation process usually helps for the first run but subsequent ones still fail.  The F/B job logs don't report the same error either.

    Thanks

    Mark

     


    Mark H
    Friday, July 01, 2011 1:31 PM
  • Well, that reboot & patching didn't help.

    The main Public Folder replication job (i.e. not the Free/Busy ones) still runs ok for the first two runs after a stop/remove/install/restart cycle and then starts to generate the above ICS Collector Object errors.

    Can anyone help?

    Thanks


    Mark H
    Tuesday, July 05, 2011 3:15 PM
  • ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].

    --------------------------------------------------------------------------

    Error 80004005
    # for hex 0x80004005 / decimal -2147467259 :
      DDERR_GENERIC                                                 ddraw.h
      DIERR_GENERIC                                                 dinput.h
      DPERR_GENERIC                                                 dplay.h
      DPNERR_GENERIC                                                dplay8.h
      DSERR_GENERIC                                                 dsound.h
      DVERR_GENERIC                                                 dvoice.h
      ecError                                                       ec.h
      MAPI_E_CALL_FAILED                                            mapicode.h
      STIERR_GENERIC                                                stierr.h
      E_FAIL                                                        winerror.h
    # Unspecified error
    # 10 matches found for "80004005"

    -----------------------------------------------------------------------

    This issue normally happens if end point mailbox database is not pointing to local public folder store. I believe you have Exchange 2010 Sp1 is configured with all the roles (HUB,CAS and Mailbox) with local public folder store

    1. Is this issue happening only with old public folders ? what happens if you create some test public folders+sub folders on exchange 2003 servers? are these getting replicating properly?

    32try to recreate the config file in the remote forest again after granting the permissions to this service account with "Create Top Level Public Folder" rights to the PF Hierarchy object with help of adsiedit

    3.If it fails again then plz post the new errors and plz confirm the build version of Exchange 2k10 (Roll up update?)

    Thanks

    Balinder

     

    Wednesday, July 06, 2011 4:31 AM
  • Thanks for your response Balinder.

    1. I've tried a new top-level PF and that does seem to continue replicating new items successfully after the first two runs whilst the existing ones do not replicate new items.  So yes, it would appear to be a problem with existing PFs.

    2. The subscriber forest service account is already a member of the 'Public Folder Management' role group which already has the 'Create Top Level Public Folder' rights in the subscriber forest according to ADSIEDIT.  Did you mean try giving the publisher forest service account these rights as well in the subscriber forest?  There is a two-way trust so this is possible.

    3. I can confirm the Exchange 2010 server is running SP1 with Rollup3-v3.

     

    I will try re-creating the config file from scratch anyway.  There are only a few dozen PFs, most of them top-level since it's a very flat structure, so won't take too long.  I will feed back.

     

    Mark


    Mark H
    Wednesday, July 06, 2011 9:45 AM
  • Unfortunately recreating the jobs from scratch has not helped.
    Mark H
    Wednesday, July 06, 2011 11:18 AM
  • Hello Mark,

     

    could you please confirm the version of this dll file from your Exchange 2003 server (emsmdb32.dll) "C:\Windows\system32" where you have IORepl Tool installed  and also post me latest errors from IORepl Tool.

     

    Thankx

    Balinder


    Balinder Singh
    Thursday, July 07, 2011 8:46 AM
  • Hi

    The dll versions on the Exchange 2003 server where the tool is installed and the Exchange 2003 server with the public folders (VMLE34 below) are:6.5.7654.12

    >>>>>>>>>>>>>>>>>>>>>>>>>>> REPLICATION STARTED <<<<<<<<<<<<<<<<<<<<<<<<<<<
    @@START 11:50:46
    Session : PFs Union to from xxx
    Start Time : Friday, July 08, 2011  11:50:46
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: ICS Synchronizer returned error, failed [80004005].
    ERROR: Unable to replicate '[LEUKTGHMX03]?Facilities Contacts' to '[VMLE34]\Facilities Contacts'.
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: ICS Synchronizer returned error, failed [80004005].
    ERROR: Unable to replicate '[LEUKTGHMX03]?Interviews' to '[VMLE34]\Interviews'.
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: ICS Synchronizer returned error, failed [80004005].
    ERROR: Unable to replicate '[LEUKTGHMX03]?LEAH Parties' to '[VMLE34]\LEAH Parties'.
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: ICS Synchronizer returned error, failed [80004005].
    ERROR: Unable to replicate '[LEUKTGHMX03]?London Office' to '[VMLE34]\London Office'.
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: ICS Synchronizer returned error, failed [80004005].
    ERROR: Unable to replicate '[LEUKTGHMX03]?The Jasmine Room' to '[VMLE34]\The Jasmine Room'.
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: ICS Synchronizer returned error, failed [80004005].
    ERROR: Unable to replicate '[LEUKTGHMX03]?Warehouse Delivery Slots' to '[VMLE34]\Warehouse Delivery Slots'.
    @@STATS 0 0 0 0 0 0 0 0
    Stop Time : Friday, July 08, 2011  11:52:39
    >>>>>>>>>>>>>>>>>>>>>>>>>>> REPLICATION STOPPED <<<<<<<<<<<<<<<<<<<<<<<<<<< 

     LEUKTGHMX03 is the exchange 2010 server.


    Mark H
    Friday, July 08, 2011 11:56 AM
  • Hello Mark,

    This issue require extensive troubleshooting and testing . I would suggest you to open a support incident for this problem with Microsoft Support team to troubleshoot it further.

    Thank You,

    Balinder


    Balinder Singh
    Wednesday, July 13, 2011 2:43 AM
  • Ok, I probably will not open an incident as we hope to finish the migration relatively soon and have the workaround described above.

    One thought is that the multi-role Exchange 2010 server is in the same AD site as the non-multi-role servers and this could be an issue despite having set the RPCClientAccess parameter.

     

     


    Mark H
    Sunday, July 17, 2011 2:16 PM
  • Hi Mark,

    I have seen similar cases where isuse got resolved after pointing the endpoint to a blank public folder database (new database) on Exchange 2010 Server (CAS+MAILBOX). I don't know if it would help in your case Or not.

    actuly this isuse require extensive troubleshooting and testing to find out the actual root cause of the issue.

    Best Regards

    Balinder

     

     


    Balinder Singh
    Tuesday, July 19, 2011 10:35 AM
  • I am now experiencing this problem after having it working fine for a few months......  did anyone else have this and was there a resolution.  here is the logs I am getting

    >>>>>>>>>>>>>>>>>>>>>>>>>>> REPLICATION STARTED <<<<<<<<<<<<<<<<<<<<<<<<<<<
    @@START 12:09:45
    Session : exchangesync
    Start Time : 06 September 2011  12:09:45
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    ERROR: Unable to configure ICS Collector object, failed [80004005].
    @@STATS 0 0 0 0 0 0 0 0
    Stop Time : 06 September 2011  12:09:47
    >>>>>>>>>>>>>>>>>>>>>>>>>>> REPLICATION STOPPED <<<<<<<<<<<<<<<<<<<<<<<<<<<
    @@STOP 12:09:47

     

     

    thanks

    Gary

    Tuesday, September 06, 2011 11:10 AM