Active Directory problems/dcdiag error
in [Windows Servers]
|
Prev: CAL's
Next: File Has No Owner, Cannot Be Deleted
From: kj [SBS MVP] on 24 Mar 2010 13:06 Yikes. So, 180 days is a critical time in which to ensure replicaiton completes. In the repadmin command, it's more important when it was last successfull not the current fail. Do a repadmin /showrepl and post the entire unedited output. Missing the ismserv is going to continue to be an issue. May be the root of the problem for that matter. first try a net start ismserv & post the output - If it fails, check the %windir% \system32 directory for the ism*.* files ( should be four of them ). If they are there then its possible the dll's need to be reregistered. You might consider putting in a call to MS support for this issue. There is a 180 day "tombstone lifetime" that is essential that you get this resolved and it sounds like you are getting close to this time frame already. ( if not already exceeded). Do you have the two locations defined as seperate AD sites with unique subnets? ( if you do not have them defined, do not do it until MS instructed or until you get replication resolved.) Wael wrote: > On Mar 23, 5:26 pm, "kj [SBS MVP]" <KevinJ....(a)SPAMFREE.gmail.com> > wrote: >> OK, for starters server 1 should have both server1 and server2 for >> DNS client configurations >> >> Server 2 should have server 2 and server1 for DNS client settings ( >> both in repesctive orders) > > Done. I scheduled the restart for the early morning because those > servers are heavily used until midnight. I noticed that some dcdiag > issues were resolved (even though i did not yet restart). The problem > that remains now is the time service issue. > >> >>> IP Address. . . . . . . . . . . . : 192.168.168.1 >> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> >>> Default Gateway . . . . . . . . . : 192.168.168.81 >> >>> DNS Servers . . . . . . . . . . . : 192.168.168.1 >> >> <add> DNS Servers . . . . . . . . . . . : 192.168.169.2 >> >> >> >>> Primary WINS Server . . . . . . . : 192.168.168.1 >> ??????? >>> Primary WINS Server . . . . . . . : 192.168.169.2 >> >> Do you have WINS replication configured? If not you probably want to >> settle on one WINS server or setup WINS replication and add >> Secondary WINS servers to both DCs. >> > > Done. I verified the configuration, still getting errors with dcdiag > though. Let's see what happens after the restart tonight. > > >> SBS server has ISMserv (Intersite messaging service) disabled by >> default. You should go into services and enable and start this >> service ( make sure its's running on both DCs). Is the other server >> a windows 2000 server or something more recent? >> > > > I couldn't find this service (or any variations for the name) on SBS. > I found it on the member server (Intersite Messaging) and it was > already started. Any idea why it is not showing in the list of > services? > >> Right not your DCs are not replicating well. How long has this >> configuration existed? >> > > 6 months probably. > >> Server 2 appears to have a second NIC that is not connected. If true >> it's better to disable it. Later OS versions can have binding order >> problems in DCs with two or more enabled NICs. >> > > It is disabled. I am using Windows 2003 SBS and R1 > >> After that, reboot the SBS server, run a fresh dcdiag, and also a >> "repadmin /replsummary" > > This test showed 0/5 errors. >> >> btw, is this SBS 2003 or SBS 2008? -- /kj
From: Wael on 24 Mar 2010 14:05 On Mar 24, 1:06 pm, "kj [SBS MVP]" <KevinJ....(a)SPAMFREE.gmail.com> wrote: > Yikes. So, 180 days is a critical time in which to ensure replicaiton > completes. > Actually I don't think there was a big problem with replication, otherwise i would've probably noticed. In the "File Replication Service" section of the event viewer the errors are months apart, but anyway I am posting the results of the replication below. > In the repadmin command, it's more important when it was last successfull > not the current fail. > > Do a repadmin /showrepl and post the entire unedited output. > > Missing the ismserv is going to continue to be an issue. May be the root of > the problem for that matter. > > first try a net start ismserv & post the output > I did "ismserv /install" and now it shows in the list of services. I also started the newly installed service afterwards. DCDiag still shows the same errors. I will post them separately shortly. This should make the thread easier to follow (I hope) > - If it fails, check the %windir% \system32 directory for the ism*.* files > ( should be four of them ). If they are there then its possible the dll's > need to be reregistered. You might consider putting in a call to MS support > for this issue. > > There is a 180 day "tombstone lifetime" that is essential that you get this > resolved and it sounds like you are getting close to this time frame > already. ( if not already exceeded). > I am not sure what this "tombstone" is. I noticed in the WINS server there were entries marked as "tombstones". I deleted those entries that I know belong to computers external to our organization. > Do you have the two locations defined as seperate AD sites with unique > subnets? ( if you do not have them defined, do not do it until MS instructed > or until you get replication resolved.) > repadmin running command /showrepl against server localhost Westmount\Server1 DC Options: IS_GC Site Options: IS_GROUP_CACHING_ENABLED DC object GUID: c022f83e-c0aa-451c-8fa4-2a089356de62 DC invocationID: c022f83e-c0aa-451c-8fa4-2a089356de62 ==== INBOUND NEIGHBORS ====================================== DC=MyOrganization,DC=local Branch-Office\Server2 via RPC DC object GUID: a675e995-26a8-4c18-9e0e-88b72f76b63d Last attempt @ 2010-03-24 13:49:59 was successful. CN=Configuration,DC=MyOrganization,DC=local Branch-Office\Server2 via RPC DC object GUID: a675e995-26a8-4c18-9e0e-88b72f76b63d Last attempt @ 2010-03-24 13:49:59 was successful. CN=Schema,CN=Configuration,DC=MyOrganization,DC=local Branch-Office\Server2 via RPC DC object GUID: a675e995-26a8-4c18-9e0e-88b72f76b63d Last attempt @ 2010-03-24 13:49:59 was successful. DC=DomainDnsZones,DC=MyOrganization,DC=local Branch-Office\Server2 via RPC DC object GUID: a675e995-26a8-4c18-9e0e-88b72f76b63d Last attempt @ 2010-03-24 13:49:59 was successful. DC=ForestDnsZones,DC=MyOrganization,DC=local Branch-Office\Server2 via RPC DC object GUID: a675e995-26a8-4c18-9e0e-88b72f76b63d Last attempt @ 2010-03-24 13:50:00 was successful.
From: Wael on 24 Mar 2010 14:10 On Mar 24, 2:05 pm, Wael <sedk...(a)gmail.com> wrote: > On Mar 24, 1:06 pm, "kj [SBS MVP]" <KevinJ....(a)SPAMFREE.gmail.com> > wrote: > > > Yikes. So, 180 days is a critical time in which to ensure replicaiton > > completes. > Below is the result for DCDiag. For my previous posting "Westmount" = "Location1" Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Location1\Server1 Starting test: Connectivity ......................... Server1 passed test Connectivity Doing primary tests Testing server: Location1\Server1 Starting test: Replications ......................... Server1 passed test Replications Starting test: NCSecDesc ......................... Server1 passed test NCSecDesc Starting test: NetLogons ......................... Server1 passed test NetLogons Starting test: Advertising Warning: Server1 is not advertising as a time server. ......................... Server1 failed test Advertising Starting test: KnowsOfRoleHolders ......................... Server1 passed test KnowsOfRoleHolders Starting test: RidManager ......................... Server1 passed test RidManager Starting test: MachineAccount ......................... Server1 passed test MachineAccount Starting test: Services ......................... Server1 passed test Services Starting test: ObjectsReplicated ......................... Server1 passed test ObjectsReplicated Starting test: frssysvol ......................... Server1 passed test frssysvol Starting test: frsevent ......................... Server1 passed test frsevent Starting test: kccevent An Error Event occured. EventID: 0xC0000520 Time Generated: 03/24/2010 13:54:58 Event String: A call to the Intersite Messaging service that An Error Event occured. EventID: 0xC000051F Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) has An Warning Event occured. EventID: 0x80000749 Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) was An Error Event occured. EventID: 0xC0000520 Time Generated: 03/24/2010 13:54:58 Event String: A call to the Intersite Messaging service that An Error Event occured. EventID: 0xC000051F Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) has An Warning Event occured. EventID: 0x80000749 Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) was An Error Event occured. EventID: 0xC0000520 Time Generated: 03/24/2010 13:54:58 Event String: A call to the Intersite Messaging service that An Error Event occured. EventID: 0xC000051F Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) has An Warning Event occured. EventID: 0x80000749 Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) was An Error Event occured. EventID: 0xC0000520 Time Generated: 03/24/2010 13:54:58 Event String: A call to the Intersite Messaging service that An Error Event occured. EventID: 0xC000051F Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) has An Warning Event occured. EventID: 0x80000749 Time Generated: 03/24/2010 13:54:58 Event String: The Knowledge Consistency Checker (KCC) was An Error Event occured. EventID: 0xC0000713 Time Generated: 03/24/2010 13:58:14 Event String: The Intersite Messaging Service encountered an ......................... Server1 failed test kccevent Starting test: systemlog An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:04 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:05 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:06 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:07 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:09 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:10 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:10 (Event String could not be retrieved) An Error Event occured. EventID: 0x00000457 Time Generated: 03/24/2010 13:52:11 (Event String could not be retrieved) ......................... Server1 failed test systemlog Starting test: VerifyReferences ......................... Server1 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 : MyOrganization Starting test: CrossRefValidation ......................... MyOrganization passed test CrossRefValidation Starting test: CheckSDRefDom ......................... MyOrganization passed test CheckSDRefDom Running enterprise tests on : MyOrganization.local Starting test: Intersite ......................... MyOrganization.local passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A Good Time Server could not be located. ......................... MyOrganization.local failed test FsmoCheck
From: Wael on 24 Mar 2010 16:01 It's me again. Now it seems all the errors are resolved except for the time server. > Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 > A Time Server could not be located. > The server holding the PDC role is down. > Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, > error 1355 > A Good Time Server could not be located. > ......................... MyOrganization.local failed test > FsmoCheck w32tm /monitor shows Getting DC list for default domain... Analyzing: 1 -- (0 of 2) Analyzing: -- 2 (1 of 2) Analyzing: -- 2 (1 of 2) resolving referer 209.87.233.53 (1 of 2)... resolving referer 209.87.233.53 (2 of 2)... Server1.MyOrganization.local *** PDC *** [192.168.168.1]: ICMP: 0ms delay. NTP: +0.0000000s offset from Server1.MyOrganization.local RefID: time1.chu.nrc.ca [209.87.233.53] Server2.MyOrganization.local [192.168.169.2]: ICMP: 400ms delay. NTP: -0.0127315s offset from Server1.MyOrganization.local RefID: time1.chu.nrc.ca [209.87.233.53]
From: kj [SBS MVP] on 24 Mar 2010 16:17
Things are getting better. ISMserv is needed for ISTG and KCC. On the SBS server you should set the service type to auto. You should define AD sites (ad sites and services) and subnets assigning each of the two DCs to it's own site. So, the PDCe role seems to be the last issue besides that. From the previous dcdiag stuff it showed that the SBS *should* be the PDCe. do a netdom query fsmo and post results. also do a repadmin /showreps from the other server too. and a w32tm /dumpreg probably would be a good idea too. Wael wrote: > It's me again. Now it seems all the errors are resolved except for the > time server. > >> Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 >> A Time Server could not be located. >> The server holding the PDC role is down. >> Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, >> error 1355 >> A Good Time Server could not be located. >> ......................... MyOrganization.local failed test >> FsmoCheck > > w32tm /monitor shows > > Getting DC list for default domain... > > Analyzing: 1 -- (0 of 2) > Analyzing: -- 2 (1 of 2) > Analyzing: -- 2 (1 of 2) > > resolving referer 209.87.233.53 (1 of 2)... > > resolving referer 209.87.233.53 (2 of 2)... > > Server1.MyOrganization.local *** PDC *** [192.168.168.1]: > ICMP: 0ms delay. > NTP: +0.0000000s offset from Server1.MyOrganization.local > RefID: time1.chu.nrc.ca [209.87.233.53] > Server2.MyOrganization.local [192.168.169.2]: > ICMP: 400ms delay. > NTP: -0.0127315s offset from Server1.MyOrganization.local > RefID: time1.chu.nrc.ca [209.87.233.53] -- /kj |