Followup, but no resolution as yet.

I've been casting about for clues regarding my 3092/MSExchangeIS
Public Folder warnings. What I write about below may well be some
barking up the wrong tree, but I find it suggestive.

I found this article:
   
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26396056.html
which mentions this attribute:
   MSExchOwningPFtree

I fired up ADSIEdit, and took a look at the PF database on our US
E2010 server, and found these entries:
   msExchOwningPFTree
   CN=Public Folders,CN=Folder Hierarchies,CN=US,CN=Administrative
Groups,CN=Example,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=example,DC=com

   msExchOwningServer
   CN=USMAILDB01P,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Example,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=example,DC=com

The "CN=US" from the first attribute is definitely from the Exchange 2003 era.

I then found this blog post:
http://blogs.technet.com/b/bill_long/archive/2010/05/12/fixing-public-folder-directory-objects-that-aren-t-linked-to-the-hierarchy.aspx
and some other murmurings that possibly the initial setup steps didn't
work as expected (setup /PrepareSchema and setup /PrepareAD).

I'm going to open a case with MSFT and see if they can guide me on this.

Kurt


On Wed, Jun 25, 2014 at 9:32 AM, Kurt Buff <[email protected]> wrote:
> All,
>
> We've recently retired our three Exchange 2003 (AU, UK and US) servers
> (Exchange uninstalled and servers shut down) in favor of two Exchange
> 2010 servers (the UK office now doesn't have an Exchange server -
> their mailboxes live on the US server). We had problems with the PFs
> on the UK server, but restored them to the US PF database from a
> backup, using the Lucid8 Digiscope product (which is pretty cool, BTW,
> and pretty darn inexpensive for what it does.)
>
> Prior to decommissioning the E2003 servers, I ran the following
> one-liner to see the state of PF replicas, and it came back clean,
> with no replicas pointing to any E2003 servers (watch the line wrap):
>
>      Get-publicfolder -recurse -resultsize unlimited |
>      Select Name,ParentPath,@{Name=’replicas’;Expression={[string]::join(";",
> ($_.replicas))}} |
>       Export-CSV c:\temp\PFReplicas.csv
>
> Now, on the US E2010 server (and not on the AU E2010 server), I'm
> seeing what's in the subject line, for about a quarter of our PFs.
>
> The main text of the error is:
>
>      Error 1129 occurred while processing a replication event.
>
> The errors are for the following three system folders:
>
> (2-FFFFFFFF0004) NON_IPM_SUBTREE\Events Root
> (5-15) NON_IPM_SUBTREE\schema-root
> (5-11) NON_IPM_SUBTREE\StoreEvents{7F591F3B-8DC1-4997-8785-50576C81BB1C}
>
> plus about 3500 out of about 12500 IPM_SUBTREE PFs. There might be
> more folders with this message, but the eventlog overflows at 20mb in
> about 30 minutes, and I not inclined to re-size it for this problem,
> unless absolutely needed.
>
> The errors might be related to the UK Exchange server with which we
> had PF problems, but AFAICT only some of the problem PFs found in the
> eventlog were on the UK E2003 server - some were only housed on the US
> E2003 server.
>
> I'm going to restart the Exchange services this evening and see if
> that makes a difference, but suspect it won't.
>
> I've been STFW for several hours, and am not seeing anything that will
> let me quell the messages and/or solve the problem. The PFs are in
> use, and need to remain.
>
> Can anyone point me in the right direction on this?
>
> Thanks,
>
> Kurt


Reply via email to