• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

RE: remote DC down preventing Exch2K from working

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2000] >> General >> RE: remote DC down preventing Exch2K from working Page: <<   < prev  1 [2]
Login
Message << Older Topic   Newer Topic >>
RE: remote DC down preventing Exch2K from working - 16.Nov.2006 12:25:17 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
Here is the response I got when I asked for details...

The keys where related to the extension of active directory for exchange server. When you install exchange server, it has to create permissions in AD for it to make entries, read, etc. These permissions where mapped to an incorrect SID on the local servers.   In the future, you may be able to easily fix it by running the latest exchange sp (update.exe) with the /forestprep and /domainprep switches.

(in reply to jchong)
Post #: 21
RE: remote DC down preventing Exch2K from working - 16.Nov.2006 12:28:42 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Thanks for sharing the fix!

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to jchong)
Post #: 22
RE: remote DC down preventing Exch2K from working - 27.Nov.2006 4:26:04 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I spoke too soon.  After demoting all but the PDC DC at our main site, bringing in two "temporary" DC's to DCPROMO and use in our main site until two new DC's come in (to be solely dedicated as DC's), we found that our AD environment seemed stable.  We think that having Veritas running backups on our main DC and allowing the temp files to fill the drive, may have corrupted AD.  This is what our outsourced IT support is saying.  We moved our catalog files off the C: drive on our PDC DC so we have plenty of drive space now.  However, we are getting the following events repeated over and over in our Exchange Server's event log.  I believe now that the cause is an issue with the SACL right on DC1 (KB316300).

Do you know if there is a way to check this without bringing Exchange down?

Event Type:       Warning
Event Source:    MSExchangeDSAccess
Event Category: Configuration
Event ID:           2090
Date:                11/25/2006
Time:                2:04:32 PM
User:                N/A
Computer:         EXCHANGE
Description:
Process INETINFO.EXE (PID=848). The Configuration Domain Controller specified in the registry (dc1.interconnect-wiring.com) is unreachable.  DSAccess will choose the Configuration Domain Controller from the list of available Domain Controllers.
======================================================================
 
Event Type:       Information
Event Source:    MSExchangeDSAccess
Event Category: Topology
Event ID:           2080
Date:                11/25/2006
Time:                2:04:32 PM
User:                N/A
Computer:         EXCHANGE
Description:
Process INETINFO.EXE (PID=848). DSAccess has discovered the following servers with the following characteristics:
 (Server name | Roles | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon)
 In-site:
dc1.interconnect-wiring.com       CDG 7 7 1 0 0 1 7
DC2.interconnect-wiring.com      CDG 7 7 1 0 1 1 7
 Out-of-site:
 
======================================================================
 
 
Event Type:       Information
Event Source:    MSExchangeDSAccess
Event Category: Configuration
Event ID:           2092
Date:                11/25/2006
Time:                2:19:33 PM
User:                N/A
Computer:         EXCHANGE
Description:
Process STORE.EXE (PID=3100). DsAccess will use Domain Controllers specified in the registry.
======================================================================
 
 
Event Type:       Information
Event Source:    MSExchangeDSAccess
Event Category: Configuration
Event ID:           2093
Date:                11/25/2006
Time:                2:19:33 PM
User:                N/A
Computer:         EXCHANGE
Description:
Process STORE.EXE (PID=3100). DsAccess will use Global Catalogs specified in the registry.
 
======================================================================
 
Event Type:       Information
Event Source:    MSExchangeDSAccess
Event Category: Configuration
Event ID:           2096
Date:                11/25/2006
Time:                2:19:33 PM
User:                N/A
Computer:         EXCHANGE
Description:
Process STORE.EXE (PID=3100). DSAccess will use the Configuration Domain Controller (dc1.interconnect-wiring.com) specified in the registry.

(in reply to jchong)
Post #: 23
RE: remote DC down preventing Exch2K from working - 27.Nov.2006 4:53:26 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Let's do this. Open adsiedit, expand configuration, go to properties of the cn=... security tab. Do you see enterprise domain controllers?

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 24
RE: remote DC down preventing Exch2K from working - 27.Nov.2006 5:47:11 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
Yes.  It has Allow checked for the following:
   Manage Replication Topology
   Replicate Directory Changes
   Replicating Directory Changes All
   Replication Synchronization

I checked the Effective Security and it lists exactly the above four only.
Should it be different?  Maybe have Read nTSecurityDescriptor and/or Write...?

(in reply to jchong)
Post #: 25
RE: remote DC down preventing Exch2K from working - 27.Nov.2006 9:27:59 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Let's do this, manually add only ONE of your local domain controllers and give it full control. Then give this a bit for Exchange to re-discovery dsaccess.



_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 26
RE: remote DC down preventing Exch2K from working - 28.Nov.2006 3:24:48 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I did this, it shows our 'DC1' DC now with Full Control, however "Auto discovery" is not checked on the "Directory Access" tab in Exchange for the Configuration DC and I'm afraid that if I check it I'll lose Exchange connectivity.  I waited a while and then ran ExBPA and it could not connect to DC1.

(in reply to jchong)
Post #: 27
RE: remote DC down preventing Exch2K from working - 28.Nov.2006 4:03:24 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
ExBPA could not connect to DC1? What's the error?

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 28
RE: remote DC down preventing Exch2K from working - 28.Nov.2006 4:08:04 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
Active Directory server cannot be contacted

The Directory Service Access (DSAccess) process on server EXCHANGE reports that Active Directory server DC1.interconnect-wiring.com is not functional.

This is what MS offers as a "tell me more"
http://www.microsoft.com/technet/prodtechnol/exchange/Analyzer/623bd742-0051-4e60-a190-8d55d5c5b96c.mspx?mfr=true 

(in reply to jchong)
Post #: 29
RE: remote DC down preventing Exch2K from working - 28.Nov.2006 4:46:44 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Hmm, yeah it may or may not mean it's not functioning it could be perm issues in which the ex cannot query the wmi namespace for this attribute, or it could mean it's screwed up. Is it possible for you to bring up another test DC locally to see if it will auto discovery it?

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to jchong)
Post #: 30
RE: remote DC down preventing Exch2K from working - 28.Nov.2006 4:48:46 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I can tonight.  I just don't want to do it while everyone is trying to do email.

