event 9518 mounting public store

keith w · Joined: 06 Aug 2007 Posts: 6

We've just installed a new Exchange 2003 Std server in our Atlanta office
and we aren't able to mount the Public Folder Store on the new server. A
check of the MDBDATA directory shows that pub1.edb doesn't exist. The mount
fails with the following errors:

The store could not be mounted because the AD information was not replicated
yet. You can either:
- Press Cancel and mount the store later from its context menu or,
- Press Retry to let the Exchange System Manager keep trying to mount the
store for you.

The Microsoft Exchange Information Store service could not find the
specified object.
ID no: c1041722
Exchange System Manager

....and generates MSExchangeIS event 9519 with the following text:

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: 1/25/2007
Time: 10:25:53 AM
User: N/A
Computer: MAIL-ATL
Description:
Error 0x8004010f starting database "First Storage
Group\3e0fddf1-fcf8-49d7-910a-da9a3d2afe82" on the Microsoft Exchange
Information Store.

For more information, click http://www.microsoft.com/contentredirect.asp.
Data:
0000: 4c 6f 6f 6b 20 75 70 20 Look up
0008: 6f 66 20 44 42 20 49 6e of DB In
0010: 66 6f 20 66 61 69 6c 65 fo faile
0018: 64 00 d.

The key line here is "First Storage
Group\3e0fddf1-fcf8-49d7-910a-da9a3d2afe82". This should read "First Storage
Group\Public Folder Store". I looked for this value under the CN=Public
Folder Store(MAIL-ATL) entry in ADSIEdit and it shows up under the homeMDBBL
attribute, but this is also the case for our other three Exchange Servers
that have working Public Folder Stores, so I can't see anything wrong here.
Can I assume this is happening because the pub1.edb file was never created?
Any ideas on how to fix this?

Archived from group: microsoft>public>exchange2000>information>store

Simon Walsh · Joined: 05 Aug 2007 Posts: 25

Pub1.edb & stm were probably never created because the store has never been
mounted.
It sounds like something may have gone wrong in the installation process or
something in AD replication.

Can you confirm that AD repl is working correctly? How about if you use ldp
to check the AD object for the PF store on all your DCs? Is it
3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 on all DCs? or only on the DC in
Atlanta?
If you take properties on the store in ESM are you getting any errors?
You can delete the PF store in Atlanta with ldp or ADSIEdit, wait for AD
replication and create a new PF store to see what happens. Make sure that
the local mailbox store then points to the newly created PF store for the
default PF store setting.

Have a check back through the progress log (C:\Exchange Server Setup
Progress.log) first to see if there was anything strange relating to the PF
store creation

/simon

"keith w" wrote in message @giganews.com...
> We've just installed a new Exchange 2003 Std server in our Atlanta office
> and we aren't able to mount the Public Folder Store on the new server. A
> check of the MDBDATA directory shows that pub1.edb doesn't exist. The
> mount fails with the following errors:
>
> The store could not be mounted because the AD information was not
> replicated yet. You can either:
> - Press Cancel and mount the store later from its context menu or,
> - Press Retry to let the Exchange System Manager keep trying to mount the
> store for you.
>
> The Microsoft Exchange Information Store service could not find the
> specified object.
> ID no: c1041722
> Exchange System Manager
>
>
> ...and generates MSExchangeIS event 9519 with the following text:
>
> Event Type: Error
> Event Source: MSExchangeIS
> Event Category: General
> Event ID: 9519
> Date: 1/25/2007
> Time: 10:25:53 AM
> User: N/A
> Computer: MAIL-ATL
> Description:
> Error 0x8004010f starting database "First Storage
> Group\3e0fddf1-fcf8-49d7-910a-da9a3d2afe82" on the Microsoft Exchange
> Information Store.
>
> For more information, click http://www.microsoft.com/contentredirect.asp.
> Data:
> 0000: 4c 6f 6f 6b 20 75 70 20 Look up
> 0008: 6f 66 20 44 42 20 49 6e of DB In
> 0010: 66 6f 20 66 61 69 6c 65 fo faile
> 0018: 64 00 d.
>
>
> The key line here is "First Storage
> Group\3e0fddf1-fcf8-49d7-910a-da9a3d2afe82". This should read "First
> Storage Group\Public Folder Store". I looked for this value under the
> CN=Public Folder Store(MAIL-ATL) entry in ADSIEdit and it shows up under
> the homeMDBBL attribute, but this is also the case for our other three
> Exchange Servers that have working Public Folder Stores, so I can't see
> anything wrong here. Can I assume this is happening because the pub1.edb
> file was never created? Any ideas on how to fix this?
>
>
>
>

