Re: SBS 2003 R" Premium stops responding to clients by tomha
tomha
Mon Jul 14 03:07:01 PDT 2008
@Thomas:
i do not agree!
Meanwhile tested with 4 GB, same behaviour.
I know that Q35 Mainboards are no dedicated server boards, but it was
choosen because of the remote management ability(VPro technology) and the
lower costs of the whole system(Desktop board and CPU).
There are 7 customers running identical systems with identical patch levels
and only one shows this faulty behaviour.
Would have been nice to hear constructive tips.
"Thomas" wrote:
> SteveB, your rock :-)
>
> Thomas from Denmark
> "SteveB" <newsgroup@public.lan> skrev i meddelelsen
> news:%23taREw54IHA.4344@TK2MSFTNGP03.phx.gbl...
> > OK you seem to already know best. Don't use a server board for a server
> > and don't give it the max memory possible with SQL installed. Perhaps
> > others will give you some additional possibilities.
> >
> > "tomha" <tomha@discussions.microsoft.com> wrote in message
> > news:EFD66979-066F-4BED-8E1A-F43288FC7215@microsoft.com...
> >> ´Don´t think my probs are sql or memory related. Sometimes the SBS lost
> >> DC
> >> functionality at night, when all clients were down and there are no sql
> >> connections to the server.
> >> The sql load on this system is very small, and there were no sql server
> >> related errors in the event log.
> >>
> >>
> >> "SteveB" wrote:
> >>
> >>> Especially with SQL involved I'd increase to the max of 4 GB if the
> >>> board
> >>> will support all of it.
> >>>
> >>> "tomha" <tomha@discussions.microsoft.com> wrote in message
> >>> news:7E2F2320-0D8B-42D0-A9BE-797869C5F3D7@microsoft.com...
> >>> >I know that this isn´t a dedicated Server board, but i have 5 customers
> >>> > running SBS2003 on the same hardware and setup without any problems.
> >>> >
> >>> > Mem is 2 GB and there are 10 clients.
> >>> >
> >>> >
> >>> >
> >>> > "SteveB" wrote:
> >>> >
> >>> >> That isn't a server type board. How much memory and how many clients?
> >>> >>
> >>> >> "tomha" <tomha@discussions.microsoft.com> wrote in message
> >>> >> news:5C1DEC0F-30B4-4AA3-8DD2-7270FF4880D7@microsoft.com...
> >>> >> > Urgently looking for help on a SBS 2003 R2 Premium Server which
> >>> >> > suddenly
> >>> >> > stops to respond to clients.
> >>> >> >
> >>> >> > After 10 months of normal operation the server shows the following
> >>> >> >
> >>> >> > The symptoms start independent of client access or network load,
> >>> >> > sometimes
> >>> >> > the problem starts with all clients shut down.
> >>> >> >
> >>> >> > The Server which is the only server in the network(DC, DNS, DHCP,
> >>> >> > Exchange,
> >>> >> > SQL2005) running a sql 2005 database suddenly stops responding to
> >>> >> > client
> >>> >> > access. SQL Server is not reachable and client logon fails.
> >>> >> > The chronology is the same all 1 or 2 days and arises at random
> >>> >> > times.
> >>> >> >
> >>> >> > The eventlog first shows an MSExchangeDSAccess Event ID 2102 Error
> >>> >> > in
> >>> >> > the
> >>> >> > application log meaning DC Server not responding
> >>> >> > after aprox. 18 seconds it shows an MSExchangeDSAccess Event ID
> >>> >> > 2103
> >>> >> > (GC-
> >>> >> > Server not responding)
> >>> >> > These event ID´s are followed by MSExchangeAC 8026 Error(Server is
> >>> >> > shut
> >>> >> > down) and MSExchangeSA Error 9154(Error Code 0x80004005)
> >>> >> > Then there are multiple Exchange errors
> >>> >> >
> >>> >> > aprox. 15 Minutes after the first Error in the Application Log the
> >>> >> > AD
> >>> >> > Log
> >>> >> > shows a NTDS General Event ID 1655 (AD connection to GC failed)
> >>> >> > following
> >>> >> > by
> >>> >> > a NTDS General Event ID 1126(AD Connection to GC failed Error: 1460
> >>> >> > timeout)
> >>> >> > 1 hour later there is an event entry 1869(AD found GC at
> >>> >> > "ServerName")
> >>> >> > followed by Event ID 1655 and 1126 again.
> >>> >> >
> >>> >> > aprox. 1 minute after the error occurs the DNS log shows an Event
> >>> >> > ID
> >>> >> > 4015
> >>> >> > (critical Error in AD) followed by 4x Event ID 4004 and then many
> >>> >> > Event
> >>> >> > ID´s
> >>> >> > 4000(DNS server could not open AD)
> >>> >> >
> >>> >> > The System log shows no Errors.
> >>> >> >
> >>> >> > The only solution to get the server back to work ist to do a
> >>> >> > restart,
> >>> >> > but
> >>> >> > the server doesn´t shut down completely for hours(hanging at blank
> >>> >> > screen
> >>> >> > with blue background(no BSOD)
> >>> >> >
> >>> >> > After a hard reset the server comes up normally and works without
> >>> >> > problems
> >>> >> > for one or two days, till the same symptoms appear again.
> >>> >> >
> >>> >> > System:
> >>> >> > SBS 2003 R2 SP2 all updates applied
> >>> >> > DCDiag and NetDiag don´t show any errors, Chkdsk is running without
> >>> >> > errors
> >>> >> > on all harddrives
> >>> >> >
> >>> >> > Hardware:
> >>> >> > Intel DQ35JOE with Core2Duo E6600
> >>> >> > onboard VGA
> >>> >> > 3x Seagate SATA HDD on onboard RAID
> >>> >> >
> >>> >> > Desperately looking for further help
> >>> >> >
> >>> >> > thomas hajek - austria
> >>> >>
> >>> >>
> >>> >>
> >>>
> >>>
> >>>
> >
> >
>
>