Re: SBS DS, DNS etc seizing up every few days



Hi Matt,

What service pack are you running for SBS and Exchange? I would advise that
you patch your system to the latest fixes.

"Matt" <Matt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:498B7195-6753-4131-9DB1-158B78E6B54E@xxxxxxxxxxxxxxxx
Hi,

We have an SBS 2003 R2 server with directory services etc seizing up every
few days and preventing logins.
It's a single nic setup, runs a dhcp service. It has SQL Server and CRM 4
installed on it. It's the only server in the domain. It's otherwise a
fairly
standard install. It has hardware raid with a mirrored system drive and a
3
disk raid-5 data drive. Backup is done onto an external usb hdd. It's not
a
new install and has been running for some time without problems, this
problem
has only started happening in the last few weeks and there have been no
changes I'm aware of that might have triggered it.

The flow of events is variable and occurs every ~1-10 days.
Typically this starts while ntbackup is running, which starts at 23:00.
Though it has happened earlier once.

Around 00:30-01:00 the following errors starts showing up periodically:
Source: Service Control Manager
ID: 7011
Description: "Timeout (30000 milliseconds) waiting for a transaction
response from the NtFrs service. [...]"

Around 04:00-05:00 (but varies a fair bit) a lot of things start
failing...
In Directory Service log:
Source: NTDS ISAM
ID: 508
Description: "NTDS (500) NTDSA: A request to write to the file
"C:\WINDOWS\NTDS\edb.log" at offset [...]"

Source: NTDS General
ID: 1126
Description: "Active Directory was unable to establish a connection with
the global catalog. [...]"

Source: NTDS KCC
ID: 1435
Description: "The Knowledge Consistency Checker (KCC) encountered an
unexpected error while performing an Active Directory operation. [...]"

In DNS Server log:
Source: DNS
ID: 4015
Description: "The DNS server has encountered a critical error from the
Active Directory. [...]"

In System log:
Source: KDC
ID: 7
Description: "The Security Account Manager failed a KDC request in an
unexpected way. [...]"

While this is occuring people usually can't login and we end up forcably
rebooting the machine around 09:00.
The backup is still running at that time, where ordinarily it would have
finished by 3 or 4am.
The quantity of these errors is variable, sometimes they're more
intermittant and authentication only fails every so often, sometimes the
KDC
errors are coming up constantly a few times a minute.

A couple of times I've been logged on whilst it's in this state and found
the server to be responding fairly normally in most regards, I just can't
login again in another session. Kernel paged memory is a bit on the high
side
~260MB, MmSt pool tag using most of it. This seems normal behaviour while
ntbackup is running and is still well below the limit which I believe is
set
at ~360MB. Plus we're not seeing any out of pool memory errors.
Disk quotas are not enabled on the System drive and administrator and the
system accounts are not included in them on the Data drive. There's plenty
of
free space on both.
We did have AVG on the server, changed it for Sophos and no change.
We've run Dell's diagnostics on the harddrives/controllers and they've
shown
no issues.

Uptime inbetween this happening has ranged between 1 and around 10 days.
Sometimes these errors have shown up and then disappeared, apparently
recovered by the next morning and it lasts another few days before having
a
more severe attack.

Any ideas?

Thanks,
Matt.


.



Relevant Pages

  • RE: upgrade windows 2000 server to sbs2k3
    ... Server (SBS) 2003-based computer in an existing domain. ... an existing SBS 2000 or SBS 2003 domain controller for migration purposes. ... To install a SBS 2003 computer in an existing Active Directory domain, ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS to SBS
    ... To move an SBS 2003 installation to the new hardware, ... server, do a bare bones install on the new server (just the OS and all ... make sure to point DNS to the old SBS server hosting active directory zone. ... Make the new SBS server an Active Directory Global Catalog Server. ...
    (microsoft.public.windows.server.sbs)
  • Re: dns problem on sbs2003
    ... SBS 2003 machine as an additional domain controller of a Windows 2000 ... The new SBS 2003 computer must be a global catalog server and must be the ... On a Windows 2000 domain, you must prepare Active Directory before you ... If you already have Microsoft Exchange Server installed in the ...
    (microsoft.public.windows.server.sbs)
  • Re: Error 1054
    ... Here I suggest you use the configure site in Active directory to create ... link to synchronize data with SBS server for example 2 hours once. ... be set to be equal to the number of SBS client access license. ...
    (microsoft.public.windows.server.sbs)
  • Re: upgrade windows 2000 server to sbs2k3
    ... > for how to install a new SBS 2003 computer in an existing domain to maintain ... > the existing Active Directory directory service infrastructure. ... > the licensing server. ... > that the computer has been successfully promoted to a domain controller. ...
    (microsoft.public.windows.server.sbs)

Loading