(in reply to jchong)
Post #: 31
RE: remote DC down preventing Exch2K from working - 29.Nov.2006 11:05:40 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I tried it tonight auto-discovering the DC's and Config DC and GC's and it only found the remote DC on the GUI and so I went back to manually selecting them.  After a while Exchange started working again (a few minutes).

The Events were:

Event Type:    Error
Event Source:    MSExchangeDSAccess
Event Category:    Topology
Event ID:    2103
Date:        11/29/2006
Time:        9:21:49 PM
User:        N/A
Computer:   EXCHANGE
Description:
Process STORE.EXE (PID=3100). All Global Catalog Servers in use are not responding: dc1.interconnect-wiring.com

Event Type:    Error
Event Source:    MSExchangeDSAccess
Event Category:    Topology
Event ID:    2103
Date:        11/29/2006
Time:        9:21:52 PM
User:        N/A
Computer:   EXCHANGE
Description:
Process EMSMTA.EXE (PID=3160). All Global Catalog Servers in use are not responding: dc1.interconnect-wiring.com

Event Type:    Error
Event Source:    MSExchangeDSAccess
Event Category:    Topology
Event ID:    2103
Date:        11/29/2006
Time:        9:21:52 PM
User:        N/A
Computer:   EXCHANGE
Description:
Process INETINFO.EXE (PID=848). All Global Catalog Servers in use are not responding: dc1.interconnect-wiring.com

Event Type:    Information
Event Source:    MSExchangeDSAccess
Event Category:    Configuration
Event ID:    2092
Date:        11/29/2006
Time:        9:22:12 PM
User:        N/A
Computer:    EXCHANGE
Description:
Process EXMGMT.EXE (PID=2684). DsAccess will use Domain Controllers specified in the registry.

Event Type:    Information
Event Source:    MSExchangeDSAccess
Event Category:    Configuration
Event ID:    2093
Date:        11/29/2006
Time:        9:22:12 PM
User:        N/A
Computer:   EXCHANGE
Description:
Process EXMGMT.EXE (PID=2684). DsAccess will use Global Catalogs specified in the registry.

Event Type:    Information
Event Source:    MSExchangeDSAccess
Event Category:    Configuration
Event ID:    2096
Date:        11/29/2006
Time:        9:22:12 PM
User:        N/A
Computer:    EXCHANGE
Description:
Process EXMGMT.EXE (PID=2684). DSAccess will use the Configuration Domain Controller (dc1.interconnect-wiring.com) specified in the registry.

