|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Free/Busy InformationDear all
I have migrated an Exchange Server from 2000 to 2007 on a different server. Since then I am getting the following error in my eventlog: Event ID: 8207 Source: MSExchangeFBPublish Type: Error Description: Error updating public folders with free-busy information on virtual machine <server name>. The error number is 0x8004010f I have tried my google articles about it but nothing helped. Does anyone have a solution for this? The old server is still available if this helps. Best regards Chris Exchange 2007 SP1? Did you flip the switch to allow public
folders (system folders) when you built the Server? Nikki "Jancso Christian" <JancsoChrist***@discussions.microsoft.com> wrote in I have migrated an Exchange Server from 2000 to 2007 on a different server.message news:A10090DF-9766-4C59-8E95-8F751D7F9AC1@microsoft.com... Dear all Since then I am getting the following error in my eventlog: Event ID: 8207 Source: MSExchangeFBPublish Type: Error Description: Error updating public folders with free-busy information on virtual machine <server name>. The error number is 0x8004010f I have tried my google articles about it but nothing helped. Does anyone have a solution for this? The old server is still available if this helps. Best regards Chris Just to add, it was the question about allowing Outlook 2003 and
below clients... Nikki "Nikki Peterson" <SkippyLetter***@hotmail.com> wrote in message Exchange 2007 SP1? Did you flip the switch to allow publicnews:eQmW1kU3JHA.1420@TK2MSFTNGP04.phx.gbl... folders (system folders) when you built the Server? Nikki "Jancso Christian" <JancsoChrist***@discussions.microsoft.com> wrote in I have migrated an Exchange Server from 2000 to 2007 on a different server.message news:A10090DF-9766-4C59-8E95-8F751D7F9AC1@microsoft.com... Dear all Since then I am getting the following error in my eventlog: Event ID: 8207 Source: MSExchangeFBPublish Type: Error Description: Error updating public folders with free-busy information on virtual machine <server name>. The error number is 0x8004010f I have tried my google articles about it but nothing helped. Does anyone have a solution for this? The old server is still available if this helps. Best regards Chris Thank you Nikki for your reply.
Yes it is Exchange SP1 but the other question I don't know to be honest. Can I check this somewhere? Best regards Chris Show quoteHide quote "Nikki Peterson" wrote: > Just to add, it was the question about allowing Outlook 2003 and > below clients... > > Nikki > > "Nikki Peterson" <SkippyLetter***@hotmail.com> wrote in message > news:eQmW1kU3JHA.1420@TK2MSFTNGP04.phx.gbl... > Exchange 2007 SP1? Did you flip the switch to allow public > folders (system folders) when you built the Server? > > Nikki > > "Jancso Christian" <JancsoChrist***@discussions.microsoft.com> wrote in > message news:A10090DF-9766-4C59-8E95-8F751D7F9AC1@microsoft.com... > Dear all > > I have migrated an Exchange Server from 2000 to 2007 on a different server. > Since then I am getting the following error in my eventlog: > > Event ID: 8207 > Source: MSExchangeFBPublish > Type: Error > Description: Error updating public folders with free-busy information on > virtual machine <server name>. The error number is 0x8004010f > > I have tried my google articles about it but nothing helped. > Does anyone have a solution for this? The old server is still available if > this helps. > > Best regards > Chris > > Jancso Christian wrote:
> Thank you Nikki for your reply. (Gosh, what's up with top-posting in this group?)> > Yes it is Exchange SP1 but the other question I don't know to be honest. Can > I check this somewhere? > > Best regards > Chris Anyway, Microsoft in its infinite wisdom (and in their desire to sell you on SharePoint) decided that PublicFolders in Exchange 2007 are only manageable via PowerShell. Google for the cmdlet to check/set the PublicFolders in Exchange 2007. Also, you can fire Outlook and check whether it sees the PublicFolders (use the "Folders" icon to open the "Folders" pane)... I think Outlook 2003 *requieres* the PublicFolders to exist, so if you can connect to Exchange 2007 using Outlook via MAPI protocol, then you have the PublicFolders in place. Show quoteHide quote > > "Nikki Peterson" wrote: > > >>Just to add, it was the question about allowing Outlook 2003 and >>below clients... >> >>Nikki >> >>"Nikki Peterson" <SkippyLetter***@hotmail.com> wrote in message >>news:eQmW1kU3JHA.1420@TK2MSFTNGP04.phx.gbl... >>Exchange 2007 SP1? Did you flip the switch to allow public >>folders (system folders) when you built the Server? >> >>Nikki >> >>"Jancso Christian" <JancsoChrist***@discussions.microsoft.com> wrote in >>message news:A10090DF-9766-4C59-8E95-8F751D7F9AC1@microsoft.com... >>Dear all >> >>I have migrated an Exchange Server from 2000 to 2007 on a different server. >>Since then I am getting the following error in my eventlog: >> >>Event ID: 8207 >>Source: MSExchangeFBPublish >>Type: Error >>Description: Error updating public folders with free-busy information on >>virtual machine <server name>. The error number is 0x8004010f >> >>I have tried my google articles about it but nothing helped. >>Does anyone have a solution for this? The old server is still available if >>this helps. >> >>Best regards >>Chris >> >> Pepe wrote:
> so if you can connect to Exchange 2007 using Outlook via MAPI Should say "using Outlook 2003 via MAPI"...> protocol, then you have the PublicFolders in place. INFO: Exchange 2007 Mailbox and Public Folder Database
The Public Folder database is created so that you can replicate any Public Folder data stored on your legacy Exchange servers to Exchange 2007. Even though you don’t use Public Folders to store data in your environment, there’s one other reason why you might want to keep the Public Folder database mounted on your Exchange 2007 Server. As some of you may already know, Exchange 2007 no longer uses a Public Folder (or more specifically a System Folder named SCHEDULE+ FREE BUSY in your Public Folder hierarchy) to store free/busy information for the mailbox users in the organization. Instead free/busy information is stored directly in each user’s mailbox, and retrieved using a new web-based service called the Availability service. The advantage of this new approach is that there no longer are any 15 minute delays when free/busy time for a user is updated. Instead the update will happen instantly. So why would I want to keep the Public Folder database on my Exchange 2007 server, if free/busy information is retrieved using this new method? Well if you still have legacy Outlook clients (that is Outlook 2003 and earlier versions) running in your organization, these clients still need to use Public Folder method to retrieve free/busy information, since only Outlook 2007 supports the new Availability service. If you don’t use Public Folders to store data and only have Outlook 2007 clients deployed in your organization, you can safely remove the Public Folder database, as you don’t have anything to use it for in that case. http://msexchangeteam.com Nikki "Pepe" <p***@naleco.com> wrote in message Should say "using Outlook 2003 via MAPI"...news:4a1c693e$1@news.x-privat.org... Pepe wrote: > so if you can connect to Exchange 2007 using Outlook via MAPI > protocol, then you have the PublicFolders in place. Thank you for your replies.
I have found the solution for my problem. I had to create a public folder first administrative group on my new server. Now the error went away and the users are able to see the free/busy information. Best, Chris Show quoteHide quote "Nikki Peterson" wrote: > INFO: Exchange 2007 Mailbox and Public Folder Database > The Public Folder database is created so that you can replicate any Public > Folder data stored on your legacy Exchange servers to Exchange 2007. Even > though you don’t use Public Folders to store data in your environment, there’s > one other reason why you might want to keep the Public Folder database > mounted on your Exchange 2007 Server. As some of you may already know, > Exchange 2007 no longer uses a Public Folder (or more specifically a System > Folder named SCHEDULE+ FREE BUSY in your Public Folder hierarchy) to store > free/busy information for the mailbox users in the organization. Instead > free/busy information is stored directly in each user’s mailbox, and > retrieved using a new web-based service called the Availability service. The > advantage of this new approach is that there no longer are any 15 minute > delays when free/busy time for a user is updated. Instead the update will > happen instantly. So why would I want to keep the Public Folder database on > my Exchange 2007 server, if free/busy information is retrieved using this > new method? Well if you still have legacy Outlook clients (that is Outlook > 2003 and earlier versions) running in your organization, these clients still > need to use Public Folder method to retrieve free/busy information, since > only Outlook 2007 supports the new Availability service. > > If you don’t use Public Folders to store data and only have Outlook 2007 > clients deployed in your organization, you can safely remove the Public > Folder database, as you don’t have anything to use it for in that case. > > http://msexchangeteam.com > > Nikki > > "Pepe" <p***@naleco.com> wrote in message > news:4a1c693e$1@news.x-privat.org... > Pepe wrote: > > > so if you can connect to Exchange 2007 using Outlook via MAPI > > protocol, then you have the PublicFolders in place. > > Should say "using Outlook 2003 via MAPI"... > > Nice! Thanks for sharing your solution.
Nikki "Jancso Christian" <JancsoChrist***@discussions.microsoft.com> wrote in Thank you for your replies.message news:54E7CB74-81ED-40BE-B82C-DAEDCF8D6AC3@microsoft.com... I have found the solution for my problem. I had to create a public folder first administrative group on my new server. Now the error went away and the users are able to see the free/busy information. Best, Chris Show quoteHide quote "Nikki Peterson" wrote: > INFO: Exchange 2007 Mailbox and Public Folder Database > The Public Folder database is created so that you can replicate any Public > Folder data stored on your legacy Exchange servers to Exchange 2007. Even > though you don’t use Public Folders to store data in your environment, > there’s > one other reason why you might want to keep the Public Folder database > mounted on your Exchange 2007 Server. As some of you may already know, > Exchange 2007 no longer uses a Public Folder (or more specifically a > System > Folder named SCHEDULE+ FREE BUSY in your Public Folder hierarchy) to store > free/busy information for the mailbox users in the organization. Instead > free/busy information is stored directly in each user’s mailbox, and > retrieved using a new web-based service called the Availability service. > The > advantage of this new approach is that there no longer are any 15 minute > delays when free/busy time for a user is updated. Instead the update will > happen instantly. So why would I want to keep the Public Folder database > on > my Exchange 2007 server, if free/busy information is retrieved using this > new method? Well if you still have legacy Outlook clients (that is Outlook > 2003 and earlier versions) running in your organization, these clients > still > need to use Public Folder method to retrieve free/busy information, since > only Outlook 2007 supports the new Availability service. > > If you don’t use Public Folders to store data and only have Outlook 2007 > clients deployed in your organization, you can safely remove the Public > Folder database, as you don’t have anything to use it for in that case. > > http://msexchangeteam.com > > Nikki > > "Pepe" <p***@naleco.com> wrote in message > news:4a1c693e$1@news.x-privat.org... > Pepe wrote: > > > so if you can connect to Exchange 2007 using Outlook via MAPI > > protocol, then you have the PublicFolders in place. > > Should say "using Outlook 2003 via MAPI"... > >
Unable to email domain, no MX record but A record available
SPF Records won't help us to prevent spam mails Very Strange Email/Connection Issue What antispam solution? problem using updateItem() in Exchange Web Services sending spam exchange 2003 internet configuration Multiple Exch2007 DR and HA questions Subject: Ntbackup of the Information Store: 0 files seem to be ver Exchange self-signed certificate |
|||||||||||||||||||||||