none
The error number is 0x80004005

    Question

  • Error updating public folder with free/busy information on virtual machine CONTOSOMAIL. The error number is 0x80004005.

     

    [PS] C:\Windows\system32>get-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+

    FREE BUSY" -Recurse | fl name,Replicas

     

    Name     : SCHEDULE+ FREE BUSY

    Replicas : {}

     

    Name     : EX:/o=SGB/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)

    Replicas : {CONTOSOMAIL\Second Storage Group\My Public Folder Database}

     

    Name     : EX:/o=SGB/ou=First Administrative Group

    Replicas : {}

     

    [PS] C:\Windows\system32>

     

    Summary: 2 item(s). 2 succeeded, 0 failed.

    Elapsed time: 00:00:01

     

    Edit Public Folders

    Completed

     

    Warning:

    The command completed successfully but no settings of '\Public Folders' have been modified.

     

    Exchange Management Shell command completed:

    set-AddressList -Instance '\Public Folders'

     

    Elapsed Time: 00:00:00

     

    Apply Public Folders

    Completed

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Schedule+ Free Busy Information - First Administrative Group" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Offline Address Book - First Administrative Group" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Offline Address Book - \/o=SGB\/cn=addrlists\/cn=oabs\/cn=Default Of" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 2" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 4" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 3a" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 2 30432942" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 4 22120282" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 3a 43829218" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Public Calendar" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Sales Forecasting Schedule" is invalid and could not be updated.

     

     

    Exchange Management Shell command completed:

    update-AddressList -Identity '\Public Folders'

     

    Elapsed Time: 00:00:00

     


    Today is a BLURR and yesterday was a nightmare
    Friday, July 16, 2010 10:30 PM

Answers

  • Yes.
    --
    Ed Crowley MVP
    "There are seldom good technological solutions to behavioral problems."
    .
    "ART_Tech" wrote in message news:b73d943c-c156-4629-80e9-d0015c00d0d5...

    The First Administrative Group is a remnant of the 2003 Exchange Server that was decommishioned. Would you still suggest this action?

     

    Name     : EX:/o=SGB/ou=First Administrative Group

    Replicas : {}


    Today is a BLURR and yesterday was a nightmare

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • Marked as answer by ART_Tech Friday, July 23, 2010 12:16 AM
    Wednesday, July 21, 2010 7:12 PM

