[LØST] Active Directory problemer med replikering

5 innlegg i emnet

Skrevet

Hei

Jeg har fått ett merklig problem etter ett strømbrudd

Vi har 3 server i våres bedrift, 1 mail 1 web og en terminal

mail og webserveren replikerer AD (Active Directory) brukere og polecsies. men den siste serveren teminal har sluttet å replikere.

Er det noen som har noen tips her ??

Feilmeldingen er som følger

Event Type: Error

Event Source: Userenv

Event Category: None

Event ID: 1030

Date: 14.03.2005

Time: 15:13:08

User: bruker\navn (fjernet pga sikerhet)

Computer: navn (fjernet pga sikerhet)

Description:

Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Microsoft har ingen hjelp på denne siden

Mvh

LPA

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet

Hei

sjekket den linken veldig nyttig sted dette, men jeg har ikke veldig lyst til å kjøre GPO tilbake til standard.

Er det noen som har prøvd dette????

Er redd for å få krøll på Exchange serveren etter dette

Fins det noen annen løsning for å få AD til å begynne replikeringen melom serverene.

Må også ta med att AD replikering ser ut til å fungere til tider men med ca 1 til 2 ukers melomrom, det tar ca 1 til 2 uker før en ny bruker blir registrert på Terminal serveren våres, hvis jeg oppretter brukeren på denne så tar det like lang tid den andre veien

De 2 andre serverene mail og web replikerer innen ca 1 time

Mvh

LPA

:wall:

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet

Får også denne feilmeldingen til stadighet

Event Type: Error

Event Source: NTDS Replication

Event Category: Replication

Event ID: 1863

Date: 14.03.2005

Time: 15:14:47

User: NT AUTHORITY\ANONYMOUS LOGON

Computer: navn

Description:

This is the replication status for the following directory partition on the local domain controller.

Directory partition:

DC=DomainDnsZones,DC=navn.no,DC=no

The local domain controller has not received replication information from a number of domain controllers within the configured latency interval.

Latency Interval (Hours):

24

Number of domain controllers in all sites:

1

Number of domain controllers in this site:

1

The latency interval can be modified with the following registry key.

Registry Key:

HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)

To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe.

You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Skrevet

Denne får jeg også hele tiden

Event Type: Error

Event Source: NtFrs

Event Category: None

Event ID: 13568

Date: 13.03.2005

Time: 14:15:45

User: N/A

Computer: navn

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:\windows\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:".

Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to 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. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.

[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.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.

Click down the key path:

"System\CurrentControlSet\Services\NtFrs\Parameters"

Double click on the value name

"Enable Journal Wrap Automatic Restore"

and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0

Del dette innlegget


Lenke til innlegg
Del på andre sider

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!


Start en konto

Logg inn

Har du allerede en konto? Logg inn her.


Logg inn nå

  • Hvem er aktive   0 medlemmer

    Ingen innloggede medlemmer aktive