|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Public Folders not Mounting in E2K7We just did a migration from our W2K3 and E2K3 server (named Server2K3) to a brand new W2K8 and E2K7 server (named Server2K8). Everything went fine except an issue that we have now with the legacy Public Folder we had on Server2K3. They are indeed visible under the Exchange Management Console in the Second Storage Group of Server2K8, but I just can't mount them. I get a message saying that the objet "Server2K8\Second Storage Group\Public Folder Database" is corrupted and in a uncoherent state, as well as a warning underneath saying that PublicFolderHierarchy is mandatory. I can do without the PF (only 40 Mb of data) but I can't even delete them, or show their properties. Exchange just won't let me do that. I get an event log entry with Event ID 8197 and an error number 0x80040111 stating that it can't see any valid Public Folder Database on the Exchange server. PowerShell and commands such as : Get-PublicFolder -server YOUR-SERVER-NAME "\" -Recurse -ResultSize:Unlimited Remove-PublicFolder -server YOUR-SERVER-NAME -Recurse -ErrorAction:SilentlyContinue or Get-PublicFolder -Server YOUR-SERVER-NAME "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited Remove-PublicFolder -Server YOUR-SERVER-NAME -Recurse -ErrorAction:SilentlyContinue are not helping since the PF Database is not visible by Exchange or not mounted. The issue in only blocking for Microsoft Outlook 2003 which won't open, and moreover I wish to make the things straight with the PF: either mounted and running, or deleted. Help appreciated Nicolas On Tue, 24 Mar 2009 18:38:21 +0100, "Nicolas Macarez"
<maca***@free.fr> wrote: >We just did a migration from our W2K3 and E2K3 server (named Server2K3) to a For you to see the Public Folders you must have a Public Folder>brand new W2K8 and E2K7 server (named Server2K8). > >Everything went fine except an issue that we have now with the legacy Public >Folder we had on Server2K3. >They are indeed visible under the Exchange Management Console in the Second >Storage Group of Server2K8, but I just can't mount them. database mounted somewhere. >I get a message saying that the objet "Server2K8\Second Storage Group\Public You say you migrated from E2K3 to E2K7 -- how did the Public Folders>Folder Database" is corrupted and in a uncoherent state, as well as a >warning underneath saying that PublicFolderHierarchy is mandatory. move from the E2K3 server to the E2K7 server? --- Rich Matheisen MCSE+I, Exchange MVP Thanks Rich for your reply
I am acting in an emergency context on this one. I did not do the migration myself. I guess the PF were just not taken care of - but there are visible under the Exchange Server 2007 Management Console and set as dismounted. The issue came up when the guy decommissioned the Exchange Server 2003 server. When he uninstalled Exchange 2003 on the old server that's when things went wrong. Do you think that I could just suppress the PF DB entry with ADSIEDIT here : Path to public folder DB is: ADSI Edit --> Configuration --> Services --> Microsot Exchange --> Organisation Name --> Administrative Groups --> Exchange Administrative Group --> Servers --> Server Name --> Information Store -- > Group --> Database. and that things could be OK after that? Is it safe? Regards Nicolas "Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> a écrit dans le message de news: d90js41595msk1cshiies0brangnp5g***@4ax.com...Show quoteHide quote > On Tue, 24 Mar 2009 18:38:21 +0100, "Nicolas Macarez" > <maca***@free.fr> wrote: > >>We just did a migration from our W2K3 and E2K3 server (named Server2K3) to >>a >>brand new W2K8 and E2K7 server (named Server2K8). >> >>Everything went fine except an issue that we have now with the legacy >>Public >>Folder we had on Server2K3. >>They are indeed visible under the Exchange Management Console in the >>Second >>Storage Group of Server2K8, but I just can't mount them. > > For you to see the Public Folders you must have a Public Folder > database mounted somewhere. > >>I get a message saying that the objet "Server2K8\Second Storage >>Group\Public >>Folder Database" is corrupted and in a uncoherent state, as well as a >>warning underneath saying that PublicFolderHierarchy is mandatory. > > You say you migrated from E2K3 to E2K7 -- how did the Public Folders > move from the E2K3 server to the E2K7 server? > --- > Rich Matheisen > MCSE+I, Exchange MVP On Wed, 25 Mar 2009 08:34:48 +0100, "Nicolas Macarez"
<maca***@free.fr> wrote: Show quoteHide quote >Thanks Rich for your reply How many public folder databases do you see in the directory? Is there> >I am acting in an emergency context on this one. I did not do the migration >myself. I guess the PF were just not taken care of - but there are visible >under the Exchange Server 2007 Management Console and set as dismounted. > >The issue came up when the guy decommissioned the Exchange Server 2003 >server. When he uninstalled Exchange 2003 on the old server that's when >things went wrong. > >Do you think that I could just suppress the PF DB entry with ADSIEDIT here : > >Path to public folder DB is: ADSI Edit --> Configuration --> Services --> >Microsot Exchange --> Organisation Name --> Administrative Groups --> >Exchange Administrative Group --> Servers --> Server Name --> Information >Store -- > Group --> Database. > >and that things could be OK after that? Is it safe? one with a suffix of ".stm"? I'm guessing that someone just copied the files from Exchange 2003 to Exchange 2007! If that's true, I'd just rename the public folder database files and then mount the PF store. That'll create a new PF database. It may not solve all your problems, though. --- Rich Matheisen MCSE+I, Exchange MVP "Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> a écrit dans le message de news: 0pfks45tflum4c48frpmpmpiihsps1j***@4ax.com...Show quoteHide quote > On Wed, 25 Mar 2009 08:34:48 +0100, "Nicolas Macarez" Rich,> <maca***@free.fr> wrote: > >>Thanks Rich for your reply >> >>I am acting in an emergency context on this one. I did not do the >>migration >>myself. I guess the PF were just not taken care of - but there are visible >>under the Exchange Server 2007 Management Console and set as dismounted. >> >>The issue came up when the guy decommissioned the Exchange Server 2003 >>server. When he uninstalled Exchange 2003 on the old server that's when >>things went wrong. >> >>Do you think that I could just suppress the PF DB entry with ADSIEDIT here >>: >> >>Path to public folder DB is: ADSI Edit --> Configuration --> Services --> >>Microsot Exchange --> Organisation Name --> Administrative Groups --> >>Exchange Administrative Group --> Servers --> Server Name --> Information >>Store -- > Group --> Database. >> >>and that things could be OK after that? Is it safe? > > How many public folder databases do you see in the directory? Is there > one with a suffix of ".stm"? I'm guessing that someone just copied the > files from Exchange 2003 to Exchange 2007! > > If that's true, I'd just rename the public folder database files and > then mount the PF store. That'll create a new PF database. It may not > solve all your problems, though. > --- > Rich Matheisen > MCSE+I, Exchange MVP In the Exchange Directory, I have those files under E:\Exchange: Mailbox Database.edb pub1.edb pub1.stm pub2.edb temp.edb In fact pub2.edb is the only one that is visible under the Exchange Management Console in the Server Configuration, Mailboxes, Database Management section under Second Storage Group, Public Folder Database with the status Not Mounted. Pub1 is nowhere to be seen under the Exchange Management Console GUI. Regards Nicolas On Wed, 25 Mar 2009 16:57:38 +0100, "Nicolas Macarez"
<maca***@free.fr> wrote: Show quoteHide quote > "Pub1" is an Exchange 2003 public folder database. I don't know why>"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> a écrit dans le >message de news: 0pfks45tflum4c48frpmpmpiihsps1j***@4ax.com... >> On Wed, 25 Mar 2009 08:34:48 +0100, "Nicolas Macarez" >> <maca***@free.fr> wrote: >> >>>Thanks Rich for your reply >>> >>>I am acting in an emergency context on this one. I did not do the >>>migration >>>myself. I guess the PF were just not taken care of - but there are visible >>>under the Exchange Server 2007 Management Console and set as dismounted. >>> >>>The issue came up when the guy decommissioned the Exchange Server 2003 >>>server. When he uninstalled Exchange 2003 on the old server that's when >>>things went wrong. >>> >>>Do you think that I could just suppress the PF DB entry with ADSIEDIT here >>>: >>> >>>Path to public folder DB is: ADSI Edit --> Configuration --> Services --> >>>Microsot Exchange --> Organisation Name --> Administrative Groups --> >>>Exchange Administrative Group --> Servers --> Server Name --> Information >>>Store -- > Group --> Database. >>> >>>and that things could be OK after that? Is it safe? >> >> How many public folder databases do you see in the directory? Is there >> one with a suffix of ".stm"? I'm guessing that someone just copied the >> files from Exchange 2003 to Exchange 2007! >> >> If that's true, I'd just rename the public folder database files and >> then mount the PF store. That'll create a new PF database. It may not >> solve all your problems, though. >> --- >> Rich Matheisen >> MCSE+I, Exchange MVP > >Rich, > >In the Exchange Directory, I have those files under E:\Exchange: > >Mailbox Database.edb >pub1.edb >pub1.stm >pub2.edb >temp.edb > >In fact pub2.edb is the only one that is visible under the Exchange >Management Console in the Server Configuration, Mailboxes, Database >Management section under Second Storage Group, Public Folder Database with >the status Not Mounted. > >Pub1 is nowhere to be seen under the Exchange Management Console GUI. it's on an Exchange 2007 server. If the pub1 file isn't referenced in the EMC that's not a problem. If you don't have a good backup of the public folder databasr to restore your options are a bit limited. Ideally, you'd restore the database and let the log files replay to bring the file back to a current state. Without a backup you could try repairing the database (using eseutil and then isinteg), but that leaves you with a database that nobody really trusts. If you had another server and you had replicas of all the folders on another server you could just delete the file and mount the store, letting replication backfill the empty copy. Or you could just rename pub1.edb to something else, mount the store, and resign yourselt to not having public folder content. --- Rich Matheisen MCSE+I, Exchange MVP "Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> a écrit dans le message de news: 62hls4p7867117l43h2u9rqmi5ni8fj***@4ax.com...Show quoteHide quote > On Wed, 25 Mar 2009 16:57:38 +0100, "Nicolas Macarez" Thanks Rich,> <maca***@free.fr> wrote: > >> >>"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> a écrit dans le >>message de news: 0pfks45tflum4c48frpmpmpiihsps1j***@4ax.com... >>> On Wed, 25 Mar 2009 08:34:48 +0100, "Nicolas Macarez" >>> <maca***@free.fr> wrote: >>> >>>>Thanks Rich for your reply >>>> >>>>I am acting in an emergency context on this one. I did not do the >>>>migration >>>>myself. I guess the PF were just not taken care of - but there are >>>>visible >>>>under the Exchange Server 2007 Management Console and set as dismounted. >>>> >>>>The issue came up when the guy decommissioned the Exchange Server 2003 >>>>server. When he uninstalled Exchange 2003 on the old server that's when >>>>things went wrong. >>>> >>>>Do you think that I could just suppress the PF DB entry with ADSIEDIT >>>>here >>>>: >>>> >>>>Path to public folder DB is: ADSI Edit --> Configuration --> >>>>Services --> >>>>Microsot Exchange --> Organisation Name --> Administrative Groups --> >>>>Exchange Administrative Group --> Servers --> Server Name --> >>>>Information >>>>Store -- > Group --> Database. >>>> >>>>and that things could be OK after that? Is it safe? >>> >>> How many public folder databases do you see in the directory? Is there >>> one with a suffix of ".stm"? I'm guessing that someone just copied the >>> files from Exchange 2003 to Exchange 2007! >>> >>> If that's true, I'd just rename the public folder database files and >>> then mount the PF store. That'll create a new PF database. It may not >>> solve all your problems, though. >>> --- >>> Rich Matheisen >>> MCSE+I, Exchange MVP >> >>Rich, >> >>In the Exchange Directory, I have those files under E:\Exchange: >> >>Mailbox Database.edb >>pub1.edb >>pub1.stm >>pub2.edb >>temp.edb >> >>In fact pub2.edb is the only one that is visible under the Exchange >>Management Console in the Server Configuration, Mailboxes, Database >>Management section under Second Storage Group, Public Folder Database with >>the status Not Mounted. >> >>Pub1 is nowhere to be seen under the Exchange Management Console GUI. > > "Pub1" is an Exchange 2003 public folder database. I don't know why > it's on an Exchange 2007 server. If the pub1 file isn't referenced in > the EMC that's not a problem. > > If you don't have a good backup of the public folder databasr to > restore your options are a bit limited. Ideally, you'd restore the > database and let the log files replay to bring the file back to a > current state. Without a backup you could try repairing the database > (using eseutil and then isinteg), but that leaves you with a database > that nobody really trusts. If you had another server and you had > replicas of all the folders on another server you could just delete > the file and mount the store, letting replication backfill the empty > copy. Or you could just rename pub1.edb to something else, mount the > store, and resign yourselt to not having public folder content. > --- > Rich Matheisen > MCSE+I, Exchange MVP I shall try the option you mentionned in your two last lines. Regards Nicolas |
|||||||||||||||||||||||