RE: [ActiveDir] SBS Dies Twice in Four Days

2006-12-16 Thread joe
SBS... uh oh there goes the neighborhood... This one could possibly get the
[OT] badge I expect and/or go to the SBS specific groups. If an SBS server
died, AD would be one of the last things on it I would suspect with
everything it runs.  ;o)
 
  joe
 
--
O'Reilly Active Directory Third Edition -
http://www.joeware.net/win/ad3e.htm 
 
 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger
Sent: Thursday, December 14, 2006 1:39 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] SBS Dies Twice in Four Days



Hi -

 

I have a client with a four-year old SBS 2000 SP4 install on a Dell
PowerEdge 2500. In the last four days, the machine has simply died -- twice.
I can find no obvious (or not so obvious) cause for this. There appears
little that correlates directly with the crashes. The event logs are pretty
clear of major errors (except below). The Open Manage software does not show
any hardware problems. The drives are somewhat fragmented but not horribly. 

 

The few errors that show up include this: Shortly before Saturday's crash,
the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is the only DC in
this domain, I followed the steps provided to set the Enabled Journal Wrap
Automatic Restore key to 1. This appeared to have cleared the error. This
error has not recurred.

 

Also, Exchange has logged some errors such as 2104 and 8197 which seem
associated with access to the GC. When I followed the steps in MSKB 828764,
I do not find any entries in the registry keys listed which are supposed to
refer to the GC. 

 

Either way, I am not sure those would bring down a server - twice. 

 

Sorry if this is rambling a bit. I have been looking at this for several
hours and don't seem to be making any headway. Any thoughts welcome. The
server is up now (after a hard reboot), but I've got to feel comfortable
with leaving this server for a week - or my earlier post about laptop
batteries will be meaningless ;-)

 

TIA

 

-- nme

 


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 12/11/2006




RE: [ActiveDir] SBS Dies Twice in Four Days

2006-12-16 Thread Susan Bradley
(I suck at lurking what can I say) The other day someone was arguing about SBS 
saying what are you going to do if the AD gets corrupted and got to say 
Well, according to the AD gurus I know, it's very rare for AD to get corrupted 
and typically is not AD that has gone wrong but something else.
   
  They came back and said Oh well I meant overall corruption 

joe [EMAIL PROTECTED] wrote:
  @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }  
P.MsoNormal {   FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Times New 
Roman  }  LI.MsoNormal {   FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: 
Times New Roman  }  DIV.MsoNormal {   FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; 
FONT-FAMILY: Times New Roman  }  A:link {   COLOR: blue; TEXT-DECORATION: 
underline  }  SPAN.MsoHyperlink {   COLOR: blue; TEXT-DECORATION: underline  }  
A:visited {   COLOR: purple; TEXT-DECORATION: underline  }  
SPAN.MsoHyperlinkFollowed {   COLOR: purple; TEXT-DECORATION: underline  }  
P.MsoAutoSig {   FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Times New 
Roman  }  LI.MsoAutoSig {   FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: 
Times New Roman  }  DIV.MsoAutoSig {   FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; 
FONT-FAMILY: Times New Roman  }  P.Body {   FONT-SIZE: 10pt; MARGIN: 0in 0in 
0pt; FONT-FAMILY: Arial  }  LI.Body {   FONT-SIZE: 10pt; MARGIN:
 0in 0in 0pt; FONT-FAMILY: Arial  }  DIV.Body {   FONT-SIZE: 10pt; MARGIN: 0in 
0in 0pt; FONT-FAMILY: Arial  }  P.SectionHead1 {   FONT-WEIGHT: bold; 
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-STYLE: italic; FONT-FAMILY: Arial  } 
 LI.SectionHead1 {   FONT-WEIGHT: bold; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; 
FONT-STYLE: italic; FONT-FAMILY: Arial  }  DIV.SectionHead1 {   FONT-WEIGHT: 
bold; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-STYLE: italic; FONT-FAMILY: 
Arial  }  P.SectionHead2 {   FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0in 
0in 0pt; FONT-FAMILY: Arial  }  LI.SectionHead2 {   FONT-WEIGHT: bold; 
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial  }  DIV.SectionHead2 { 
  FONT-WEIGHT: bold; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Arial  
}  SPAN.EmailStyle20 {   COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: 
personal-compose  }  DIV.Section1 {   page: Section1  }  SBS... uh oh there 
goes the neighborhood... This one could possibly get the
 [OT] badge I expect and/or go to the SBS specific groups. If an SBS server 