keith w · Joined: 06 Aug 2007 Posts: 6

Thanks, I'll take a look at the logs and let you know what I find.

"Simon Walsh" wrote in message @TK2MSFTNGP02.phx.gbl...
> Pub1.edb & stm were probably never created because the store has never
> been mounted.
> It sounds like something may have gone wrong in the installation process
> or something in AD replication.
>
> Can you confirm that AD repl is working correctly? How about if you use
> ldp to check the AD object for the PF store on all your DCs? Is it
> 3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 on all DCs? or only on the DC in
> Atlanta?
> If you take properties on the store in ESM are you getting any errors?
> You can delete the PF store in Atlanta with ldp or ADSIEdit, wait for AD
> replication and create a new PF store to see what happens. Make sure that
> the local mailbox store then points to the newly created PF store for the
> default PF store setting.
>
> Have a check back through the progress log (C:\Exchange Server Setup
> Progress.log) first to see if there was anything strange relating to the
> PF store creation
>
> /simon
>
>
> "keith w" wrote in message
> @giganews.com...
>> We've just installed a new Exchange 2003 Std server in our Atlanta office
>> and we aren't able to mount the Public Folder Store on the new server. A
>> check of the MDBDATA directory shows that pub1.edb doesn't exist. The
>> mount fails with the following errors:
>>
>> The store could not be mounted because the AD information was not
>> replicated yet. You can either:
>> - Press Cancel and mount the store later from its context menu or,
>> - Press Retry to let the Exchange System Manager keep trying to mount the
>> store for you.
>>
>> The Microsoft Exchange Information Store service could not find the
>> specified object.
>> ID no: c1041722
>> Exchange System Manager
>>
>>
>> ...and generates MSExchangeIS event 9519 with the following text:
>>
>> Event Type: Error
>> Event Source: MSExchangeIS
>> Event Category: General
>> Event ID: 9519
>> Date: 1/25/2007
>> Time: 10:25:53 AM
>> User: N/A
>> Computer: MAIL-ATL
>> Description:
>> Error 0x8004010f starting database "First Storage
>> Group\3e0fddf1-fcf8-49d7-910a-da9a3d2afe82" on the Microsoft Exchange
>> Information Store.
>>
>> For more information, click http://www.microsoft.com/contentredirect.asp.
>> Data:
>> 0000: 4c 6f 6f 6b 20 75 70 20 Look up
>> 0008: 6f 66 20 44 42 20 49 6e of DB In
>> 0010: 66 6f 20 66 61 69 6c 65 fo faile
>> 0018: 64 00 d.
>>
>>
>> The key line here is "First Storage
>> Group\3e0fddf1-fcf8-49d7-910a-da9a3d2afe82". This should read "First
>> Storage Group\Public Folder Store". I looked for this value under the
>> CN=Public Folder Store(MAIL-ATL) entry in ADSIEdit and it shows up under
>> the homeMDBBL attribute, but this is also the case for our other three
>> Exchange Servers that have working Public Folder Stores, so I can't see
>> anything wrong here. Can I assume this is happening because the pub1.edb
>> file was never created? Any ideas on how to fix this?
>>
>>
>>
>>
>
>

keith w · Joined: 06 Aug 2007 Posts: 6

Nothing in the logs that raise any red flags. I tried mounting the store
from one of our other Exchange servers and got the same error with the same
event 9519, same alias 3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 in place of the
'Public Folder Store' value. In ADSIEdit this alias is the same format as
for the 'homeMDBBL' attribute for all of our other Exchange server PF
stores, so I didn't think this was significant. No errors when I view
property sheet for the Public store in ESM.

