(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 Saturdays 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 dont seem to be making any headway. Any thoughts welcome. The server
is up now (after a hard reboot), but Ive 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