died, AD would be one of the last things on it I would suspect with everything 
it runs.  ;o)
   
joe
   
  --
O'Reilly Active Directory Third Edition - 
http://www.joeware.net/win/ad3e.htm 
   

   


-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger
Sent: Thursday, December 14, 2006 1:39 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] SBS Dies Twice in Four Days


  
Hi –
   
  I have a client with a four-year old SBS 2000 SP4 install on a Dell PowerEdge 
2500. In the last four days, the machine has simply died -- twice. I can find 
no obvious (or not so obvious) cause for this. There appears little that 
correlates directly with the crashes. The event logs are pretty clear of major 
errors (except below). The Open Manage software does not show any hardware 
problems. The drives are somewhat fragmented but not horribly. 
   
  The few errors that show up include this: Shortly before Saturday’s crash, 
the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is the only DC in this 
domain, I followed the steps provided to set the “Enabled Journal Wrap 
Automatic Restore” key to 1. This appeared to have cleared the error. This 
error has not recurred.
   
  Also, Exchange has logged some errors such as 2104 and 8197 which seem 
associated with access to the GC. When I followed the steps in MSKB 828764, I 
do not find any entries in the registry keys listed which are supposed to refer 
to the GC. 
   
  Either way, I am not sure those would bring down a server – twice. 
   
  Sorry if this is rambling a bit. I have been looking at this for several 
hours and don’t seem to be making any headway. Any thoughts welcome. The server 
is up now (after a hard reboot), but I’ve got to feel comfortable with leaving 
this server for a week – or my earlier post about laptop batteries will be 
meaningless ;-)
   
  TIA
   
  -- nme
   


  --
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 12/11/2006




RE: [ActiveDir] SBS Dies Twice in Four Days

2006-12-14 Thread Eric Fleischman
Can you give us some data? Like, when it dies, what do you see? Is death
a blue screen? Or something else?

 

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger
Sent: Wednesday, December 13, 2006 10:39 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] SBS Dies Twice in Four Days

 

Hi -

 

I have a client with a four-year old SBS 2000 SP4 install on a Dell
PowerEdge 2500. In the last four days, the machine has simply died --
twice. I can find no obvious (or not so obvious) cause for this. There
appears little that correlates directly with the crashes. The event logs
are pretty clear of major errors (except below). The Open Manage
software does not show any hardware problems. The drives are somewhat
fragmented but not horribly. 

 

The few errors that show up include this: Shortly before Saturday's
crash, the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is the
only DC in this domain, I followed the steps provided to set the
Enabled Journal Wrap Automatic Restore key to 1. This appeared to have
cleared the error. This error has not recurred.

 

Also, Exchange has logged some errors such as 2104 and 8197 which seem
associated with access to the GC. When I followed the steps in MSKB
828764, I do not find any entries in the registry keys listed which are
supposed to refer to the GC. 

 

Either way, I am not sure those would bring down a server - twice. 

 

Sorry if this is rambling a bit. I have been looking at this for several
hours and don't seem to be making any headway. Any thoughts welcome. The
server is up now (after a hard reboot), but I've got to feel comfortable
with leaving this server for a week - or my earlier post about laptop
batteries will be meaningless ;-)

 

TIA

 

-- nme

 

 

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date:
12/11/2006



Re: [ActiveDir] SBS Dies Twice in Four Days

