December 2, 2008 02:55am pst

1. TechSoEasy 1,685,353
2. RobWill 961,681
3. KCTS 354,546
4. leew 292,560
5. tigermatt 258,887
6. MPECSInc 179,504
7. Sembee 176,880
8. kieran_b 176,007
9. mwecom... 164,232
10. suppsaws 160,725
11. ormerodru... 159,028
12. 18526 150,302
13. olafdc 144,452
14. Dave_AND 140,505
15. plug1 125,986
16. waynewill... 124,317
17. SysExpert 95,282
18. DrDave242 90,383
19. MrMander... 86,615
20. ryansoto 82,095
21. hypercat 78,766
22. keith_ala... 72,614
23. tomcahill 68,246
24. MarkMich... 64,017
25. Chris-Dent 63,710

1. TechSoEasy 7,077,342
2. RobWill 1,170,371
3. Sembee 831,712
4. leew 665,426
5. olafdc 608,417
6. KCTS 600,301
7. tigermatt 359,435
8. suppsaws 348,090
9. MPECSInc 294,885
10. redseatec... 254,480
11. ormerodru... 240,208
12. vico1 233,770
13. Dave_AND 224,620
14. keith_ala... 202,990
15. MrMander... 185,123
16. mwecom... 182,757
17. hypercat 178,121
18. kieran_b 176,007
19. 18526 153,802
20. SysExpert 142,450
21. sguinn100 142,295
22. MarkMich... 136,504
23. DanKoster 134,829
24. rakeshmig... 131,891
25. plug1 125,986

09.20.2008 at 08:02AM PDT, ID: 23748276

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.0

SBS Domain Migration DCDIAG issues

Asked by Michaelgoff79 in SBS Small Business Server

We attempted a domain migration a couple of weeks ago FYC-DC1 is the one we added, promoted etc, ran in to some issues during the course of the migration and the roles were given back to SERVER-FYC and the server was removed, but in running DCDIAG on Server-FYC I can see that FYC-DC1is still listed as the domain owner and now there are some replication issues with a server that does not exist. We still need to do a domain migration and I am not sure as to how I should proceed. Any comments or suggestions will be greatly appreciated.

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVER-FYC
Starting test: Connectivity
......................... SERVER-FYC passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SERVER-FYC
Starting test: Replications
[Replications Check,SERVER-FYC] A recent replication attempt failed:
From FYC-DC1 to SERVER-FYC
Naming Context: DC=ForestDnsZones,DC=FYCNET,DC=local
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2008-09-20 08:49:10.
The last success occurred at 2008-08-30 17:45:45.
498 failures have occurred since the last success.
[FYC-DC1] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,SERVER-FYC] A recent replication attempt failed:
From FYC-DC1 to SERVER-FYC
Naming Context: DC=DomainDnsZones,DC=FYCNET,DC=local
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2008-09-20 08:49:10.
The last success occurred at 2008-08-30 17:52:53.
498 failures have occurred since the last success.
[Replications Check,SERVER-FYC] A recent replication attempt failed:
From FYC-DC1 to SERVER-FYC
Naming Context: CN=Schema,CN=Configuration,DC=FYCNET,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2008-09-20 08:49:52.
The last success occurred at 2008-08-30 17:45:44.
498 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,SERVER-FYC] A recent replication attempt failed:
From FYC-DC1 to SERVER-FYC
Naming Context: CN=Configuration,DC=FYCNET,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2008-09-20 08:49:31.
The last success occurred at 2008-08-30 17:45:44.
498 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,SERVER-FYC] A recent replication attempt failed:
From FYC-DC1 to SERVER-FYC
Naming Context: DC=FYCNET,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2008-09-20 08:49:10.
The last success occurred at 2008-08-30 17:47:51.
498 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION-RECEIVED LATENCY WARNING
SERVER-FYC: Current time is 2008-09-20 09:45:08.
DC=ForestDnsZones,DC=FYCNET,DC=local
Last replication recieved from FYC-DC1 at 2008-08-30 17:44:26.
DC=DomainDnsZones,DC=FYCNET,DC=local
Last replication recieved from FYC-DC1 at 2008-08-30 17:51:34.
CN=Schema,CN=Configuration,DC=FYCNET,DC=local
Last replication recieved from FYC-DC1 at 2008-08-30 17:44:26.
CN=Configuration,DC=FYCNET,DC=local
Last replication recieved from FYC-DC1 at 2008-08-30 17:44:26.
DC=FYCNET,DC=local
Last replication recieved from FYC-DC1 at 2008-08-30 17:46:32.
......................... SERVER-FYC passed test Replications
Starting test: NCSecDesc
......................... SERVER-FYC passed test NCSecDesc
Starting test: NetLogons
......................... SERVER-FYC passed test NetLogons
Starting test: Advertising
......................... SERVER-FYC passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: FYC-DC1 is the Domain Owner, but is not responding to DS RPC Bind.
[FYC-DC1] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
Warning: FYC-DC1 is the Domain Owner, but is not responding to LDAP Bind.
......................... SERVER-FYC failed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER-FYC passed test RidManager
Starting test: MachineAccount
......................... SERVER-FYC passed test MachineAccount
Starting test: Services
IsmServ Service is stopped on [SERVER-FYC]
......................... SERVER-FYC failed test Services
Starting test: ObjectsReplicated
......................... SERVER-FYC passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER-FYC passed test frssysvol
Starting test: frsevent
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.
......................... SERVER-FYC failed test frsevent
Starting test: kccevent
......................... SERVER-FYC passed test kccevent
Starting test: systemlog
......................... SERVER-FYC passed test systemlog
Starting test: VerifyReferences
......................... SERVER-FYC passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : FYCNET
Starting test: CrossRefValidation
......................... FYCNET passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... FYCNET passed test CheckSDRefDom

Running enterprise tests on : FYCNET.local
Starting test: Intersite
......................... FYCNET.local passed test Intersite
Starting test: FsmoCheck
......................... FYCNET.local passed test FsmoCheck
Start Free Trial

Keywords: SBS Domain Migration DCDIAG issues

	Title
1	Active Directory (dcdiag)
2	LDAP latency issue in Exchange v2
3	Dcdiag failing [CSLDC01] DsBindWi…
4	SBS 2003 dcdiag problem
5	Microsoft, sbs 2003, SP 1, dns…
6	DCDiag errors

Loading Advertisement...

20080716-EE-VQP-32 / EE_QW_2_20070628

SBS Domain Migration DCDIAG issues

Asked by Michaelgoff79 in SBS Small Business Server

About this solution