SBS 2008 fails to launch Exchange after restart, DNS Active Directory Issues?

Posted on 2009-05-20
Last Modified: 2013-11-05
I have a new deployment of SBS 2008. This will be a remotely hosted machine and therefor will service as an exchange server using RPC over HTTP/HTTPS. The AD functions as well as DHCP/DNS are not needed for the staff connecting to it. (However they are needed for Exchange to function!)

I had it installed, configured and working correctly.

I then addedd users and noticed that the SBS first email was unable to be sent to the users. I had also noticed that the server was requesting a restart for Update Rollup 2.

So I restarted...

Since that point I have restarted countless times and it's been over 36 hours of troubleshooting.

Here is what I know:
In Safe Mode, all things function as they should (with their safe mode limitations of course)

When I boot to standard mode I cannot open a single MSC (eventvwr.msc or services.msc for example) I also notice that the network icon in the system tray has a red X on it. However I am able to ping out and in.

Remote Desktop Connection is down (the server is not listening on port 3389)

Exchange Transport will not start, and MAD.exe is reporting Topology errors. (see below)

If I try to open a control panel Icon/Applet Explorer stops responding. Explorer stops responding if I try to open too many MSC's. (none successfully open)

Basically anything I want to do that requires elevated privileges doesn't happen (and no I don't even make it to the UAC prompt

I have since fixed a couple of DNS mis-configurations (from Safe Mode as I cannot launch a MSC in regualr mode) and removed the Update Rollup 2 (from Safe Mode)

I am attempting to re install the update rollup 2. To see if my DNS issues caused the problem in the first place.

It seems as though the domain.local. dns zones are mis configured. But I can't figure out why the trailing period. And from safe mode Im not able to edit the DNS (can open an MSC in regular mode either!)

as a recap:
Exchange Transport Service will not run
MSCs will not launch
Explorer stops responding
RDC is not working.

Errors from the System Log:

Event ID 40960
Source: LsaSrv
The Security System detected and authentication error for the server DNS/ The failurecode from authentication protocol Kerberos was "There are currently no logon servers available to servie the logon request. (0xc000005e)".

Event ID 15021
Source HttpEvent
An error occured while using SSL configuration for sockett address The error status code is contained within the returned data.

(The above error repeats 3x for different ip addresses)

Event ID: 7024
Source: Service Control Manager Eventlog Provider
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).

Event ID: 5781
Dynamic registration or deletion of one or more DNS records associated with DNS domain 'mydomain.local.' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).

Possible causes of failure inclide:
-TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers
-Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registerd is not running
- Preferred or alternate DNS servers are configured with wrond root hints
- Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration.

(The above error repeats for DomainDnsZones.mydomain.local. and ForestDnsZones.mydomain.local.)

Event ID: 7022
Source Service Control Manager Eventlog Provider
The Microsoft Exchange Transport service hung on starting.

From the App Log

Event ID: 2106
Source MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1988). Exchange Active Directory Provider failed to obtain DNS records for forest DC=(mydomain),DC=local. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight).

(error repeated for "domain (mydomain).local.")

Event ID: 2114
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1988). Topology discovery failed, error 0z80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

Event ID: 2106
Source: MSExchange ADAccess
Process STORE.EXE (PID=1584). Exchange Active Directory Provider failed to obtain DNS records for forest DC=(my domain),DC=local. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight).

Thanks for your help!
Question by:Namtrok
1 Comment

Accepted Solution

Namtrok earned 0 total points
ID: 24435225
Wow, I figured it out, ipv6 was disabled. Re-enabling it solved all my issues.

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
This script can help you clean up your user profile database by comparing profiles to Active Directory users in a particular OU, and removing the profiles that don't match.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

786 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question