2006-12-14 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
As a generalization if the Microsoft O/S event logs are blank the 
issue tends to be hardware related (and those are the hardest ones to 
nail down at times)


Eric Fleischman wrote:


Can you give us some data? Like, when it dies, what do you see? Is 
death a blue screen? Or something else?


*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of *Noah Eiger

*Sent:* Wednesday, December 13, 2006 10:39 PM
*To:* ActiveDir@mail.activedir.org
*Subject:* [ActiveDir] SBS Dies Twice in Four Days

Hi –

I have a client with a four-year old SBS 2000 SP4 install on a Dell 
PowerEdge 2500. In the last four days, the machine has simply died -- 
twice. I can find no obvious (or not so obvious) cause for this. There 
appears little that correlates directly with the crashes. The event 
logs are pretty clear of major errors (except below). The Open Manage 
software does not show any hardware problems. The drives are somewhat 
fragmented but not horribly.


The few errors that show up include this: Shortly before Saturday’s 
crash, the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is the 
only DC in this domain, I followed the steps provided to set the 
“Enabled Journal Wrap Automatic Restore” key to 1. This appeared to 
have cleared the error. This error has not recurred.


Also, Exchange has logged some errors such as 2104 and 8197 which seem 
associated with access to the GC. When I followed the steps in MSKB 
828764, I do not find any entries in the registry keys listed which 
are supposed to refer to the GC.


Either way, I am not sure those would bring down a server – twice.

Sorry if this is rambling a bit. I have been looking at this for 
several hours and don’t seem to be making any headway. Any thoughts 
welcome. The server is up now (after a hard reboot), but I’ve got to 
feel comfortable with leaving this server for a week – or my earlier 
post about laptop batteries will be meaningless ;-)


TIA

-- nme//

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 
12/11/2006




--
Letting your vendors set your risk analysis these days?  
http://www.threatcode.com


If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will 
hunt you down...
http://blogs.technet.com/sbs

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


Re: [ActiveDir] SBS Dies Twice in Four Days

2006-12-14 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
[I don't mean really blank.. I just mean that they don't point to 
anything useful blank]


Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
As a generalization if the Microsoft O/S event logs are blank the 
issue tends to be hardware related (and those are the hardest ones to 
nail down at times)


Eric Fleischman wrote:


Can you give us some data? Like, when it dies, what do you see? Is 
death a blue screen? Or something else?


*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of *Noah Eiger

*Sent:* Wednesday, December 13, 2006 10:39 PM
*To:* ActiveDir@mail.activedir.org
*Subject:* [ActiveDir] SBS Dies Twice in Four Days

Hi –

I have a client with a four-year old SBS 2000 SP4 install on a Dell 
PowerEdge 2500. In the last four days, the machine has simply died -- 
twice. I can find no obvious (or not so obvious) cause for this. 
There appears little that correlates directly with the crashes. The 
event logs are pretty clear of major errors (except below). The Open 
Manage software does not show any hardware problems. The drives are 
somewhat fragmented but not horribly.


The few errors that show up include this: Shortly before Saturday’s 
crash, the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is 
the only DC in this domain, I followed the steps provided to set the 
“Enabled Journal Wrap Automatic Restore” key to 1. This appeared to 
have cleared the error. This error has not recurred.


Also, Exchange has logged some errors such as 2104 and 8197 which 
seem associated with access to the GC. When I followed the steps in 
MSKB 828764, I do not find any entries in the registry keys listed 
which are supposed to refer to the GC.


Either way, I am not sure those would bring down a server – twice.

Sorry if this is rambling a bit. I have been looking at this for 
several hours and don’t seem to be making any headway. Any thoughts 
welcome. The server is up now (after a hard reboot), but I’ve got to 
feel comfortable with leaving this server for a week – or my earlier 
post about laptop batteries will be meaningless ;-)


TIA

-- nme//

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 
12/11/2006






