I'm moving from 2013.1 (on Server 2008 R2) to 2014.1 (on Server 2012 R2) and am going from a single server to 2 new servers and will shut down the 2013.1 server when I get this completed.
I installed Adaxes on one server and had it share it's configuration from the 2013.1 server with no issues and it's been up for a couple of weeks.
I'm now installing a second server so we can do load balancing for 2014.1 with our F5's to these two new servers, however, during the install, it's giving me an error:
Add error on entry starting on line 17: 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:...
It then rolls back the installation.
In looking at the event viewer for the new server, I see this error:
The directory server has failed to update the host name and/or ports information for this service on the following remote server. This operation will be retried. Other directory servers in this configuration set (if any) will be unable to replicate changes from this directory server until this change is performed and replicated to them.
Additional Data
Target DSA object:
CN=NTDS Settings,CN=<SERVER>$AdaxesBackend,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={A95E89DB-8B8F-45AF-8428-BE9FF17D0490}
Error value:
8601 The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data.
Internal ID:
32b0cb6
How do I fix this?
** edit **
On the server it's mentioning (the 2013.1), I'm seeing this error (and it just started after the server was rebooted last week).
Log Name: ADAM (AdaxesBackend)
Source: ADAM [AdaxesBackend] Replication
Date: 8/23/2014 1:01:53 AM
Event ID: 2092
Task Category: Replication
Level: Warning
Keywords: Classic
User: ANONYMOUS LOGON
Computer: <2013.1 server>.tasconline.com
Description:
This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role.
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
FSMO Role: CN=Schema,CN=Configuration,CN={A95E89DB-8B8F-45AF-8428-BE9FF17D0490}
User Action:
1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476.
2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors. Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication.
3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
The following operations may be impacted:
Schema: You will no longer be able to modify the schema for this forest.
Domain Naming: You will no longer be able to add or remove domains from this forest.
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Lightweight Directory Services accounts.
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.
Would another reboot fix this possibly?