All replies

  • Do you have a question?
    --
    Ed Crowley MVP
    "There are seldom good technological solutions to behavioral problems."
    .
    "ART_Tech" wrote in message news:6a4b83cd-7d98-49b1-beac-5b20a489c431...

    Error updating public folder with free/busy information on virtual machine CONTOSOMAIL. The error number is 0x80004005.

     

    [PS] C:\Windows\system32>get-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+

    FREE BUSY" -Recurse | fl name,Replicas

     

    Name     : SCHEDULE+ FREE BUSY

    Replicas : {}

     

    Name     : EX:/o=SGB/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)

    Replicas : {CONTOSOMAIL\Second Storage Group\My Public Folder Database}

     

    Name     : EX:/o=SGB/ou=First Administrative Group

    Replicas : {}

     

    [PS] C:\Windows\system32>

     

    Summary: 2 item(s). 2 succeeded, 0 failed.

    Elapsed time: 00:00:01

     

    Edit Public Folders

    Completed

     

    Warning:

    The command completed successfully but no settings of '\Public Folders' have been modified.

     

    Exchange Management Shell command completed:

    set-AddressList -Instance '\Public Folders'

     

    Elapsed Time: 00:00:00

     

    Apply Public Folders

    Completed

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Schedule+ Free Busy Information - First Administrative Group" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Offline Address Book - First Administrative Group" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Offline Address Book - \/o=SGB\/cn=addrlists\/cn=oabs\/cn=Default Of" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 2" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 4" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 3a" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 2 30432942" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 4 22120282" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/OAB Version 3a 43829218" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Public Calendar" is invalid and could not be updated.

     

    Warning:

    The recipient "contoso.com/Microsoft Exchange System Objects/Sales Forecasting Schedule" is invalid and could not be updated.

     

     

    Exchange Management Shell command completed:

    update-AddressList -Identity '\Public Folders'

     

    Elapsed Time: 00:00:00

     


    Today is a BLURR and yesterday was a nightmare

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Saturday, July 17, 2010 12:52 AM
  • Are you saying users are not able to share free/busy information among themself.

    This problem occurs because the following components were not replicated to the computer that is running Exchange 2007 before the Exchange Server 2003 or Exchange 2000 Server computers were decommissioned:
    "      The "Schedule+ Free/Busy" system folder on the servers that were running Exchange Server 2003
    "      The Exchange 2000 Server Administrative Group"

    Users who use Outlook 2003 cannot publish their free/busy data in Exchange Server 2010 or in Exchange Server 2007:: http://support.microsoft.com/kb/945602


    Anil
    Sunday, July 18, 2010 4:18 AM
  • How would I correct this error condition in the logs. I am not at all concerned with users running Outlook 2003 or earlier, just would like to correct the indication.


    Today is a BLURR and yesterday was a nightmare
    Monday, July 19, 2010 3:05 PM
  • If you're asking about an event in your event log, then you should post the complete event log entry.
    --
    Ed Crowley MVP
    "There are seldom good technological solutions to behavioral problems."
    .
    "ART_Tech" wrote in message news:90a372f0-4c27-4f32-9657-47712d2c2555...

    How would I correct this error condition in the logs. I am not at all concerned with users running Outlook 2003 or earlier, just would like to correct the indication.


    Today is a BLURR and yesterday was a nightmare

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Tuesday, July 20, 2010 2:24 PM
  • Error updating public folder with free/busy information on virtual machine CONTOSOMAIL. The error number is 0x80004005.

     

    - System

       
    - Provider
          [ Name] MSExchangeFBPublish
       
    - EventID 8207
          [ Qualifiers] 49153
       
      Level 2
       
      Task 1
       
      Keywords 0x80000000000000
       
    - TimeCreated
          [ SystemTime] 2010-07-20T14:53:00.000000000Z
       
      EventRecordID 21396
       
      Channel Application
       
      Computer contosomail.contoso.com
       
      Security

    - EventData

        CONTOSOMAIL
        0x80004005

    Today is a BLURR and yesterday was a nightmare
    Tuesday, July 20, 2010 3:20 PM
  • The problem could be that you don't have a replica for one of your two folders.  Try adding a replica for the second one listed in your original post on your public folder database.
    --
    Ed Crowley MVP
    "There are seldom good technological solutions to behavioral problems."
    .
    "ART_Tech" wrote in message news:e4e7d8fe-a650-41e3-86e7-283f9b8bdc86...

    Error updating public folder with free/busy information on virtual machine CONTOSOMAIL. The error number is 0x80004005.

     

    - System

       
    - Provider
          [ Name] MSExchangeFBPublish
       
    - EventID 8207
          [ Qualifiers] 49153
       
      Level 2
       
      Task 1
       
      Keywords 0x80000000000000
       
    - TimeCreated
          [ SystemTime] 2010-07-20T14:53:00.000000000Z
       
      EventRecordID 21396
       
      Channel Application
       
      Computer contosomail.contoso.com
       
      Security

    - EventData

        CONTOSOMAIL
        0x80004005

    Today is a BLURR and yesterday was a nightmare

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • Proposed as answer by Alan.Gim Thursday, July 22, 2010 11:02 AM
    Tuesday, July 20, 2010 3:27 PM
  • The First Administrative Group is a remnant of the 2003 Exchange Server that was decommishioned. Would you still suggest this action?

     

    Name     : EX:/o=SGB/ou=First Administrative Group

    Replicas : {}


    Today is a BLURR and yesterday was a nightmare
    Wednesday, July 21, 2010 6:16 PM
  • Yes.
    --
    Ed Crowley MVP
    "There are seldom good technological solutions to behavioral problems."
    .
    "ART_Tech" wrote in message news:b73d943c-c156-4629-80e9-d0015c00d0d5...

    The First Administrative Group is a remnant of the 2003 Exchange Server that was decommishioned. Would you still suggest this action?

     

    Name     : EX:/o=SGB/ou=First Administrative Group

    Replicas : {}


    Today is a BLURR and yesterday was a nightmare

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • Marked as answer by ART_Tech Friday, July 23, 2010 12:16 AM
    Wednesday, July 21, 2010 7:12 PM
  • Microsoft recommends that you do not remove the original Administrative groups from an organization. Typically, when an administrative group is removed and mail begins to back up in the System Attendant mailbox, this indicates that the Free/Busy folder from the old administrative group was not replicated correctly to one of the remaining administrative groups

    ----------Refer to <How to Remove the Last Legacy Exchange Server from an Organization>


    James Luo
    TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
    If you have any feedback on our support, please contact tngfb@microsoft.com
    Thursday, July 22, 2010 11:02 AM
  • Ed, thank you for your time, expertise and patience. The error has not replicated itself for the last day; I will keep an eye on it and let you know if it reoccurs. Thank you once again.


    Today is a BLURR and yesterday was a nightmare
    Friday, July 23, 2010 12:17 AM