--
Letting your vendors set your risk analysis these days?  
http://www.threatcode.com


If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will 
hunt you down...
http://blogs.technet.com/sbs

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


RE: [ActiveDir] SBS Dies Twice in Four Days

2006-12-14 Thread Noah Eiger
Hi -

Thanks for the links, Susan. Yes, those are the errors regarding Exchange /
AD and the FRS errors seem to have gone away. 

The UPS is a good one to point to. The only thing that has changed is that
we replaced the UPS. Ah ha, you might say. We had a UPS on this for years,
but it did not run APC's PowerChute. That battery started beeping, and we
installed the application. Then the UPS died. This is a new battery and new
UPS. Do you know of any incompatibilities with APC's PowerChute? PowerChute
does not show anything out of the ordinary around the time of the crashes.

Finally, someone asked what was on the screen. I did not see it because I
was not on site. The person who did the restart for me said the screen was
blank. The screen is on a KVM.

Regardless, I am calling Dell today.

Thanks.

-- nme

-Original Message-
From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 14, 2006 9:17 AM
To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] SBS Dies Twice in Four Days

[I don't mean really blank.. I just mean that they don't point to 
anything useful blank]

Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
 As a generalization if the Microsoft O/S event logs are blank the 
 issue tends to be hardware related (and those are the hardest ones to 
 nail down at times)

 Eric Fleischman wrote:

 Can you give us some data? Like, when it dies, what do you see? Is 
 death a blue screen? Or something else?

 *From:* [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] *On Behalf Of *Noah Eiger
 *Sent:* Wednesday, December 13, 2006 10:39 PM
 *To:* ActiveDir@mail.activedir.org
 *Subject:* [ActiveDir] SBS Dies Twice in Four Days

 Hi –

 I have a client with a four-year old SBS 2000 SP4 install on a Dell 
 PowerEdge 2500. In the last four days, the machine has simply died -- 
 twice. I can find no obvious (or not so obvious) cause for this. 
 There appears little that correlates directly with the crashes. The 
 event logs are pretty clear of major errors (except below). The Open 
 Manage software does not show any hardware problems. The drives are 
 somewhat fragmented but not horribly.

 The few errors that show up include this: Shortly before Saturday’s 
 crash, the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is 
 the only DC in this domain, I followed the steps provided to set the 
 “Enabled Journal Wrap Automatic Restore” key to 1. This appeared to 
 have cleared the error. This error has not recurred.

 Also, Exchange has logged some errors such as 2104 and 8197 which 
 seem associated with access to the GC. When I followed the steps in 
 MSKB 828764, I do not find any entries in the registry keys listed 
 which are supposed to refer to the GC.

 Either way, I am not sure those would bring down a server – twice.

 Sorry if this is rambling a bit. I have been looking at this for 
 several hours and don’t seem to be making any headway. Any thoughts 
 welcome. The server is up now (after a hard reboot), but I’ve got to 
 feel comfortable with leaving this server for a week – or my earlier 
 post about laptop batteries will be meaningless ;-)

 TIA

 -- nme//

 -- 
 No virus found in this outgoing message.
 Checked by AVG Free Edition.
 Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 
 12/11/2006



-- 
Letting your vendors set your risk analysis these days?  
http://www.threatcode.com

If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will
hunt you down...
http://blogs.technet.com/sbs

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 12/11/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 12/11/2006
 

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


Re: [ActiveDir] SBS Dies Twice in Four Days

2006-12-14 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
For many/most they just use the built in (uh.. does 2k have built in?) 
UPS software in Windows rather than the Powerchute third party stuff.


I just know that Powerchute had an expired Java cert in their program 
and brought servers to their knees a year or so ago making symptoms like 
DNS issues.  So when it doubt pull it off.


Noah Eiger wrote:

Hi -

Thanks for the links, Susan. Yes, those are the errors regarding Exchange /
AD and the FRS errors seem to have gone away. 