When you say 'delete the PF store in Atlanta with ldp or ADSIEdit' are you
referring to the CN=Public Folder Store (MAIL-ATL) entry? The full path is
CN=Public Folder Store (MAIL-ATL),CN=First Storage
Group,CN=InformationStore,CN=MAIL-ATL,CN=Servers,CN=,CN=Administrative
Groups,CN=,CN=Microsoft Exchange,CN=Services,CN=Configuration (
and are our Exchange site and organization). Do we need to stop and
start the IS service to do this?

"keith w" wrote in message @giganews.com...
> Thanks, I'll take a look at the logs and let you know what I find.
>
>
> "Simon Walsh" wrote in message
> @TK2MSFTNGP02.phx.gbl...
>> Pub1.edb & stm were probably never created because the store has never
>> been mounted.
>> It sounds like something may have gone wrong in the installation process
>> or something in AD replication.
>>
>> Can you confirm that AD repl is working correctly? How about if you use
>> ldp to check the AD object for the PF store on all your DCs? Is it
>> 3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 on all DCs? or only on the DC in
>> Atlanta?
>> If you take properties on the store in ESM are you getting any errors?
>> You can delete the PF store in Atlanta with ldp or ADSIEdit, wait for AD
>> replication and create a new PF store to see what happens. Make sure that
>> the local mailbox store then points to the newly created PF store for the
>> default PF store setting.
>>
>> Have a check back through the progress log (C:\Exchange Server Setup
>> Progress.log) first to see if there was anything strange relating to the
>> PF store creation
>>
>> /simon
>>

Simon Walsh · Joined: 05 Aug 2007 Posts: 25

Yes that is the correct distinguished name. You should not need to restart
the IS for this.
When you make the deletion you should let it replicate to the entire AD
before creating a new one.
As I mentioned before you will need to make sure that the newlyc created PF
store is the default PF store the Mailbox Store in Atlanta.

/Simon

"keith w" wrote in message @giganews.com...
> Nothing in the logs that raise any red flags. I tried mounting the store
> from one of our other Exchange servers and got the same error with the
> same event 9519, same alias 3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 in place
> of the 'Public Folder Store' value. In ADSIEdit this alias is the same
> format as for the 'homeMDBBL' attribute for all of our other Exchange
> server PF stores, so I didn't think this was significant. No errors when I
> view property sheet for the Public store in ESM.
>
> When you say 'delete the PF store in Atlanta with ldp or ADSIEdit' are you
> referring to the CN=Public Folder Store (MAIL-ATL) entry? The full path is
> CN=Public Folder Store (MAIL-ATL),CN=First Storage
> Group,CN=InformationStore,CN=MAIL-ATL,CN=Servers,CN=,CN=Administrative
> Groups,CN=,CN=Microsoft Exchange,CN=Services,CN=Configuration (
> and are our Exchange site and organization). Do we need to stop and
> start the IS service to do this?
>
>
> "keith w" wrote in message
> @giganews.com...
>> Thanks, I'll take a look at the logs and let you know what I find.
>>
>>
>> "Simon Walsh" wrote in message
>> @TK2MSFTNGP02.phx.gbl...
>>> Pub1.edb & stm were probably never created because the store has never
>>> been mounted.
>>> It sounds like something may have gone wrong in the installation process
>>> or something in AD replication.
>>>
>>> Can you confirm that AD repl is working correctly? How about if you use
>>> ldp to check the AD object for the PF store on all your DCs? Is it
>>> 3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 on all DCs? or only on the DC in
>>> Atlanta?
>>> If you take properties on the store in ESM are you getting any errors?
>>> You can delete the PF store in Atlanta with ldp or ADSIEdit, wait for AD
>>> replication and create a new PF store to see what happens. Make sure
>>> that the local mailbox store then points to the newly created PF store
>>> for the default PF store setting.
>>>
>>> Have a check back through the progress log (C:\Exchange Server Setup
>>> Progress.log) first to see if there was anything strange relating to the
>>> PF store creation
>>>
>>> /simon
>>>
>
>

keith w · Joined: 06 Aug 2007 Posts: 6

