From: Neadom Tucker on
Hello I am having lots of Exchange and ESE error in my event logs and
the microsoft site really does not help. Here is the error:

ExchangeServer_SEVENTS001 (5124) ExchangeServer_SEVENTS001: Database
recovery failed with error -1216 because it encountered references to
a database, 'C:\Program Files\Exchsrvr
\ExchangeServer_SEVENTS001\ExchangeServer_SEVENTS001.edb', which is no
longer present. The database was not brought to a Clean Shutdown state
before it was removed (or possibly moved or renamed). The database
engine will not permit recovery to complete for this instance until
the missing database is re-instated. If the database is truly no
longer available and no longer required, procedures for recovering
from this error are available in the Microsoft Knowledge Base or by
following the "more information" link at the bottom of this message.
For more information, click http://www.microsoft.com/contentredirect.asp.

But the EDB file is there. What do I do?

Neadom Tucker

From: "Rudi Dollenberg" vrudid on
Hi

Have you looked at KB823168?
http://support.microsoft.com/kb/823168/en-us

I would suggest checking the log files to make sure that they are not
corrupt KB248122 http://support.microsoft.com/kb/248122/en-us

have you run a repair or defrag on the database? If you have run either of
these and left the log files in the log files folder you will get this
error.

If you cannot replay the logs into the database correctly to bring them back
up you may have to do a hard repair on the database.


"Neadom Tucker" <neadom(a)kotoritechnologies.com> wrote in message
news:1173960766.998574.54740(a)d57g2000hsg.googlegroups.com...
> Hello I am having lots of Exchange and ESE error in my event logs and
> the microsoft site really does not help. Here is the error:
>
> ExchangeServer_SEVENTS001 (5124) ExchangeServer_SEVENTS001: Database
> recovery failed with error -1216 because it encountered references to
> a database, 'C:\Program Files\Exchsrvr
> \ExchangeServer_SEVENTS001\ExchangeServer_SEVENTS001.edb', which is no
> longer present. The database was not brought to a Clean Shutdown state
> before it was removed (or possibly moved or renamed). The database
> engine will not permit recovery to complete for this instance until
> the missing database is re-instated. If the database is truly no
> longer available and no longer required, procedures for recovering
> from this error are available in the Microsoft Knowledge Base or by
> following the "more information" link at the bottom of this message.
> For more information, click http://www.microsoft.com/contentredirect.asp.
>
> But the EDB file is there. What do I do?
>
> Neadom Tucker
>


From: Neadom Tucker on
On Mar 15, 11:10 am, "Rudi Dollenberg" <vrudid@ gmail.com> wrote:
> Hi
>
> Have you looked at KB823168?http://support.microsoft.com/kb/823168/en-us
>
> I would suggest checking the log files to make sure that they are not
> corrupt KB248122http://support.microsoft.com/kb/248122/en-us
>
> have you run a repair or defrag on the database? If you have run either of
> these and left the log files in the log files folder you will get this
> error.
>
> If you cannot replay the logs into the database correctly to bring them back
> up you may have to do a hard repair on the database.
>
> "NeadomTucker" <nea...(a)kotoritechnologies.com> wrote in message
>
> news:1173960766.998574.54740(a)d57g2000hsg.googlegroups.com...
>
>
>
> > Hello I am having lots of Exchange and ESE error in my event logs and
> > the microsoft site really does not help. Here is the error:
>
> > ExchangeServer_SEVENTS001 (5124) ExchangeServer_SEVENTS001: Database
> > recovery failed with error -1216 because it encountered references to
> > a database, 'C:\Program Files\Exchsrvr
> > \ExchangeServer_SEVENTS001\ExchangeServer_SEVENTS001.edb', which is no
> > longer present. The database was not brought to a Clean Shutdown state
> > before it was removed (or possibly moved or renamed). The database
> > engine will not permit recovery to complete for this instance until
> > the missing database is re-instated. If the database is truly no
> > longer available and no longer required, procedures for recovering
> > from this error are available in the Microsoft Knowledge Base or by
> > following the "more information" link at the bottom of this message.
> > For more information, clickhttp://www.microsoft.com/contentredirect.asp.
>
> > But the EDB file is there. What do I do?
>
> >NeadomTucker- Hide quoted text -
>
> - Show quoted text -

I have not done anything though. I ran the Troubleshooting Assistant
to view the exchange logs... because tha is the only way I know how.
I see where the database is trying to be defragmented. I am not doing
this. I run a Disk Defragementation monthly on the server. I would
not think that is the same. Is this something that is happening
automatically? Not to sound stupid but how do I find the log file? I
go under: C:\Program Files\Exchsrvr and I see a folder or something
that says sevents001.log is that what I am looking for. Also when I
type in eseutil /ml sevents001.log it tells me that the command
eseutil is not recognized.

