15. januar 2002 - 13:46Der er
6 kommentarer og 1 løsning
Hjælp! Win2000 server nede.
Serveren er nede, og jeg har eventlog fejl i massevis. Jeg tror at det altsammen bunder i at Active Directory er gået på røven.
dcdiag rapporter (blandt andet): Error: No record of File Replication System, SYSVOL started. The Active Directory may be prevented from starting. There are errors after the SYSVOL has been shared. The SYSVOL can prevent the AD from starting.
Hvor skal jeg begynde og lede efter fejlen, og hvordan retter man op på den?
I dette særtema ser vi på, hvordan cloud og AI bliver fundamentet for virksomhedernes digitale forretning, og hvordan de nye muligheder for automatisering og forretningsværdi kan udnyttes uden at miste overblik, sikkerhed og menneskelig kontrol.
Jeg har fundet følgende i eventlog på det tidspunkt det først gik galt:
Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13561 Date: 14-01-2002 Time: 19:37:51 User: N/A Computer: SRV02 Description: The File Replication Service has detected that the replica set \"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\" is in JRNL_WRAP_ERROR.
Replica set name is : \"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\" Replica root path is : \"c:\\winnt\\sysvol\\domain\" Replica root volume is : \"\\\\.\\C:\" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume \"\\\\.\\C:\" has been formatted. [2] The NTFS USN journal on volume \"\\\\.\\C:\" has been deleted. [3] The NTFS USN journal on volume \"\\\\.\\C:\" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on \"\\\\.\\C:\".
Following recovery steps will be taken to automatically recover from this error state. [1] At the first poll which will occur in 5 minutes this computer will be deleted from the replica set. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
Starting test: FsmoCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC\'s are down. 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. Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355 A KDC could not be located - All the KDCs are down. ......................... <domain>.dk failed test FsmoCheck
Men det er vel bare stadig at AD ikke kører, ikke?
Ny warning (masser af dem): Event Type: Warning Event Source: NTDS LDAP Event Category: LDAP Interface Event ID: 1216 Date: 15-01-2002 Time: 15:14:43 User: N/A Computer: SRV02 Description: The LDAP server closed a socket to a client because of an error condition, 995. (Internal ID c060274::67).
Samt stadig: Event Type: Error Event Source: NTDS General Event Category: Global Catalog Event ID: 1126 Date: 15-01-2002 Time: 15:12:30 User: Everyone Computer: SRV02 Description: Unable to establish connection with global catalog.
Jeg har fået maskinen til at køre igen, men kun ved at sætte følgende flag i registry (dette er ikke anbefalet af Microsoft): [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters] "SysvolReady"=dword:00000001
Det er stadig et mysterium hvorfor dette er krævet, men alt fungerer når flaget er sat, og holder op når det ikke er sat.
Er der nogen der har en ide hvorfor det forholder sig sådan?
Ingen har kommet med et ordentligt svar, så jeg lukker...
Synes godt om
Ny brugerNybegynder
Din løsning...
Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.