fSMORoleOwner in CN=Infrastructure DomainDNSZones & ForestDNSZones

[chupparustam]

I am getting an error message that says "The role owner attribute could not be read." when I am trying to change the fSMORoleOwner attribute by using ADSIEDIT. The FSMORoleOwner is showing "CN=NTDS Settings\0ADEL:9e2f14ec-9e95-4f07-bf7c-1a862a4ed8d6,CN=OLDSERVERNAME\0ADEL:27e107a1-3085-4e72-a7bc-80f05e4769ca,CN=Servers,CN=Default,CN=Sites,CN=Configuration,DC=Company_Name,DC=com"

I am also getting some alerts that are "The script 'AD Replication Monitoring' encountered a runtime error. Failed to obtain the InfrastructureMaster using a well known GUID. The error returned was: 'Failed to get the 'fSMORoleOwner' attribute from the object 'LDAP://DomainController1.company.com/<WKGUID=2fbac1870ade11d297c400c04fd8d5cd,DC=DomainDnsZones,DC=Company_Name,DC=com>'. The error returned was: 'There is no such object on the server.' (0x80072030)' (0x80072030)"

Can anyone pleases help me out? Thanks

[Actionguy]

It looks to me like you might have a problem where an old DC was never properly removed, which was crashed and rebuilt, from AD. You can try to check the below link and look through and see if it can help you:

http://support.microsoft.com/?id=216498

[unidentified]

Could you please let us know what do you mean by "DomainDNSZones & ForestDNSZones are incorrect, and displays the GUID of an older server"? Also note that "seizing" of Operation Master roles does not happen automatically, as a matter of a fact, as long as the previous Infrastructure Master Role has been decommissioned prior to the role trasfer, seizing the role would be the proper way to go ahead. Have you tried to seize the role using the procedure described here - http://support.microsoft.com/kb/255504

[chupparustam]

Thanks, but I went through with that article and when I use NTDSUTIL and go through the steps, the current production servers are the only ones listed. So, metadata cleanup isnt helping me.

[Tomthegreat]

Did you try to perform DNS cleanup by switching it to non-AD integrated format, removing the default application partitions using ntdsutil, and reverting back to the original configuration afterwards? As far as metadata cleanup is concerned, you can check the microsoft article provided here - http://support.microsoft.com/kb/216498