Thanks for your help!
Neadom Tucker

From: Neadom Tucker on
On Mar 15, 2:46 pm, "Neadom Tucker" <nea...(a)kotoritechnologies.com>
wrote:
> On Mar 15, 11:10 am, "Rudi Dollenberg" <vrudid@ gmail.com> wrote:
>
>
>
>
>
> > Hi
>
> > Have you looked at KB823168?http://support.microsoft.com/kb/823168/en-us
>
> > I would suggest checking the log files to make sure that they are not
> > corrupt KB248122http://support.microsoft.com/kb/248122/en-us
>
> > have you run a repair or defrag on the database? If you have run either of
> > these and left the log files in the log files folder you will get this
> > error.
>
> > If you cannot replay the logs into the database correctly to bring them back
> > up you may have to do a hard repair on the database.
>
> > "NeadomTucker" <nea...(a)kotoritechnologies.com> wrote in message
>
> >news:1173960766.998574.54740(a)d57g2000hsg.googlegroups.com...
>
> > > Hello I am having lots of Exchange and ESE error in my event logs and
> > > the microsoft site really does not help. Here is the error:
>
> > > ExchangeServer_SEVENTS001 (5124) ExchangeServer_SEVENTS001: Database
> > > recovery failed with error -1216 because it encountered references to
> > > a database, 'C:\Program Files\Exchsrvr
> > > \ExchangeServer_SEVENTS001\ExchangeServer_SEVENTS001.edb', which is no
> > > longer present. The database was not brought to a Clean Shutdown state
> > > before it was removed (or possibly moved or renamed). The database
> > > engine will not permit recovery to complete for this instance until
> > > the missing database is re-instated. If the database is truly no
> > > longer available and no longer required, procedures for recovering
> > > from this error are available in the Microsoft Knowledge Base or by
> > > following the "more information" link at the bottom of this message.
> > > For more information, clickhttp://www.microsoft.com/contentredirect.asp.
>
> > > But the EDB file is there. What do I do?
>
> > >NeadomTucker- Hide quoted text -
>
> > - Show quoted text -
>
> I have not done anything though. I ran the Troubleshooting Assistant
> to view the exchange logs... because tha is the only way I know how.
> I see where the database is trying to be defragmented. I am not doing
> this. I run a Disk Defragementation monthly on the server. I would
> not think that is the same. Is this something that is happening
> automatically? Not to sound stupid but how do I find the log file? I
> go under: C:\Program Files\Exchsrvr and I see a folder or something
> that says sevents001.log is that what I am looking for. Also when I
> type in eseutil /ml sevents001.log it tells me that the command
> eseutil is not recognized.
>
> Thanks for your help!
> Neadom Tucker- Hide quoted text -
>
> - Show quoted text -

I am getting these Errors in the Event Logs:

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 494
Date: 3/15/2007
Time: 12:26:26 AM
User: N/A
Computer: SEVENTS001
Description:
ExchangeServer_SEVENTS001 (5124) ExchangeServer_SEVENTS001: Database
recovery failed with error -1216 because it encountered references to
a database, 'C:\Program Files\Exchsrvr
\ExchangeServer_SEVENTS001\ExchangeServer_SEVENTS001.edb', which is no
longer present. The database was not brought to a Clean Shutdown state
before it was removed (or possibly moved or renamed). The database
engine will not permit recovery to complete for this instance until
the missing database is re-instated. If the database is truly no
longer available and no longer required, procedures for recovering
from this error are available in the Microsoft Knowledge Base or by
following the "more information" link at the bottom of this message.

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date: 3/15/2007
Time: 12:26:26 AM
User: N/A
Computer: SEVENTS001
Description:
ExchangeServer_SEVENTS001 (5124) ExchangeServer_SEVENTS001: Database
recovery/restore failed with unexpected error -1216.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error
Event Source: Microsoft Search
Event Category: Gatherer
Event ID: 3014
Date: 3/15/2007
Time: 12:26:30 AM
User: N/A
Computer: SEVENTS001
Description:
An exception occurred. ID: 15. This is an internal error. Reproduce
the error with the debugger attached and enable exceptions, then
contact PSS. One of the components loaded in your system is bad. You
may be able to avoid the problem by recreating the catalog.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Microsoft Search
Event Category: Indexer
Event ID: 7010
Date: 3/15/2007
Time: 12:26:26 AM
User: N/A
Computer: SEVENTS001
Description:
The project <ExchangeServer_SEVENTS001 priv067FB8B4> cannot be
initialized. Error: 8004111e - The Indexer failed to update or access
information because of a database error. Stop and restart the Search
service. If errors continue, reset the catalog and rebuild the
index. In some cases, it may be necessary to delete and recreate the
catalog. .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Microsoft Search
Event Category: Indexer
Event ID: 7039
Date: 3/15/2007
Time: 12:26:26 AM
User: N/A
Computer: SEVENTS001
Description:
The Content Index for project <ExchangeServer_SEVENTS001 priv067FB8B4>
cannot be loaded. Error: 8004111e - The Indexer failed to update or
access information because of a database error. Stop and restart the
Search service. If errors continue, reset the catalog and rebuild the
index. In some cases, it may be necessary to delete and recreate the
catalog. .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Microsoft Search
Event Category: Indexer
Event ID: 7037
Date: 3/15/2007
Time: 12:26:26 AM
User: N/A
Computer: SEVENTS001
Description:
The Property Store <C:\Program Files\Exchsrvr
\ExchangeServer_SEVENTS001\Projects\priv067FB8B4\Build\Indexer\NlFiles
\> failed to initialize. Error: 8004111e - The Indexer failed to
update or access information because of a database error. Stop and
restart the Search service. If errors continue, reset the catalog and
rebuild the index. In some cases, it may be necessary to delete and
recreate the catalog. .

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Microsoft Search
Event Category: Search Service
Event ID: 9000
Date: 3/15/2007
Time: 12:26:26 AM
User: N/A
Computer: SEVENTS001
Description:
The Microsoft Search service is unable to open the Jet property
store. Error: |­ªÝ3Æw.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Totally Lost on this one.

