[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 229
  • Last Modified:

Exchange 2007 Error

We Dcpromo'd a 2003 server and now we are getting errors in Exchange 2007 with event ID 8026 i can only find answers for Exchange 2003
0
davecoleman146
Asked:
davecoleman146
  • 6
  • 5
1 Solution
 
madhuskCommented:
Is this a random one-off error?? Are you seeing 8026's sporadically? all the time?
Is LDAP automatically setup ?
LDAP is controlled by AD.. by default it should be working without issue... any kind of firewall on or between these systems that might be adversly affecting connectivity?


Run a quick tracert and nslookup on the exchange server to verify that nothing is traversing the firewall... then verify that the domain controllers are healthy...    
0
 
davecoleman146Author Commented:
All else is fine connectivity is good and no firewall issues the error only happens when i try to create or edit a mailbox
0
 
MesthaCommented:
DCPROMO of a server on its own shouldn't have caused a problem. Although you didn't say which way you went.

Restart the Exchange System Attendant Service and see what happens then.

Simon.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
davecoleman146Author Commented:
Hi

  I tried restating all services as the first port of call with no effect
0
 
MesthaCommented:
You still haven't said which way the DCPROMO was - was it adding a domain controller or removing it? It is quite important.

Simon.
0
 
davecoleman146Author Commented:
Sorry removing a server
0
 
MesthaCommented:
Do you have other global catalogs?
Have you checked that the Exchange server can see other domain controllers, wasn't hard coded to use that specific domain controller in any way?
Was DNS etc updated to remove that machine from the network configuration?

Simon.
0
 
davecoleman146Author Commented:
Hi Simon

  Yes there are other GC servers in fact the exchange server is a DC so conetivity to other DC is not a problem and yes DNS was updated.
0
 
MesthaCommented:
If the Exchange server itself is a DC then it MUST be a GC as well.

Simon.
0
 
davecoleman146Author Commented:
Yes it is a GC server
0
 
MesthaCommented:
In that case removing a domain controller shouldn't have caused a problem because Exchange only uses itself for domain controller functionality when installed on a DC.
Was that server that you removed holding any of the FSMO roles? That shouldn't affect Exchange, but is something to check.

Have you run the best practises tool against the environment?

Simon.
0
 
davecoleman146Author Commented:
Hi Simon

  No all the roles wher on the other DC's and no i have not run the best practice tool yet but a good idea and i will do it later today.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now