After much troubleshooting and hair pulling, we were still unable to resolve
this. However, the situation "resolved" itself, when the domain controller
for the domain the Exchange server was a member of suffered a catastrophic
hardware failure yesterday. Since it was the only domain controller in the
domain, the domain itself was lost. We believe now that this machine was
causing multiple domain replication issues during it's downward slide into
failure, and this is what was causing the public store mounting problem. We
moved the Exchange server into an existing domain, and added the server to
the Exchange Domain Servers group and when the server was rebooted, the
public folder store was able to mount. We still have a number of details to
work out before we'll be able to get the thing into production, mainly
having to do with lost system accounts and such.

"Simon Walsh" wrote in message @TK2MSFTNGP02.phx.gbl...
> Yes that is the correct distinguished name. You should not need to restart
> the IS for this.
> When you make the deletion you should let it replicate to the entire AD
> before creating a new one.
> As I mentioned before you will need to make sure that the newlyc created
> PF store is the default PF store the Mailbox Store in Atlanta.
>
> /Simon
>
> "keith w" wrote in message
> @giganews.com...
>> Nothing in the logs that raise any red flags. I tried mounting the store
>> from one of our other Exchange servers and got the same error with the
>> same event 9519, same alias 3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 in place
>> of the 'Public Folder Store' value. In ADSIEdit this alias is the same
>> format as for the 'homeMDBBL' attribute for all of our other Exchange
>> server PF stores, so I didn't think this was significant. No errors when
>> I view property sheet for the Public store in ESM.
>>
>> When you say 'delete the PF store in Atlanta with ldp or ADSIEdit' are
>> you referring to the CN=Public Folder Store (MAIL-ATL) entry? The full
>> path is CN=Public Folder Store (MAIL-ATL),CN=First Storage
>> Group,CN=InformationStore,CN=MAIL-ATL,CN=Servers,CN=,CN=Administrative
>> Groups,CN=,CN=Microsoft Exchange,CN=Services,CN=Configuration
>> ( and are our Exchange site and organization). Do we need to
>> stop and start the IS service to do this?
>>
>>
>> "keith w" wrote in message
>> @giganews.com...
>>> Thanks, I'll take a look at the logs and let you know what I find.
>>>
>>>
>>> "Simon Walsh" wrote in message
>>> @TK2MSFTNGP02.phx.gbl...
>>>> Pub1.edb & stm were probably never created because the store has never
>>>> been mounted.
>>>> It sounds like something may have gone wrong in the installation
>>>> process or something in AD replication.
>>>>
>>>> Can you confirm that AD repl is working correctly? How about if you use
>>>> ldp to check the AD object for the PF store on all your DCs? Is it
>>>> 3e0fddf1-fcf8-49d7-910a-da9a3d2afe82 on all DCs? or only on the DC in
>>>> Atlanta?
>>>> If you take properties on the store in ESM are you getting any errors?
>>>> You can delete the PF store in Atlanta with ldp or ADSIEdit, wait for
>>>> AD replication and create a new PF store to see what happens. Make sure
>>>> that the local mailbox store then points to the newly created PF store
>>>> for the default PF store setting.
>>>>
>>>> Have a check back through the progress log (C:\Exchange Server Setup
>>>> Progress.log) first to see if there was anything strange relating to
>>>> the PF store creation
>>>>
>>>> /simon
>>>>
>>
>>
>
>

delete public folder store I was testing the creation of public folder stores one day and I ran into a problem of deleting them after I was done. The error message says, ""You cannot delete this public folder store because it contains folder replicas. To avoid data loss, right clic

Informatio Store memory use Hi,, On my Exchange 2000 server, any reason why the Information store is using almost 800MB from 1GB that the server has.

Searching Information Store We may be involved in a litigation where we would need to search all mailboxes for certain keywords. Is there a way to do this natively in Exchange or any third party software we could use?

Restoring information store I am trying to restore the information store after a fresh new installation of Exchange on a Win2K Domain Controller. I have the MDB data folder. If anyone can advise or point me in the right direction. That'd be great. Thanks.

Information Store takes all available RAM Recently moved E2K over to a new Have E2K+SP3 and post-SP3 Rollup installed. The store.exe process starts small (100MB or so) and slowly, but surely, takes more and more RAM until there's only about 30MB left. Once that happens, the SMT