The UPS is a good one to point to. The only thing that has changed is that
we replaced the UPS. Ah ha, you might say. We had a UPS on this for years,
but it did not run APC's PowerChute. That battery started beeping, and we
installed the application. Then the UPS died. This is a new battery and new
UPS. Do you know of any incompatibilities with APC's PowerChute? PowerChute
does not show anything out of the ordinary around the time of the crashes.

Finally, someone asked what was on the screen. I did not see it because I
was not on site. The person who did the restart for me said the screen was
blank. The screen is on a KVM.

Regardless, I am calling Dell today.

Thanks.

-- nme

-Original Message-
From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 14, 2006 9:17 AM

To: ActiveDir@mail.activedir.org
Subject: Re: [ActiveDir] SBS Dies Twice in Four Days

[I don't mean really blank.. I just mean that they don't point to 
anything useful blank]


Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
  
As a generalization if the Microsoft O/S event logs are blank the 
issue tends to be hardware related (and those are the hardest ones to 
nail down at times)


Eric Fleischman wrote:

Can you give us some data? Like, when it dies, what do you see? Is 
death a blue screen? Or something else?


*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of *Noah Eiger

*Sent:* Wednesday, December 13, 2006 10:39 PM
*To:* ActiveDir@mail.activedir.org
*Subject:* [ActiveDir] SBS Dies Twice in Four Days

Hi –

I have a client with a four-year old SBS 2000 SP4 install on a Dell 
PowerEdge 2500. In the last four days, the machine has simply died -- 
twice. I can find no obvious (or not so obvious) cause for this. 
There appears little that correlates directly with the crashes. The 
event logs are pretty clear of major errors (except below). The Open 
Manage software does not show any hardware problems. The drives are 
somewhat fragmented but not horribly.


The few errors that show up include this: Shortly before Saturday’s 
crash, the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is 
the only DC in this domain, I followed the steps provided to set the 
“Enabled Journal Wrap Automatic Restore” key to 1. This appeared to 
have cleared the error. This error has not recurred.


Also, Exchange has logged some errors such as 2104 and 8197 which 
seem associated with access to the GC. When I followed the steps in 
MSKB 828764, I do not find any entries in the registry keys listed 
which are supposed to refer to the GC.


Either way, I am not sure those would bring down a server – twice.

Sorry if this is rambling a bit. I have been looking at this for 
several hours and don’t seem to be making any headway. Any thoughts 
welcome. The server is up now (after a hard reboot), but I’ve got to 
feel comfortable with leaving this server for a week – or my earlier 
post about laptop batteries will be meaningless ;-)


TIA

-- nme//

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 
12/11/2006


  


  


--
Letting your vendors set your risk analysis these days?  
http://www.threatcode.com


If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will 
hunt you down...
http://blogs.technet.com/sbs

List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


Re: [ActiveDir] SBS Dies Twice in Four Days

2006-12-13 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Microsoft partners have a service called Server down.  If you are 
merely a registered Microsoft partner (which since you say clients and 
you are touching a SBS box.. you should be) you can log into your 
www.microsoft.com/partner profile (need passport) go to the support 
section, find the Business critical section and you have a number 
there and either a local number or toll free one to call.


If this is a SBS 2000 sp4 box.. how old are those drives? 


Call Server Down when you get stuck.. the resource is there... use it IMHO.

Now then... when did it die?  What occurs in the event logs right 
before?  Those JRNL wrap errors don't occur that often to SBS boxes.


2104 after a reboot is SBS tripping on Exchange and AD toes as it boots up.
http://msmvps.com/blogs/bradley/archive/2004/01/22/1997.aspx
http://msmvps.com/blogs/bradley/archive/2004/01/22/1998.aspx

http://www.eventid.net/display.asp?eventid=8197eventno=840source=MSExchangeFBPublishphase=1
8197?  Like that?

Noah Eiger wrote:


Hi –

 