Event Type:    Warning
Event Source:    MSExchangeDSAccess
Event Category:    Configuration
Event ID:    2090
Date:        11/29/2006
Time:        9:22:12 PM
User:        N/A
Computer:   EXCHANGE
Description:
Process EXMGMT.EXE (PID=2684). The Configuration Domain Controller specified in the registry (dc1.interconnect-wiring.com) is unreachable.  DSAccess will choose the Configuration Domain Controller from the list of available Domain Controllers.

Event Type:    Error
Event Source:    MSExchangeDSAccess
Event Category:    Topology
Event ID:    2102
Date:        11/29/2006
Time:        9:22:12 PM
User:        N/A
Computer:   EXCHANGE
Description:
Process EXMGMT.EXE (PID=2684). All Domain Controller Servers in use are not responding: dc1.interconnect-wiring.com

Event Type:    Information
Event Source:    MSExchangeDSAccess
Event Category:    Topology
Event ID:    2080
Date:        11/29/2006
Time:        9:22:12 PM
User:        N/A
Computer:    EXCHANGE
Description:
Process EXMGMT.EXE (PID=2684). DSAccess has discovered the following servers with the following characteristics:
(Server name | Roles | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon)
In-site:
dc1.interconnect-wiring.com    CDG 7 7 1 0 0 1 7
DC2.interconnect-wiring.com    --G 1 7 1 0 1 1 7
rbc1.interconnect-wiring.com    --G 1 7 1 0 0 1 7
Out-of-site:

Event Type:    Error
Event Source:    MSExchangeIS Public Store
Event Category:    Logons
Event ID:    1024
Date:        11/29/2006
Time:        9:24:50 PM
User:        N/A
Computer:    EXCHANGE
Description:
NT AUTHORITY\SYSTEM was unable to log on as NT AUTHORITY\SYSTEM to the Public Folder Store "First Storage Group\Public Folder Store (EXCHANGE)".

<then it cycles through these same events with the manually entered DC's and here's what the 2080 event showed....>

Event Type:    Information
Event Source:    MSExchangeDSAccess
Event Category:    Topology
Event ID:    2080
Date:        11/29/2006
Time:        9:27:14 PM
User:        N/A
Computer:    EXCHANGE
Description:
Process STORE.EXE (PID=3100). DSAccess has discovered the following servers with the following characteristics:
(Server name | Roles | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon)
In-site:
dc1.interconnect-wiring.com    CDG 7 7 1 0 0 1 7
DC2.interconnect-wiring.com    --G 1 7 1 0 1 1 7
rbc1.interconnect-wiring.com    CDG 7 7 1 0 0 1 7
RBC2.interconnect-wiring.com    CD- 6 6 0 0 0 1 6
Out-of-site:

< the above events cycle through several more times in a matter of minutes and then....>

Event Type:    Information
Event Source:    MSExchangeDSAccess
Event Category:    Topology
Event ID:    2080
Date:        11/29/2006
Time:        9:35:26 PM
User:        N/A
Computer:    EXCHANGE
Description:
Process EMSMTA.EXE (PID=3160). DSAccess has discovered the following servers with the following characteristics:
(Server name | Roles | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon)
In-site:
dc1.interconnect-wiring.com    CDG 7 7 1 0 0 1 7
dc2.interconnect-wiring.com    CDG 7 7 1 0 1 1 7
rbc1.interconnect-wiring.com    CDG 7 7 1 0 0 1 7
RBC2.interconnect-wiring.com    CDG 6 6 1 0 0 1 6
Out-of-site:

==========================
I don't understand about the "Out-of-site" - if DC2 is in another "site" shouldn't it be listed below Out-of-site and not above it?

What about the "SACL right" - only DC1 has a 1 in that column and the others have zero (0)?  Do I need to do something there?  What does that mean?

Also, on our Exchange server, I looked in the H/W Manager and found that the DELL Driver "Systems Management IPMI Driver" has a yellow exclamation point on it.  It says, "The device is not working properly because windows cannot load the drivers required for this device (Code 31)."  I believe that only has to do with DELL Open Manage but I wanted to run that by you.

(in reply to dougsymes)
Post #: 32
RE: remote DC down preventing Exch2K from working - 21.Dec.2006 2:57:10 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I'm trying to run DCPROMO on two new DC's we just got.
I want to see if Exchange will connect to them but our domain is 2000 and for some reason DCPROMO won't run.  I'm looking at KB325379 but is there something else that can help me get this done as well?

(in reply to dougsymes)
Post #: 33

Page:   <<   < prev  1 [2] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2000] >> General >> RE: remote DC down preventing Exch2K from working Page: <<   < prev  1 [2]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter