| Author |
Message |
Chris Guimbellot
Guest
|
 Posted:
Thu Nov 03, 2005 1:50 pm Post subject:
Server Sporadically Shutting Down |
|
|
Hello,
SBS2K, Win2K & XP clients.
For the past few days, my server has been experiencing problems. The other
day, I received the following error:
"LSASS.EXE - System Error, security accounts manager initialization failed
because of the following error: Directory Services cannot start. Error
status 0xc00002e1.
Please click OK to shutdown this system and reboot into directory services
restore mode, check the event log for more detailed information. "
With no other options, I called Microsoft PSS. We worked on the server a
little while. In essence, he performed the steps in KB258062. To do this, I
had to reinstall the OS on a different drive just to be able to log in.
Anyway, he mentioned to me that the System State database may be corrupt
still. I also read that in the article.
Later that day, and one in a while for the days leading up to that day, my
Microsoft Exchange Information Store service would just stop. I saw two
events in the Application log that read as follows:
EventID: 474
Source: ESE
Category: Database Page Cache
Description:
Information Store (4508) The database page read from the file
"D:\Exchange\priv1.edb" at offset 5657198592 (0x0000000151320000) for 4096
(0x00001000) bytes failed verification due to a page checksum mismatch. The
expected checksum was 1001692875 (0x3bb49ecb) and the actual checksum was
984915659 (0x3ab49ecb). The read operation will fail with error -1018
(0xfffffc06). If this condition persists then please restore the database
from a previous backup.
EventID: 705
Source: ESE
Category: Online Defragmentation
Description:
Information Store (4508) Online defragmentation of database
'D:\Exchange\priv1.edb' terminated prematurely after encountering unexpected
error -1018. The next time online defragmentation is started on this
database, it will resume from the point of interruption.
So when I come in today, the server had shut down and was performing a
memory dump when I walked in. When I rebooted, the server came up correctly.
I reviewed the logs, and could find nothing that triggered the shutdown.
I guess what I am wondering is where do I begin here? It looks to me like
System State and my Exchange DB are corrupt. Are these problems related? I
know that you can check the memory dump to see what types of problems may
have caused the shutdown, but I am not sure how to do it. I think this all
may stem from some hardware issue, but how would I go about verifying that.
Any ideas would be most appreciated considering that I have never had all
this happen before and I would love to not have to buy and set up a new
server. Thanks,
Chris |
|
| Back to top |
|
 |