I have a client with a four-year old SBS 2000 SP4 install on a Dell 
PowerEdge 2500. In the last four days, the machine has simply died -- 
twice. I can find no obvious (or not so obvious) cause for this. There 
appears little that correlates directly with the crashes. The event 
logs are pretty clear of major errors (except below). The Open Manage 
software does not show any hardware problems. The drives are somewhat 
fragmented but not horribly.


 

The few errors that show up include this: Shortly before Saturday’s 
crash, the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is the 
only DC in this domain, I followed the steps provided to set the 
“Enabled Journal Wrap Automatic Restore” key to 1. This appeared to 
have cleared the error. This error has not recurred.


 

Also, Exchange has logged some errors such as 2104 and 8197 which seem 
associated with access to the GC. When I followed the steps in MSKB 
828764, I do not find any entries in the registry keys listed which 
are supposed to refer to the GC.


 


Either way, I am not sure those would bring down a server – twice.

 

Sorry if this is rambling a bit. I have been looking at this for 
several hours and don’t seem to be making any headway. Any thoughts 
welcome. The server is up now (after a hard reboot), but I’ve got to 
feel comfortable with leaving this server for a week – or my earlier 
post about laptop batteries will be meaningless ;-)


 


TIA

 


-- nme//

 



--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 
12/11/2006



List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


Re: [ActiveDir] SBS Dies Twice in Four Days

2006-12-13 Thread Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]

Other ideas:

UPS good?


Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
Microsoft partners have a service called Server down.  If you are 
merely a registered Microsoft partner (which since you say clients 
and you are touching a SBS box.. you should be) you can log into your 
www.microsoft.com/partner profile (need passport) go to the support 
section, find the Business critical section and you have a number 
there and either a local number or toll free one to call.


If this is a SBS 2000 sp4 box.. how old are those drives?
Call Server Down when you get stuck.. the resource is there... use it 
IMHO.


Now then... when did it die?  What occurs in the event logs right 
before?  Those JRNL wrap errors don't occur that often to SBS boxes.


2104 after a reboot is SBS tripping on Exchange and AD toes as it 
boots up.

http://msmvps.com/blogs/bradley/archive/2004/01/22/1997.aspx
http://msmvps.com/blogs/bradley/archive/2004/01/22/1998.aspx

http://www.eventid.net/display.asp?eventid=8197eventno=840source=MSExchangeFBPublishphase=1 


8197?  Like that?

Noah Eiger wrote:


Hi –

 

I have a client with a four-year old SBS 2000 SP4 install on a Dell 
PowerEdge 2500. In the last four days, the machine has simply died -- 
twice. I can find no obvious (or not so obvious) cause for this. 
There appears little that correlates directly with the crashes. The 
event logs are pretty clear of major errors (except below). The Open 
Manage software does not show any hardware problems. The drives are 
somewhat fragmented but not horribly.


 

The few errors that show up include this: Shortly before Saturday’s 
crash, the FRS log recorded a 13568 JRNL_WRAP_ERROR. Since this is 
the only DC in this domain, I followed the steps provided to set the 
“Enabled Journal Wrap Automatic Restore” key to 1. This appeared to 
have cleared the error. This error has not recurred.


 

Also, Exchange has logged some errors such as 2104 and 8197 which 
seem associated with access to the GC. When I followed the steps in 
MSKB 828764, I do not find any entries in the registry keys listed 
which are supposed to refer to the GC.


 


Either way, I am not sure those would bring down a server – twice.

 

Sorry if this is rambling a bit. I have been looking at this for 
several hours and don’t seem to be making any headway. Any thoughts 
welcome. The server is up now (after a hard reboot), but I’ve got to 
feel comfortable with leaving this server for a week – or my earlier 
post about laptop batteries will be meaningless ;-)


 


TIA

 


-- nme//

 



--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.16/582 - Release Date: 
12/11/2006



List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/


List info   : http://www.activedir.org/List.aspx
List FAQ: http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir@mail.activedir.org/