Возникла ошибка код события eventid 0x000016ad

Posted by ZooM_00 2019-03-03T11:52:24Z

• 

  Interesting topic. Subscribed so I too can learn from it.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  I Wonder if there’s a way to delete this replication group and re-create it, and if that would actually solve the issue,

  However, I can’t seem to find a way to delete it

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• You won’t be be able to manage Sysvol with the dfsrdiag command or the DFS console. It is a protected replication group.

  For troubleshooting please post the output this.  From a known good DC and the one that is not working. You can obfuscate the DC names as you see fit.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  You won’t be be able to manage Sysvol with the dfsrdiag command or the DFS console. It is a protected replication group.

  For troubleshooting please post the output this.  From a known good DC and the one that is not working. You can obfuscate the DC names as you see fit.

  Hi Justin,

  Thank you for your reply,

  output below, I believe that FRS is not configured and supposed not to be working, I don’t understand why it’s flagged as an error, 

  

  Can you advise on next step?

  Zoom,

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Have you migrated from FRS to DFSR and did the migration succeed?  One of the errors above is the FRS service being disabled which it shouldn’t be unless your DFSR migration was done and was successful.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  This is the output when running the command on AD02

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Also looks like your DNS settings are incorrect.  Ensure that DC1 points to DC2 for its primary DNS and itself as secondary.  Ensure that DC2 points to DC1 for its primary and itself as secondary.  Ensure that external DNS servers, including your router, are defined nowhere except in the forwarders tab of the DNS management tool.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Da_Schmoo wrote:

  Also looks like your DNS settings are incorrect.  Ensure that DC1 points to DC2 for its primary DNS and itself as secondary.  Ensure that DC2 points to DC1 for its primary and itself as secondary.  Ensure that external DNS servers, including your router, are defined nowhere except in the forwarders tab of the DNS management tool.

  Setting DC1 DNS to: DC2 then DC1

  and DC2 to: DC1 then DC2 seems to have caused me many issues,

  My DC1 was set to 127.0.0.1 only, DC2 was DC1 then DC2

  Forwarder was configured to 8.8.8.8 on both DNS servers

  below is output of dcdiag /v /c /e /q after the modification of DNS

  Text

  C:UsersUser.MYDOMAIN>dcdiag /v /c /e /q
           [MYDOMAIN-AD01] No security related replication errors were found on this DC!  To target the connection to a
           specific source DC use /ReplSource:<DC>.
           ** Did not run Outbound Secure Channels test because /testdomain: was not entered
              Invalid service startup type: NtFrs on MYDOMAIN-AD01, current value DISABLED, expected value AUTO_START
              NtFrs Service is stopped on [MYDOMAIN-AD01]
           ......................... MYDOMAIN-AD01 failed test Services
           An error event occurred.  EventID: 0x80001778
              Time Generated: 03/03/2019   20:49:08
              Event String: The previous system shutdown at 8:42:23 PM on 3/3/2019 was unexpected.
           An error event occurred.  EventID: 0xC004002E
              Time Generated: 03/03/2019   20:47:45
              Event String: Crash dump initialization failed!
           An error event occurred.  EventID: 0x00000029
              Time Generated: 03/03/2019   20:47:47
              Event String:
              The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
           An error event occurred.  EventID: 0x0000410B
              Time Generated: 03/03/2019   20:49:45
              Event String:
              The request for a new account-identifier pool failed. The operation will be retried until the request succeeds. The error is
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   20:51:00
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   20:55:37
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1b0c (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   20:58:14
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   20:58:14
              Event String:
              The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   21:03:43
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:05:06
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1adc (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:05:06
              Event String:
              DCOM was unable to communicate with the computer 168.63.129.16 using any of the configured protocols; requested by PID     1adc (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:16:30
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1940 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:16:30
              Event String:
              DCOM was unable to communicate with the computer 168.63.129.16 using any of the configured protocols; requested by PID     1940 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000165B
              Time Generated: 03/03/2019   21:25:05
              Event String:
              The session setup from computer 'PC1-A213' failed because the security database does not contain a trust account 'PC1-A213$' referenced by the specified computer.
           An error event occurred.  EventID: 0x000016AD
              Time Generated: 03/03/2019   21:27:29
              Event String:
              The session setup from the computer PC1-A213 failed to authenticate. The following error occurred:
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:32:54
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1870 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:32:54
              Event String:
              DCOM was unable to communicate with the computer 168.63.129.16 using any of the configured protocols; requested by PID     1870 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:36:40
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1aa0 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:36:40
              Event String:
              DCOM was unable to communicate with the computer 168.63.129.16 using any of the configured protocols; requested by PID     1aa0 (C:Windowssystem32dcdiag.exe).
           ......................... MYDOMAIN-AD01 failed test SystemLog
           Some objects relating to the DC MYDOMAIN-AD01 have problems:
              [1] Problem: Missing Expected Value
               Base Object: CN=MYDOMAIN-AD01,OU=Domain Controllers,DC=ad,DC=MYDOMAIN,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
  
           ......................... MYDOMAIN-AD01 failed test VerifyReferences
           [MYDOMAIN-AD02] No security related replication errors were found on this DC!  To target the connection to a
           specific source DC use /ReplSource:<DC>.
           There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL
           replication problems may cause Group Policy problems.
           ......................... MYDOMAIN-AD02 failed test DFSREvent
           ** Did not run Outbound Secure Channels test because /testdomain: was not entered
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   20:46:51
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   20:46:52
              Event String:
              The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   20:46:52
              Event String:
              The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x00000469
              Time Generated: 03/03/2019   20:49:00
              Event String:
              The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   20:49:02
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000410B
              Time Generated: 03/03/2019   20:49:50
              Event String:
              The request for a new account-identifier pool failed. The operation will be retried until the request succeeds. The error is
           An error event occurred.  EventID: 0x00000469
              Time Generated: 03/03/2019   20:49:56
              Event String:
              The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   20:49:58
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000168E
              Time Generated: 03/03/2019   20:50:13
              Event String:
              The dynamic registration of the DNS record '_ldap._tcp.Azure._sites.ad.MYDOMAIN.com. 600 IN SRV 0 100 389 MYDOMAIN-AD02.ad.MYDOMAIN.com.' failed on the following DNS server:
           An error event occurred.  EventID: 0x0000165B
              Time Generated: 03/03/2019   20:54:52
              Event String:
              The session setup from computer 'PC1-A213' failed because the security database does not contain a trust account 'PC1-A213$' referenced by the specified computer.
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   20:56:32
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1ba8 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   20:58:13
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   20:58:14
              Event String:
              The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   20:58:14
              Event String:
              The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   20:59:25
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x00000469
              Time Generated: 03/03/2019   20:59:31
              Event String:
              The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
           An error event occurred.  EventID: 0x00000469
              Time Generated: 03/03/2019   20:59:34
              Event String:
              The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   21:00:48
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1a28 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   21:01:14
              Event String:
              The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   21:01:35
              Event String:
              The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x0000165B
              Time Generated: 03/03/2019   21:09:57
              Event String:
              The session setup from computer 'PC1-A213' failed because the security database does not contain a trust account 'PC1-A213$' referenced by the specified computer.
           An error event occurred.  EventID: 0x000016AD
              Time Generated: 03/03/2019   21:12:07
              Event String:
              The session setup from the computer PC1-A213 failed to authenticate. The following error occurred:
           ......................... MYDOMAIN-AD02 failed test SystemLog
  

  Do you have any handy tutorial on how to troubleshoot and fix DNS in such cases?

  I feel like things are getting more and more complicated!

  Zoom,

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Da_Schmoo wrote:

  Have you migrated from FRS to DFSR and did the migration succeed?  One of the errors above is the FRS service being disabled which it shouldn’t be unless your DFSR migration was done and was successful.

  This is a recent setup, I believe FRS was never configured here, they went directly to DFSR

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• I still think you have external DNS set on the DC’s — DCDiag is complaining about 8.8.8.8 and another external address.  It shouldn’t be doing that unless those addresses are configured somewhere outside of the Forwarder’s tab.  

  It’s also complaining that the FRS service is disabled.  If you really are using DFSR it shouldn’t complain about that service being disabled.

  See what 

  Dfsrmig /getmigrationstate  shows.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Da_Schmoo wrote:

  Also looks like your DNS settings are incorrect.  Ensure that DC1 points to DC2 for its primary DNS and itself as secondary.  Ensure that DC2 points to DC1 for its primary and itself as secondary.  Ensure that external DNS servers, including your router, are defined nowhere except in the forwarders tab of the DNS management tool.

  It’s mentioned here Opens a new window, that :

  Text

  If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners.
  

  I found that loopback ip is the only DNS server for my DC01, I’ll put more time into DNS tomorrow, I’m done for today!!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Da_Schmoo wrote:

  I still think you have external DNS set on the DC’s — DCDiag is complaining about 8.8.8.8 and another external address.  It shouldn’t be doing that unless those addresses are configured somewhere outside of the Forwarder’s tab.  

  It’s also complaining that the FRS service is disabled.  If you really are using DFSR it shouldn’t complain about that service being disabled.

  See what 

  Dfsrmig /getmigrationstate  shows.

  I get your point, Migstate indicates that AD is in Start state, yet globalstate indicates that it’s in eliminated state:

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• The results on any of the diagnostic tools are suspect until your get your DNS in order.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Da_Schmoo wrote:

  The results on any of the diagnostic tools are suspect until your get your DNS in order.

  I Agree,

  To Sum it up:

  DC1 DNS should be: DC2 then Loopback IP

  DC2 DNS: DC1 then Loopback IP

  8.8.8.8 should only be configured like this:

  

  A restart for both DCs then? anything else?

  I really appreciate you support, thank you,

  Zoom,

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• That looks right.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  So I revised my DNS configs:

  output:

  Text

  C:UsersUser>dcdiag /v /c /e /q
           [MYDOMAIN-AD01] No security related replication errors were found on this DC!  To target the connection to a specific source DC use /ReplSource:<DC>.
           An error event occurred.  EventID: 0xC0000827
              Time Generated: 03/03/2019   22:30:04
              Event String:
              Active Directory Domain Services could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory Domain Services from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
           ......................... MYDOMAIN-AD01 failed test KccEvent
           ** Did not run Outbound Secure Channels test because /testdomain: was not entered
              Invalid service startup type: NtFrs on MYDOMAIN-AD01, current value DISABLED, expected value AUTO_START
              NtFrs Service is stopped on [MYDOMAIN-AD01]
           ......................... MYDOMAIN-AD01 failed test Services
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   22:28:28
              Event String: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   22:28:28
              Event String: The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   22:28:28
              Event String: The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   22:28:28
              Event String: The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   22:34:07
              Event String: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   22:39:17
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     1244 (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   22:39:17
              Event String:
              DCOM was unable to communicate with the computer 168.63.129.16 using any of the configured protocols; requested by PID     1244 (C:Windowssystem32dcdiag.exe).
           ......................... MYDOMAIN-AD01 failed test SystemLog
           Some objects relating to the DC MYDOMAIN-AD01 have problems:
              [1] Problem: Missing Expected Value
               Base Object: CN=MYDOMAIN-AD01,OU=Domain Controllers,DC=ad,DC=MYDOMAIN,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
  
           ......................... MYDOMAIN-AD01 failed test VerifyReferences
           [MYDOMAIN-AD02] No security related replication errors were found on this DC!  To target the connection to a specific source DC use /ReplSource:<DC>.
           There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL replication problems may cause Group Policy
           problems.
           ......................... MYDOMAIN-AD02 failed test DFSREvent
           An error event occurred.  EventID: 0xC0000827
              Time Generated: 03/03/2019   22:29:47
              Event String:
              Active Directory Domain Services could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory Domain Services from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
           ......................... MYDOMAIN-AD02 failed test KccEvent
           ** Did not run Outbound Secure Channels test because /testdomain: was not entered
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   22:28:27
              Event String: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000271A
              Time Generated: 03/03/2019   22:28:28
              Event String: The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
           An error event occurred.  EventID: 0x00000469
              Time Generated: 03/03/2019   22:29:35
              Event String:
              The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   22:29:42
              Event String: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x00002720
              Time Generated: 03/03/2019   22:31:00
              Event String: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
           An error event occurred.  EventID: 0x0000165B
              Time Generated: 03/03/2019   22:40:33
              Event String:
              The session setup from computer 'PC1-A213' failed because the security database does not contain a trust account 'PC1-A213$' referenced by the specified computer.
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   22:40:55
              Event String:
              DCOM was unable to communicate with the computer 168.63.129.16 using any of the configured protocols; requested by PID     16bc (C:Windowssystem32dcdiag.exe).
           An error event occurred.  EventID: 0x0000272C
              Time Generated: 03/03/2019   22:40:55
              Event String:
              DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID     16bc (C:Windowssystem32dcdiag.exe).
           ......................... MYDOMAIN-AD02 failed test SystemLog
        Test results for domain controllers:
  
           DC: MYDOMAIN-AD01.ad.MYDOMAIN.com
           Domain: ad.MYDOMAIN.com
  
  
              TEST: Records registration (RReg)
                 Error: Record registrations cannot be found for all the network adapters
  
           Summary of DNS test results:
  
                                              Auth Basc Forw Del  Dyn  RReg Ext
              _________________________________________________________________
              Domain: ad.MYDOMAIN.com
                 MYDOMAIN-AD01                   PASS WARN PASS PASS PASS FAIL n/a
  
           ......................... ad.MYDOMAIN.com failed test DNS
  

  Dfsrmig /getmigrationstate  still reports AD01 to be in «start» State,

  @Da_schmoo

  Could you please let me know if there’s anything dangerous that might cause my DC to cease working? 

  Zoom,

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Set the startup type of the File Replication Service to Automatic and start it.  Some of your errors are because of that.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Running: Repadmin /Syncall and Repadmin /Syncall /AdeP returned no errors

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Da_Schmoo wrote:

  Set the startup type of the File Replication Service to Automatic and start it.  Some of your errors are because of that.

  It won’t start

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Missing with the «CN=DFSR-LocalSettings» led the following:

  

  Is there a way to set up DFSR from scratch? or is it time to buy a Microsoft Incident Support ticket?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  adam344

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  New contributor
  sonora

  I am actually having the very same issue. We had an existing 2012 server, implemented a 2019 server, dcpromo and sysvol is having issues. Almost identical to what you’re experiencing. 

  
  1 found this helpful
  thumb_up
  thumb_down
  

• I think your issue is your FRS to DFSR  migration didn’t complete.  One server thinks it’s done, the other doesn’t.  This is likely due to your DNS not being configured properly.  Getting the file replication service running on the server it isn’t may let the process complete or you might be able to restart the process.

  I’d focus on seeing why you can’t start the service — System Event Log may give an answer to that.

  As far as dropping the $500 to have Microsoft fix the issue — I think you’re past the point where I would have done that but I’d try to fix the FRS service issue myself first.

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  adam344 wrote:

  I am actually having the very same issue. We had an existing 2012 server, implemented a 2019 server, dcpromo and sysvol is having issues. Almost identical to what you’re experiencing. 

  The case for me is different, the setup is new, implemented immediately on W2k16, no upgrades, nothing. It was done for my client by an IT service provider, signed off, and considered operational, I just took over the project.

  I have no idea if FRS was ever configured or no, replication never actually worked. But I just found out now after joining 2k+ pcs, I found out when we started creating GPOs.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Da_Schmoo wrote:

  I think your issue is your FRS to DFSR  migration didn’t complete.  One server thinks it’s done, the other doesn’t.  This is likely due to your DNS not being configured properly.  Getting the file replication service running on the server it isn’t may let the process complete or you might be able to restart the process.

  I’d focus on seeing why you can’t start the service — System Event Log may give an answer to that.

  As far as dropping the $500 to have Microsoft fix the issue — I think you’re past the point where I would have done that but I’d try to fix the FRS service issue myself first.

  I tried going through the migration, set state to 1,2,3. but always returning that the selected state is invalid.

  I don’t know how to troubleshoot the DNS, or how to start, I did exactly as you recommended, can you recommend any articles for that?

  As I said earlier, I doubt that the FRS service ever worked.

  What is the worst case scenario here? would demoting a DC, cleaning it up, and promoting it again solve the issue?

  Zoom,

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Microsoft has been working on this for two days now, and it doesn’t seem that they are close to solve it

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Finally I received a procedure from MS to fix this, tested it on my lab environment, it worked fine, 

  Gonna do it during weekend, and will post the method and result after that

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  OP
  ZooM_00

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  anaheim

  Hello,

  Finally I got this solved with Microsoft support,

  I’ve published a «How-To» to explain the solution, find it here:

  https://community.spiceworks.com/how_to/160786-how-to-re-build-sysvol-dfsr-replication-group-without…

  
  Was this post helpful?
  thumb_up
  thumb_down