Dave Nickason [SBS MVP]
Guest
|
| Posted:
Thu Nov 03, 2005 5:51 pm Post subject:
Re: Server Sporadically Shutting Down |
|
|
Two comments, Chris:
- since you have opened a PSS ticket, they should stick with you until your
problem is solved. The advice of a dedicated support rep focusing only on
your issue should hopefully be better than anything you'll get in a
newsgroup.
- without researching the specific errors you posted, I wonder if this could
be hard drive related. I'd consider running a chkdsk /f just to see what
the results look like. I do know from experience that Exchange database
corruption can be directly related to drive and/or controller issues. You
may even have controller or drive issues logged in your system log, although
I'm guessing you've already checked your logs.
"Chris Guimbellot" <cguimbellot@FORGETSPAM.hifranchise.com> wrote in message
news:%23tZZQ1H4FHA.700@TK2MSFTNGP15.phx.gbl...
| Quote: | Hello,
SBS2K, Win2K & XP clients.
For the past few days, my server has been experiencing problems. The other
day, I received the following error:
"LSASS.EXE - System Error, security accounts manager initialization failed
because of the following error: Directory Services cannot start. Error
status 0xc00002e1.
Please click OK to shutdown this system and reboot into directory services
restore mode, check the event log for more detailed information. "
With no other options, I called Microsoft PSS. We worked on the server a
little while. In essence, he performed the steps in KB258062. To do this,
I had to reinstall the OS on a different drive just to be able to log in.
Anyway, he mentioned to me that the System State database may be corrupt
still. I also read that in the article.
Later that day, and one in a while for the days leading up to that day, my
Microsoft Exchange Information Store service would just stop. I saw two
events in the Application log that read as follows:
EventID: 474
Source: ESE
Category: Database Page Cache
Description:
Information Store (4508) The database page read from the file
"D:\Exchange\priv1.edb" at offset 5657198592 (0x0000000151320000) for 4096
(0x00001000) bytes failed verification due to a page checksum mismatch.
The expected checksum was 1001692875 (0x3bb49ecb) and the actual checksum
was 984915659 (0x3ab49ecb). The read operation will fail with error -1018
(0xfffffc06). If this condition persists then please restore the database
from a previous backup.
EventID: 705
Source: ESE
Category: Online Defragmentation
Description:
Information Store (4508) Online defragmentation of database
'D:\Exchange\priv1.edb' terminated prematurely after encountering
unexpected error -1018. The next time online defragmentation is started on
this database, it will resume from the point of interruption.
So when I come in today, the server had shut down and was performing a
memory dump when I walked in. When I rebooted, the server came up
correctly. I reviewed the logs, and could find nothing that triggered the
shutdown.
I guess what I am wondering is where do I begin here? It looks to me like
System State and my Exchange DB are corrupt. Are these problems related? I
know that you can check the memory dump to see what types of problems may
have caused the shutdown, but I am not sure how to do it. I think this all
may stem from some hardware issue, but how would I go about verifying
that. Any ideas would be most appreciated considering that I have never
had all this happen before and I would love to not have to buy and set up
a new server. Thanks,
Chris
|
|
|
| Back to top |
|
|
MoiToo
Guest
|
| Posted:
Sat Nov 05, 2005 1:50 pm Post subject:
Re: Server Sporadically Shutting Down |
|
|
I would be suspecting drive problems. I would be running diagnostic
software on the server out of hours, to determine the probable cause. If
you are running hardware RAID, what does the controller software report? I
would bet lots of money you have some dead hardware!
"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:O4tQGtJ4FHA.820@tk2msftngp13.phx.gbl...
| Quote: | Two comments, Chris:
- since you have opened a PSS ticket, they should stick with you until
your problem is solved. The advice of a dedicated support rep focusing
only on your issue should hopefully be better than anything you'll get in
a newsgroup.
- without researching the specific errors you posted, I wonder if this
could be hard drive related. I'd consider running a chkdsk /f just to see
what the results look like. I do know from experience that Exchange
database corruption can be directly related to drive and/or controller
issues. You may even have controller or drive issues logged in your
system log, although I'm guessing you've already checked your logs.
"Chris Guimbellot" <cguimbellot@FORGETSPAM.hifranchise.com> wrote in
message news:%23tZZQ1H4FHA.700@TK2MSFTNGP15.phx.gbl...
Hello,
SBS2K, Win2K & XP clients.
For the past few days, my server has been experiencing problems. The
other day, I received the following error:
"LSASS.EXE - System Error, security accounts manager initialization
failed because of the following error: Directory Services cannot start.
Error status 0xc00002e1.
Please click OK to shutdown this system and reboot into directory
services restore mode, check the event log for more detailed information.
"
With no other options, I called Microsoft PSS. We worked on the server a
little while. In essence, he performed the steps in KB258062. To do this,
I had to reinstall the OS on a different drive just to be able to log in.
Anyway, he mentioned to me that the System State database may be corrupt
still. I also read that in the article.
Later that day, and one in a while for the days leading up to that day,
my Microsoft Exchange Information Store service would just stop. I saw
two events in the Application log that read as follows:
EventID: 474
Source: ESE
Category: Database Page Cache
Description:
Information Store (4508) The database page read from the file
"D:\Exchange\priv1.edb" at offset 5657198592 (0x0000000151320000) for
4096 (0x00001000) bytes failed verification due to a page checksum
mismatch. The expected checksum was 1001692875 (0x3bb49ecb) and the
actual checksum was 984915659 (0x3ab49ecb). The read operation will fail
with error -1018 (0xfffffc06). If this condition persists then please
restore the database from a previous backup.
EventID: 705
Source: ESE
Category: Online Defragmentation
Description:
Information Store (4508) Online defragmentation of database
'D:\Exchange\priv1.edb' terminated prematurely after encountering
unexpected error -1018. The next time online defragmentation is started
on this database, it will resume from the point of interruption.
So when I come in today, the server had shut down and was performing a
memory dump when I walked in. When I rebooted, the server came up
correctly. I reviewed the logs, and could find nothing that triggered the
shutdown.
I guess what I am wondering is where do I begin here? It looks to me like
System State and my Exchange DB are corrupt. Are these problems related?
I know that you can check the memory dump to see what types of problems
may have caused the shutdown, but I am not sure how to do it. I think
this all may stem from some hardware issue, but how would I go about
verifying that. Any ideas would be most appreciated considering that I
have never had all this happen before and I would love to not have to buy
and set up a new server. Thanks,
Chris
|
|
|
| Back to top |
|
|
Z.G. Wiedemann
Guest
|
| Posted:
Mon Nov 07, 2005 9:51 am Post subject:
Re: Sporadic Shutting Downs - |
|
|
maybe its just phases of the moon or ???
but out of the blue I have experienced 3 (or more) shutdowns in the last 2-3
days
(not had such problems on this single cpu, ide drive system before)
I walked in on two "memory dumps" with an "IRQL_NOT_LESS_OR_EQUAL" error
ntoskrnl.exe error
haven't been able to fully research it yet ... but post here in case this is
a precursor to others problems ... |
|
| Back to top |
|
|
Dave Nickason [SBS MVP]
Guest
|
| Posted:
Mon Nov 07, 2005 5:51 pm Post subject:
Re: Sporadic Shutting Downs - |
|
|
IMO you need to give a high priority to troubleshooting the cause of any
unexplained shutdown or blue screen error. You could be experiencing an
issue that is caused by a pending hardware failure, virus or trojan,
database corruption, or some other situation that may rapidly worsen into a
disaster situation.
A mild example: I ignored unexplained startup errors on a workstation
recently. A week later, the hard drive failed, so the user was down while I
rebuilt the workstation from scratch. If I'd chosen not to ignore the
situation, I could have ghosted the drive before it failed and recovered in
hours, instead of having the user down for a whole day and part of the next.
Server situations can be worse since they effect the whole organization.
"Z.G. Wiedemann" <ZGWiedemann@discussions.microsoft.com> wrote in message
news:1A0860B0-6B99-4D13-8659-D73431678A28@microsoft.com...
| Quote: | maybe its just phases of the moon or ???
but out of the blue I have experienced 3 (or more) shutdowns in the last
2-3
days
(not had such problems on this single cpu, ide drive system before)
I walked in on two "memory dumps" with an "IRQL_NOT_LESS_OR_EQUAL" error
ntoskrnl.exe error
haven't been able to fully research it yet ... but post here in case this
is
a precursor to others problems ...
|
|
|
| Back to top |
|
|
Z.G. Wiedemann
Guest
|
| Posted:
Wed Nov 09, 2005 1:50 am Post subject:
Re: Sporadic Shutting Downs - |
|
|
Thanks Dave ... I agree ... good advise
just wondering if any others are also experiencing similar events ...
btw ... its been "good" since ... |
|
| Back to top |
|
|
Chris Guimbellot
Guest
|
| Posted:
Wed Nov 09, 2005 5:51 pm Post subject:
Re: Server Sporadically Shutting Down |
|
|
Thanks to all that have replied. I believe the problem is the Exchange
database. I am working with Microsoft on the issue right now. I will post
back when I find out more information. Once again, thanks,
Chris.
"MoiToo" <newsgroups@dodo.com.au> wrote in message
news:ew9uhog4FHA.2872@TK2MSFTNGP15.phx.gbl...
| Quote: | I would be suspecting drive problems. I would be running diagnostic
software on the server out of hours, to determine the probable cause. If
you are running hardware RAID, what does the controller software report? I
would bet lots of money you have some dead hardware!
"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in
message news:O4tQGtJ4FHA.820@tk2msftngp13.phx.gbl...
Two comments, Chris:
- since you have opened a PSS ticket, they should stick with you until
your problem is solved. The advice of a dedicated support rep focusing
only on your issue should hopefully be better than anything you'll get in
a newsgroup.
- without researching the specific errors you posted, I wonder if this
could be hard drive related. I'd consider running a chkdsk /f just to
see what the results look like. I do know from experience that Exchange
database corruption can be directly related to drive and/or controller
issues. You may even have controller or drive issues logged in your
system log, although I'm guessing you've already checked your logs.
"Chris Guimbellot" <cguimbellot@FORGETSPAM.hifranchise.com> wrote in
message news:%23tZZQ1H4FHA.700@TK2MSFTNGP15.phx.gbl...
Hello,
SBS2K, Win2K & XP clients.
For the past few days, my server has been experiencing problems. The
other day, I received the following error:
"LSASS.EXE - System Error, security accounts manager initialization
failed because of the following error: Directory Services cannot start.
Error status 0xc00002e1.
Please click OK to shutdown this system and reboot into directory
services restore mode, check the event log for more detailed
information. "
With no other options, I called Microsoft PSS. We worked on the server a
little while. In essence, he performed the steps in KB258062. To do
this, I had to reinstall the OS on a different drive just to be able to
log in. Anyway, he mentioned to me that the System State database may be
corrupt still. I also read that in the article.
Later that day, and one in a while for the days leading up to that day,
my Microsoft Exchange Information Store service would just stop. I saw
two events in the Application log that read as follows:
EventID: 474
Source: ESE
Category: Database Page Cache
Description:
Information Store (4508) The database page read from the file
"D:\Exchange\priv1.edb" at offset 5657198592 (0x0000000151320000) for
4096 (0x00001000) bytes failed verification due to a page checksum
mismatch. The expected checksum was 1001692875 (0x3bb49ecb) and the
actual checksum was 984915659 (0x3ab49ecb). The read operation will fail
with error -1018 (0xfffffc06). If this condition persists then please
restore the database from a previous backup.
EventID: 705
Source: ESE
Category: Online Defragmentation
Description:
Information Store (4508) Online defragmentation of database
'D:\Exchange\priv1.edb' terminated prematurely after encountering
unexpected error -1018. The next time online defragmentation is started
on this database, it will resume from the point of interruption.
So when I come in today, the server had shut down and was performing a
memory dump when I walked in. When I rebooted, the server came up
correctly. I reviewed the logs, and could find nothing that triggered
the shutdown.
I guess what I am wondering is where do I begin here? It looks to me
like System State and my Exchange DB are corrupt. Are these problems
related? I know that you can check the memory dump to see what types of
problems may have caused the shutdown, but I am not sure how to do it. I
think this all may stem from some hardware issue, but how would I go
about verifying that. Any ideas would be most appreciated considering
that I have never had all this happen before and I would love to not
have to buy and set up a new server. Thanks,
Chris
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in