none
Dcdiag test failed on VerifyEnterpriseReferences

    Question

  • I just upgrade 2003 Active Directory to 2008 version.
    My 2008 Active Directory environment is just a single domain controller
    Every thing seems to be fine.
    After I execute dcdiag testing.
    There is a failed test on VerifyEnterpriseReferences.
    Follow is the error description :

    [1] Problem: Missing Expected Value
    Base Object: CN=AD2008,OU=Domain Controllers,DC=abc,DC=com
    Base Object Description: "DC Account Object"
    Value Object Attribute Name: msDFSR-ComputerReferenceBL
    Value Object Description: "SYSVOL FRS Member Object"
    Recommended Action: Please See Knowledge Base Article Q312862
    LDAP Error 0x20 (32) - No Such Object
    ....................... ......AD2008 failed test VerifyEnterpriseReferences


    Does any one know what this problem is and how to solve ?

    Thanks!!
     



    Sunday, November 16, 2008 5:16 PM

Answers

  •  

    Hi,

     

    Based on the attribute name msDFSR-ComputerReferenceBL, I believe that the domain function level has been raised to Windows Server 2008. Therefore, the KB article Q312862 may not apply to your environment.

     

    The error means that the value of the attribute msDFSR-ComputerReferenceBL is not correct. You can verify it by performing the following steps:

     

    1.    On the Domain Controller, open Active Directory Users and Computers console.

    2.    In the console, select Domain Controllers, and then double-click the DC object AD2008 in the right pane.

    3.    Cliekt the tab “Attribute Editor, click the button Filter, and then check the Backlinks.

    4.    After that you should see the attribute msDFSR-ComputerReferenceBL. The expected value is CN=AD2008,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,Cn=system, DC=abc,DC=com.

     

    If you need further assistance, please use the utility ldifde to export the following objects:

     

    ·         Ldifde –f computer.txt –d “CN=AD2008,OU=Domain Controllers,DC=abc,DC=com”

    ·         Ldifde –f dfsr.txt –d “CN=Domain System Volume,CN=DFSR-GlobalSettings,Cn=system, DC=abc,DC=com”

     

    And then, upload the files (computer.txt and dfsr.txt) to the following space:

     

    https://sftasia.one.microsoft.com/choosetransfer.aspx?key=0614749e-437f-4369-9c45-9dc96de38a5a

    Password: rji%+WRX)e

     

    I will check the files and provide more detailed steps.

    Tuesday, November 18, 2008 9:36 AM
    Moderator

