Missing Expected Value causing VerifyEnterpriseReferences failed ?

People,

When I run the DCDIAG from any of my Domain Controller, I can see the following error:

      Starting test: VerifyEnterpriseReferences

         The following problems were found while verifying various important DN
         references.  Note, that  these problems can be reported because of
         latency in replication.  So follow up to resolve the following
         problems, only if the same problem is reported on all DCs for a given
         domain or if  the problem persists after replication has had
         reasonable time to replicate changes. 
		 
            [1] Problem: Missing Expected Value

             Base Object:

            CN=SiteOffice2K8FS,OU=Domain Controllers 2K8,OU=Domain Controllers,DC=domain,DC=com
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: frsComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862

         ......................... PRODHQDC01 failed test

Open in new window


The command above was executed from the newly installed Windows Server 2012 R2 DC (PRODHQDC01) but why the error above can be seen when I logged in to different domain controller as well ?

I've checked the Computer Object SiteOffice2K8FS it is exist in the OU=Domain Controllers 2K8,OU=Domain Controllers,DC=domain,DC=com container.

how to fix that error ?
LVL 9
Senior IT System EngineerIT ProfessionalAsked:
Who is Participating?
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.

Randy DownsOWNERCommented:
Does this continue to fail? if it doesn't happen on all DCs or if it hasn't had time to replicate then this is not something you need to worry about.

Note, that  these problems can be reported because of
         latency in replication.  So follow up to resolve the following
         problems, only if the same problem is reported on all DCs for a given
         domain or if  the problem persists after replication has had
         reasonable time to replicate changes.
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
Senior IT System EngineerIT ProfessionalAuthor Commented:
Yes, somehow I can see the same error / alert above when performing the DCDIAG /V /C /D in my Domain Controllers.
0
Senior IT System EngineerIT ProfessionalAuthor Commented:
Thanks !
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
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.