Have to keep rebooting server to fix recurring Userenv 1030, MSExchangeDSAccess 2104, and MSExchangeAL 8026 errors

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi, All,
For the past several weeks, every 3 or 4 days I have to reboot my SBS
2003 SP1 server to alleviate a recurring series of Application Event
errors that screw up my domain -- Active Directory, Exchange, client
access to Outlook and Public folders, networked printers, remote
access, etc. The errors seem to occur in a similar pattern -- first a
Userenv 1030 "Windows cannot query for the list of Group Policy
objects", followed in a couple of minutes by a MSExchangeDSAccess 2104
"Process MAD.EXE (PID=4028). All the DS Servers in domain are not
responding." (sometimes as 2101 error). And then, a flood of
MSExchangeAL 8026 "LDAP Bind was unsuccessful on directory
myserver-00.mydomain-etc.local for distinguished name ''. Directory
returned error:[0x51] Server Down. DC=mydomain-
etc,DC=local." (substituting myserver, mydomain for actual names).
These MSExchangeAL 8026 errors soon fill up my event log.

Within an hour or so, DNS errors beging logging in Event viewer for
DNS -- 4015 "The DNS server has encountered a critical error from the
Active Directory. Check that the Active Directory is functioning
properly"; 4004 "The DNS server was unable to complete directory
service enumeration of zone myserver-00.mydomain-etc.local. . ."; and
4000 "The DNS server was unable to open Active Directory. . ." This
4000 error keeps recurring every 3 minutes.

Meanwhile, when logging on to the server (on location, no remote
access); or to one of the clients, an Error message pops up at login
-- "One or more domain controllers do not meet the licensing
requirements. . . ." Nothing unusual appears on any Client event log
and ipconfigs seem okay (pointing to server for DNS, DHCP, etc) --
however, I've only checked the ipconfigs after rebooting. (Next time
problem occurs, I will check client ipconfigs before rebooting the
server, ie, when the problem is occurring. Though, I'm uncertain the
problem is originating from any client).

I've researched the Event errors mentioned in the first paragraph
above, but have been unable to resolve the recurring issue and what
triggers it. Researching each of these errors takes me off on
different tangents that I'm not always sure are relevant. As I
mentioned, rebooting the server temporarily alleviates the problem,
but then the AD screw-up cycle begins again within a few days.

Any suggestions much appreciated!
Thank you,
Greg Brown
.



Relevant Pages

  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT Domain to AD migration
    ... Windows 2000/XP always prefer Kerberos authentication, ... Server 2003 Active Directory service, ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 Migration
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: i got 6 server in company which contains NT4 , windows 2000 , windowser 2003
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)