API tools faq
paste
Advertisement
Guest User

Terminal-Dogma DCDIAG

a guest
Dec 6th, 2015
876
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 19.74 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Directory Server Diagnosis
  3.  
  4.  
  5. Performing initial setup:
  6.  
  7. Trying to find home server...
  8.  
  9. Home Server = Terminal-Dogma
  10.  
  11. * Identified AD Forest.
  12. Done gathering initial info.
  13.  
  14.  
  15. Doing initial required tests
  16.  
  17.  
  18. Testing server: Default-First-Site-Name\TERMINAL-DOGMA
  19.  
  20. Starting test: Connectivity
  21.  
  22. ......................... TERMINAL-DOGMA passed test Connectivity
  23.  
  24.  
  25.  
  26. Doing primary tests
  27.  
  28.  
  29. Testing server: Default-First-Site-Name\TERMINAL-DOGMA
  30.  
  31. Starting test: Advertising
  32.  
  33. ......................... TERMINAL-DOGMA passed test Advertising
  34.  
  35. Starting test: FrsEvent
  36.  
  37. There are warning or error events within the last 24 hours after the
  38.  
  39. SYSVOL has been shared. Failing SYSVOL replication problems may cause
  40.  
  41. Group Policy problems.
  42. ......................... TERMINAL-DOGMA passed test FrsEvent
  43.  
  44. Starting test: DFSREvent
  45.  
  46. ......................... TERMINAL-DOGMA passed test DFSREvent
  47.  
  48. Starting test: SysVolCheck
  49.  
  50. ......................... TERMINAL-DOGMA passed test SysVolCheck
  51.  
  52. Starting test: KccEvent
  53.  
  54. ......................... TERMINAL-DOGMA passed test KccEvent
  55.  
  56. Starting test: KnowsOfRoleHolders
  57.  
  58. ......................... TERMINAL-DOGMA passed test
  59.  
  60. KnowsOfRoleHolders
  61.  
  62. Starting test: MachineAccount
  63.  
  64. ......................... TERMINAL-DOGMA passed test MachineAccount
  65.  
  66. Starting test: NCSecDesc
  67.  
  68. ......................... TERMINAL-DOGMA passed test NCSecDesc
  69.  
  70. Starting test: NetLogons
  71.  
  72. ......................... TERMINAL-DOGMA passed test NetLogons
  73.  
  74. Starting test: ObjectsReplicated
  75.  
  76. ......................... TERMINAL-DOGMA passed test ObjectsReplicated
  77.  
  78. Starting test: Replications
  79.  
  80. [Replications Check,TERMINAL-DOGMA] A recent replication attempt
  81.  
  82. failed:
  83.  
  84. From CENTRAL-DOGMA to TERMINAL-DOGMA
  85.  
  86. Naming Context: DC=ForestDnsZones,DC=Nerv,DC=com
  87.  
  88. The replication generated an error (1256):
  89.  
  90. The remote system is not available. For information about network troubleshooting, see Windows Help.
  91.  
  92.  
  93.  
  94. The failure occurred at 2015-12-05 20:54:01.
  95.  
  96. The last success occurred at 2015-10-26 22:47:30.
  97.  
  98. 963 failures have occurred since the last success.
  99.  
  100. [CENTRAL-DOGMA] DsBindWithSpnEx() failed with error -2146893022,
  101.  
  102. The target principal name is incorrect..
  103. [Replications Check,TERMINAL-DOGMA] A recent replication attempt
  104.  
  105. failed:
  106.  
  107. From CENTRAL-DOGMA to TERMINAL-DOGMA
  108.  
  109. Naming Context: DC=DomainDnsZones,DC=Nerv,DC=com
  110.  
  111. The replication generated an error (1256):
  112.  
  113. The remote system is not available. For information about network troubleshooting, see Windows Help.
  114.  
  115.  
  116.  
  117. The failure occurred at 2015-12-05 20:54:01.
  118.  
  119. The last success occurred at 2015-10-26 22:47:30.
  120.  
  121. 961 failures have occurred since the last success.
  122.  
  123. [Replications Check,TERMINAL-DOGMA] A recent replication attempt
  124.  
  125. failed:
  126.  
  127. From CENTRAL-DOGMA to TERMINAL-DOGMA
  128.  
  129. Naming Context: CN=Schema,CN=Configuration,DC=Nerv,DC=com
  130.  
  131. The replication generated an error (-2146893022):
  132.  
  133. The target principal name is incorrect.
  134.  
  135. The failure occurred at 2015-12-05 20:54:01.
  136.  
  137. The last success occurred at 2015-10-26 22:47:30.
  138.  
  139. 961 failures have occurred since the last success.
  140.  
  141. [Replications Check,TERMINAL-DOGMA] A recent replication attempt
  142.  
  143. failed:
  144.  
  145. From CENTRAL-DOGMA to TERMINAL-DOGMA
  146.  
  147. Naming Context: CN=Configuration,DC=Nerv,DC=com
  148.  
  149. The replication generated an error (-2146893022):
  150.  
  151. The target principal name is incorrect.
  152.  
  153. The failure occurred at 2015-12-05 20:54:01.
  154.  
  155. The last success occurred at 2015-10-26 22:47:29.
  156.  
  157. 961 failures have occurred since the last success.
  158.  
  159. [Replications Check,TERMINAL-DOGMA] A recent replication attempt
  160.  
  161. failed:
  162.  
  163. From CENTRAL-DOGMA to TERMINAL-DOGMA
  164.  
  165. Naming Context: DC=Nerv,DC=com
  166.  
  167. The replication generated an error (-2146893022):
  168.  
  169. The target principal name is incorrect.
  170.  
  171. The failure occurred at 2015-12-05 20:54:01.
  172.  
  173. The last success occurred at 2015-10-26 22:47:29.
  174.  
  175. 961 failures have occurred since the last success.
  176.  
  177. ......................... TERMINAL-DOGMA failed test Replications
  178.  
  179. Starting test: RidManager
  180.  
  181. ......................... TERMINAL-DOGMA passed test RidManager
  182.  
  183. Starting test: Services
  184.  
  185. ......................... TERMINAL-DOGMA passed test Services
  186.  
  187. Starting test: SystemLog
  188.  
  189. An error event occurred. EventID: 0x00000422
  190.  
  191. Time Generated: 12/05/2015 20:05:38
  192.  
  193. Event String:
  194.  
  195. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  196.  
  197.  
  198. An error event occurred. EventID: 0x00000422
  199.  
  200. Time Generated: 12/05/2015 20:10:38
  201.  
  202. Event String:
  203.  
  204. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  205.  
  206.  
  207. An error event occurred. EventID: 0x00000422
  208.  
  209. Time Generated: 12/05/2015 20:15:39
  210.  
  211. Event String:
  212.  
  213. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  214.  
  215.  
  216. An error event occurred. EventID: 0x00000422
  217.  
  218. Time Generated: 12/05/2015 20:20:39
  219.  
  220. Event String:
  221.  
  222. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  223.  
  224.  
  225. An error event occurred. EventID: 0x00000422
  226.  
  227. Time Generated: 12/05/2015 20:25:40
  228.  
  229. Event String:
  230.  
  231. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  232.  
  233.  
  234. An error event occurred. EventID: 0x00000422
  235.  
  236. Time Generated: 12/05/2015 20:30:40
  237.  
  238. Event String:
  239.  
  240. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  241.  
  242.  
  243. An error event occurred. EventID: 0x00000422
  244.  
  245. Time Generated: 12/05/2015 20:35:41
  246.  
  247. Event String:
  248.  
  249. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  250.  
  251.  
  252. An error event occurred. EventID: 0x00000422
  253.  
  254. Time Generated: 12/05/2015 20:40:41
  255.  
  256. Event String:
  257.  
  258. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  259.  
  260.  
  261. An error event occurred. EventID: 0x00000422
  262.  
  263. Time Generated: 12/05/2015 20:45:42
  264.  
  265. Event String:
  266.  
  267. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  268.  
  269.  
  270. An error event occurred. EventID: 0x40000004
  271.  
  272. Time Generated: 12/05/2015 20:48:45
  273.  
  274. Event String:
  275.  
  276. The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server central-dogma$. The target name used was NERV\CENTRAL-DOGMA$. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (NERV.COM) is different from the client domain (NERV.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
  277.  
  278. An error event occurred. EventID: 0x00000422
  279.  
  280. Time Generated: 12/05/2015 20:50:42
  281.  
  282. Event String:
  283.  
  284. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  285.  
  286.  
  287. An error event occurred. EventID: 0x40000004
  288.  
  289. Time Generated: 12/05/2015 20:54:01
  290.  
  291. Event String:
  292.  
  293. The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server central-dogma$. The target name used was E3514235-4B06-11D1-AB04-00C04FC2DCD2/65041656-2bfb-49ae-836c-268734964653/Nerv.com@Nerv.com. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (NERV.COM) is different from the client domain (NERV.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
  294.  
  295. An error event occurred. EventID: 0x00000422
  296.  
  297. Time Generated: 12/05/2015 20:55:43
  298.  
  299. Event String:
  300.  
  301. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  302.  
  303.  
  304. An error event occurred. EventID: 0x40000004
  305.  
  306. Time Generated: 12/05/2015 21:00:44
  307.  
  308. Event String:
  309.  
  310. The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server central-dogma$. The target name used was cifs/central-dogma.Nerv.com. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (NERV.COM) is different from the client domain (NERV.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
  311.  
  312. An error event occurred. EventID: 0x00000422
  313.  
  314. Time Generated: 12/05/2015 21:00:44
  315.  
  316. Event String:
  317.  
  318. The processing of Group Policy failed. Windows attempted to read the file \\Nerv.com\sysvol\Nerv.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
  319.  
  320.  
  321. An error event occurred. EventID: 0x40000004
  322.  
  323. Time Generated: 12/05/2015 21:00:45
  324.  
  325. Event String:
  326.  
  327. The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server central-dogma$. The target name used was DNS/central-dogma.nerv.com. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (NERV.COM) is different from the client domain (NERV.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
  328.  
  329. An error event occurred. EventID: 0x00000457
  330.  
  331. Time Generated: 12/05/2015 21:01:34
  332.  
  333. Event String:
  334.  
  335. Driver Adobe PDF Converter required for printer Adobe PDF is unknown. Contact the administrator to install the driver before you log in again.
  336.  
  337. An error event occurred. EventID: 0x00000457
  338.  
  339. Time Generated: 12/05/2015 21:01:37
  340.  
  341. Event String:
  342.  
  343. Driver RingCentral Internet Fax 2.1.1.0 required for printer RingCentral Internet Fax is unknown. Contact the administrator to install the driver before you log in again.
  344.  
  345. An error event occurred. EventID: 0x00000457
  346.  
  347. Time Generated: 12/05/2015 21:01:37
  348.  
  349. Event String:
  350.  
  351. Driver EPSON WF-3620 Series required for printer WF-3620 Series(Network) is unknown. Contact the administrator to install the driver before you log in again.
  352.  
  353. An error event occurred. EventID: 0x40000004
  354.  
  355. Time Generated: 12/05/2015 21:01:52
  356.  
  357. Event String:
  358.  
  359. The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server central-dogma$. The target name used was LDAP/65041656-2bfb-49ae-836c-268734964653._msdcs.Nerv.com. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (NERV.COM) is different from the client domain (NERV.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
  360.  
  361. ......................... TERMINAL-DOGMA failed test SystemLog
  362.  
  363. Starting test: VerifyReferences
  364.  
  365. ......................... TERMINAL-DOGMA passed test VerifyReferences
  366.  
  367.  
  368.  
  369. Running partition tests on : ForestDnsZones
  370.  
  371. Starting test: CheckSDRefDom
  372.  
  373. ......................... ForestDnsZones passed test CheckSDRefDom
  374.  
  375. Starting test: CrossRefValidation
  376.  
  377. ......................... ForestDnsZones passed test
  378.  
  379. CrossRefValidation
  380.  
  381.  
  382. Running partition tests on : DomainDnsZones
  383.  
  384. Starting test: CheckSDRefDom
  385.  
  386. ......................... DomainDnsZones passed test CheckSDRefDom
  387.  
  388. Starting test: CrossRefValidation
  389.  
  390. ......................... DomainDnsZones passed test
  391.  
  392. CrossRefValidation
  393.  
  394.  
  395. Running partition tests on : Schema
  396.  
  397. Starting test: CheckSDRefDom
  398.  
  399. ......................... Schema passed test CheckSDRefDom
  400.  
  401. Starting test: CrossRefValidation
  402.  
  403. ......................... Schema passed test CrossRefValidation
  404.  
  405.  
  406. Running partition tests on : Configuration
  407.  
  408. Starting test: CheckSDRefDom
  409.  
  410. ......................... Configuration passed test CheckSDRefDom
  411.  
  412. Starting test: CrossRefValidation
  413.  
  414. ......................... Configuration passed test CrossRefValidation
  415.  
  416.  
  417. Running partition tests on : Nerv
  418.  
  419. Starting test: CheckSDRefDom
  420.  
  421. ......................... Nerv passed test CheckSDRefDom
  422.  
  423. Starting test: CrossRefValidation
  424.  
  425. ......................... Nerv passed test CrossRefValidation
  426.  
  427.  
  428. Running enterprise tests on : Nerv.com
  429.  
  430. Starting test: LocatorCheck
  431.  
  432. ......................... Nerv.com passed test LocatorCheck
  433.  
  434. Starting test: Intersite
  435.  
  436. ......................... Nerv.com passed test Intersite
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!