Hi, I am seeing the following error in the application event log and having trouble identifying the cause. Event Type:ErrorEvent Source:MSExchangeFBPublishEvent Category:General Event ID:8207Date:28/01/2009Time:3:23:32 PMUser:N/AComputer:<namewithheld>Description:Error updating public folder with free/busy information on virtual machine <namewithheld>. The error number is 0x8004010f. I am using a clustered setup: Exchange CCR Node 1Exchange CCR Node 2Exchange HT/CA Running Exchange Server 2007 (migrated from 2003). All clients are using Outlook 2007. Can anyone help? ThanksDave.

Further to this, I have noticed if I schedule an appointment, Outlook is unable to retreive the free/busy information for some people, others work fine. I have tested from OWA and also have the same issue. I have run the 'Test E-mail AutoConfiguration' tool and AutoDiscover seems to be working fine, no errors reported.I have also checked the permissions on the users calendar for which I am unable to retrieve free/busy data. It is OK. Ideas?

I managed to resolve the second issue. The usersemail address in AD was invalid and this somehow affected free/busy. As soon as it was corrected free/busy information was available. However I'm still having the problem mentioned in the original post.

Hi, From your description, I notice that you only have a Clustered Mailbox Server with contains the mailbox database and public folder database. If I am off base, please let me know. Firstly, please understand CCR and public folder replication are two very different forms of replication built into Exchange. Due to interoperability limitations between continuous replication and public folder replication, if more than one Mailbox server in the Exchange organization has a public folder database, public folder replication is enabled and public folder databases should not be hosted in CCR environments. Regarding the event 8207, please run the following command and post the output here for further research: get-publicfolder "\non_ipm_subtree\schedule+ free busy" recurse Mike

Hi Mike,Thanks for the reply.I'm not full bottle on Exchange but from what I can see in EMC the First SG is the mailbox DB and the Second SG is the public folders. Our department does not use public folders at all and because all clients use outlook 2007 we don't need it for free/busy either.Therefore the previous admin suspended the replication on the Second SG. Hope that makes sense. Here is the output from EMS. ( I've hidden server name etc ;)[PS] C:\Documents and Settings\Administrator.AAAAAA01>Get-PublicFolder "\non_ipm_subtree\schedule+ free busy" -recurse |fl AgeLimit :EntryId : 000000001A447390AA6611CD9BC800AA002FC45A0300AC 4D12AC37FAD14783090154A43191370000000000040000HasSubFolders : TrueHiddenFromAddressListsEnabled : FalseLocalReplicaAgeLimit :MailEnabled : FalseMaxItemSize :Name : SCHEDULE+ FREE BUSYParentPath : \NON_IPM_SUBTREEPerUserReadStateEnabled : TruePostStorageQuota :Replicas : {}ReplicationSchedule : {}RetainDeletedItemsFor :StorageQuota :UseDatabaseAgeDefaults : TrueUseDatabaseQuotaDefaults : TrueUseDatabaseReplicationSchedule : TrueUseDatabaseRetentionDefaults : TrueIdentity : \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSYIsValid : TrueOriginatingServer : <<hidden>> AgeLimit : 100.00:00:00EntryId : 000000001A447390AA6611CD9BC800AA002FC45A03008D 71CF790DB3394CBBD0057E1B473CE70000000000070000HasSubFolders : FalseHiddenFromAddressListsEnabled : TrueLocalReplicaAgeLimit :MailEnabled : FalseMaxItemSize :Name : EX:/o=AAA/ou=Exchange Administrative Group (FY DIBOHF23SPDLT)ParentPath : \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSYPerUserReadStateEnabled : TruePostStorageQuota :Replicas : {Public Folders}ReplicationSchedule : {}RetainDeletedItemsFor :StorageQuota :UseDatabaseAgeDefaults : FalseUseDatabaseQuotaDefaults : TrueUseDatabaseReplicationSchedule : TrueUseDatabaseRetentionDefaults : TrueIdentity : \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=AAA /ou=Exchange Administrative Group (FYDIBOHF23S PDLT)IsValid : TrueOriginatingServer : <<hidden>> Thanks,Dave

Hi Dave, Thanks for your response. Based on your description, I think that you have two options currently: 1. As you do not use public folder at all, I think you can simply ignore the issue. I would like to explain that for Exchange 2007 and Outlook 2007, they obtain free/busy information by using Availability service instead of public folder which used by Exchange 2003 and Outlook 2003. The availability service obtains the users free/busy information from his mailbox directly. 2. As you may already know, the Outlook publishes Free/Busy information into public folder based on its LegacyExchangeDN attribute. For example, if the users LegacyExchangeDN attribute is /o=contoso/ou=First Administrative Group/cn=Recipients/cn=testuser, the Free/Busy information for the user is published to the \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX: /o=contoso/ou=First Administrative Group folder. For new users whose mailbox are created on Exchange 2007 directly, the Free/Busy information is published into \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=orgname /ou=Exchange Administrative Group (FYDIBOHF23SPDLT) folder. It is because the legacyexchangedn of the users are /o=orgname/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=username. Nevertheless, for users whose mailbox is migrated into Exchange 2007 from Exchange 2003, their legacyexchangedn is /o=orgname/ou=First Administrative Group/cn=Recipients/cn=username. Therefore, the free/busy information for the users should be published into \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX: /o=orgname/ou=First Administrative Group folder. From your output, the \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX: /o=orgname/ou=First Administrative Group folder does not exists. Therefore, I think the issue mostly occurs because the legacy mailbox which is moved to Exchange 2007 unable to locate the Free/Busy folder to publish the Free/Busy information. I suggest you create a public folder to check whether the issue can be solved. You can refer to following command to create a new public folder: New-Publicfolder -name "EX:/o=ORGName/ou=First Administrative Group" -path "\non_ipm_subtree\schedule+ free busy" Note: If your original Exchange has different Admin Group name, you need to change the command. Mike

Hi Mike,Thanks for the info. As free/busy appears to be working correctly I know I could ignore the error but I like my event logs to be error free =)Rather than creating the public folder, do you know what would happen if I was to change the value of thelegacyExchangeDN attribute to/o=org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=username for the old users who were migrated to 2007. Would this work or would it cause problems? Regards,David.

Hi David, Please understand Outlook submit message by using sender and recipients legacyexchangedn attribute. Please consider the following situation: UserA sends to a message to UserB. In the message, the senders legacyexchangedn attribute is saved in the message as a MAPI property (PR_SENDER_EMAIL_ADDRESS). After that, you modify the senders legacyexchangedn attribute. Then, UserB reply the message. Please understand old legacyexchangedn attribute is submitted when UserB reply the message as the old legacyexchangedn is saved in the original message as a MAPI property. Then, Exchange may generate NDR for the message because the user cannot be found in AD. Therefore, we do not recommand to change the users legacyexchangedn attribute value. Mike

Hi Mike,Thanks for all your help. Creating the public folder seems to have worked. No errors so far.Dave.

I have tons of 03 clients and have been searching for days to find this answer. After much searching and looking through forums, I finally came across this. During our exch 2007 migration, I read many how-to's and guides for the migration. I don't remember seeing this information anywhere.