DRINGEND HILFE!!!! BITTE!!!!
From: Luciano Moneta (lmoneta_at_web.de)
Date: 03/04/04
- Next message: anonymous_at_discussions.microsoft.com: "Re: Temporäre Internetfiles"
- Previous message: Detlef Schaper: "Re: Fehler während Replikation"
- Next in thread: anonymous_at_discussions.microsoft.com: "DRINGEND HILFE!!!! BITTE!!!!"
- Reply: anonymous_at_discussions.microsoft.com: "DRINGEND HILFE!!!! BITTE!!!!"
- Reply: Detlef Schaper: "Re: DRINGEND HILFE!!!! BITTE!!!!"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 4 Mar 2004 10:50:44 +0100
Hallo!!!
Wir haben gestern den server neu installiert, weil die festplatte kaputt
gegangen war.
Heute haben wir dieser Fehler jede 5 minuten:
Ereignistyp: Fehler
Ereignisquelle: SAM
Ereigniskategorie: Keine
Ereigniskennung: 16650
Datum: 04.03.2004
Zeit: 10:37:16
Benutzer: Nicht zutreffend
Computer: SRV-FILE01
Beschreibung:
Die Kontenkennungszuweisung wurde nicht richtig initialisiert. Der Datensatz
enthält den NT-Fehlercode, der den Fehler verursacht hat. Windows 2000
wiederholt den Initialisierungsvorgang, bis dieser durchgeführt werden kann.
Bis dahin ist keine Kontenerstellung auf diesem Domänencontroller möglich.
Suchen Sie eventuell nach anderen SAM-Ereignisprotokolleinträgen, die auf
den exakten Fehlergrund hinweisen.
Daten:
0000: a7 02 00 c0 §..À
Bei www.eventid.net habe ich das gefunden:
Aber das Problem bleibt noch!!!! Wie könnten wir das Problem lösen?? Vielen
Dank in Voraus!!!! Grüße Luciano
Event ID: 16650
Source SAM
Type Error
Description The account-identifier allocator failed to initialize
properly. The record data contains the NT error code that caused the
failure. Windows 2000 may retry the initialization until it succeeds; until
that time, account creation will be denied on this Domain Controller. Please
look for other SAM event logs that may indicate the exact reason for the
failure.
Comments Ionut Marin (Last update 2/9/2004):
Aa per Microsoft: "When you use Dcpromo.exe to create a new domain
controller replica in a forest consisting of a single domain and one
existing domain controller, you may receive an "Access Denied" error message
when you use Dssite.msc to replicate from the new domain controller to the
existing one. In addition, the new domain controller's Directory Service log
may record Error 16650". See Q285836 to resolve this problem.
From a newsgroup post: "I just had this situation last week and I got
out of it successfully. It sounds like you took the route I did when
retiring my old server. This is to say that you most likely never demoted
the old server gracefully and it still appears in you AD database. There is
no need to worry. If you are no longer planning to have the retired server
in your domain, transfer the FSMO roles to the new server and then use
ntdsutil.exe to cleanup the Metadata of the outgoing server. Read these
three articles closely: Q216498, Q223787 and Q298450.
If you did demote the old machine before reinstalling, run "netdom
query fsmo" from the command prompt to determine who owns the RID master
role. Netdom.exe is part of the support tools that comes with your server
media. Sometimes FSMO roles do not transfer gracefully to another replica
when you demote a DC that holds a role. In that, case you will need to seize
the role".
From a newsgroup post: "Check and make sure that the FSMO role RID
Master is available and operational in the domain. By default, this is
created on the first DC that was created in the domain. You can determine
who the RID Master is supposed to be by bringing up AD Users and Computers
and right clicking on the domain and selecting Operations Masters. The RID
role should be on a DC in your domain. If it is not, you may have removed
the DC that it was originally on, but did not transfer it before the
removal. In this case, you will have to use ntdsutil to seize the role to a
current operational DC".
Anonymous (Last update 8/7/2003):
I found that one of my Domain Controller which was Infrastucture
Master was also a Global Catalogue. One I disable GC on Inf Master DC and
forced replication to other DC, all was fine.
Rick Dalechek
I have encountered this issue when I have multiple domains
represented in the same site. Replication choose by the KCC is arbitrary.
Adrian Grigorof
As per Microsoft: This behavior can occur because the RID Master FSMO
is unavailable or fails to replicate. The Domain Controller cannot obtain
and initialize the RID pool. This behavior can also occur when the User
Right "Access this computer from the network" has not been given to the
appropriate groups such as "Enterprise Domain Controllers" or "Authenticated
Users". See the link below for more details.
Joseph Hornsey
I had this error occur on two of five new domain controller
installations. Both DCs were at branch offices with extremely limited
bandwidth (approx 64Kpbs) back to the main office. After about 30 minutes,
the problem resolved itself after the branch DC was able to fully replicate
and find the RID Master.
Nikolaus Porkert
See Q255504 for instructions on using NDSUTIL.
Our Approach This information is only available to subscribers. An
example of "approach" is available here.
Links Q216498 , Q223787 , Q248410 , Q255504 , Q285836 , Q298450
- Next message: anonymous_at_discussions.microsoft.com: "Re: Temporäre Internetfiles"
- Previous message: Detlef Schaper: "Re: Fehler während Replikation"
- Next in thread: anonymous_at_discussions.microsoft.com: "DRINGEND HILFE!!!! BITTE!!!!"
- Reply: anonymous_at_discussions.microsoft.com: "DRINGEND HILFE!!!! BITTE!!!!"
- Reply: Detlef Schaper: "Re: DRINGEND HILFE!!!! BITTE!!!!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