All replies

  • This error is discussed in the Recovering from deleted FRS objects section in Microsoft Knowledgebase article 312862.
    Sunday, November 16, 2008 10:23 PM
  •  

    Hi,

     

    Based on the attribute name msDFSR-ComputerReferenceBL, I believe that the domain function level has been raised to Windows Server 2008. Therefore, the KB article Q312862 may not apply to your environment.

     

    The error means that the value of the attribute msDFSR-ComputerReferenceBL is not correct. You can verify it by performing the following steps:

     

    1.    On the Domain Controller, open Active Directory Users and Computers console.

    2.    In the console, select Domain Controllers, and then double-click the DC object AD2008 in the right pane.

    3.    Cliekt the tab “Attribute Editor, click the button Filter, and then check the Backlinks.

    4.    After that you should see the attribute msDFSR-ComputerReferenceBL. The expected value is CN=AD2008,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,Cn=system, DC=abc,DC=com.

     

    If you need further assistance, please use the utility ldifde to export the following objects:

     

    ·         Ldifde –f computer.txt –d “CN=AD2008,OU=Domain Controllers,DC=abc,DC=com”

    ·         Ldifde –f dfsr.txt –d “CN=Domain System Volume,CN=DFSR-GlobalSettings,Cn=system, DC=abc,DC=com”

     

    And then, upload the files (computer.txt and dfsr.txt) to the following space:

     

    https://sftasia.one.microsoft.com/choosetransfer.aspx?key=0614749e-437f-4369-9c45-9dc96de38a5a

    Password: rji%+WRX)e

     

    I will check the files and provide more detailed steps.

    Tuesday, November 18, 2008 9:36 AM
    Moderator
  • Dear Joson,

    I have exactly the same problem on my 2008 domain controllers. When I follow the steps you have listed above the value for the attribute msDFSR-ComputerReferenceBL is "Not Set". I would be grateful if you could advise how I correct this problem.

    Many Thanks
    Paul
    Monday, February 9, 2009 12:15 PM
  • Hi Joson, I followed the steps you presented in your post.  However, I can not edit the attribute as it is readonly (through ADUC or ADSIEDIT).  Is there a way that I can edit this value.
    geek
    Thursday, July 23, 2009 3:36 PM
  • I believe this is from the Domain System Volume (SYSVOL Share) still living under System\File Replication Service instead of being migrated to System\DFSR-GlobalSettings (check in ADUC to verify.) 

    Before moving forward, I would run "ntfrsutl ds" to verify everything looks okay there.  If not, clean up everything according to http://support.microsoft.com/kb/312862 - I found this still applies to Windows 2008 domains even though they're not mentioned.

    Once you have that completed, running "dfsrmig /getglobalstate" (that's read only and is safe to perform any time) to find out what stage of the SYSVOL migration your domain is in.  'Start' is the default state prior to migration.  'Eliminated' is the state after full migration has been completed.  The other two states are 'Prepared' and 'Redirected'.

    To migrate completely through to the 'Elminiated' state you would run the command "dfsrmig /setglobalstate 3".  I would recommend running the migration to each state by running "dfsrmig /setglobalstate 1" to move to the 'Prepared' state.  Check your state after each step by running "dfsrmig /getglobalstate".  Wait until all of your domain controllers are at the same state before moving to the next state.  Running "dfsrmig /setglobalstate 2" will move to the 'Redirected' state and "dfsrmig /setglobalstate 3" will complete the migration and move to the 'Eliminated' state.

    A full article on dfsrmig can be found here:  http://technet.microsoft.com/en-us/library/dd639789(WS.10).aspx

    Hope that helps.
    • Proposed as answer by Jimmy_Martin_ Thursday, October 8, 2009 2:11 PM
    Thursday, October 8, 2009 2:11 PM
  • I believe this is from the Domain System Volume (SYSVOL Share) still living under System\File Replication Service instead of being migrated to System\DFSR-GlobalSettings (check in ADUC to verify.) 

    Before moving forward, I would run "ntfrsutl ds" to verify everything looks okay there.  If not, clean up everything according to http://support.microsoft.com/kb/312862 - I found this still applies to Windows 2008 domains even though they're not mentioned.

    Once you have that completed, running "dfsrmig /getglobalstate" (that's read only and is safe to perform any time) to find out what stage of the SYSVOL migration your domain is in.  'Start' is the default state prior to migration.  'Eliminated' is the state after full migration has been completed.  The other two states are 'Prepared' and 'Redirected'.

    To migrate completely through to the 'Elminiated' state you would run the command "dfsrmig /setglobalstate 3".  I would recommend running the migration to each state by running "dfsrmig /setglobalstate 1" to move to the 'Prepared' state.  Check your state after each step by running "dfsrmig /getglobalstate".  Wait until all of your domain controllers are at the same state before moving to the next state.  Running "dfsrmig /setglobalstate 2" will move to the 'Redirected' state and "dfsrmig /setglobalstate 3" will complete the migration and move to the 'Eliminated' state.

    A full article on dfsrmig can be found here:  http://technet.microsoft.com/en-us/library/dd639789(WS.10).aspx

    Hope that helps.

    Wow, I ran a dcdiag and found this problem..

    replicate changes.
                [1] Problem: Missing Expected Value

                 Base Object: CN=IBTSDC2008,OU=Domain Controllers,DC=ibts,DC=org

                 Base Object Description: "DC Account Object"

                 Value Object Attribute Name: msDFSR-ComputerReferenceBL

                 Value Object Description: "SYSVOL FRS Member Object"

                 Recommended Action: See Knowledge Base Article: Q312862

                
                [2] Problem: Missing Expected Value

                 Base Object: CN=OMNITRON,OU=Domain Controllers,DC=ibts,DC=org

                 Base Object Description: "DC Account Object"

                 Value Object Attribute Name: msDFSR-ComputerReferenceBL

                 Value Object Description: "SYSVOL FRS Member Object"

                 Recommended Action: See Knowledge Base Article: Q312862

                
                [3] Problem: Missing Expected Value

                 Base Object: CN=HALFUS,OU=Domain Controllers,DC=ibts,DC=org

                 Base Object Description: "DC Account Object"

                 Value Object Attribute Name: msDFSR-ComputerReferenceBL

                 Value Object Description: "SYSVOL FRS Member Object"

                 Recommended Action: See Knowledge Base Article: Q312862

                
                LDAP Error 0x5e (94) - No result present in message.
             ......................... IBTSDC2008 failed test VerifyEnterpriseReferences

     

    Although I haven't seen any serious replication problems with my domain after upgrading to 2008, i have seen some minor random problems.  So I ran this command "dfsrmig /getglobalstate" and the domain is in state "start".  I had already read the KB article but it doesn't mention that particular state, so I was about to assume that this portion of the domain was in a good state.  Now I see from your post that it's not.  I will run the setglobal state commands.  Good post!

     

    Friday, October 28, 2011 8:40 PM
  • I am preparing to upgrade from Windows 2008 functional domain level to Windows 2012 and while performing the tests ahead of the migration i too got the following error and my current global state is "Start" What is the risk associated with performing the DFS migration?

          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=DCXX,OU=Domain Controllers,DC=domain,DC=ca

                 Base Object Description: "DC Account Object"

                 Value Object Attribute Name: msDFSR-ComputerReferenceBL

                 Value Object Description: "SYSVOL FRS Member Object"

                 Recommended Action: See Knowledge Base Article: Q312862

                
                [2] Problem: Missing Expected Value

                 Base Object: CN=DCXX,OU=Domain Controllers,DC=domain,DC=ca

                 Base Object Description: "DC Account Object"

                 Value Object Attribute Name: msDFSR-ComputerReferenceBL

                 Value Object Description: "SYSVOL FRS Member Object"

                 Recommended Action: See Knowledge Base Article: Q312862

                
                LDAP Error 0x5e (94) - No result present in message.
             ......................... DC07 failed test VerifyEnterpriseReferences

    Monday, September 9, 2013 7:59 PM
  • This is an older thread but since it is at the top of Google's results I thought I'd post and say I found that this may be an expected error and can be ignored.  See: http://support.microsoft.com/kb/2512643.  Running dcdiag /v /c /d /e from a 2012 R2 domain controller shows the error too, but may be because of the 2008 DC.
    Thursday, July 31, 2014 6:54 PM
  • This is an older thread but since it is at the top of Google's results I thought I'd post and say I found that this may be an expected error and can be ignored.  See: http://support.microsoft.com/kb/2512643.  Running dcdiag /v /c /d /e from a 2012 R2 domain controller shows the error too, but may be because of the 2008 DC.

    OK, so what happened to the  "Problem: Missing Expected Value" can be safely ignored ?


    /* Server Support Specialist */

    Monday, March 2, 2015 1:12 AM
  • This is an older thread but since it is at the top of Google's results I thought I'd post and say I found that this may be an expected error and can be ignored.  See: http://support.microsoft.com/kb/2512643.  Running dcdiag /v /c /d /e from a 2012 R2 domain controller shows the error too, but may be because of the 2008 DC.

    Please remember that dcdiag /e - test all the servers in the entire enterprise. Please check what you have on the screen, after running command dcdiag /v /c /d /e. I am sure you will be able to define correlation between particular server and the problem. If you want to have only listed errors, and not all the passed tests, I encourage to use parameter /q. With /q parameter it is way easier to spot issue. There is another way to find problem... Most common words in dcdiag for issues are "fail" and "error". Click left top corner in command prompt (cmd), choose Edit / Find / and write there "fail" or "error".
    • Edited by Miroslaw K Friday, May 15, 2015 4:28 PM
    Friday, May 15, 2015 9:58 AM
  • I realize this is a very old post but since it is among the top results in google I figured I would save a bunch of people a lot of the trouble.

    If you run dcdiag on a Win Server 2008 or later box and get the errors mentioned by the OP, you can safely ignore them and move on. See this article for all expected errors.

    https://support.microsoft.com/en-us/kb/2512643
    • Proposed as answer by Ken2020 Wednesday, May 24, 2017 5:13 PM
    Wednesday, June 8, 2016 12:00 AM
  • i had this error after upgrading the domain functional level from 2003 to 2008 R2

    the reason? I had nnot migrated replication mechanism to DFSR. As you can see from the error this is the reason it does not work.

    following this helped me and also got rid of the error

    https://blogs.technet.microsoft.com/filecab/2008/03/05/sysvol-migration-series-part-3-migrating-to-the-prepared-state/

    hope this helps. following joson advice does not work because you cannot add a value to the attribute causing the issue

    • Proposed as answer by metallicor Monday, June 27, 2016 8:40 AM
    Monday, June 27, 2016 8:40 AM