Neadom

From: "Rudi Dollenberg" vrudid on
Hi.

If you go into the properties of the storage group in exchange system
manager you will see the path to the Transaction logs, you have to run the
eseutil command from the C:\Program Files\Exchsrvr\bin folder it should look
something like this eseutil /ml "Transaction log path\*.log"

I suggest you run an eseutil /mh to check if the database is in a dirty
shutdown state. have you tried replaying the logs into the database?



"Neadom Tucker" <neadom(a)kotoritechnologies.com> wrote in message
news:1173984394.944148.115270(a)d57g2000hsg.googlegroups.com...
> On Mar 15, 11:10 am, "Rudi Dollenberg" <vrudid@ gmail.com> wrote:
>> Hi
>>
>> Have you looked at KB823168?http://support.microsoft.com/kb/823168/en-us
>>
>> I would suggest checking the log files to make sure that they are not
>> corrupt KB248122http://support.microsoft.com/kb/248122/en-us
>>
>> have you run a repair or defrag on the database? If you have run either
>> of
>> these and left the log files in the log files folder you will get this
>> error.
>>
>> If you cannot replay the logs into the database correctly to bring them
>> back
>> up you may have to do a hard repair on the database.
>>
>> "NeadomTucker" <nea...(a)kotoritechnologies.com> wrote in message
>>
>> news:1173960766.998574.54740(a)d57g2000hsg.googlegroups.com...
>>
>>
>>
>> > Hello I am having lots of Exchange and ESE error in my event logs and
>> > the microsoft site really does not help. Here is the error:
>>
>> > ExchangeServer_SEVENTS001 (5124) ExchangeServer_SEVENTS001: Database
>> > recovery failed with error -1216 because it encountered references to
>> > a database, 'C:\Program Files\Exchsrvr
>> > \ExchangeServer_SEVENTS001\ExchangeServer_SEVENTS001.edb', which is no
>> > longer present. The database was not brought to a Clean Shutdown state
>> > before it was removed (or possibly moved or renamed). The database
>> > engine will not permit recovery to complete for this instance until
>> > the missing database is re-instated. If the database is truly no
>> > longer available and no longer required, procedures for recovering
>> > from this error are available in the Microsoft Knowledge Base or by
>> > following the "more information" link at the bottom of this message.
>> > For more information,
>> > clickhttp://www.microsoft.com/contentredirect.asp.
>>
>> > But the EDB file is there. What do I do?
>>
>> >NeadomTucker- Hide quoted text -
>>
>> - Show quoted text -
>
> I have not done anything though. I ran the Troubleshooting Assistant
> to view the exchange logs... because tha is the only way I know how.
> I see where the database is trying to be defragmented. I am not doing
> this. I run a Disk Defragementation monthly on the server. I would
> not think that is the same. Is this something that is happening
> automatically? Not to sound stupid but how do I find the log file? I
> go under: C:\Program Files\Exchsrvr and I see a folder or something
> that says sevents001.log is that what I am looking for. Also when I
> type in eseutil /ml sevents001.log it tells me that the command
> eseutil is not recognized.
>
> Thanks for your help!
> Neadom Tucker
>


 |  Next  |  Last
Pages: 1 2
Prev: Outlook Web Access
Next: One database not backing up