Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

multiple schema-root system folders (public folders)

21 views
Skip to first unread message

Keith W

unread,
Dec 10, 2008, 2:08:40 PM12/10/08
to
How many schema-root folders should I see under system folders in Exchange
Public Folders? We have three instances of this folder, and my impression is
that there should only be one. I'm asking this in regard to troubleshooting
Public Folder replication, which is not happening on one of our Exchange
servers. We see this error event in the offending server's app logs:

Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3079
Date: 12/10/2008
Time: 7:02:10 AM
User: N/A
Computer: <our server>
Description:
Unexpected replication thread error 0xfffffa84 on database "First Storage
Group\Public Folder Store (our server)".

REPL::EcSeek
REPL::EcGetReplicaList
EcUpdateReplState
EcReplStartup
FReplAgent

...immediately followed by this one:

Event Type: Error
Event Source: EXOLEDB
Event Category: Events
Event ID: 112
Date: 12/10/2008
Time: 7:02:10 AM
User: N/A
Computer: <our server>
Description:
Microsoft Exchange OLEDB was unable to register OnSyncSave event for Schema
propagation on MDB startup HRESULT = 0x8000ffff.

I've been unable to find anything on the MSExchangeIS Public Store error
event, but I did find one reference to the EXOLEDB error event that refers
to multiple copies of the schema-root folder and recommends isolating the
one that is good and removing the others. I'd really like to get a second
opinion before I go about removing system folders from Exchange.

Fazal Mohammad Khan (MCT)

unread,
Dec 11, 2008, 3:08:34 AM12/11/08
to
http://support.microsoft.com/kb/826767

--
Regards
Fazal Mohammad Khan
MCSA, MCSE (2003), MCT
Karachi, Pakistan


Keith W

unread,
Dec 11, 2008, 7:49:49 AM12/11/08
to
Thanks. I ran an 'isinteg -s server_name -test replstate' last night and got
an error pointing to a missing index, so I pretty much concluded that we
would need to remove and rebuild the pub1.edb. I also failed to mention that
we are using Exchange 2003. The solution that you reference doesn't mention
the .stm file. Does this also need to be removed, or just the .edb?

In regard to the original question, I renamed the two oldest schema-root
folders and restarted the IS. The EXOLEDB error no longer occurs, so that
question has been answered.


"Fazal Mohammad Khan (MCT)" <faz...@hotmail.com> wrote in message
news:OrC$oe2WJH...@TK2MSFTNGP06.phx.gbl...

Fazal Mohammad Khan (MCT)

unread,
Dec 12, 2008, 1:22:54 AM12/12/08
to
Im not sure about the .stm file
Thus dont wana guide you in a wrong direction :)

--
Regards
Fazal Mohammad Khan
MCSA, MCSE (2003), MCT
Karachi, Pakistan

"Keith W" <n...@this.net> wrote in message
news:796BBAA0-1436-44FC...@microsoft.com...

0 new messages