Exchange 2010 Free+Busy Errors, Event ID 14031
Our organization is using Exchange 2010, migrated from Exchange 2003. Everything *appeared* to have migrated over with the exception of the public folder replicas. We have about half of our clients using Outlook 2007 and the other half using Outlook 2003. Events keep getting logged to the mail server indicating our Outlook 2003 users do not have a freebusy public folder.
Log Name: Application
Source: MSExchangeMailboxAssistant
Date: 1/18/2011 4:18:17 PM
Event ID: 14031
Task Category: FreeBusy Assistant
Level: Error
Keywords: Classic
User: N/A
Computer: mail1.domain.org
Description:
Unable to find freebusy public folder: EX:/o=First Organization/ou=First Administrative Group on the server: mail1.domain.org for the user: User Name:8a0fe0f2-5359-4a48-8d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeMailboxAss
<EventID Qualifiers="49156">14031</
<Level>2</Level>
<Task>15</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-01-18T22:
<EventRecordID>19734</Even
<Channel>Application</Chan
<Computer>mail1.domain.org
<Security />
</System>
<EventData>
<Data>EX:/o=First Organization/ou=First Administrative Group</Data>
<Data>mail1.domain.org</Da
<Data>User Name:8a0fe0f2-5359-4a48-8d
<Data>/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=use
</EventData>
</Event>
The Exchange 2003 server has been fully decommissioned and is permanently offline. There is no way for us to bring it back up.
Trying to create replicas in the Public Folder Management Console doesn't work (understandably) since the old mail server does not exist and cannot be connected to. Is there a way to clear up this issue?
Server mail1 has Hub Transport, CAS, and Mailbox roles. Also has public folders, OAB generation, and is on a member server, not a domain controller. It is running on 2008 R2 Enterprise, Exchange version is 2010 Enterprise.
I was told by one of my engineers that public folders had "stopped working" on the old mail server a long time ago, but never mentioned it until recently. I'm not sure what was meant by that, but everything seems to have come over to Exchange 2010 just fine. I believe I shouldn't ignore these errors since one or more of them may try to use the Out Of Office assistant and get slapped with an error message, so I'd like to get rid of this problem before it becomes a problem.
Log Name: Application
Source: MSExchangeMailboxAssistant
Date: 1/18/2011 4:18:17 PM
Event ID: 14031
Task Category: FreeBusy Assistant
Level: Error
Keywords: Classic
User: N/A
Computer: mail1.domain.org
Description:
Unable to find freebusy public folder: EX:/o=First Organization/ou=First Administrative Group on the server: mail1.domain.org for the user: User Name:8a0fe0f2-5359-4a48-8d
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeMailboxAss
<EventID Qualifiers="49156">14031</
<Level>2</Level>
<Task>15</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-01-18T22:
<EventRecordID>19734</Even
<Channel>Application</Chan
<Computer>mail1.domain.org
<Security />
</System>
<EventData>
<Data>EX:/o=First Organization/ou=First Administrative Group</Data>
<Data>mail1.domain.org</Da
<Data>User Name:8a0fe0f2-5359-4a48-8d
<Data>/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=use
</EventData>
</Event>
The Exchange 2003 server has been fully decommissioned and is permanently offline. There is no way for us to bring it back up.
Trying to create replicas in the Public Folder Management Console doesn't work (understandably) since the old mail server does not exist and cannot be connected to. Is there a way to clear up this issue?
Server mail1 has Hub Transport, CAS, and Mailbox roles. Also has public folders, OAB generation, and is on a member server, not a domain controller. It is running on 2008 R2 Enterprise, Exchange version is 2010 Enterprise.
I was told by one of my engineers that public folders had "stopped working" on the old mail server a long time ago, but never mentioned it until recently. I'm not sure what was meant by that, but everything seems to have come over to Exchange 2010 just fine. I believe I shouldn't ignore these errors since one or more of them may try to use the Out Of Office assistant and get slapped with an error message, so I'd like to get rid of this problem before it becomes a problem.
Shreedhar Ette
- Right click on the Exchange 2010 Mailbox Database under Org Config/Mailbox. On the Client Settings tab, it should be pointed to the correct public folder server\storage group\database.
Migration isnt done properly,Change the legacyexchangedn value of the users who are migrated using admodify in bulk, try for one user and then for rest:
Change the LegacyExchangeDN attribute of users from the old administrative group to point to one of the remaining administrative groups. To do this, follow these steps:
a.Download the Admodify.exe tool from http://www.codeplex.com/admodify, and then extract the contents of the .zip file to a folder.
b.Double-click Admodify.exe. If you are prompted to run the program, click Run.
c.In the ADModify.NET dialog box, click Modify Attributes.
d.Under Domain List, click the domain entry that corresponds to the domain in which the affected Exchange server is located. For example, click DC=corp,DC=example,DC=com.
e.Under Domain Controller List, click the fully qualified domain name of the domain controller that hosts the affected Exchange users. For example, click DC-1.corp.example.com.
f.Click to clear the following check boxes:
Groups
Contacts
Public Folders
Show Containers Only
Note:
Do not clear the Users check box.
Click the green arrow button that is beside Domain Controller List.
a.Under Domain Tree List, expand the domain object that is displayed.
b.Click the container in which the affected users are located. For example, click Users.
c.Click Add to List, click Select All, and then click Next.
d.Click the Custom tab, and then click to select the Make a customized attribute modification check box.
e.In the Attribute Name box, type LegacyExchangeDN.
f.In the Attribute Value box, type an entry that corresponds to the string value that is appropriate for your organization. You must replace the last part of the string value with a variable that is appropriate for all users. For example, type a value that resembles the following:
/o=First Organization/ou=Exchange Administrative Group (Internal_Name)/cn=Recipie
In this example, the following information applies to the cn=%'Alias' part of the string value:
a.Click Go.
That info is pulled from http://technet.microsoft.com/en-gb/library/bb288905(EXCHG.80).aspx
and now to avoide any mailflow issue add x500 address on all the users which were migrated, no need to do for the mailboxes that were created in e2k10. follow below article.
http://support.microsoft.com/kb/909271
or do you still have your legacy exchange adminstrative group or it is deleted check through Adsiedit, if it is there then let me know else follwo above things.
Change the LegacyExchangeDN attribute of users from the old administrative group to point to one of the remaining administrative groups. To do this, follow these steps:
a.Download the Admodify.exe tool from http://www.codeplex.com/admodify, and then extract the contents of the .zip file to a folder.
b.Double-click Admodify.exe. If you are prompted to run the program, click Run.
c.In the ADModify.NET dialog box, click Modify Attributes.
d.Under Domain List, click the domain entry that corresponds to the domain in which the affected Exchange server is located. For example, click DC=corp,DC=example,DC=com.
e.Under Domain Controller List, click the fully qualified domain name of the domain controller that hosts the affected Exchange users. For example, click DC-1.corp.example.com.
f.Click to clear the following check boxes:
Groups
Contacts
Public Folders
Show Containers Only
Note:
Do not clear the Users check box.
Click the green arrow button that is beside Domain Controller List.
a.Under Domain Tree List, expand the domain object that is displayed.
b.Click the container in which the affected users are located. For example, click Users.
c.Click Add to List, click Select All, and then click Next.
d.Click the Custom tab, and then click to select the Make a customized attribute modification check box.
e.In the Attribute Name box, type LegacyExchangeDN.
f.In the Attribute Value box, type an entry that corresponds to the string value that is appropriate for your organization. You must replace the last part of the string value with a variable that is appropriate for all users. For example, type a value that resembles the following:
/o=First Organization/ou=Exchange Administrative Group (Internal_Name)/cn=Recipie
In this example, the following information applies to the cn=%'Alias' part of the string value:
a.Click Go.
That info is pulled from http://technet.microsoft.com/en-gb/library/bb288905(EXCHG.80).aspx
and now to avoide any mailflow issue add x500 address on all the users which were migrated, no need to do for the mailboxes that were created in e2k10. follow below article.
http://support.microsoft.com/kb/909271
or do you still have your legacy exchange adminstrative group or it is deleted check through Adsiedit, if it is there then let me know else follwo above things.
ASKER
shreedhar: The mailbox store is currently pointing to the correct public folder database and the default OAB is correct as well.
Narayan_singh: I looked in ADSI Edit and found the legacy admin group under Configuration context. It is no longer in use as far as I know. All mail is being routed by Exchange 2010.
Narayan_singh: I looked in ADSI Edit and found the legacy admin group under Configuration context. It is no longer in use as far as I know. All mail is being routed by Exchange 2010.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Narayan_singh: Will try that tonight. We have scheduled an outage time this evening so I will be doing that then. Will let you know what happens.
ASKER
This did it. No more of those events being logged and everything is working as it should. Thanks a million!
hi,
our exchange organization upgrated from exchange 2007.
under the configuration in adsi.edit there are two Administrative Groups
1- CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
2- CN=First Administrative Group
but both of them have same siteFolderServer attribute with same syntax
Which is our Legacy group.?
and we are getting Event 4030 MSExchange Availability Error:
"Process Microsoft.Exchange.InfoWor
at the Public Folder Management Console I can't add Public Folder on the Replication tab for "SCHEDULE+ FREE BUSY" folder. it is giving security error (is'nt allowed)
how can i fix this.?
our exchange organization upgrated from exchange 2007.
under the configuration in adsi.edit there are two Administrative Groups
1- CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
2- CN=First Administrative Group
but both of them have same siteFolderServer attribute with same syntax
Which is our Legacy group.?
and we are getting Event 4030 MSExchange Availability Error:
"Process Microsoft.Exchange.InfoWor
at the Public Folder Management Console I can't add Public Folder on the Replication tab for "SCHEDULE+ FREE BUSY" folder. it is giving security error (is'nt allowed)
how can i fix this.?
I receive this error when I try the following link
http://technet.microsoft.com/en-gb/library/bb288905(EXCHG.80).aspx
type="Failure" attribute="LegacyExchangeD
http://technet.microsoft.com/en-gb/library/bb288905(EXCHG.80).aspx
type="Failure" attribute="LegacyExchangeD