Link to home
Start Free TrialLog in
Avatar of hongedit
hongeditFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Exchange 2010 SP2 installation errors

Hi

I am trying to install SP2 onto my Exhange 2010 SP1 servers.

Pre-install checks complete fine but when I hit upgrade it automatically fails with an error:

Entry DN: CN=ms-Exch-ELC-Expiry-Action,CN=Schema,CN=Configuration,DC=evo,DC=local
Add error on entry starting on line 1: Operations Error

The server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.

The extended server error is:

000021A2: SvcErr: DSID-030A0AE6, problem 5012 (DIR_ERROR), data 8610


An error has occurred in the program

I have 2 Exchange 2010 Servers in a DAG/CAS, and a single DC.

Any ideas?
Avatar of Neil Russell
Neil Russell
Flag of United Kingdom of Great Britain and Northern Ireland image

Have you run DCDIAG to check for an errors? As its a single domain we can rule out replication errors that I would normally suguest....
Firewall dissabled on all servers? IPV6 installed? enabled/dissabled?
Avatar of hongedit

ASKER

IPV6 enabled
Firewall disabled

DCDIAG:

C:\Users\administrator.EVO>dcdiag /s:EVODC

Directory Server Diagnosis

Performing initial setup:
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\EVODC
      Starting test: Connectivity
         ......................... EVODC passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\EVODC
      Starting test: Advertising
         ......................... EVODC passed test Advertising
      Starting test: FrsEvent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... EVODC passed test FrsEvent
      Starting test: DFSREvent
         ......................... EVODC passed test DFSREvent
      Starting test: SysVolCheck
         ......................... EVODC passed test SysVolCheck
      Starting test: KccEvent
         A warning event occurred.  EventID: 0x8000082C
            Time Generated: 02/06/2012   17:19:57
            Event String:
         ......................... EVODC passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... EVODC passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... EVODC passed test MachineAccount
      Starting test: NCSecDesc
         ......................... EVODC passed test NCSecDesc
      Starting test: NetLogons
         ......................... EVODC passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... EVODC passed test ObjectsReplicated
      Starting test: Replications
         [Replications Check,EVODC] A recent replication attempt failed:
            From ECSDC to EVODC
            Naming Context: DC=DomainDnsZones,DC=evo,DC=local
            The replication generated an error (1256):
            The remote system is not available. For information about network tr
oubleshooting, see Windows Help.

            The failure occurred at 2012-02-06 16:58:39.
            The last success occurred at 2011-10-20 10:56:25.
            2607 failures have occurred since the last success.

Aha...I did have an old DC, called ECSDC. I decommissioned this server as it was getting too unreliable. If I remember correctly I think I had to seize roles...

Maybe something there?
Sorry, cut part of the log out:

         [Replications Check,EVODC] A recent replication attempt failed:
            From ECSDC to EVODC
            Naming Context: CN=Schema,CN=Configuration,DC=evo,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2012-02-06 16:59:21.
            The last success occurred at 2011-10-20 10:56:25.
            2602 failures have occurred since the last success.
            The source remains down. Please check the machine.
         [Replications Check,EVODC] A recent replication attempt failed:
            From ECSDC to EVODC
            Naming Context: CN=Configuration,DC=evo,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2012-02-06 16:59:00.
            The last success occurred at 2011-10-20 10:56:25.
            2602 failures have occurred since the last success.
            The source remains down. Please check the machine.
         [Replications Check,EVODC] A recent replication attempt failed:
            From ECSDC to EVODC
            Naming Context: DC=evo,DC=local
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2012-02-06 16:58:39.
            The last success occurred at 2011-10-20 11:42:58.
            2602 failures have occurred since the last success.
            The source remains down. Please check the machine.
         ......................... EVODC failed test Replications
      Starting test: RidManager
         ......................... EVODC passed test RidManager
      Starting test: Services
         ......................... EVODC passed test Services
      Starting test: SystemLog
         ......................... EVODC passed test SystemLog
      Starting test: VerifyReferences
         ......................... EVODC passed test VerifyReferences


   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation

   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : evo
      Starting test: CheckSDRefDom
         ......................... evo passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... evo passed test CrossRefValidation

   Running enterprise tests on : evo.local
      Starting test: LocatorCheck
         ......................... evo.local passed test LocatorCheck
      Starting test: Intersite
         ......................... evo.local passed test Intersite
ASKER CERTIFIED SOLUTION
Avatar of Jessie Gill, CISSP
Jessie Gill, CISSP
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok, followed the petri link and removed a lot of old DC objects.

DCDIAG is clean.

Will try upgrade again now!
Yep, sorry for delay was having my tea! As Jessiepak says, do a metadata cleanup of the deleted server and you should be fine to install.

Always when in doubt and doing an exchange or AD install and it fails, do a DCDIAG, 99% of the time it will hold the answer.