The role owner attribute could not be read

LDIFDE error hile attempting to update the Schema for active directory. Error message:

Add error on line 1: Busy
The server side error is "The role owner attribute could not be read."
0 entries modified successfully.
An error has occurred in the program

This happens when performing the ldifde update as suggested in Microsoft Knowledgebase article 314649 for preventing mangled Exchange attributes when upgrading to a Windows 2003 domain.  The account that is logged on is part of schema admins and enterprise admins groups.  The domain controller is the schema master too.

I've searched everywhere on the web and can't find anything...HELP!!

Thanks
ipmcincAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BigC666Commented:
howdy,

the only references that i can find state that reinstalling sp4 seems to overcome the problem

hope that this helps
0
jdeclueCommented:
On the Domain Controller from the command prompt run dcdiag and see what it tells you. If you receive a bunch of errors messages like the following:

DEL:8361290b-8c28-4a21-be7e-c395dcee70aa",CN=NT-PDC,CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=engineering,DC=eng,DC=lmu,DC=edu is the PDC Owner, but is deleted.
        Warning: CN="NTDS Settings
DEL:8361290b-8c28-4a21-be7e-c395dcee70aa",CN=Server1,CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=engineering,DC=eng,DC=lmu,DC=edu is the R
id Owner, but is deleted.
        Warning: CN="NTDS Settings
DEL:8361290b-8c28-4a21-be7e-c395dcee70aa",CN=Server1,CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=engineering,DC=eng,DC=lmu,DC=edu is the I
nfrastructure Update Owner, but is deleted.

Then your FSMO roles owner is deleted.

This can be fixed by seizing all of the roles again.
Here is the link to the Microsoft KB on how to seize the FSMO roles with NTDSUTIL.exe

http://support.microsoft.com/default.aspx?scid=kb;EN-US;255504
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ipmcincAuthor Commented:
I'd also like to add that assigning the FSMO role of Schema Master to different domain controller and installing the file from the new schema master would also have worked.

Thanks for the quick responses!
0
jdeclueCommented:
No problem, and you are right. I just stick to the old tried and true methods with good walk throughs. Glad I could help, take care.

J
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Languages and Standards

From novice to tech pro — start learning today.