| 0x1 | Knowledge Consistency Checker |
Knowledge Consistency Checker |
| 0x2 | Sikkerhet |
Security |
| 0x3 | ExDS-grensesnitt |
ExDS Interface |
| 0x4 | MAPI-grensesnitt |
MAPI Interface |
| 0x5 | Replikering |
Replication |
| 0x6 | Datasanering |
Garbage Collection |
| 0x7 | Intern konfigurasjon |
Internal Configuration |
| 0x8 | Katalogtilgang |
Directory Access |
| 0x9 | Intern behandling |
Internal Processing |
| 0xA | Ytelse |
Performance |
| 0xB | Initialisering/avslutning |
Initialization/Termination |
| 0xC | Tjenestekontroll |
Service Control |
| 0xD | Navneløsing |
Name Resolution |
| 0xE | Sikkerhetskopi |
Backup |
| 0xF | Feltutvikling |
Field Engineering |
| 0x10 | LDAP-grensesnitt |
LDAP Interface |
| 0x11 | Oppsett |
Setup |
| 0x12 | Global katalog |
Global Catalog |
| 0x13 | Intersite Messaging |
Intersite Messaging |
| 0x14 | Gruppehurtigbufring |
Group Caching |
| 0x15 | Replikering av koblet verdi |
Linked-Value Replication |
| 0x16 | DS RPC-klient |
DS RPC Client |
| 0x17 | DS RPC-server |
DS RPC Server |
| 0x18 | DS-skjema |
DS Schema |
| 0x19 | Transformeringsmotor |
Transformation Engine |
| 0x1A | Påstandsbasert tilgangskontroll |
Claims-Based Access Control |
| 0x320 | Alvorsgrad: %1%nKategori: %2%n%3 |
Severity: %1%nCategory: %2%n%3 |
| 0x400003E8 | Oppstart av Microsoft Active Directory Lightweight Directory Services er fullført |
Microsoft Active Directory Lightweight Directory Services startup complete |
| 0x400003E9 | Active Directory Lightweight Directory Services kan ikke startes. Se tidligere logghendelser hvis du vil ha mer informasjon.%n%nTilleggsdata%nFeilkode:%n%1%nIntern ID (DSID):%n%2 |
Active Directory Lightweight Directory Services could not be started. See previous event log entry for details.%n%nAdditional Data%nFailure code:%n%1%nInternal ID (DSID):%n%2 |
| 0x400003EC | Active Directory Lightweight Directory Services ble avsluttet. |
Active Directory Lightweight Directory Services was shut down successfully. |
| 0x400003ED | Internal event: Started to remove deleted objects that have expired (garbage collection). |
Internal event: Started to remove deleted objects that have expired (garbage collection). |
| 0x400003EE | Internal event: Finished removing deleted objects that have expired (garbage collection). Number of expired deleted objects that have been removed: %1. |
Internal event: Finished removing deleted objects that have expired (garbage collection). Number of expired deleted objects that have been removed: %1. |
| 0x400003EF | Internal event: The Knowledge Consistency Checker (KCC) successfully initialized. |
Internal event: The Knowledge Consistency Checker (KCC) successfully initialized. |
| 0x400003F1 | Internal event: The Knowledge Consistency Checker (KCC) has started updating the replication topology for the directory service. |
Internal event: The Knowledge Consistency Checker (KCC) has started updating the replication topology for the directory service. |
| 0x400003F5 | Internal event: The replication topology update task terminated normally. |
Internal event: The replication topology update task terminated normally. |
| 0x400003F7 | Internal event: The Knowledge Consistency Checker (KCC) successfully updated the replication topology after the directory service was shut down or restarted. |
Internal event: The Knowledge Consistency Checker (KCC) successfully updated the replication topology after the directory service was shut down or restarted. |
| 0x40000415 | Internal event: The directory replication agent was prompted to modify the repsFrom attribute with the following parameters.%n%nDirectory partition:%n%1%nSource UUID:%n%2%nSource address:%n%3%nReplica-Flags:%n0x%4%nModify-Fields:%n0x%5%nOptions:%n0x%6 |
Internal event: The directory replication agent was prompted to modify the repsFrom attribute with the following parameters.%n%nDirectory partition:%n%1%nSource UUID:%n%2%nSource address:%n%3%nReplica-Flags:%n0x%4%nModify-Fields:%n0x%5%nOptions:%n0x%6 |
| 0x40000423 | Internal event: The invocationID attribute of the directory system agent object has been set to the following parameter.%n%nInvocationID attribute:%n%1 |
Internal event: The invocationID attribute of the directory system agent object has been set to the following parameter.%n%nInvocationID attribute:%n%1 |
| 0x40000424 | Internal event: The directory replication agent request was successfully completed. |
Internal event: The directory replication agent request was successfully completed. |
| 0x40000426 | Domenet %1 blir ikke lenger representert på serveren %4 med adressen %2, eller er ikke lengerkompatibelt med domenet på den lokale maskinen. Dette domenet blir ikke lengerreplikert fra denne kilden.%n%nFjerning av innholdet på dette domenet fra den lokale serveren har begynt.Fremdrift gjøres ved å fjerne resten av objektene i nestekjøring av KCC (Knowledge Consistency Checker). |
Domain %1 is no longer instantiated on server %4 at address %2, or is no longercompatible with the domain on the local machine. This domain is no longerreplicated from this source.%n%nRemoval of the contents of this domain from the local server has begun.Progress will be made in removing the remainder of these objects on the nextexecution of the Knowledge Consistency Checker (KCC). |
| 0x40000427 | Denne domenekontrolleren er ikke lenger en global katalog. Den replikerer ikke lenger følgende katalogpartisjon fra domenekontrolleren med følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%4%nNettverksadresse:%n%2%n%nFjerning av katalogpartisjonen har begynt. Fremdrift gjøres ved å fjerne resten av objektene i neste oppdatering av Knowledge Consistency Checker. |
This domain controller is no longer a global catalog. It will no longer replicate the following directory partition from the domain controller at the following network address.%n%nDirectory partition:%n%1%nDomain controller:%n%4%nNetwork address:%n%2%n%nRemoval of the directory partition has begun. Progress in removing the remainder of these objects will occur at the next Knowledge Consistency Checker update. |
| 0x40000428 | Denne domenekontrolleren replikerer ikke lenger følgende katalogpartisjon fra domenekontrolleren med følgende nettverksadresse fordi katalogpartisjonen har blitt fjernet fra Active Directory Lightweight Directory Services.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%4%nNettverksadresse:%n%2%n%nFjerning av katalogpartisjonen har begynt. Fremdrift gjøres ved å fjerne resten av objektene i neste oppdatering av Knowledge Consistency Checker. |
This domain controller will no longer replicate the following directory partition from the domain controller at the following network address. This is because the directory partition has been removed from Active Directory Lightweight Directory Services.%n%nDirectory partition:%n%1%nDomain controller:%n%4%nNetwork address:%n%2%n%nRemoval of the directory partition on this domain controller has begun. Progress in removing the remainder of these objects will occur at the next Knowledge Consistency Checker update. |
| 0x4000042A | Internal event: The directory service was prompted by the directory service at the following network address to add a replica of the following directory partition with these options.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3 |
Internal event: The directory service was prompted by the directory service at the following network address to add a replica of the following directory partition with these options.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3 |
| 0x4000042B | Internal event: The directory service was prompted by the directory service at the following network address to delete a replica of the following directory partition with these options.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3 |
Internal event: The directory service was prompted by the directory service at the following network address to delete a replica of the following directory partition with these options.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3 |
| 0x4000042C | Internal event: The directory service was prompted by the directory service at the following network address to update references for the following directory partition with these options.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3 |
Internal event: The directory service was prompted by the directory service at the following network address to update references for the following directory partition with these options.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3 |
| 0x4000042D | Gradvis fremdrift har blitt registrert ved å fjerne resten av objektene fra følgende katalogpartisjon på denne domenekontrolleren.%n%nKatalogpartisjon:%n%1%n%nTilleggsobjekter fjernes ved neste oppdatering av KCC (Knowledge Consistency Checker). |
Incremental progress has been made in removing the remainder of the objects from the following directory partition on this domain controller.%n%nDirectory partition:%n%1%n%nAdditional objects will be removed at the next Knowledge Consistency Checker (KCC) update. |
| 0x4000042E | Internal event: The directory service was prompted to synchronize a replica of the following directory partition with the directory service at the following network address with these options%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3%nActive ReplicaSync sessions:%n%4 |
Internal event: The directory service was prompted to synchronize a replica of the following directory partition with the directory service at the following network address with these options%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3%nActive ReplicaSync sessions:%n%4 |
| 0x40000430 | Internal event: This directory service was prompted by the directory service at the following network address with a request for retrieval of changes for the following directory partition with these options.%n%nDirectory partition:%n%2%nNetwork address:%n%1%nUpdate sequence number:%n%3%nFlags:%n0x%4%nSensitivity:%n%5%nOperation:%n%6%nDirSync Control Flags:%n0x%7%nActive GetNC sessions:%n%8 |
Internal event: This directory service was prompted by the directory service at the following network address with a request for retrieval of changes for the following directory partition with these options.%n%nDirectory partition:%n%2%nNetwork address:%n%1%nUpdate sequence number:%n%3%nFlags:%n0x%4%nSensitivity:%n%5%nOperation:%n%6%nDirSync Control Flags:%n0x%7%nActive GetNC sessions:%n%8 |
| 0x40000431 | Internal event: This directory service returned changes with the following information.%n%nTotal number of objects:%n%1%nTotal bytes:%n%2%nUpdate sequence number:%n%3%nExtended return:%n%4%nTime Taken (msec):%n%5%nRemaining GetNC sessions:%n%6 |
Internal event: This directory service returned changes with the following information.%n%nTotal number of objects:%n%1%nTotal bytes:%n%2%nUpdate sequence number:%n%3%nExtended return:%n%4%nTime Taken (msec):%n%5%nRemaining GetNC sessions:%n%6 |
| 0x40000434 | Unused message |
Unused message |
| 0x4000043F | Internal event: Active Directory Lightweight Directory Services could not locate the following registry parameters in the registry.%nRegistry key:%n%1 |
Internal event: Active Directory Lightweight Directory Services could not locate the following registry parameters in the registry.%nRegistry key:%n%1 |
| 0x40000441 | Internal event: Not all the parameters necessary to start the DSP layer are present in the Windows registry. The DSP will not be initialized. |
Internal event: Not all the parameters necessary to start the DSP layer are present in the Windows registry. The DSP will not be initialized. |
| 0x40000446 | Bufring av programvareskriving for følgende diskstasjon har blitt deaktivert for å hindre mulige tap av data ved systemsvikt, for eksempel strømbrudd eller feil på maskinvarekomponenter som kan føre til at systemet plutselig avsluttes. Diskstasjonen som lagrer Active Directory Lightweight Directory Services-loggfiler, er den eneste stasjonen som påvirkes av denne endringen.%n%nDiskstasjon:%n%1 |
Software write caching for the following disk drive has been disabled to prevent possible data loss during system failures such as power outages or hardware component failures that can cause a sudden shutdown of the system. The disk drive that stores Active Directory Lightweight Directory Services log files is the only drive affected by this change.%n%nDisk drive:%n%1 |
| 0x4000044D | Active Directory Lightweight Directory Services oppdaterte følgende objekt med attributtendringer etter at én eller flere av de mislykkede attributtendringene ble tilbakeført.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%n%nDenne tilbakeføringen av attributtendringen medfører at de opprinnelige endringene annulleres. |
Active Directory Lightweight Directory Services updated the following object with attribute changes after reversing one or more of the failed attribute changes.%n%nObject:%n%1%nObject GUID:%n%2%n%nThis attribute change reversal will have the effect of cancelling the changes. |
| 0x4000044E | Internal event: Active Directory Lightweight Directory Services submitted an update-request message while requesting updates at the following directory partition during intersite replication.%n%nMessage size:%n%1%nDirectory partition:%n%2%nSource directory service:%n%3 |
Internal event: Active Directory Lightweight Directory Services submitted an update-request message while requesting updates at the following directory partition during intersite replication.%n%nMessage size:%n%1%nDirectory partition:%n%2%nSource directory service:%n%3 |
| 0x4000044F | Internal event: Active Directory Lightweight Directory Services submitted an update-replica message while updating the replica of the following directory partition during intersite replication.%n%nMessage size:%n%1%nDirectory partition:%n%2%nDestination directory service:%n%3 |
Internal event: Active Directory Lightweight Directory Services submitted an update-replica message while updating the replica of the following directory partition during intersite replication.%n%nMessage size:%n%1%nDirectory partition:%n%2%nDestination directory service:%n%3 |
| 0x40000450 | KCC (Knowledge Consistency Checker) avsluttet følgende endringsvarslinger.%n%nKatalogpartisjon:%n%1%nMålnettverksadresse:%n%2%nMålkatalogtjeneste (hvis tilgjengelig):%n%3%n%nDette kan forekomme hvis denne katalogtjenesten eller målkatalogtjenesten har blitt flyttet til et annet område. |
The Knowledge Consistency Checker (KCC) successfully terminated the following change notifications.%n%nDirectory partition:%n%1%nDestination network address:%n%2%nDestination directory service (if available):%n%3%n%nThis event can occur if either this directory service or the destination directory service has been moved to another site. |
| 0x40000454 | Internal event: The Knowledge Consistency Checker (KCC) has selected the following number of candidate connections to replicate the directory partition from this site.%n%nCandidate connections:%n%1%nDirectory partition:%n%2%nSite:%n%3 |
Internal event: The Knowledge Consistency Checker (KCC) has selected the following number of candidate connections to replicate the directory partition from this site.%n%nCandidate connections:%n%1%nDirectory partition:%n%2%nSite:%n%3 |
| 0x40000455 | InvocationID-attributtet for denne katalogserveren er endret. Det høyeste oppdateringssekvensnummeret på tidspunktet sikkerhetskopien ble opprettet, er som følger:%n%nInvocationID-attributt (gammel verdi):%n%1%nInvocationID-attributt (ny verdi):%n%2%nOppdateringssekvensnummer:%n%3%n%nAktiverings-IDen endres når en katalogserver gjenopprettes fra sikkerhetskopimedier, konfigureres som vert for en skrivbar programkatalogpartisjon, blir gjenopptatt etter at et øyeblikksbilde for virtuell maskin er brukt, etter en import for virtuell maskin eller etter en direktemigrering. Virtualiserte domenekontrollere bør ikke gjenopprettes ved hjelp av øyeblikksbilder for virtuell maskin. Den støttede metoden for gjenoppretting eller tilbakeføring av innholdet i en Active Directory Domain Services-database er å gjenopprette en sikkerhetskopi av en systemtilstand som er foretatt med et Active Directory Domain Services-kompatibelt sikkerhetskopieringsprogram. |
The invocationID attribute for this directory server has been changed. The highest update sequence number at the time the backup was created is as follows:%n%nInvocationID attribute (old value):%n%1%nInvocationID attribute (new value):%n%2%nUpdate sequence number:%n%3%n%nThe invocationID is changed when a directory server is restored from backup media, is configured to host a writeable application directory partition, has been resumed after a virtual machine snapshot has been applied, after a virtual machine import operation, or after a live migration operation. Virtualized domain controllers should not be restored using virtual machine snapshots. The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services-aware backup application. |
| 0x40000456 | Nivåheving for denne domenekontrolleren til en global katalog blir forsinket med følgende intervall.%n%nIntervall (minutter):%n%1%n%nDenne forsinkelsen er nødvendig slik at de obligatoriske katalogpartisjonene kan klargjøres før den globale katalogen annonseres. I registret kan du angi hvor mange sekunder katalogsystemagenten skal vente før nivået for den lokale domenekontrolleren heves til en global katalog. Se Resource Kit Distributed Systems Guide hvis du vil ha mer informasjon om registerverdien for forsinkelse av annonsering av den globale katalogen. |
Promotion of this domain controller to a global catalog will be delayed for the following interval.%n%nInterval (minutes):%n%1%n%nThis delay is necessary so that the required directory partitions can be prepared before the global catalog is advertised. In the registry, you can specify the number of seconds that the directory system agent will wait before promoting the local domain controller to a global catalog. For more information about the Global Catalog Delay Advertisement registry value, see the Resource Kit Distributed Systems Guide. |
| 0x40000457 | Internal event: Active Directory Lightweight Directory Services made progress during a replica synchronization of the following directory partition.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nObjects received:%n%3%nObjects applied:%n%4%nValues received:%n%6%nTotal objects at source (approx.):%n%5%nTotal values at source (approx.):%n%7 |
Internal event: Active Directory Lightweight Directory Services made progress during a replica synchronization of the following directory partition.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nObjects received:%n%3%nObjects applied:%n%4%nValues received:%n%6%nTotal objects at source (approx.):%n%5%nTotal values at source (approx.):%n%7 |
| 0x4000045A | Inngående replikering har blitt aktivert av brukeren. |
Inbound replication has been enabled by the user. |
| 0x4000045C | Utgående replikering har blitt aktivert av brukeren. |
Outbound replication has been enabled by the user. |
| 0x4000045F | Denne domenekontrolleren er nå en global katalog. |
This domain controller is now a global catalog. |
| 0x40000460 | Denne domenekontrolleren er ikke lenger en global katalog. |
This domain controller is no longer a global catalog. |
| 0x40000462 | Den lokale domenekontrolleren har ikke fullført replikeringen fordi et slettet overordnet objekt for følgende innkommende objekt har blitt registrert på en skrivebeskyttet katalogpartisjon.%n%nInnkommende objekt:%n%1%n%nDomenekontrollerne som dette objektet er skrivbart for, må korrigeres.%n%nBrukerhandling%nFlytt dette objektet til LostAndFound-beholderen ved hjelp av Active Directory Lightweight Directory Services Sites and Services. |
The local domain controller has not completed replication because a deleted parent for the following incoming object has been detected on a read-only directory partition.%n%nIncoming object:%n%1%n%nThe domain controllers for which this object is writeable must be corrected.%n%nUser Action%nMove this object into the LostAndFound container using Active Directory Lightweight Directory Services Sites and Services. |
| 0x40000463 | KCC (Knowledge Consistency Checker) slettet følgende Connection-objekt fordi kildekatalogtjenesten det refererte til, har blitt slettet.%n%nObjekt:%n%1 |
The Knowledge Consistency Checker (KCC) deleted the following Connection object because the source directory service that it referenced has been deleted.%n%nObject:%n%1 |
| 0x40000464 | Internal event: Active Directory Lightweight Directory Services failed to receive a remote procedure call (RPC) binding handle for the following directory service.%n%nDirectory service:%n%1%n%nAdditional Data%nError value:%n%2 |
Internal event: Active Directory Lightweight Directory Services failed to receive a remote procedure call (RPC) binding handle for the following directory service.%n%nDirectory service:%n%1%n%nAdditional Data%nError value:%n%2 |
| 0x40000468 | En replikeringstilkobling ble opprettet fra følgende kildekatalogtjeneste til den lokale katalogtjenesten.%n%nKildekatalogtjeneste:%n%1%nLokal katalogtjeneste:%n%2%n%nTilleggsdata%nÅrsakskode:%n0x%3%nIntern ID for opprettingspunkt:%n%4%n |
A replication connection was created from the following source directory service to the local directory service.%n%nSource directory service:%n%1%nLocal directory service:%n%2%n%nAdditional Data%nReason Code:%n0x%3%nCreation Point Internal ID:%n%4%n |
| 0x40000469 | Replikeringsbelastningen for Active Directory Lightweight Directory Services ble forbedret ved at en replikeringstilkobling fra følgende kildekatalogtjeneste til den lokale katalogtjenesten ble slettet.%n%nKildekatalogtjeneste:%n%1%nLokal katalogtjeneste:%n%2%n%nTilleggsdata%nÅrsakskode:%n0x%3%nIntern ID for slettepunkt:%n%4%n |
To improve the replication load of Active Directory Lightweight Directory Services, a replication connection from the following source directory service to the local directory service was deleted.%n%nSource directory service:%n%1%nLocal directory service:%n%2%n%nAdditional Data%nReason Code:%n0x%3%nDeletion Point Internal ID:%n%4%n |
| 0x4000046C | Internal event: The Directory Service removed the expired, deleted object %1 from the database. |
Internal event: The Directory Service removed the expired, deleted object %1 from the database. |
| 0x4000046D | Internal event: This directory service is the intersite topology generator for the following site.%n%nSite:%n%1 |
Internal event: This directory service is the intersite topology generator for the following site.%n%nSite:%n%1 |
| 0x40000471 | Active Directory Lightweight Directory Services opprettet en indeks for følgende attributt.%n%nAttributtidentifikator:%n%1%nAttributtnavn:%n%2 |
Active Directory Lightweight Directory Services successfully created an index for the following attribute.%n%nAttribute identifier:%n%1%nAttribute name:%n%2 |
| 0x40000472 | Internal event: Function %1 entered.%n SID: %2%n Source IP: %3%n Operation identifier: %4%n Data1: %5%n Data2: %6%n Data3: %7%n Data4: %8%n |
Internal event: Function %1 entered.%n SID: %2%n Source IP: %3%n Operation identifier: %4%n Data1: %5%n Data2: %6%n Data3: %7%n Data4: %8%n |
| 0x40000473 | Internal event: Function %1 exited.%n Elapsed time (ms): %2%n SID: %3%n Source IP: %4%n Operation identifier: %5%n Data1: %6%n Data2: %7%n Data3: %8%n |
Internal event: Function %1 exited.%n Elapsed time (ms): %2%n SID: %3%n Source IP: %4%n Operation identifier: %5%n Data1: %6%n Data2: %7%n Data3: %8%n |
| 0x4000047F | Internal event: A new database column was created for the following new attribute.%n%nDatabase column:%n%1%nAttribute identifier:%n%2%nAttribute name:%n%3 |
Internal event: A new database column was created for the following new attribute.%n%nDatabase column:%n%1%nAttribute identifier:%n%2%nAttribute name:%n%3 |
| 0x4000048A | Internal event: The Address Book hierarchy table has been rebuilt. |
Internal event: The Address Book hierarchy table has been rebuilt. |
| 0x4000048E | Internal event: Active Directory Lightweight Directory Services might use the following index to optimize a query. The approximate record count for using this index is as follows.%n%nIndex:%n%1%nRecord count:%n%2 |
Internal event: Active Directory Lightweight Directory Services might use the following index to optimize a query. The approximate record count for using this index is as follows.%n%nIndex:%n%1%nRecord count:%n%2 |
| 0x4000048F | Internal event: Active Directory Lightweight Directory Services will use the following index as the optimal index for this query.%n%nIndex:%n%1 |
Internal event: Active Directory Lightweight Directory Services will use the following index as the optimal index for this query.%n%nIndex:%n%1 |
| 0x40000494 | Internal event: A client process has connected to Active Directory Lightweight Directory Services with the following RPC binding.%n%nRPC binding:%n%1 |
Internal event: A client process has connected to Active Directory Lightweight Directory Services with the following RPC binding.%n%nRPC binding:%n%1 |
| 0x40000496 | Internal event: A privileged operation (rights required = 0x%1) was successfully performed on object %2. |
Internal event: A privileged operation (rights required = 0x%1) was successfully performed on object %2. |
| 0x40000497 | Internal event: A privileged operation (rights required = 0x%1) on object %2 failed because a non-security related error occurred. |
Internal event: A privileged operation (rights required = 0x%1) on object %2 failed because a non-security related error occurred. |
| 0x40000498 | Internal event: A client process has attempted an anonymous bind to an interface that Active Directory Lightweight Directory Services is configured not to accept. As a result, this connection was rejected. |
Internal event: A client process has attempted an anonymous bind to an interface that Active Directory Lightweight Directory Services is configured not to accept. As a result, this connection was rejected. |
| 0x40000499 | Sikkerhetsattributtene for objektet %1 ble endret. |
The security attributes on object %1 were modified. |
| 0x4000049C | Active Directory Lightweight Directory Services kan ikke slette følgende kolonne fra databasen. Denne kolonnen er ikke lenger i bruk. Den ble tidligere brukt av følgende attributt, som har blitt slettet.%n%nKolonne:%n%1%nAttributt:%n%2%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
Active Directory Lightweight Directory Services could not delete the following column from the database. This column is no longer used. It was previously used by the following attribute, which has been deleted.%n%nColumn:%n%1%nAttribute:%n%2%n%nAdditional Data%nError value:%n%3 %4 |
| 0x4000049D | Active Directory Lightweight Directory Services kan ikke slette følgende kolonne fra databasen fordi den brukes av en indeks. Denne kolonnen ble tidligere brukt av følgende attributt, som har blitt slettet.%n%nKolonne:%n%1%nAttributt:%n%2 |
Active Directory Lightweight Directory Services could not delete the following column from the database because it is being used by an index. This column was previously used by the following attribute, which has been deleted.%n%nColumn:%n%1%nAttribute:%n%2 |
| 0x4000049E | Active Directory Lightweight Directory Services slettet følgende kolonne fra databasen. Denne kolonnen ble tidligere brukt av følgende attributt, som har blitt slettet.%n%nKolonne:%n%1%nAttributt:%n%2 |
Active Directory Lightweight Directory Services successfully deleted the following column from the database. This column was previously used by the following attribute, which has been deleted.%n%nColumn:%n%1%nAttribute:%n%2 |
| 0x400004A1 | Active Directory Lightweight Directory Services slettet indeksen for følgende attributt.%n%nAttributtnavn:%n%1%nAttributtidentifikator:%n%2 |
Active Directory Lightweight Directory Services successfully deleted the index for the following attribute.%n%nAttribute name:%n%1%nAttribute ID:%n%2 |
| 0x400004A6 | Internal event: Active Directory Lightweight Directory Services received an exception during a RPC connection to the directory service at the following network address.%n%nException:%n%1%nNetwork address:%n%2%n%nAdditional Data%nError value:%n%3 %4 |
Internal event: Active Directory Lightweight Directory Services received an exception during a RPC connection to the directory service at the following network address.%n%nException:%n%1%nNetwork address:%n%2%n%nAdditional Data%nError value:%n%3 %4 |
| 0x400004A7 | Internal event: A call made by the Active Directory Lightweight Directory Services replication agent returned the following warning.%n%nWarning:%n%1%n%2 |
Internal event: A call made by the Active Directory Lightweight Directory Services replication agent returned the following warning.%n%nWarning:%n%1%n%2 |
| 0x400004A8 | Internal event: Active Directory Lightweight Directory Services added a new source directory service for replication of the following directory partition with these flags.%n%nDirectory partition:%n%1%nNew source directory service:%n%2%nReplica flags:%n%3 |
Internal event: Active Directory Lightweight Directory Services added a new source directory service for replication of the following directory partition with these flags.%n%nDirectory partition:%n%1%nNew source directory service:%n%2%nReplica flags:%n%3 |
| 0x400004A9 | Internal event: Active Directory Lightweight Directory Services deleted the following source directory service for replication of the following directory partition.%n%nDirectory partition:%n%1%nSource directory service:%n%2%n%nAdditional Data%nError value:%n%4 %3 |
Internal event: Active Directory Lightweight Directory Services deleted the following source directory service for replication of the following directory partition.%n%nDirectory partition:%n%1%nSource directory service:%n%2%n%nAdditional Data%nError value:%n%4 %3 |
| 0x400004AA | Internal event: Active Directory Lightweight Directory Services fully synchronized the following directory partition from a source directory service.%n%nDirectory partition:%n%1 |
Internal event: Active Directory Lightweight Directory Services fully synchronized the following directory partition from a source directory service.%n%nDirectory partition:%n%1 |
| 0x400004AB | Internal event: Active Directory Lightweight Directory Services has completed a full synchronization of all directory partitions on the local domain controller. Completion however does not guarantee that these synchronizations were successful.%n%nThe directory service will not be accessible by clients until the following additional conditions are satisfied ?%n%n- The domain directory partition must have successfully completed at least one full synchronization from a single source domain controller since the domain controller was installed.%n%n- If this domain controller is a global catalog, all of the read-only directory partitions must have successfully completed at least one full synchronization since this domain controller was promoted to a global catalog. |
Internal event: Active Directory Lightweight Directory Services has completed a full synchronization of all directory partitions on the local domain controller. Completion however does not guarantee that these synchronizations were successful.%n%nThe directory service will not be accessible by clients until the following additional conditions are satisfied ?%n%n- The domain directory partition must have successfully completed at least one full synchronization from a single source domain controller since the domain controller was installed.%n%n- If this domain controller is a global catalog, all of the read-only directory partitions must have successfully completed at least one full synchronization since this domain controller was promoted to a global catalog. |
| 0x400004AD | Internal event: The directory partition has the following number of full-replica sites and partial-replica sites.%n%nDirectory partition:%n%1%nFull-replica sites:%n%2%nPartial-replica sites:%n%3 |
Internal event: The directory partition has the following number of full-replica sites and partial-replica sites.%n%nDirectory partition:%n%1%nFull-replica sites:%n%2%nPartial-replica sites:%n%3 |
| 0x400004AF | Internal event: Active Directory Lightweight Directory Services could not delete the following localized language index. This index is no longer needed.%n%nLocalized language index:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
Internal event: Active Directory Lightweight Directory Services could not delete the following localized language index. This index is no longer needed.%n%nLocalized language index:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0x400004B0 | Internal event: Active Directory Lightweight Directory Services deleted the following localized language index. This index was no longer needed.%n%nLocalized language index:%n%1 |
Internal event: Active Directory Lightweight Directory Services deleted the following localized language index. This index was no longer needed.%n%nLocalized language index:%n%1 |
| 0x400004B1 | Internal event: An intersite replication message has been compressed.%n%nOriginal size (bytes):%n%1%nCompressed size (bytes):%n%2 |
Internal event: An intersite replication message has been compressed.%n%nOriginal size (bytes):%n%1%nCompressed size (bytes):%n%2 |
| 0x400004BB | Internal event: An LDAP client connection was closed because the directory service is shutting down. |
Internal event: An LDAP client connection was closed because the directory service is shutting down. |
| 0x400004BC | Internal event: The directory service received a UDP packet that did not contain a complete LDAP request.%n%nUDP packet length:%n%1%n%nLDAP requests sent over UDP must be contained in a single packet. This packet will be ignored. |
Internal event: The directory service received a UDP packet that did not contain a complete LDAP request.%n%nUDP packet length:%n%1%n%nLDAP requests sent over UDP must be contained in a single packet. This packet will be ignored. |
| 0x400004BD | Internal event: An LDAP client connection was closed because it was disconnected on the client side.%n%nAdditional Data%nInternal ID:%n%1 |
Internal event: An LDAP client connection was closed because it was disconnected on the client side.%n%nAdditional Data%nInternal ID:%n%1 |
| 0x400004BF | Internal event: An LDAP client connection was closed because the client closed the connection. |
Internal event: An LDAP client connection was closed because the client closed the connection. |
| 0x400004C5 | LDAP over SSL (Secure Sockets Layer) er nå tilgjengelig. |
LDAP over Secure Sockets Layer (SSL) is now available. |
| 0x400004C9 | Følgende objekt fikk nytt navn på en ekstern katalogtjeneste med et objektnavn som allerede eksisterer på den lokale katalogtjenesten.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nNavn på nytt objekt:%n%3%nEksisterende objekt-GUID:%n%4%n%nObjektet med følgende GUID får nytt navn fordi det andre objektet brukte dette navnet sist.%n%nObjekt-GUID:%n%6%nObjekt med nytt navn:%n%5 |
The following object was renamed on a remote directory service with an object name that already exists on the local directory service.%n%nObject:%n%1%nObject GUID:%n%2%nNew object name:%n%3%nExisting object GUID:%n%4%n%nThe object with the following GUID will be renamed since the other object had this name more recently.%n%nObject GUID:%n%6%nRenamed object name:%n%5 |
| 0x400004CA | Følgende objekt ble opprettet på en ekstern katalogtjeneste med et objektnavn som allerede eksisterer på den lokale katalogtjenesten.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nEksisterende objekt-GUID:%n%3%n%nObjektet med følgende GUID får nytt navn fordi det andre objektet brukte dette navnet sist.%n%nObjekt-GUID:%n%5%nObjekt med nytt navn:%n%4 |
The following object was created on a remote directory service with an object name that already exists on the local directory service.%n%nObject:%n%1%nObject GUID:%n%2%nExisting object GUID:%n%3%n%nThe object with the following GUID will be renamed since the other object had this name more recently.%n%nObject GUID:%n%5%nRenamed object name:%n%4 |
| 0x400004CB | Ledig melding |
Unused message |
| 0x400004D7 | Internal event: The attribute of the following object was not sent to the following directory service because its up-to-dateness vector indicates that the change is redundant.%n%nAttribute:%n%1%nObject:%n%2%nObject GUID:%n%3%ndirectory service GUID:%n%4 |
Internal event: The attribute of the following object was not sent to the following directory service because its up-to-dateness vector indicates that the change is redundant.%n%nAttribute:%n%1%nObject:%n%2%nObject GUID:%n%3%ndirectory service GUID:%n%4 |
| 0x400004D8 | Internal event: The attribute of the following object was sent to the following directory service.%n%nAttribute:%n%1%nObject:%n%2%nObject GUID:%n%3%ndirectory service GUID:%n%4 |
Internal event: The attribute of the following object was sent to the following directory service.%n%nAttribute:%n%1%nObject:%n%2%nObject GUID:%n%3%ndirectory service GUID:%n%4 |
| 0x400004DF | Sikkerhetskontohaveren %1 finnes ikke på det lokale domenet og kan ikke overføres. |
Security principal %1 is not in the local domain and cannot be transferred. |
| 0x400004E9 | Internal event: The security descriptor propagation task is processing a propagation event starting from the following container.%n%nContainer:%n%1 |
Internal event: The security descriptor propagation task is processing a propagation event starting from the following container.%n%nContainer:%n%1 |
| 0x400004EA | Internal event: The security descriptor propagation task has finished processing a propagation event starting from the following container.%n%nContainer:%n%1%nNumber of objects processed:%n%2 |
Internal event: The security descriptor propagation task has finished processing a propagation event starting from the following container.%n%nContainer:%n%1%nNumber of objects processed:%n%2 |
| 0x400004EB | Internal event: The security descriptor propagation task has started. |
Internal event: The security descriptor propagation task has started. |
| 0x400004EC | Internal event: The security descriptor propagation task is waiting for a propagation event. |
Internal event: The security descriptor propagation task is waiting for a propagation event. |
| 0x400004ED | Internal event: The security descriptor propagation task has been notified of waiting propagation events. |
Internal event: The security descriptor propagation task has been notified of waiting propagation events. |
| 0x400004EF | Internal event: The security descriptor propagation task has successfully completed its task. |
Internal event: The security descriptor propagation task has successfully completed its task. |
| 0x400004F0 | KCC (Knowledge Consistency Checker) la til en replikeringsavtale for følgende katalogpartisjon.%n%nKatalogpartisjon:%n%1%nKildekatalogtjeneste:%n%2 |
The Knowledge Consistency Checker (KCC) successfully added a replication agreement for the following directory partition.%n%nDirectory partition:%n%1%nSource directory service:%n%2 |
| 0x400004F2 | Det nye forsøket på å fullføre den lokale fjerningen av objekter fra domenet %1 var vellykket. |
The retry to complete the local removal of objects from domain %1 was successful. |
| 0x400004F3 | Forsøket på å fullføre fjerningen av objekter fra domenet %1 ble avsluttet med følgende status:%n%n%3%n%nDenne operasjonen vil bli prøvd på nytt.%n%nTilleggsdata%nFeilverdi:%n%4 |
The attempt to complete the removal of objects from domain %1 terminated with the following status:%n%n%3%n%nThis operation will be retried.%n%nAdditional data%nError value:%n%4 |
| 0x400004F4 | Den lokale domenekontrolleren er ikke lenger en global katalog. Det fører til at følgende katalogpartisjon ikke lenger replikeres fra kildedomenekontrolleren med følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nKildedomenekontroller:%n%3%nNettverksadresse:%n%2 |
The local domain controller is no longer a global catalog. As a result, the following directory partition is no longer replicated from the source domain controller at the following network address.%n%nDirectory partition:%n%1%nSource domain controller:%n%3%nNetwork address:%n%2 |
| 0x400004F5 | Den lokale domenekontrolleren er ikke lenger en global katalog. KCC (Knowledge Consistency Checker) gjorde et forsøk på å stoppe ytterligere inngående replikering for følgende katalogpartisjon fra kildedomenekontrolleren med følgende nettverksadresse, men forsøket mislyktes.%n%nKatalogpartisjon:%n%1%nKildedomenekontroller:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt neste gang KCC oppdateres.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The local domain controller is no longer a global catalog. An attempt by the Knowledge Consistency Checker (KCC) to stop further inbound replication of the following directory partition from the source domain controller at the following network address failed.%n%nDirectory partition:%n%1%nSource domain controller:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again at the next KCC update.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400004F6 | Følgende katalogpartisjon har blitt fjernet fra konfigurasjonssettet. Det fører til at følgende katalogpartisjon ikke lenger replikeres fra kildekatalogserveren med følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nKildekatalogserver:%n%3%nNettverksadresse:%n%2 |
The following directory partition has been removed from the configuration set. As a result, the following directory partition is no longer replicated from the source directory server at the following network address.%n%nDirectory partition:%n%1%nSource directory server:%n%3%nNetwork address:%n%2 |
| 0x400004F7 | Følgende katalogpartisjon har blitt fjernet fra konfigurasjonssettet. KCC (Knowledge Consistency Checker) gjorde et forsøk på å stoppe ytterligere inngående replikering for følgende katalogpartisjon fra kildedomenekontrolleren med følgende nettverksadresse, men forsøket mislyktes.%n%nKatalogpartisjon:%n%1%nKildedomenekontroller:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt neste gang KCC oppdateres.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The following directory partition has been removed from the configuration set. An attempt by the Knowledge Consistency Checker (KCC) to stop further inbound replication of this directory partition from the source directory server at the following network address failed.%n%nDirectory partition:%n%1%nSource directory server:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again at the next KCC update.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400004F8 | Følgende katalogpartisjon blir ikke lenger replikert fra kildekatalogserveren med følgende nettverksadresse fordi det ikke finnes et Connection-objekt for katalogtjenesten.%n%nKatalogpartisjon:%n%1%nKildekatalogtjeneste:%n%3%nNettverksadresse:%n%2 |
The following directory partition is no longer replicated from the source directory service at the following network address because there is no Connection object for the directory service.%n%nDirectory partition:%n%1%nSource directory service:%n%3%nNetwork address:%n%2 |
| 0x400004F9 | KCC (Knowledge Consistency Checker) gjorde et forsøk på å stoppe ytterligere inngående replikering for følgende katalogpartisjon fra kildekatalogtjenesten med følgende nettverksadresse, men forsøket mislyktes.%n%nKatalogpartisjon:%n%1%nKildekatalogtjeneste:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt neste gang KCC oppdateres.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
An attempt by the Knowledge Consistency Checker (KCC) to stop further inbound replication of the following directory partition from the source directory service at the following network address failed.%n%nDirectory partition:%n%1%nSource directory service:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again at the next KCC update.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400004FA | Active Directory Lightweight Directory Services kan ikke replikere katalogpartisjonen %1 fra den eksterne Active Directory Lightweight Directory Services-forekomsten %2. |
Active Directory Lightweight Directory Services could not replicate the directory partition %1 from the remote Active Directory Lightweight Directory Services instance %2. |
| 0x400004FB | Active Directory Lightweight Directory Services kan ikke opprette katalogpartisjonen %1 på den lokale Active Directory Lightweight Directory Services-forekomsten. Kontroller at dette navnet er unikt. |
Active Directory Lightweight Directory Services could not create the directory partition %1 on the local Active Directory Lightweight Directory Services instance. Ensure that this name is unique. |
| 0x400004FC | Active Directory Lightweight Directory Services kan ikke opprette objektet %1. Kontroller hendelsesloggen for mulige systemfeil. |
Active Directory Lightweight Directory Services could not create the object %1. Check the event log for possible system errors. |
| 0x400004FD | Active Directory Lightweight Directory Services kan ikke opprette NTDS-innstillingsobjektet %1. Kontroller at navnet på denne versjonen av Active Directory Lightweight Directory Services er unikt på området. |
Active Directory Lightweight Directory Services could not create the NTDS Settings object %1. Ensure that the name of this Active Directory Lightweight Directory Services is unique within the site. |
| 0x400004FE | Active Directory Lightweight Directory Services kan ikke opprette objektet %1 for domenekatalogpartisjonen. Kontroller at NetBIOS-navnet på dette domenet er unikt i skogen. |
Active Directory Lightweight Directory Services could not create the domain directory partition object %1. Ensure that the NetBIOS name of this domain is unique within the forest. |
| 0x400004FF | Active Directory Lightweight Directory Services-databasen kan ikke startes (feil %1). Se hendelsesloggen hvis du vil ha mer informasjon. |
The Active Directory Lightweight Directory Services database failed to initialize (error %1). Check the event log for more information. |
| 0x40000500 | Active Directory Lightweight Directory Services kan ikke installeres. |
Active Directory Lightweight Directory Services could not install. |
| 0x40000501 | En LDAP-tilkobling kan ikke opprettes med Active Directory Lightweight Directory Services-forekomsten %1. |
An LDAP connection could not be established with the Active Directory Lightweight Directory Services instance %1. |
| 0x40000502 | Veiviseren kan ikke godkjenne at Active Directory Lightweight Directory Services-forekomsten %1 bruker den oppgitte legitimasjonen. |
The wizard could not authenticate to Active Directory Lightweight Directory Services instance %1 using the supplied credentials. |
| 0x40000503 | Active Directory Lightweight Directory Services kan ikke fastslå området som denne serveren skal installeres på. Kontroller at områdekonfigurasjonen er riktig angitt. |
Active Directory Lightweight Directory Services could not determine the site in which to install this server. Ensure that the site configuration is correctly set. |
| 0x40000504 | Konfigurasjonsinnstillinger angir at denne Active Directory Lightweight Directory Services-forekomsten skal installeres på området %1, men området finnes ikke. Kontroller at områdekonfigurasjonen er riktig angitt. |
Configuration settings indicate that this Active Directory Lightweight Directory Services instance should be installed in site %1, but this site does not exist. Ensure that the site configuration is correctly set. |
| 0x40000505 | Active Directory Lightweight Directory Services kan ikke fastslå om navnet %1 på denne katalogserveren er unikt på den eksterne katalogserveren %2. Hvis dette navnet ikke er unikt, gir du nytt navn til denne katalogserveren. |
Active Directory Lightweight Directory Services could not determine if this directory server name %1 is unique on the remote directory server %2. If this name is not unique, rename this directory server. |
| 0x40000506 | Den eksterne katalogserveren %1 forsøkte å fjerne katalogserveren %2, men operasjonen mislyktes. |
The attempt at remote directory server %1 to remove directory server %2 was unsuccessful. |
| 0x40000507 | Active Directory Lightweight Directory Services kan ikke fastslå om domenenavnet %1 er unikt på den eksterne domenekontrolleren %2. Hvis dette navnet ikke er unikt, gir du nytt navn til domenet. |
Active Directory Lightweight Directory Services could not determine if the domain name %1 is unique on the remote domain controller %2. If this name is not unique, rename the domain. |
| 0x40000508 | Den eksterne katalogserveren %1 forsøkte å fjerne partisjonen %2, men operasjonen mislyktes. |
The attempt at remote directory server %1 to remove the partition %2 was unsuccessful. |
| 0x4000050A | Veiviseren har ikke tilgang til registret. |
The wizard could not access the registry. |
| 0x4000050C | Active Directory Lightweight Directory Services kan ikke laste SAM-databasen (security account manager). |
Active Directory Lightweight Directory Services could not load the security account manager (SAM) database. |
| 0x4000050D | Active Directory Lightweight Directory Services kan ikke opprette ny kontoinformasjon. |
Active Directory Lightweight Directory Services could not create new account information. |
| 0x4000050E | Active Directory Lightweight Directory Services kan ikke registrere denne serveren for et sertifikat automatisk. |
Active Directory Lightweight Directory Services could not auto-enroll this server for a certificate. |
| 0x4000050F | Active Directory Lightweight Directory Services kan ikke legge til et alternativ for gjenopprettingsmodus for katalogtjenester på oppstartsmenyen. |
Active Directory Lightweight Directory Services could not add a Directory Services Restore Mode option to the startup menu. |
| 0x40000510 | Active Directory Lightweight Directory Services er allerede installert, eller denne domenekontrolleren er i gjenopprettingsmodus for katalogtjenester. |
Active Directory Lightweight Directory Services is already installed or this domain controller is in Directory Services Restore Mode. |
| 0x40000511 | Det oppstod en ukjent feil under installasjon av Active Directory Lightweight Directory Services. |
An unknown error occurred while installing Active Directory Lightweight Directory Services. |
| 0x40000512 | Veiviseren kan ikke lese driftsattributter fra den eksterne Active Directory Lightweight Directory Services-forekomsten %1 ved hjelp av LDAP. |
The wizard could not read operational attributes from the remote Active Directory Lightweight Directory Services instance %1 using LDAP. |
| 0x40000513 | Skjemavalideringskontrollen mislyktes. |
The schema validation check was not successful. |
| 0x40000514 | Active Directory Lightweight Directory Services kan ikke fastslå et gyldig domenenavn for DNS-navnet %1. Velg et annet DNS-navn. |
Active Directory Lightweight Directory Services could not determine a valid DN for the DNS name %1. Choose another DNS name. |
| 0x40000515 | Active Directory Lightweight Directory Services kan ikke legge til sikkerhetskontohavere i AD LDS-databasen. |
Active Directory Lightweight Directory Services could not add security principals to the AD LDS database. |
| 0x40000516 | Active Directory Lightweight Directory Services kan ikke legge til objekter i AD LDS-databasen. |
Active Directory Lightweight Directory Services could not add objects to the AD LDS database. |
| 0x40000517 | Active Directory Lightweight Directory Services kan ikke fastslå om den lokale Active Directory Lightweight Directory Services-forekomsten er den siste AD LDS-forekomsten i partisjonen. |
Active Directory Lightweight Directory Services could not determine if the local Active Directory Lightweight Directory Services instance is the last AD LDS instance in its partition. |
| 0x40000518 | Active Directory Lightweight Directory Services kan ikke fjernes på denne Active Directory Lightweight Directory Services-forekomsten fordi dette er den siste AD LDS-forekomsten i partisjonen, og domenet har et underordnet domene. |
Active Directory Lightweight Directory Services could not be removed on this Active Directory Lightweight Directory Services instance because this is the last AD LDS instance in the partition and the domain has a child domain. |
| 0x40000519 | Active Directory Lightweight Directory Services kan ikke avsluttes for fjerning. |
Active Directory Lightweight Directory Services could not be shut down for removal. |
| 0x4000051A | En tilkobling for Active Directory Lightweight Directory Services-replikering fra en kildekatalogtjeneste til en målkatalogtjeneste kan ikke slettes av KCC (Knowledge Consistency Checker).%n%nKildekatalogtjeneste:%n%1%nMålkatalogtjeneste:%n%2%n%nDenne operasjonen blir forsøkt på nytt neste gang KCC oppdateres.%n%nTilleggsdata%nFeilverdi:%n%3%nIntern ID for slettepunkt:%n%4%n |
An Active Directory Lightweight Directory Services replication connection from a source directory service to a destination directory service could not be deleted by the Knowledge Consistency Checker (KCC).%n%nSource directory service:%n%1%nDestination directory service:%n%2%n%nThis operation will be tried again at the next KCC update.%n%nAdditional Data%nError value:%n%3%nDeletion Point Internal ID:%n%4%n |
| 0x40000524 | Internal event: The Knowledge Consistency Checker (KCC) is preserving all intersite connections due to a failure to generate complete intersite topologies for one or more directory partitions.%n%nThis condition will persist until a complete spanning tree is generated for all directory partitions. |
Internal event: The Knowledge Consistency Checker (KCC) is preserving all intersite connections due to a failure to generate complete intersite topologies for one or more directory partitions.%n%nThis condition will persist until a complete spanning tree is generated for all directory partitions. |
| 0x40000525 | Internal event: The directory service has disconnected the LDAP connection from the following network address due to a time-out.%n%nNetwork address:%n%1 |
Internal event: The directory service has disconnected the LDAP connection from the following network address due to a time-out.%n%nNetwork address:%n%1 |
| 0x40000526 | Klargjør SAM (security account manager) og Active Directory Lightweight Directory Services for nivåsenking... |
Preparing the security account manager (SAM) and Active Directory Lightweight Directory Services for demotion... |
| 0x40000527 | Validerer fjerningen av denne Active Directory Lightweight Directory Services-forekomsten... |
Validating the removal of this Active Directory Lightweight Directory Services instance... |
| 0x40000528 | Godkjenner angitt legitimasjon |
Authenticating supplied credentials |
| 0x40000529 | Oppretter informasjon om ny lokal konto ... |
Creating new local account information... |
| 0x4000052A | Oppretter en ny database for lokal sikkerhetskontobehandling (SAM) ... |
Creating a new local security account manager (SAM) database... |
| 0x4000052B | Angir informasjon om den nye LSA-kontoen (lokal sikkerhetsinstans) ... |
Setting the new Local Security Authority (LSA) account information... |
| 0x4000052C | Fjerner Active Directory Lightweight Directory Services-objekter som refererer til den lokale Active Directory Lightweight Directory Services-forekomsten, fra den eksterne Active Directory Lightweight Directory Services-forekomsten %1 ... |
Removing Active Directory Lightweight Directory Services objects that refer to the local Active Directory Lightweight Directory Services instance from the remote Active Directory Lightweight Directory Services instance %1... |
| 0x4000052D | Fjerner alle driftsovervåkerrollene som eies av den lokale Active Directory Lightweight Directory Services-forekomsten ... |
Removing all operations master roles owned by the local Active Directory Lightweight Directory Services instance... |
| 0x4000052E | Fjerner LDAP- og RPC-tilgang (remote procedure call) til Active Directory Lightweight Directory Services ... |
Removing LDAP and remote procedure call (RPC) access to Active Directory Lightweight Directory Services... |
| 0x4000052F | Fullfører fjerning av Active Directory Lightweight Directory Services, SAM og LSA ... |
Completing removal of Active Directory Lightweight Directory Services, SAM and LSA... |
| 0x40000530 | Starter installasjonen av Active Directory Lightweight Directory Services |
Starting Active Directory Lightweight Directory Services installation |
| 0x40000531 | Validerer brukerangitte alternativer |
Validating user supplied options |
| 0x40000532 | Fastsetter et område for installasjon |
Determining a site in which to install |
| 0x40000533 | Undersøker et eksisterende konfigurasjonssett ... |
Examining an existing configuration set... |
| 0x40000537 | Konfigurerer den lokale datamaskinen som vert for Active Directory Lightweight Directory Services |
Configuring the local computer to host Active Directory Lightweight Directory Services |
| 0x40000539 | Oppretter en sikkerhets-ID (SID) for den nye partisjonen ... |
Creating a security identifier (SID) for the new partition... |
| 0x4000053A | Replikerer skjemakatalogpartisjonen |
Replicating the schema directory partition |
| 0x4000053B | Oppretter katalogpartisjon: %1; %2 objekter gjenstår |
Creating directory partition: %1; %2 objects remaining |
| 0x4000053C | Replikerer konfigurasjonskatalogpartisjonen |
Replicating the configuration directory partition |
| 0x4000053E | Replikerer viktig partisjonsinformasjon ... |
Replicating critical partition information... |
| 0x40000540 | Oppretter Active Directory Lightweight Directory Services-objekter på den lokale Active Directory Lightweight Directory Services-forekomsten |
Creating Active Directory Lightweight Directory Services objects on the local Active Directory Lightweight Directory Services instance |
| 0x40000541 | Flytter eksisterende brukere, grupper og datamaskinobjekter til Active Directory Lightweight Directory Services |
Moving existing users, groups, and computer objects to Active Directory Lightweight Directory Services |
| 0x40000542 | Oppretter nye partisjonsbrukere, grupper og datamaskinobjekter |
Creating new partition users, groups, and computer objects |
| 0x40000543 | Fullfører installasjonen av Active Directory Lightweight Directory Services |
Completing Active Directory Lightweight Directory Services installation |
| 0x40000544 | Internal event: The DirSearch operation was called with the following parameters.%n%nCaller type:%n%1%nSearch scope:%n%2%nBase object:%n%3%nFilter:%n%4%nRequired attributes:%n%5%nCommon Args:%n%6%n%nThis information is generally used for event tracing. |
Internal event: The DirSearch operation was called with the following parameters.%n%nCaller type:%n%1%nSearch scope:%n%2%nBase object:%n%3%nFilter:%n%4%nRequired attributes:%n%5%nCommon Args:%n%6%n%nThis information is generally used for event tracing. |
| 0x40000545 | Internal event: The DirSearch operation completed with the following status.%n%nFilter:%n%2%nIndexes:%n%3%nSearch Sub-operations:%n%4%nReturned Results:%n%5%n%nThis information is generally used for event tracing. |
Internal event: The DirSearch operation completed with the following status.%n%nFilter:%n%2%nIndexes:%n%3%nSearch Sub-operations:%n%4%nReturned Results:%n%5%n%nThis information is generally used for event tracing. |
| 0x40000546 | Internal event: The DirAddEntry operation was called with the following parameters.%n%nCaller type:%n%1%nObject:%n%2%n%nThis event is generally used for event tracing. |
Internal event: The DirAddEntry operation was called with the following parameters.%n%nCaller type:%n%1%nObject:%n%2%n%nThis event is generally used for event tracing. |
| 0x40000547 | Internal event: The DirAddEntry operation completed with the following status.%n%nStatus:%n1%n%nThis information is generally used for event tracing. |
Internal event: The DirAddEntry operation completed with the following status.%n%nStatus:%n1%n%nThis information is generally used for event tracing. |
| 0x40000548 | Internal event: The DirRemove operation was called with the following parameters.%n%nCaller type:%n%1%nObject:%n%2%n%nThis information is generally used for event tracing. |
Internal event: The DirRemove operation was called with the following parameters.%n%nCaller type:%n%1%nObject:%n%2%n%nThis information is generally used for event tracing. |
| 0x40000549 | Internal event: The DirRemove operation completed with the following status.%n%nStatus:%n1%n%nThis information is generally used for event tracing. |
Internal event: The DirRemove operation completed with the following status.%n%nStatus:%n1%n%nThis information is generally used for event tracing. |
| 0x4000054A | Internal event: The DirModify operation was called with the following parameters.%n%nCaller type:%n1%nObject:%n2%n%nThis information is generally used for event tracing. |
Internal event: The DirModify operation was called with the following parameters.%n%nCaller type:%n1%nObject:%n2%n%nThis information is generally used for event tracing. |
| 0x4000054B | Internal event: The DirModify operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
Internal event: The DirModify operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
| 0x4000054C | Internal event: The DirModifyDN operation was called with the following parameters.%n%nCaller type:%n%1%nParent object:%n%2%nNew parent object:%n%3%nRelative DN:%n%4%n%nThis information is generally used for event tracing. |
Internal event: The DirModifyDN operation was called with the following parameters.%n%nCaller type:%n%1%nParent object:%n%2%nNew parent object:%n%3%nRelative DN:%n%4%n%nThis information is generally used for event tracing. |
| 0x4000054D | Internal event: The DirModifyDN operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
Internal event: The DirModifyDN operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
| 0x4000054E | Internal event: The DirCompare operation was called with the following parameters.%n%nCaller type:%n%1%nAttribute:%n%2%nObject:%n%3%n%nThis information is generally used for event tracing. |
Internal event: The DirCompare operation was called with the following parameters.%n%nCaller type:%n%1%nAttribute:%n%2%nObject:%n%3%n%nThis information is generally used for event tracing. |
| 0x4000054F | Internal event: The DirCompare operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
Internal event: The DirCompare operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
| 0x40000550 | Internal event: The ReplicaSync operation completed with the following status.%n%nStatus:%n%1%nTime Taken (msec):%n%2%nRemaining ReplicaSync sessions:%n%3%n%nThis information is generally used for event tracing. |
Internal event: The ReplicaSync operation completed with the following status.%n%nStatus:%n%1%nTime Taken (msec):%n%2%nRemaining ReplicaSync sessions:%n%3%n%nThis information is generally used for event tracing. |
| 0x40000552 | Replikerer domenekatalogpartisjonen ... |
Replicating the domain directory partition... |
| 0x40000553 | Internal event: Active Directory Lightweight Directory Services has updated the up-to-dateness vector for the directory server with the following GUID.%n%nDSA GUID:%n%1%nDirectory partition:%n%4%nOld update sequence number (USN):%n%2%nNew USN:%n%3 |
Internal event: Active Directory Lightweight Directory Services has updated the up-to-dateness vector for the directory server with the following GUID.%n%nDSA GUID:%n%1%nDirectory partition:%n%4%nOld update sequence number (USN):%n%2%nNew USN:%n%3 |
| 0x40000554 | Internal event: Active Directory Lightweight Directory Services has updated the update sequence number (USN) vector for the directory service with the following GUID.%n%nDSA GUID:%n%1%nDirectory partition:%n%6%nOld object USN:%n%2%nNew object USN:%n%4%nOld property USN:%n%3%nNew property USN:%n%5 |
Internal event: Active Directory Lightweight Directory Services has updated the update sequence number (USN) vector for the directory service with the following GUID.%n%nDSA GUID:%n%1%nDirectory partition:%n%6%nOld object USN:%n%2%nNew object USN:%n%4%nOld property USN:%n%3%nNew property USN:%n%5 |
| 0x40000555 | Internal event: The following object was created.%n%nObject:%n%1%nObject GUID:%n%2 |
Internal event: The following object was created.%n%nObject:%n%1%nObject GUID:%n%2 |
| 0x40000556 | Internal event: The following object was updated.%n%nObject:%n%1%nObject GUID:%n%2 |
Internal event: The following object was updated.%n%nObject:%n%1%nObject GUID:%n%2 |
| 0x40000557 | Replikerer %1: mottok %2 av ca. %3 objekter |
Replicating %1: received %2 out of approximately %3 objects |
| 0x4000055A | Internal event: The Intersite Messaging service successfully sent data to a service at the following network address through the following transport.%n%nData (bytes):%n%1%nService:%n%2%nNetwork address:%n%3%nTransport:%n%4%nMessage subject:%n%5 |
Internal event: The Intersite Messaging service successfully sent data to a service at the following network address through the following transport.%n%nData (bytes):%n%1%nService:%n%2%nNetwork address:%n%3%nTransport:%n%4%nMessage subject:%n%5 |
| 0x4000055C | Internal event: The Intersite Messaging service received data for the following service through the following transport.%n%nData (bytes):%n%1%nService:%n%2%nTransport:%n%3%nMessage subject:%n%4 |
Internal event: The Intersite Messaging service received data for the following service through the following transport.%n%nData (bytes):%n%1%nService:%n%2%nTransport:%n%3%nMessage subject:%n%4 |
| 0x40000563 | Internal event: A message is pending for the following service using the following transport.%n%nService:%n%1%nTransport:%n%2 |
Internal event: A message is pending for the following service using the following transport.%n%nService:%n%1%nTransport:%n%2 |
| 0x40000568 | Den lokale domenekontrolleren har anskaffet et X.509-sertifikat for domenekontroller.%n%nReplikering mellom områder ved hjelp av SMTP-transport mellom den lokale domenekontrolleren og domenekontrollere på andre områder kan gjenopptas. |
The local domain controller has acquired a DomainController X.509 certificate.%n%nIntersite replication using SMTP transport between the local domain controller and domain controllers in other sites can resume. |
| 0x40000570 | Kan ikke fjerne Active Directory Lightweight Directory Services-forekomsten. |
This Active Directory Lightweight Directory Services instance could not be removed. |
| 0x40000572 | Alle problemer som hindrer oppdateringer av Active Directory Lightweight Directory Services-databasen, har blitt fjernet.Nye oppdateringer av Active Directory Lightweight Directory Services-databasen blir utført. Net Logon-tjenesten har startet på nytt. |
All problems preventing updates to the Active Directory Lightweight Directory Services database have been cleared.New updates to the Active Directory Lightweight Directory Services database are succeeding. The Net Logon service has restarted. |
| 0x40000573 | Active Directory Lightweight Directory Services kan ikke overføre driftsovervåkerrollene på alle domener til en annen Active Directory Lightweight Directory Services-forekomst på denne partisjonen. Mulige årsaker kan være følgende: Ingen andre AD LDS-forekomster kan motta en driftsovervåkerrolle, eller AD LDS har registrert at en AD LDS-forekomst ikke lenger finnes. |
Active Directory Lightweight Directory Services was unable to transfer the domain-wide operations master roles to another Active Directory Lightweight Directory Services instance in this partition. Possible causes include: No other AD LDS instance is available to receive an operations master role, or AD LDS has a record of a AD LDS instance that no longer exists. |
| 0x40000575 | Overfører driftsovervåkerroller på alle domener på den lokale Active Directory Lightweight Directory Services-forekomsten til en annen AD LDS-forekomst i skogen ... |
Transferring domain-wide operations master roles on the local Active Directory Lightweight Directory Services instance to other AD LDS instance in the forest... |
| 0x40000576 | Overfører driftsovervåkerroller på denne Active Directory Lightweight Directory Services-forekomsten til en annen Active Directory Lightweight Directory Services-forekomst ... |
Transferring operations master roles on this Active Directory Lightweight Directory Services instance to another Active Directory Lightweight Directory Services instance... |
| 0x40000579 | Internal event: A site connection edge is needed by the Knowledge Consistency Checker (KCC) to complete the topology graph.%n%nSource site:%n%1%nDestination directory service:%n%2%nSource directory service:%n%3%nTransport:%n%4 |
Internal event: A site connection edge is needed by the Knowledge Consistency Checker (KCC) to complete the topology graph.%n%nSource site:%n%1%nDestination directory service:%n%2%nSource directory service:%n%3%nTransport:%n%4 |
| 0x4000057A | Active Directory Lightweight Directory Services-databasen ble dumpet til følgende fil.%n%nFil:%n%2%nAntall poster:%n%1 |
The Active Directory Lightweight Directory Services database was successfully dumped to the following file.%n%nFile:%n%2%nNumber of records:%n%1 |
| 0x4000057C | Katalogtjenesten er nå områdetopologigeneratoren, og har tatt ansvar for å generere og vedlikeholde områdereplikeringstopologier for dette området. |
This directory service is now the intersite topology generator and has assumed responsibility for generating and maintaining intersite replication topologies for this site. |
| 0x40000580 | Intersite Messaging-tjenesten som bruker SMTP-transporten, har konfigurert en e-postadresse automatisk for den lokale domenekontrolleren. Følgende e-postadresse ble valgt for bruk med SMTP.%n%nE-postadresse:%n%1 |
The Intersite Messaging service using the SMTP transport has auto-configured a mail address for the local domain controller. The following mail address was chosen for use with SMTP.%n%nMail address:%n%1 |
| 0x40000582 | Active Directory Lightweight Directory Services kan ikke endre rollen for denne serveren på grunn av en ugyldig registernøkkelverdi for produkttypen. |
Active Directory Lightweight Directory Services could not change the role of this server because of an incorrect product type registry key value. |
| 0x40000584 | Internal event: The following object changes were applied to the local Active Directory Lightweight Directory Services database.%n%nProperty:%n%1%nObject:%n%2%nObject GUID:%n%3%nRemote version:%n%4%nRemote timestamp:%n%5%nRemote Originating USN:%n%6 |
Internal event: The following object changes were applied to the local Active Directory Lightweight Directory Services database.%n%nProperty:%n%1%nObject:%n%2%nObject GUID:%n%3%nRemote version:%n%4%nRemote timestamp:%n%5%nRemote Originating USN:%n%6 |
| 0x40000585 | Internal event: The following object changes were not applied to the local Active Directory Lightweight Directory Services database because the local metadata for the object indicates that the change is redundant.%n%nProperty:%n%1%nObject:%n%2%nObject GUID:%n%3%nLocal version number:%n%4 |
Internal event: The following object changes were not applied to the local Active Directory Lightweight Directory Services database because the local metadata for the object indicates that the change is redundant.%n%nProperty:%n%1%nObject:%n%2%nObject GUID:%n%3%nLocal version number:%n%4 |
| 0x4000058D | Internal event: The infrastructure update task has completed with the following results.%n%nQueried phantom references:%n%1%nPhantom references that exist on the local domain controller:%n%2%nUpdated phantom references:%n%3%n%nThe infrastructure update task will resume after the following interval.%n%nInterval (seconds):%n%4 |
Internal event: The infrastructure update task has completed with the following results.%n%nQueried phantom references:%n%1%nPhantom references that exist on the local domain controller:%n%2%nUpdated phantom references:%n%3%n%nThe infrastructure update task will resume after the following interval.%n%nInterval (seconds):%n%4 |
| 0x4000058E | Internal event: The local domain controller has determined it is not the infrastructure operations master. This check will continue to occur at the following interval.%n%nInterval (seconds):%n%1 |
Internal event: The local domain controller has determined it is not the infrastructure operations master. This check will continue to occur at the following interval.%n%nInterval (seconds):%n%1 |
| 0x4000058F | SAM (security account manager) har fastslått at sikkerhetsidentifikatoren (SID) for denne datamaskinen allerede er i bruk i skogen du vil koble til. Dette kan skje når du gjenoppretter en Active Directory Lightweight Directory Services-forekomst med en ugyldig sikkerhetskopi. Installer operativsystemet på nytt på den lokale AD LDS-forekomsten for å generere en ny SID. |
The security account manager (SAM) has determined that the security identifier (SID) for this computer is already in use in the Forest you want to join. This can happen when restoring an Active Directory Lightweight Directory Services instance with an improper backup. Reinstall the operating system on the local AD LDS instance to obtain a new SID. |
| 0x40000590 | Starter en replikeringssyklus mellom %1 og RID-driftsovervåkeren %2 slik at den nye replikaen kan opprette brukerobjekter, gruppeobjekter og datamaskinobjekter ... |
Starting a replication cycle between %1 and the RID operations master (%2), so that the new replica will be able to create users, groups, and computer objects... |
| 0x40000594 | Internal event: The cross-domain move of the following object succeeded at the destination domain.%n%nSource object DN:%n%1%nDestination object DN:%n%2 |
Internal event: The cross-domain move of the following object succeeded at the destination domain.%n%nSource object DN:%n%1%nDestination object DN:%n%2 |
| 0x40000599 | Internal event: The following registry key does not have a value. The following default value will be used instead.%n%nRegistry key:%n%1%nDefault registry value:%n%2 |
Internal event: The following registry key does not have a value. The following default value will be used instead.%n%nRegistry key:%n%1%nDefault registry value:%n%2 |
| 0x4000059A | En endring i navnet på en diskstasjon ble registrert, og banen som var angitt av følgende registernøkkel, ble endret.%n%nRegisternøkkel:%n%1%nGammel bane:%n%2%nNy bane:%n%3 |
A disk drive name change was detected and the path specified by the following registry key was changed.%n%nRegistry key:%n%1%nOld path:%n%2%nNew path:%n%3 |
| 0x400005A0 | Active Directory Lightweight Directory Services kan ikke opprette NTDS-innstillingsobjektet for denne Active Directory Lightweight Directory Services-forekomsten %1 på den eksterne AD LDS-forekomsten %2. Kontroller at den oppgitte nettverkslegitimasjonen har tilstrekkelige tillatelser. |
Active Directory Lightweight Directory Services could not create the NTDS Settings object for this Active Directory Lightweight Directory Services instance %1 on the remote AD LDS instance %2. Ensure the provided network credentials have sufficient permissions. |
| 0x400005A1 | Oppretter NTDS-innstillingsobjektet for denne Active Directory Lightweight Directory Services-forekomsten på den eksterne AD LDS-forekomsten %1 ... |
Creating the NTDS Settings object for this Active Directory Lightweight Directory Services instance on the remote AD LDS instance %1... |
| 0x400005A2 | NTDS-innstillingsobjektet for den lokale katalogserveren kunne ikke slettes fra den eksterne katalogtjenesten i løpet av oppryddingen av en mislykket installasjon av Active Directory Lightweight Directory Services.%n%nLokal katalogtjeneste:%n%1%nEkstern katalogtjeneste:%n%2%n%nBrukerhandling%nSlett dette objektet manuelt.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
During the cleanup operation of a failed Active Directory Lightweight Directory Services installation, the NTDS Settings object for the local directory service could not be deleted from the remote directory service.%n%nLocal directory service:%n%1%nRemote directory service:%n%2%n%nUser Action%nDelete this object manually.%n%nAdditional Data%nError value:%n%3 %4 |
| 0x400005A3 | Følgende objekt kunne ikke slettes fra den eksterne katalogtjenesten i løpet av oppryddingen av en mislykket installasjon av Active Directory Lightweight Directory Services.%n%nObjekt:%n%1%nEkstern katalogtjeneste:%n%2%n%nBrukerhandling%nSlett dette objektet manuelt.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
During the cleanup operation of a failed Active Directory Lightweight Directory Services installation, the following object could not be deleted from the remote directory service.%n%nObject:%n%1%nRemote directory service:%n%2%n%nUser Action%nDelete this object manually.%n%nAdditional Data%nError value:%n%3 %4 |
| 0x400005A4 | Active Directory Lightweight Directory Services kan ikke opprette objektet %1 på den eksterne Active Directory Lightweight Directory Services-forekomsten %2. Dette kan skyldes utilstrekkelige rettigheter eller at nettverket midlertidig ikke fungerer som det skal. Opprett objektet manuelt eller utfør operasjonen på nytt. |
Active Directory Lightweight Directory Services could not create the object %1 on the remote Active Directory Lightweight Directory Services instance %2. This could be a result of either insufficient rights or transient network behavior. Create the object manually or try this again. |
| 0x400005A5 | Active Directory Lightweight Directory Services finner ikke datamaskinkontoen for denne serveren på den eksterne Active Directory Lightweight Directory Services-forekomsten %1. |
Active Directory Lightweight Directory Services could not find the computer account for this server on the remote Active Directory Lightweight Directory Services instance %1. |
| 0x400005A9 | Overføringen av sikkerhetsbeskrivelsen registrerte at følgende objekt hadde følgende klasse-ID. Fant ikke denne klassen i skjemaet.%n%nObjekt:%n%1%nKlasse-ID:%n%2 |
The security descriptor propagation task found that the following object had the following class ID. This class was not found in the schema.%n%nObject:%n%1%nClass ID:%n%2 |
| 0x400005AD | Overføringen av sikkerhetsbeskrivelsen prøvde en operasjon på nytt uten suksess.%n%nAntall nye forsøk:%n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The security descriptor propagation task retried an operation without success.%n%nNumber of retries:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0x400005AE | Søker etter en Active Directory Lightweight Directory Services-forekomst for å replikere utgående endringer ... |
Searching for a Active Directory Lightweight Directory Services instance to replicate outgoing changes... |
| 0x400005AF | Active Directory Lightweight Directory Services finner ikke en Active Directory Lightweight Directory Services-forekomst for å replikere utgående endringer. |
Active Directory Lightweight Directory Services could not find a Active Directory Lightweight Directory Services instance to replicate outgoing changes. |
| 0x400005B0 | Replikerer utgående endringer til den eksterne Active Directory Lightweight Directory Services-forekomsten %1 ... |
Replicating outgoing changes to the remote Active Directory Lightweight Directory Services instance %1... |
| 0x400005B1 | Active Directory Lightweight Directory Services kan ikke replikere utgående endringer som ble gjort på den lokale Active Directory Lightweight Directory Services-forekomsten. |
Active Directory Lightweight Directory Services could not replicate outgoing changes made on the local Active Directory Lightweight Directory Services instance. |
| 0x400005B2 | Driftsovervåkerrollen som representeres av følgende objekt, har blitt overført til følgende katalogtjeneste etter anmodning fra en bruker.%n%nObjekt:%n%1%nKatalogtjeneste:%n%2%nTidligere eier av driftsovervåkerrolle:%n%3 |
The operations master role represented by the following object has been transferred to the following directory service at the request of a user.%n%nObject:%n%1%nDirectory service:%n%2%nPrevious operations master role owner:%n%3 |
| 0x400005B3 | Internal event: The DirFind operation was called with the following parameters.%n%nCaller type:%n%1%nAttribute ID: 0x%2%n%nThis information is generally used for event tracing. |
Internal event: The DirFind operation was called with the following parameters.%n%nCaller type:%n%1%nAttribute ID: 0x%2%n%nThis information is generally used for event tracing. |
| 0x400005B4 | Internal event: The DirFind operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
Internal event: The DirFind operation completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
| 0x400005B5 | Internal event: The LDAP bind operation was called.%n%nThis information is generally used for event tracing. |
Internal event: The LDAP bind operation was called.%n%nThis information is generally used for event tracing. |
| 0x400005B6 | Internal event: The LDAP bind operation has completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
Internal event: The LDAP bind operation has completed with the following status.%n%nStatus:%n%1%n%nThis information is generally used for event tracing. |
| 0x400005B8 | Under søk etter en indeks registrerte Active Directory Lightweight Directory Services at en ny indeks kreves for følgende attributt.%n%nAttributt:%n%1%nNavn på ny indeks:%n%2%n%nEn ny indeks opprettes automatisk.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
While searching for an index, Active Directory Lightweight Directory Services detected that a new index is needed for the following attribute.%n%nAttribute:%n%1%nNew index name:%n%2%n%nA new index will be automatically created.%n%nAdditional Data%nError value:%n%3 %4 |
| 0x400005BE | Intersite Messaging-tjenesten som bruker SMTP-transport, har konfigurert følgende domene for SMTP-e-postruting automatisk for følgende domenekontroller.%n%nRutingdomene:%n%2%nDomenekontroller:%n%1%n%nRutingdomenet mottar e-post i denne mappen for sending av e-post.%n%nMappe for sending av e-post:%n%3 |
The Intersite Messaging service using the SMTP transport has automatically configured the following SMTP mail routing domain for the following domain controller.%n%nRouting domain:%n%2%nDomain controller:%n%1%n%nThe routing domain will receive mail in this drop folder.%n%nDrop folder:%n%3 |
| 0x400005C5 | Katalogtjenesten har registrert NTDS-ytelsestellerne. |
The Directory Service has successfully registered the NTDS performance counters. |
| 0x400005C6 | Internal event: Compressed %1 bytes into %2 bytes for outbound RPC replication to DirectoryService %3. |
Internal event: Compressed %1 bytes into %2 bytes for outbound RPC replication to DirectoryService %3. |
| 0x400005CA | Følgende katalogpartisjon er ikke lenger tilgjengelig på katalogtjenesten med følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nKatalogtjeneste:%n%3%nNettverksadresse:%n%2%n%nDet fører til at den lokale katalogtjenesten ikke lenger replikerer denne katalogpartisjonen fra denne katalogtjenesten. |
The following directory partition is no longer available on the directory service at the following network address.%n%nDirectory partition:%n%1%nDirectory service:%n%3%nNetwork address:%n%2%n%nAs a result, the local directory service will no longer replicate this directory partition from this directory service. |
| 0x400005CB | Følgende katalogpartisjon er ikke lenger tilgjengelig på følgende kildekatalogserver. Det fører til at KCC (Knowledge Consistency Checker) forsøkte å slette replikeringskoblingen på den lokale katalogtjenesten, men forsøket mislyktes.%n%nKatalogpartisjon:%n%1%nKildekatalogtjeneste:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt neste gang KCC oppdateres.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The following directory partition is no longer available on the following source directory server. As a result, the Knowledge Consistency Checker (KCC) attempted to delete the replication link on the local directory service, but the attempt failed.%n%nDirectory partition:%n%1%nSource directory service:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again at the next KCC update.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400005CC | Active Directory Lightweight Directory Services kan ikke kontakte navngivingsovervåkeren %1. |
Active Directory Lightweight Directory Services could not contact the naming master %1. |
| 0x400005CD | Internal event: The Knowledge Consistency Checker (KCC) task has started. |
Internal event: The Knowledge Consistency Checker (KCC) task has started. |
| 0x400005CE | Internal event: The Knowledge Consistency Checker (KCC) task has ended. |
Internal event: The Knowledge Consistency Checker (KCC) task has ended. |
| 0x400005CF | Internal event: Active Directory Lightweight Directory Services received a request to begin inbound replication with the following parameters.%n%nDirectory partition:%n%1%nSource directory system agent address:%n%2%nSource directory system agent GUID:%n%3%nFlags:%n%4 |
Internal event: Active Directory Lightweight Directory Services received a request to begin inbound replication with the following parameters.%n%nDirectory partition:%n%1%nSource directory system agent address:%n%2%nSource directory system agent GUID:%n%3%nFlags:%n%4 |
| 0x400005D0 | Internal event: Active Directory Lightweight Directory Services completed the request to begin inbound replication.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to begin inbound replication.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005D1 | Internal event: Active Directory Lightweight Directory Services received a request for outbound changes with the following parameters.%n%nDestination directory system agent:%n%1%nDirectory partition:%n%2%nObject update sequence number (USN):%n%3%nAttribute filter USN:%n%4%nFlags:%n%5%nObject limit:%n%6%nByte limit:%n%7%nExtended operation:%n%8 |
Internal event: Active Directory Lightweight Directory Services received a request for outbound changes with the following parameters.%n%nDestination directory system agent:%n%1%nDirectory partition:%n%2%nObject update sequence number (USN):%n%3%nAttribute filter USN:%n%4%nFlags:%n%5%nObject limit:%n%6%nByte limit:%n%7%nExtended operation:%n%8 |
| 0x400005D2 | Internal event: Active Directory Lightweight Directory Services completed the request for outbound changes with the following results.%n%nObject update sequence number (USN):%n%1%nAttribute filter USN:%n%2%nObject count:%n%3%nByte count:%n%4%nExtended operation result:%n%5%nStatus:%n%6%nCompressed byte count:%n%7%nInstance name:%n%8%nDestination directory system agent:%n%9%nDirectory partition:%n%10%nTotal execution time(msec):%n%11%nTime wait for thread slot(msec):%n%12%Time spent to prepare package(msec):%n%13 |
Internal event: Active Directory Lightweight Directory Services completed the request for outbound changes with the following results.%n%nObject update sequence number (USN):%n%1%nAttribute filter USN:%n%2%nObject count:%n%3%nByte count:%n%4%nExtended operation result:%n%5%nStatus:%n%6%nCompressed byte count:%n%7%nInstance name:%n%8%nDestination directory system agent:%n%9%nDirectory partition:%n%10%nTotal execution time(msec):%n%11%nTime wait for thread slot(msec):%n%12%Time spent to prepare package(msec):%n%13 |
| 0x400005D3 | Internal event: Active Directory Lightweight Directory Services received a request to update the list of directory servers to which it sends change notifications with the following parameters.%n%nDirectory partition:%n%1%nDestination directory service address:%n%2%nDestination directory service GUID:%n%3%nFlags:%n%4 |
Internal event: Active Directory Lightweight Directory Services received a request to update the list of directory servers to which it sends change notifications with the following parameters.%n%nDirectory partition:%n%1%nDestination directory service address:%n%2%nDestination directory service GUID:%n%3%nFlags:%n%4 |
| 0x400005D4 | Internal event: Active Directory Lightweight Directory Services completed the request to update the list of directory servers to which it sends change notifications.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to update the list of directory servers to which it sends change notifications.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005D5 | Internal event: Active Directory Lightweight Directory Services received a request to add an inbound replication agreement with the following parameters.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nIntersite transport DN:%n%3%nSource directory service address:%n%4%nFlags:%n%5 |
Internal event: Active Directory Lightweight Directory Services received a request to add an inbound replication agreement with the following parameters.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nIntersite transport DN:%n%3%nSource directory service address:%n%4%nFlags:%n%5 |
| 0x400005D6 | Internal event: Active Directory Lightweight Directory Services completed the request to add an inbound replication link.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to add an inbound replication link.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005D7 | Internal event: Active Directory Lightweight Directory Services received a request to modify an inbound replication agreement with the following parameters.%n%nDirectory partition:%n%1%nSource directory service GUID:%n%2%nSource directory service address:%n%3%nAgreement flags:%n%4%nAgreement fields to update:%n%5%nFlags:%n%6 |
Internal event: Active Directory Lightweight Directory Services received a request to modify an inbound replication agreement with the following parameters.%n%nDirectory partition:%n%1%nSource directory service GUID:%n%2%nSource directory service address:%n%3%nAgreement flags:%n%4%nAgreement fields to update:%n%5%nFlags:%n%6 |
| 0x400005D8 | Internal event: Active Directory Lightweight Directory Services completed the request to modify an inbound replication link.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to modify an inbound replication link.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005D9 | Internal event: Active Directory Lightweight Directory Services received a request to remove an inbound replication agreement with the following parameters.%n%nDirectory partition:%n%1%nSource directory service address:%n%2%nFlags:%n%3 |
Internal event: Active Directory Lightweight Directory Services received a request to remove an inbound replication agreement with the following parameters.%n%nDirectory partition:%n%1%nSource directory service address:%n%2%nFlags:%n%3 |
| 0x400005DA | Internal event: Active Directory Lightweight Directory Services completed the request to remove an inbound replication agreement.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to remove an inbound replication agreement.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005DB | Internal event: Active Directory Lightweight Directory Services received a request to verify the following number of names with these flags.%n%nNumber of names:%n%1%nFlags:%n%2 |
Internal event: Active Directory Lightweight Directory Services received a request to verify the following number of names with these flags.%n%nNumber of names:%n%1%nFlags:%n%2 |
| 0x400005DC | Internal event: Active Directory Lightweight Directory Services completed the request to verify names.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to verify names.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005DD | Internal event: Active Directory Lightweight Directory Services received a request to accept a cross-domain move with the following parameters.%n%nSource domain controller:%n%1%nFrom DN:%n%2%nTo DN:%n%3%nTo directory partition:%n%4 |
Internal event: Active Directory Lightweight Directory Services received a request to accept a cross-domain move with the following parameters.%n%nSource domain controller:%n%1%nFrom DN:%n%2%nTo DN:%n%3%nTo directory partition:%n%4 |
| 0x400005DE | Internal event: Active Directory Lightweight Directory Services completed the request to process a cross-domain move.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to process a cross-domain move.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005DF | Internal event: The Directory Service has been asked to create %1 objects fora remote DSA:%n%n%2%n%3 |
Internal event: The Directory Service has been asked to create %1 objects fora remote DSA:%n%n%2%n%3 |
| 0x400005E0 | Internal event: Active Directory Lightweight Directory Services completed the request to create objects. The following number of objects was created.%n%nNumber of objects:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
Internal event: Active Directory Lightweight Directory Services completed the request to create objects. The following number of objects was created.%n%nNumber of objects:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0x400005E1 | Internal event: Active Directory Lightweight Directory Services received a request to process the following Knowledge Consistency Checker (KCC) task.%n%nTask:%n%1%nFlags:%n%2 |
Internal event: Active Directory Lightweight Directory Services received a request to process the following Knowledge Consistency Checker (KCC) task.%n%nTask:%n%1%nFlags:%n%2 |
| 0x400005E2 | Internal event: Active Directory Lightweight Directory Services completed the request to process a Knowledge Consistency Checker (KCC) task.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to process a Knowledge Consistency Checker (KCC) task.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005E3 | Internal event: Active Directory Lightweight Directory Services received a request for the following replication state information with the following parameters.%n%nInformation type:%n%1%nObject DN:%n%2%nSource directory service GUID:%n%3 |
Internal event: Active Directory Lightweight Directory Services received a request for the following replication state information with the following parameters.%n%nInformation type:%n%1%nObject DN:%n%2%nSource directory service GUID:%n%3 |
| 0x400005E4 | Internal event: Active Directory Lightweight Directory Services completed the request for replication state information.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request for replication state information.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005E5 | Internal event: Active Directory Lightweight Directory Services received a request for replication information to support domain controllers running Windows NT 4.0 or earlier with the following parameters.%n%nFlags:%n%1%nPreferred maximum length:%n%2 |
Internal event: Active Directory Lightweight Directory Services received a request for replication information to support domain controllers running Windows NT 4.0 or earlier with the following parameters.%n%nFlags:%n%1%nPreferred maximum length:%n%2 |
| 0x400005E6 | Internal event: Active Directory Lightweight Directory Services completed the request for replication information to support domain controllers running Windows NT 4.0 or earlier.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request for replication information to support domain controllers running Windows NT 4.0 or earlier.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005E7 | Internal event: Active Directory Lightweight Directory Services received a request to resolve names with the following parameters.%n%nNumber of names:%n%1%nCode page:%n%2%nLocale ID:%n%3%nFormat offered:%n%4%nFormat desired:%n%5%nFlags:%n%6 |
Internal event: Active Directory Lightweight Directory Services received a request to resolve names with the following parameters.%n%nNumber of names:%n%1%nCode page:%n%2%nLocale ID:%n%3%nFormat offered:%n%4%nFormat desired:%n%5%nFlags:%n%6 |
| 0x400005E8 | Internal event: Active Directory Lightweight Directory Services completed the request to resolve names with the following results.%n%nNumber of names:%n%2%nNumber resolved:%n%3%nNumber not resolved:%n%4%nLast status:%n%5 %7%n%nAdditional Data%nError value:%n%1 %6 |
Internal event: Active Directory Lightweight Directory Services completed the request to resolve names with the following results.%n%nNumber of names:%n%2%nNumber resolved:%n%3%nNumber not resolved:%n%4%nLast status:%n%5 %7%n%nAdditional Data%nError value:%n%1 %6 |
| 0x400005E9 | Internal event: Active Directory Lightweight Directory Services has received a request to update SPNs with the following parameters.%n%nAccount:%n%1%nOperation:%n%2%nNumber of SPNs:%n%3%nFlags:%n%4 |
Internal event: Active Directory Lightweight Directory Services has received a request to update SPNs with the following parameters.%n%nAccount:%n%1%nOperation:%n%2%nNumber of SPNs:%n%3%nFlags:%n%4 |
| 0x400005EA | Internal event: Active Directory Lightweight Directory Services completed the request to update SPNs.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to update SPNs.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400005EB | Internal event: Active Directory Lightweight Directory Services received a request for directory service information for the following directory partition.%n%nDirectory partition:%n%1%nInformation level:%n%2 |
Internal event: Active Directory Lightweight Directory Services received a request for directory service information for the following directory partition.%n%nDirectory partition:%n%1%nInformation level:%n%2 |
| 0x400005EC | Internal event: Active Directory Lightweight Directory Services completed the request for directory service information.%n%nAdditional Data%nStatus:%n%1 |
Internal event: Active Directory Lightweight Directory Services completed the request for directory service information.%n%nAdditional Data%nStatus:%n%1 |
| 0x400005ED | Internal event: Active Directory Lightweight Directory Services received a request for group memberships with the following parameters.%n%nNumber of names:%n%1%nOperation type:%n%2%nLimiting domain:%n%3%nFlags:%n%4 |
Internal event: Active Directory Lightweight Directory Services received a request for group memberships with the following parameters.%n%nNumber of names:%n%1%nOperation type:%n%2%nLimiting domain:%n%3%nFlags:%n%4 |
| 0x400005EE | Internal event: Active Directory Lightweight Directory Services completed the request for group memberships.%n%nAdditional Data%nStatus:%n%1 |
Internal event: Active Directory Lightweight Directory Services completed the request for group memberships.%n%nAdditional Data%nStatus:%n%1 |
| 0x400005F4 | Internal event: The following LDAP request operation was called by a client at the following network address using the following protocol.%n%nOperation:%n%1%nClient network address:%n%2%nProtocol:%n%3%n%nThis event is generally used for event tracing. |
Internal event: The following LDAP request operation was called by a client at the following network address using the following protocol.%n%nOperation:%n%1%nClient network address:%n%2%nProtocol:%n%3%n%nThis event is generally used for event tracing. |
| 0x400005F5 | Internal event: The following LDAP request operation completed with the following status.%n%nOperation:%n%3%nExit ID:%n%1%n%nThis information is generally used for event tracing.%n%nAdditional Data%nError value:%n%2 %4 |
Internal event: The following LDAP request operation completed with the following status.%n%nOperation:%n%3%nExit ID:%n%1%n%nThis information is generally used for event tracing.%n%nAdditional Data%nError value:%n%2 %4 |
| 0x400005F6 | Tidsplanen for følgende Connection-objekt har blitt oppdatert. Dette objektet representerer en replikeringstilkobling mellom følgende katalogservere.%n%nConnection-objekt:%n%1%nKildekatalogtjeneste:%n%2%nMålkatalogtjeneste:%n%3 |
The schedule on the following Connection object has been updated. This object represents a replication connection between the following directory servers.%n%nConnection object:%n%1%nSource directory service:%n%2%nDestination directory service:%n%3 |
| 0x400005FA | Internal event; During intersite replication, the local domain controller received a message of the following size.%n%nLength of message (bytes):%n%1%nMessage description:%n%2 |
Internal event; During intersite replication, the local domain controller received a message of the following size.%n%nLength of message (bytes):%n%1%nMessage description:%n%2 |
| 0x400005FD | Internal event: The transport type for the following Connection object has been updated. This object represents replication between the following directory servers.%n%nConnection object:%n%1%nSource directory service:%n%2%nDestination directory service:%n%3%nNew transport type:%n%4 |
Internal event: The transport type for the following Connection object has been updated. This object represents replication between the following directory servers.%n%nConnection object:%n%1%nSource directory service:%n%2%nDestination directory service:%n%3%nNew transport type:%n%4 |
| 0x400005FF | Internal event: The LDAP server returned an error.%n%nAdditional Data%nError value:%n%1 |
Internal event: The LDAP server returned an error.%n%nAdditional Data%nError value:%n%1 |
| 0x40000604 | En sikkerhetsidentifikator (SID) kan ikke legges til i følgende objekt.%n%nObjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %4%nIntern ID:%n%2 |
A security identifier (SID) could not be added to the following object.%n%nObject:%n%1%n%nAdditional Data%nError value:%n%3 %4%nInternal ID:%n%2 |
| 0x40000605 | Internal event: A security identifier (SID) has been added to the following object.%n%nObject:%n%1%nSID:%n%2 |
Internal event: A security identifier (SID) has been added to the following object.%n%nObject:%n%1%nSID:%n%2 |
| 0x40000606 | Internal event: The following connection is considered to be an active, viable connection for replication from the following site.%n%nConnection object:%n%1%nDirectory partition:%n%2%nTransport:%n%3%nSite:%n%4%n%nNo new connections will need to be created for this site. |
Internal event: The following connection is considered to be an active, viable connection for replication from the following site.%n%nConnection object:%n%1%nDirectory partition:%n%2%nTransport:%n%3%nSite:%n%4%n%nNo new connections will need to be created for this site. |
| 0x40000607 | Internal event: The following connection may or may not be considered active at present. However, it is a viable connection for replication from the following site.%n%nConnection object:%n%1%nDirectory partition:%n%2%nTransport:%n%3%nSite:%n%4%nConnection reason code:%n0x%5%nGlobal catalog topology flag:%n%6%n%nThis existing connection will be preserved. |
Internal event: The following connection may or may not be considered active at present. However, it is a viable connection for replication from the following site.%n%nConnection object:%n%1%nDirectory partition:%n%2%nTransport:%n%3%nSite:%n%4%nConnection reason code:%n0x%5%nGlobal catalog topology flag:%n%6%n%nThis existing connection will be preserved. |
| 0x40000608 | Internal event: The following directory service was chosen as a bridgehead server for this site.%n%nDirectory service:%n%1%nSite:%n%2%nDirectory partition:%n%3%nTransport:%n%4 |
Internal event: The following directory service was chosen as a bridgehead server for this site.%n%nDirectory service:%n%1%nSite:%n%2%nDirectory partition:%n%3%nTransport:%n%4 |
| 0x4000060C | I løpet av replikeringen fant Active Directory Lightweight Directory Services følgende objekt eller dets overordnede objekt i en katalogpartisjon på den lokale domenekontrolleren, som skiller seg fra følgende katalogpartisjon som endringer replikeres fra. Dette kan skje når objektet eller dets overordnede objekt har blitt flyttet på tvers av partisjoner. På grunn av replikeringsventetiden har imidlertid én av katalogserverne ennå ikke motatt varsling om flyttingen.%n%nObjekt:%n%2%nObjekt-GUID:%n%3%nGUID for overordnet objekt (hvis tilgjengelig):%n%4%nKatalogpartisjon:%n%1%nKildekatalogserver:%n%5%n%nReplikering av denne katalogpartisjonen fra denne kildekatalogserveren kan ikke fortsette på dette tidspunktet. Denne tilstanden er midlertidig. Et forsøk på å replikere denne katalogpartisjonen vil bli utført på nytt senere. |
During replication, Active Directory Lightweight Directory Services found the following object or its parent object in a directory partition on the local domain controller that is different from the following directory partition from which changes are being replicated. This can occur when the object or its parent object has been moved across partitions. However, due to replication latency, one of the directory servers has not yet received notification of the move.%n%nObject:%n%2%nObject GUID:%n%3%nParent object GUID (if available):%n%4%nDirectory partition:%n%1%nSource directory server:%n%5%n%nReplication of this directory partition from this source directory server cannot continue at this time. This condition is transient. An attempt to replicate this directory partition will be tried again later. |
| 0x4000060F | Internal event: The local domain controller is up to date with its immediate replication partners and has verified that it has synchronized the primary domain directory partition at least once since the Active Directory Lightweight Directory Services installation.%n%nThe local domain controller can now be accessed by clients. |
Internal event: The local domain controller is up to date with its immediate replication partners and has verified that it has synchronized the primary domain directory partition at least once since the Active Directory Lightweight Directory Services installation.%n%nThe local domain controller can now be accessed by clients. |
| 0x40000610 | Internal event: The local domain controller is not being advertised by the domain controller locator service. As a result, this domain controller cannot be accessed by other domain controllers and clients. |
Internal event: The local domain controller is not being advertised by the domain controller locator service. As a result, this domain controller cannot be accessed by other domain controllers and clients. |
| 0x40000611 | Internal event: This directory service is making progress performing an initial synchronization of the following directory partition.%n%nDirectory partition:%n%1 |
Internal event: This directory service is making progress performing an initial synchronization of the following directory partition.%n%nDirectory partition:%n%1 |
| 0x40000613 | Denne katalogserveren er ikke tilgjengelig for klienter før den har fullført en første synkronisering av hver skrivbare katalogpartisjon den inneholder. For øyeblikket er ikke disse første synkroniseringene fullført.%n%nSynkroniseringene fortsetter. |
This directory server will not be available to clients until it has completed an initial synchronization of each writeable directory partition that it holds. At this time, these initial synchronizations have not been completed.%n%nThe synchronizations will continue. |
| 0x40000614 | Internal event: This directory service could not complete the initial synchronization of the following directory partition from any source directory servers.%n%nDirectory partition:%n%1 |
Internal event: This directory service could not complete the initial synchronization of the following directory partition from any source directory servers.%n%nDirectory partition:%n%1 |
| 0x40000615 | Denne katalogserveren har ikke fullført en fullstendig synkronisering av følgende katalogpartisjon. Denne katalogserveren er ikke tilgjengelig for klienter før denne oppgaven er fullført.%n%nKatalogpartisjon:%n%1%n%nEt forsøk på en fullstendig replikering av denne katalogpartisjonen vil bli utført på nytt senere. |
This directory server has not completed a full synchronization of the following directory partition. This directory server will not available to clients until this task is completed.%n%nDirectory partition:%n%1%n%nAn attempt to complete a full synchronization of this directory partition will be tried again later. |
| 0x40000616 | Den lokale domenekontrolleren har blitt valgt til å være global katalog. Domenekontrolleren har imidlertid aldri fullført en fullstendig synkronisering av følgende katalogpartisjon.%n%nKatalogpartisjon:%n%1%n%nEn forutsetning for å bli global katalog er at hver katalogpartisjon som driftes av den lokale domenekontrolleren, må fullføre minst én fullstendig synkronisering. Hvis den lokale domenekontrolleren nylig var en global katalog og fikk nivået senket, er det mulig at den tidligere kopien av katalogpartisjonen er i ferd med å fjernes.%n%n%nEt forsøk på en fullstendig replikering av denne katalogpartisjonen vil bli utført på nytt senere. |
The local domain controller has been selected to be a global catalog. However, the domain controller has never completed a full synchronization of the following directory partition.%n%nDirectory partition:%n%1%n%nA precondition to become a global catalog is that every directory partition hosted by the local domain controller must complete at least one full synchronization. If the local domain controller was recently a global catalog and was demoted, it is possible that the previous copy of the directory partition is in the process of being removed.%n%n%nAn attempt to complete a full synchronization of this directory partition will be tried again later. |
| 0x40000617 | Den lokale domenekontrolleren har blitt valgt til å være global katalog. Domenekontrolleren er imidlertid ikke vert for en skrivebeskyttet replika av følgende katalogpartisjon.%n%nKatalogpartisjon:%n%1%n%nEn forutsetning for å bli global katalog er at en domenekontroller må være vert for en skrivebeskyttet replika av alle katalogpartisjoner i skogen. Denne hendelsen har kanskje oppstått fordi en KCC-oppgave (Knowledge Consistency Checker) ikke er fullført, eller fordi domenekontrolleren ikke kan legge til en replika av katalogpartisjonen på grunn av utilgjengelige kildedomenekontrollere.%n%nEt forsøk på å legge til replikaen blir utført på nytt ved neste KCC-intervall. |
The local domain controller has been selected to be a global catalog. However, the domain controller does not host a read-only replica of the following directory partition.%n%nDirectory partition:%n%1%n%nA precondition to becoming a global catalog is that a domain controller must host a read-only replica of all directory partitions in the forest. This event might have occurred because a Knowledge Consistency Checker (KCC) task has not completed or because the domain controller is unable to add a replica of the directory partition due to unavailable source domain controllers.%n%nAn attempt to add the replica will be tried again at the next KCC interval. |
| 0x40000618 | Internal event: A new replica for the following directory partition has been added to this directory service. This directory service will now perform a synchronization for the first time from the following source directory service with these options.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nOptions:%n0x%3 |
Internal event: A new replica for the following directory partition has been added to this directory service. This directory service will now perform a synchronization for the first time from the following source directory service with these options.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nOptions:%n0x%3 |
| 0x40000619 | Internal event: The user has requested a full synchronization of the following directory partition from the source directory service.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nOptions:%n0x%3 |
Internal event: The user has requested a full synchronization of the following directory partition from the source directory service.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nOptions:%n0x%3 |
| 0x4000061A | Internal event: An attempt to synchronize the following directory partition for the first time from the source directory service is progressing.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nOptions:%n0x%3 |
Internal event: An attempt to synchronize the following directory partition for the first time from the source directory service is progressing.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nOptions:%n0x%3 |
| 0x4000061C | Active Directory Lightweight Directory Services utførte ikke første gangs synkroniseringer fordi følgende registernøkkel har blitt angitt til å deaktivere dem.%n%nRegisternøkkel:%nHKLM\\%1%nRegisterverdi:%nReplikering som utfører første synkronisering%n%nBekreftelse på at hver katalogpartisjon har blitt fullført minst én gang, blir fortsatt utført. Denne katalogserveren synkroniseres med replikeringspartnerne i en normal periodisk tidsplan, men det utføres ikke en første synkronisering hver gang katalogserveren startes på nytt. |
Active Directory Lightweight Directory Services did not perform initial synchronizations because the following registry key has been set to disable them.%n%nRegistry key:%nHKLM\\%1%nRegistry value:%nRepl Perform Initial Synchronizations%n%nVerification that each directory partition has successfully synchronized at least once will still be performed. This directory server will synchronize with its replication partners on a normal periodic schedule, but it will not perform an initial synchronization each time it is restarted. |
| 0x40000621 | Installasjonen av Active Directory Lightweight Directory Services ble avbrutt. |
Active Directory Lightweight Directory Services installation was cancelled. |
| 0x40000622 | Intersite Messaging-tjenesten som bruker SMTP-transport, har konfigurert en mappe for levering av SMTP-e-post automatisk for denne domenekontrolleren, og den mappen skal brukes til e-postbaserte replikeringsmeldinger. Følgende mappe ble valgt for bruk med SMTP-tjenesten.%n%nMappe for levering av SMTP-e-post:%n%1 |
The Intersite Messaging service using the SMTP transport has auto-configured a SMTP mail drop folder for this domain controller to be used for mail-based replication messages. The following folder was chosen for use with the SMTP service.%n%nSMTP mail drop folder:%n%1 |
| 0x40000627 | Ett eller flere nye attributter har blitt lagt til i det delvise attributtsettet for følgende katalogpartisjon. En fullstendig synkronisering utføres fra kildedomenekontrolleren i den neste replikeringssyklusen.%n%nKatalogpartisjon:%n%1%nKildedomenekontroller:%n%2 |
One or more new attributes has been added to the partial attribute set for the following directory partition. A full synchronization will be performed from the source domain controller on the next replication cycle.%n%nDirectory partition:%n%1%nSource domain controller:%n%2 |
| 0x40000629 | Internal event: The following object has inherited the security identifier (SID) of an object that is now deleted.%n%nObject:%n%2%nDeleted object:%n%1 |
Internal event: The following object has inherited the security identifier (SID) of an object that is now deleted.%n%nObject:%n%2%nDeleted object:%n%1 |
| 0x4000062A | Nivåheving av den lokale domenekontrolleren til en global katalog har blitt forsinket fordi kravet til antall personer for katalogpartisjonen ikke er oppfylt. Kravnivået for antall personer og gjeldende domenekontrollernivå er følgende.%n%nKravnivå for antall personer:%n%1%nDomenekontrollernivå:%n%2%n%nFølgende registernøkkelverdi definerer kravnivået for antall personer for katalogpartisjonen.%n%nRegisternøkkelverdi:%nHKeyLocalMachine\\System\\ CurrentControlSet\\Services\\NTDS\\Parameters\\Global Catalog Partition Occupancy%n%nHøyere krav til antall personer inkluderer de lavere nivåene. Nivåene er definert på følgende måte:%n%n(0) Angir ingen krav til antall personer.%n(1) Angir at minst én skrivebeskyttet katalogpartisjon på området har blitt lagt til ved hjelp av KCC (Knowledge Consistency Checker).%n(2) Angir at minst én katalogpartisjon på området har blitt fullstendig synkronisert.%n(3) Angir at alle skrivebeskyttede katalogpartisjoner på området har blitt lagt til av KCC (minst én har blitt synkronisert).%n(4) Angir at alle katalogpartisjoner på området har blitt fullstendig synkronisert.%n(5) Angir at alle skrivebeskyttede katalogpartisjoner i skogen har blitt lagt til av KCC (minst én har blitt synkronisert).%n(6) Angir at alle katalogpartisjoner i skogen har blitt fullstendig synkronisert. |
Promotion of the local domain controller to a global catalog has been delayed because the directory partition occupancy requirements have not been met. The occupancy requirement level and current domain controller level are as follows.%n%nOccupancy requirement level:%n%1%nDomain controller level:%n%2%n%nThe following registry key value defines the directory partition occupancy requirement level.%n%nRegistry key value:%nHKeyLocalMachine\\System\\ CurrentControlSet\\Services\\NTDS\\Parameters\\Global Catalog Partition Occupancy%n%nHigher occupancy requirement levels include the lower levels. The levels are defined as follows:%n%n(0) Indicates no occupancy requirement.%n(1) Indicates at least one read-only directory partition in the site has been added by the Knowledge Consistency Checker (KCC).%n(2) Indicates at least one directory partition in the site has been fully synchronized.%n(3) Indicates all read-only directory partitions in the site have been added by the KCC (at least one has been synchronized).%n(4) Indicates all directory partitions in the site have been fully synchronized.%n(5) Indicates all read-only directory partitions in the forest have been added by the KCC (at least one has been synchronized).%n(6) Indicates all directory partitions in the forest have been fully synchronized. |
| 0x4000062C | Internal event: A long-running Active Directory Lightweight Directory Services inbound replication task has finished with the following parameters.%n%nElapsed time (minutes):%n%1%nOperation:%n%2%nOptions:%n0x%3%nParameter 1:%n%5%nParameter 2:%n%6%nParameter 3:%n%7%nParameter 4:%n%8%n%nA long-running replication task may also occur when a system has been unavailable or a directory partition has been unavailable for an extended period of time. A long running replication task may indicate a large number of updates, or a number of complex updates occurring at the source directory service. Performing these updates during non-critical times may prevent replication delays.%n%nA long running replication task is normal in the case of adding a new directory partition to Active Directory Lightweight Directory Services. This can occur because of a new installation, global catalog promotion, or a connection generated by the Knowledge Consistency Checker (KCC).%n%nAdditional Data%nError value:%n%4 |
Internal event: A long-running Active Directory Lightweight Directory Services inbound replication task has finished with the following parameters.%n%nElapsed time (minutes):%n%1%nOperation:%n%2%nOptions:%n0x%3%nParameter 1:%n%5%nParameter 2:%n%6%nParameter 3:%n%7%nParameter 4:%n%8%n%nA long-running replication task may also occur when a system has been unavailable or a directory partition has been unavailable for an extended period of time. A long running replication task may indicate a large number of updates, or a number of complex updates occurring at the source directory service. Performing these updates during non-critical times may prevent replication delays.%n%nA long running replication task is normal in the case of adding a new directory partition to Active Directory Lightweight Directory Services. This can occur because of a new installation, global catalog promotion, or a connection generated by the Knowledge Consistency Checker (KCC).%n%nAdditional Data%nError value:%n%4 |
| 0x4000062E | Internal event: Active Directory Lightweight Directory Services schema cache has been updated successfully. |
Internal event: Active Directory Lightweight Directory Services schema cache has been updated successfully. |
| 0x40000631 | Internal event: The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was successful. |
Internal event: The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was successful. |
| 0x40000633 | Denne katalogtjenesten har blitt gjenopprettet eller har blitt konfigurert til å være vert for en programkatalogpartisjon.Det fører til at katalogtjenestens replikerings-ID har blitt endret. En partner har bedt om replikeringsendringerved hjelp av vår gamle ID. Startsekvensnummeret har blitt endret.%nMålkatalogtjenesten som tilsvarer følgende objekt-GUID, har bedt om endringer som starter på en USN som kommer før USNen som den lokale katalogtjenesten ble gjenopprettet fra, fra sikkerhetskopieringsmediet.%n%nObjekt-GUID:%n%1%nUSN på gjenopprettingstidspunktet:%n%2%n%nDet fører til at UpToDateness Vector for målkatalogtjenesten har blitt konfigurert med følgende innstillinger.%n%nGUID for forrige database:%n%3%nUSN for forrige objekt:%n%4%nUSN for forrige egenskap:%n%5%nGUID for ny database:%n%6%nUSN for nytt objekt:%n%7%nUSN for ny egenskap:%n%8 |
This directory service has been restored or has been configured to host an application directory partition.As a result, its replication identity has changed. A partner has requested replication changesusing our old identity. The starting sequence number has been adjusted.%nThe destination directory service corresponding to the following object GUID has requested changes starting at a USN that precedes the USN at which the local directory service was restored from backup media.%n%nObject GUID:%n%1%nUSN at the time of restore:%n%2%n%nAs a result, the up-to-dateness vector of the destination directory service has been configured with the following settings.%n%nPrevious database GUID:%n%3%nPrevious object USN:%n%4%nPrevious property USN:%n%5%nNew database GUID:%n%6%nNew object USN:%n%7%nNew property USN:%n%8 |
| 0x40000638 | get changes%0 |
get changes%0 |
| 0x4000063C | unused |
unused |
| 0x40000644 | Internal event: The following client called the NspiUpdateStat operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiUpdateStat operation.%n%nClient:%n%1 |
| 0x40000645 | Internal event: The following client called the NspiUpdateStat operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiUpdateStat operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000646 | Internal event: The following client called the NspiCompareDNTs operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiCompareDNTs operation.%n%nClient:%n%1 |
| 0x40000647 | Internal event: The following client called the NspiCompareDNTs operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiCompareDNTs operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000648 | Internal event: The following client called the NspiQueryRows operation to read the following rows.%n%nClient:%n%1%nRows:%n%2 |
Internal event: The following client called the NspiQueryRows operation to read the following rows.%n%nClient:%n%1%nRows:%n%2 |
| 0x40000649 | Internal event: The following client called the NspiQueryRows operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiQueryRows operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x4000064A | Internal event: The following client called the NspiSeekEntries operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiSeekEntries operation.%n%nClient:%n%1 |
| 0x4000064B | Internal event: The following client called the NspiSeekEntries operation. The operation completed with the following status.%n%nClient:%n%1%n%nStatus code:%n%2 |
Internal event: The following client called the NspiSeekEntries operation. The operation completed with the following status.%n%nClient:%n%1%n%nStatus code:%n%2 |
| 0x4000064C | Internal event: The following client called the NspiGetMatches operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiGetMatches operation.%n%nClient:%n%1 |
| 0x4000064D | Internal event: The following client called the NspiGetMatches operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiGetMatches operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x4000064E | Internal event: The following client called the NspiResolveNames operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiResolveNames operation.%n%nClient:%n%1 |
| 0x4000064F | Internal event: The following client called the NspiResolveNames operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiResolveNames operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000650 | Internal event: The following client called the NspiDNToEph operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiDNToEph operation.%n%nClient:%n%1 |
| 0x40000651 | Internal event: The following client called the NspiDNToEph operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiDNToEph operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000652 | Internal event: The following client called the NspiGetHierarchyInfo operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiGetHierarchyInfo operation.%n%nClient:%n%1 |
| 0x40000653 | Internal event: The following client called the NspiGetHierarchyInfo operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiGetHierarchyInfo operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000654 | Internal event: The following client called the NspiResortRestriction operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiResortRestriction operation.%n%nClient:%n%1 |
| 0x40000655 | Internal event: The following client called the NspiResortRestriction operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiResortRestriction operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000656 | Internal event: The NspiBind operation was requested. |
Internal event: The NspiBind operation was requested. |
| 0x40000657 | Internal event: The following client called the NspiBind operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiBind operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000658 | Internal event: The following client called the NspiGetNamesFromIDs operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiGetNamesFromIDs operation.%n%nClient:%n%1 |
| 0x40000659 | Internal event: The following client called the NspiGetNamesFromIDs operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiGetNamesFromIDs operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x4000065A | Internal event: The following client called the NspiGetIDsFromNames operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiGetIDsFromNames operation.%n%nClient:%n%1 |
| 0x4000065B | Internal event: The following client called the NspiGetIDsFromNames operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiGetIDsFromNames operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x4000065C | Internal event: The following client called the NspiGetPropList operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiGetPropList operation.%n%nClient:%n%1 |
| 0x4000065D | Internal event: The following client called the NspiGetPropList operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiGetPropList operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x4000065E | Internal event: The following client called the NspiQueryColumns operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiQueryColumns operation.%n%nClient:%n%1 |
| 0x4000065F | Internal event: The following client called the NspiQueryColumns operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiQueryColumns operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000660 | Internal event: The following client called the NspiGetProps operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiGetProps operation.%n%nClient:%n%1 |
| 0x40000661 | Internal event: The following client called the NspiGetProps operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiGetProps operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000662 | Internal event: The following client called the NspiGetTemplateInfo operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiGetTemplateInfo operation.%n%nClient:%n%1 |
| 0x40000663 | Internal event: The following client called the NspiGetTemplateInfo operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiGetTemplateInfo operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000664 | Internal event: The following client called the NspiModProps operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiModProps operation.%n%nClient:%n%1 |
| 0x40000665 | Internal event: The following client called the NspiModProps operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiModProps operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000666 | Internal event: The following client called the NspiModLinkAtt operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiModLinkAtt operation.%n%nClient:%n%1 |
| 0x40000667 | Internal event: The following client called the NspiModLinkAtt operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiModLinkAtt operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x40000668 | Internal event: The following client called the NspiDeleteEntries operation.%n%nClient:%n%1 |
Internal event: The following client called the NspiDeleteEntries operation.%n%nClient:%n%1 |
| 0x40000669 | Internal event: The following client called the NspiDeleteEntries operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
Internal event: The following client called the NspiDeleteEntries operation. The operation completed with the following status.%n%nClient:%n%1%nStatus:%n%2 |
| 0x4000066B | Internal event: Active Directory Lightweight Directory Services performed the following number of search operations within this time interval.%n%nTime interval (hours):%n%1%nNumber of search operations:%n%2%n%nDuring this time interval, the following number of search operations were characterized as either expensive or inefficient.%n%nExpensive search operations:%n%3%nInefficient search operations:%n%4 |
Internal event: Active Directory Lightweight Directory Services performed the following number of search operations within this time interval.%n%nTime interval (hours):%n%1%nNumber of search operations:%n%2%n%nDuring this time interval, the following number of search operations were characterized as either expensive or inefficient.%n%nExpensive search operations:%n%3%nInefficient search operations:%n%4 |
| 0x4000066C | Internal event: A client issued a search operation with the following options.%n%nClient:%n%5%nStarting node:%n%1%nFilter:%n%2%nSearch scope:%n%6%nAttribute selection:%n%7%nServer controls:%n%8%nVisited entries:%n%3%nReturned entries:%n%4%nUsed indexes:%n%9%nPages referenced:%n%10%nPages read from disk:%n%11%nPages preread from disk:%n%12%nClean pages modified:%n%13%nDirty pages modified:%n%14%nSearch time (ms):%n%15%nAttributes Preventing Optimization:%n%16%nUser:%n%17 |
Internal event: A client issued a search operation with the following options.%n%nClient:%n%5%nStarting node:%n%1%nFilter:%n%2%nSearch scope:%n%6%nAttribute selection:%n%7%nServer controls:%n%8%nVisited entries:%n%3%nReturned entries:%n%4%nUsed indexes:%n%9%nPages referenced:%n%10%nPages read from disk:%n%11%nPages preread from disk:%n%12%nClean pages modified:%n%13%nDirty pages modified:%n%14%nSearch time (ms):%n%15%nAttributes Preventing Optimization:%n%16%nUser:%n%17 |
| 0x4000066E | Internal event: The Active Directory Lightweight Directory Services database has the following amount of free hard disk space remaining.%n%nFree hard disk space (megabytes):%n%1%nTotal allocated hard disk space (megabytes):%n%2 |
Internal event: The Active Directory Lightweight Directory Services database has the following amount of free hard disk space remaining.%n%nFree hard disk space (megabytes):%n%1%nTotal allocated hard disk space (megabytes):%n%2 |
| 0x40000671 | Legg til replika%0 |
Add Replica%0 |
| 0x40000672 | Slett replika%0 |
Delete Replica%0 |
| 0x40000673 | Synkroniser replika%0 |
Synchronize Replica%0 |
| 0x40000674 | Oppdater referanser%0 |
Update References%0 |
| 0x40000675 | Endre replika%0 |
Modify Replica%0 |
| 0x4000067A | Denne katalogtjenesten er ikke lenger konfigurert til å være vert for følgende katalogpartisjon. Det fører til at objektene i denne katalogpartisjonen fjernes fra den lokale Active Directory Lightweight Directory Services-databasen.%n%nKatalogpartisjon:%n%1%nAntall objekter som skal fjernes (omtrentlig):%n%2%nAntall navneverdier som skal fjernes (omtrentlig):%n%3%n%nFør disse objektene er fullstendig fjernet, kan ikke denne katalogtjenesten konfigureres på nytt for å være vert for denne katalogpartisjonen. |
This directory service is no longer configured to host the following directory partition. As a result, the objects in this directory partition will be removed from the local Active Directory Lightweight Directory Services database.%n%nDirectory partition:%n%1%nNumber of objects to be removed (approximately):%n%2%nNumber of name values to be removed (approximately):%n%3%n%nUntil these objects are completely removed, this directory service cannot be reconfigured to host this directory partition. |
| 0x4000067B | Fjerningen av følgende katalogpartisjon fra den lokale Active Directory Lightweight Directory Services-databasen har blitt gjenopptatt.%n%nKatalogpartisjon:%n%1%nAntall gjenstående objekter som skal fjernes (omtrentlig):%n%2%nAntall gjenstående navneverdier som skal fjernes (omtrentlig):%n%3 |
The removal of the following directory partition from the local Active Directory Lightweight Directory Services database has resumed.%n%nDirectory partition:%n%1%nNumber of objects remaining be removed (approximately):%n%2%nNumber of name values remaining be removed (approximately):%n%3 |
| 0x4000067C | Fjerningen av følgende katalogpartisjon fra den lokale Active Directory Lightweight Directory Services-databasen ble fullført.%n%nKatalogpartisjon:%n%1 |
The removal of the following directory partition from the local Active Directory Lightweight Directory Services database completed successfully.%n%nDirectory partition:%n%1 |
| 0x4000067D | Active Directory Lightweight Directory Services fjernet ikke objekter for følgende katalogpartisjon fra den lokale Active Directory Lightweight Directory Services-databasen.%n%nKatalogpartisjon:%n%1%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
Active Directory Lightweight Directory Services did not remove objects of the following directory partition from the local Active Directory Lightweight Directory Services database.%n%nDirectory partition:%n%1%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%3 %2 |
| 0x40000681 | Internal event: Active Directory Lightweight Directory Services has been tasked to get group memberships for the following number of users.%n%nNumber of users:%n%1 |
Internal event: Active Directory Lightweight Directory Services has been tasked to get group memberships for the following number of users.%n%nNumber of users:%n%1 |
| 0x40000682 | Internal event: Active Directory Lightweight Directory Services processed the group memberships of the requested users.%n%nAdditional Data%nError value:%n%2 %1 |
Internal event: Active Directory Lightweight Directory Services processed the group memberships of the requested users.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x40000689 | Internal Event: A request was made to apply a new value to an object. The value exists on the system, but it is marked as absent.%n%nObject:%n%1%nAttribute:%n%2%nValue:%n%3%nDeletion Time:%n%4%n%nThe absent value will be changed to a present value. |
Internal Event: A request was made to apply a new value to an object. The value exists on the system, but it is marked as absent.%n%nObject:%n%1%nAttribute:%n%2%nValue:%n%3%nDeletion Time:%n%4%n%nThe absent value will be changed to a present value. |
| 0x4000068B | Internal Event: A request was made to replace all the values of an attribute. An incoming value was not found in the existing attribute. The value exists on the attribute, but it is marked as absent.%n%nObject:%n%1%nAttribute:%n%2%nValue:%n%3%nDeletion Time:%n%4%n%nThe absent value will be changed to a present value. |
Internal Event: A request was made to replace all the values of an attribute. An incoming value was not found in the existing attribute. The value exists on the attribute, but it is marked as absent.%n%nObject:%n%1%nAttribute:%n%2%nValue:%n%3%nDeletion Time:%n%4%n%nThe absent value will be changed to a present value. |
| 0x4000068D | Internal Event: A request was made to remove all values of an attribute. A value was marked as absent.%n%nObject:%n%1%nAttribute:%n%2%nValue:%n%3%nDeletion Time:%n%4 |
Internal Event: A request was made to remove all values of an attribute. A value was marked as absent.%n%nObject:%n%1%nAttribute:%n%2%nValue:%n%3%nDeletion Time:%n%4 |
| 0x4000068E | Internal event: A request was made to remove a single value of an attribute.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4%n%nThe value was marked as absent. |
Internal event: A request was made to remove a single value of an attribute.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4%n%nThe value was marked as absent. |
| 0x4000068F | Internal event: The following metadata is associated with an attribute value.%n%nTime created:%n%1%nVersion:%n%2%nSource directory service GUID:%n%3%nSource directory service USN:%n%4%nTime changed:%n%5%nUSN changed:%n%6 |
Internal event: The following metadata is associated with an attribute value.%n%nTime created:%n%1%nVersion:%n%2%nSource directory service GUID:%n%3%nSource directory service USN:%n%4%nTime changed:%n%5%nUSN changed:%n%6 |
| 0x40000690 | Internal event: A change was filtered because the attribute was not a part of the partial attribute set.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5 |
Internal event: A change was filtered because the attribute was not a part of the partial attribute set.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5 |
| 0x40000691 | Internal event: A change was filtered because of the object's group type.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5 |
Internal event: A change was filtered because of the object's group type.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5 |
| 0x40000692 | Internal event: A change was filtered because it was not needed by the destination directory service.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5%nDestination directory service direct USN:%n%6%nDestination directory service UTD USN:%n%7 |
Internal event: A change was filtered because it was not needed by the destination directory service.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5%nDestination directory service direct USN:%n%6%nDestination directory service UTD USN:%n%7 |
| 0x40000693 | Internal event: A change was sent with the following parameters.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5%nDestination directory service direct USN:%n%6%nDestination directory service UTD USN:%n%7 |
Internal event: A change was sent with the following parameters.%n%nDirectory service USN:%n%1%nObject:%n%2%nObject GUID:%n%3%nAttribute:%n%4%nAttribute value:%n%5%nDestination directory service direct USN:%n%6%nDestination directory service UTD USN:%n%7 |
| 0x40000694 | Internal event: An attribute value change was not applied because the following object has been recycled.%n%nObject GUID:%n%1 |
Internal event: An attribute value change was not applied because the following object has been recycled.%n%nObject GUID:%n%1 |
| 0x40000695 | Internal event: An attribute value change was not applied because the following object was not found.%n%nObject GUID:%n%1%nAttribute:%n%2%nAttribute value:%n%3%n%nThis operation will be tried again later. Objects will be reordered to increase the chance that this object will be included in the packet. |
Internal event: An attribute value change was not applied because the following object was not found.%n%nObject GUID:%n%1%nAttribute:%n%2%nAttribute value:%n%3%n%nThis operation will be tried again later. Objects will be reordered to increase the chance that this object will be included in the packet. |
| 0x40000696 | Internal event: An attribute value change was not applied because the attribute value was not needed.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5 |
Internal event: An attribute value change was not applied because the attribute value was not needed.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5 |
| 0x40000697 | Internal event: The following metadata was retrieved from an attribute value.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4 |
Internal event: The following metadata was retrieved from an attribute value.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4 |
| 0x40000698 | Internal event: The following remote metadata is associated with the following attribute value.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute value:%n%3%nTime created:%n%4%nVersion:%n%5%nSource directory service GUID:%n%6%nSource directory service USN:%n%7%nTime changed:%n%8 |
Internal event: The following remote metadata is associated with the following attribute value.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute value:%n%3%nTime created:%n%4%nVersion:%n%5%nSource directory service GUID:%n%6%nSource directory service USN:%n%7%nTime changed:%n%8 |
| 0x40000699 | Internal event: The following attribute value change was applied.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5%nPresent:%n%6 |
Internal event: The following attribute value change was applied.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5%nPresent:%n%6 |
| 0x4000069A | Internal event: A timestamp conflict occurred between an attribute value created on the local directory service and an incoming attribute value created on the source directory service.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5%nTime the value was created on the source directory service:%n%6%nTime the value was created on the local directory service:%n%7%n%nWhen this directory service replicated with the other directory service, this conflict was detected. Both values were identical. As a result, the attribute value that was created later will be applied on the local directory service. |
Internal event: A timestamp conflict occurred between an attribute value created on the local directory service and an incoming attribute value created on the source directory service.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5%nTime the value was created on the source directory service:%n%6%nTime the value was created on the local directory service:%n%7%n%nWhen this directory service replicated with the other directory service, this conflict was detected. Both values were identical. As a result, the attribute value that was created later will be applied on the local directory service. |
| 0x4000069B | Internal event: An incoming attribute value on the following source object refers to a target object that has been recycled.%n%nSource Object DN:%n%1%nSource Object GUID:%n%2%nAttribute:%n%3%nTarget Object DN:%n%4%nTarget Object GUID:%n%5%n%nThe incoming attribute value change will be ignored. |
Internal event: An incoming attribute value on the following source object refers to a target object that has been recycled.%n%nSource Object DN:%n%1%nSource Object GUID:%n%2%nAttribute:%n%3%nTarget Object DN:%n%4%nTarget Object GUID:%n%5%n%nThe incoming attribute value change will be ignored. |
| 0x4000069C | Internal event: Active Directory Lightweight Directory Services cannot apply an incoming attribute value change during replication because the following object is not present in the local Active Directory Lightweight Directory Services database.%n%nObject GUID:%n%1%nAttribute:%n%2%nAttribute value:%n%3%n%nAn attempt was made to reorder the objects according to their parent objects, but this did not resolve the problem. The incoming attribute value change will not be applied. The source directory service may have replicated with the local directory service within a tombstone lifetime. |
Internal event: Active Directory Lightweight Directory Services cannot apply an incoming attribute value change during replication because the following object is not present in the local Active Directory Lightweight Directory Services database.%n%nObject GUID:%n%1%nAttribute:%n%2%nAttribute value:%n%3%n%nAn attempt was made to reorder the objects according to their parent objects, but this did not resolve the problem. The incoming attribute value change will not be applied. The source directory service may have replicated with the local directory service within a tombstone lifetime. |
| 0x4000069D | Internal event: A request was made to add a value to an attribute.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4%n%nThe value does not exist on this attribute in any form. The state of the value is absent. As a result, the new value was created. |
Internal event: A request was made to add a value to an attribute.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4%n%nThe value does not exist on this attribute in any form. The state of the value is absent. As a result, the new value was created. |
| 0x4000069F | Denne katalogtjenesten støtter nå replikering med koblet verdi. Hver verdi i et attributt med flere verdier replikeres nå enkeltvis for å redusere nettverksbåndbredden og for å gi en bedre grad av konfliktløsing. |
This directory service now supports linked-valued replication. Each value of a multivalued attribute now replicates individually to reduce network bandwidth and to provide a finer degree of conflict resolution. |
| 0x400006A0 | Replikerer dataene %1: Mottok %2 av omtrent %3 objekter og %4 av omtrent %5 unike navneverdier ... |
Replicating data %1: Received %2 out of approximately %3 objects and %4 out of approximately %5 distinguished name (DN) values... |
| 0x400006A1 | Internal event: Active Directory Lightweight Directory Services removed the following expired, deleted attribute value from the following object.%n%nObject:%n%2%nAttribute value:%n%1 |
Internal event: Active Directory Lightweight Directory Services removed the following expired, deleted attribute value from the following object.%n%nObject:%n%2%nAttribute value:%n%1 |
| 0x400006A6 | Den globale katalogen fullførte synkronisering av det delvise attributtsettet for følgende katalogpartisjon fra følgende domenekontroller.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%2%n%nDette er en spesiell replikeringssyklus på grunn av tillegg av ett eller flere attributter i det delvise attributtsettet. |
The global catalog completed synchronization of the partial attribute set for the following directory partition from the following domain controller.%n%nDirectory partition:%n%1%nDomain controller:%n%2%n%nThis is a special replication cycle due to the addition of one or more attributes to the partial attribute set. |
| 0x400006A7 | Den globale katalogen startet en fullstendig synkronisering for følgende katalogpartisjon. Dette er en spesiell replikeringssyklus på grunn av tillegg av ett eller flere attributter i det delvise attributtsettet.%n%nKatalogpartisjon:%n%1%n%nDette kan føre til omfattende nettverkstrafikk. |
The global catalog initiated a full synchronization for the following directory partition. This is a special replication cycle due to the addition of one or more attributes to the partial attribute set.%n%nDirectory partition:%n%1%n%nThis might result in substantial network traffic. |
| 0x400006A8 | Den globale katalogen startet replikering av et medlem av det delvise attributtsettet for følgende katalogpartisjon fra følgende domenekontroller.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%2%n%nDette er en spesiell replikeringssyklus på grunn av tillegg av ett eller flere attributter i det delvise attributtsettet. |
The global catalog initiated replication of a member of the partial attribute set for the following directory partition from the following domain controller.%n%nDirectory partition:%n%1%nDomain controller:%n%2%n%nThis is a special replication cycle due to the addition of one or more attributes to the partial attribute set. |
| 0x400006A9 | Internal event: The global catalog found the following domain controller to replicate the partial attribute set for the following directory partition.%n%nDomain controller:%n%1%nDirectory partition:%n%2%n%nThe previous replication attempt was unsuccessful. |
Internal event: The global catalog found the following domain controller to replicate the partial attribute set for the following directory partition.%n%nDomain controller:%n%1%nDirectory partition:%n%2%n%nThe previous replication attempt was unsuccessful. |
| 0x400006AA | Internal event: The global catalog found the following domain controller to replicate the partial attribute set for the following directory partition.%n%nDomain controller:%n%1%nDirectory partition:%n%2 |
Internal event: The global catalog found the following domain controller to replicate the partial attribute set for the following directory partition.%n%nDomain controller:%n%1%nDirectory partition:%n%2 |
| 0x400006AB | Den globale katalogen fant ikke en replikapartner for replikering avdet delvise attributtsettet for følgende katalogpartisjon.%n%n%nKatalogpartisjon:%n%1 |
The global catalog has failed to find a replica partner for replication ofthe partial attribute set for the following directory partition.%n%n%nDirectory partition:%n%1 |
| 0x400006AC | Internal event: The global catalog registered the following source domain controller to replicate the partial attribute set for the following directory partition.%n%nSource domain controller:%n%1%nDirectory partition:%n%2 |
Internal event: The global catalog registered the following source domain controller to replicate the partial attribute set for the following directory partition.%n%nSource domain controller:%n%1%nDirectory partition:%n%2 |
| 0x400006AD | Internal event: The global catalog reset registration for the following source domain controller as a replication partner for replication of the partial attribute set for the following directory partition.%n%nSource domain controller:%n%1%nDirectory partition:%n%2 |
Internal event: The global catalog reset registration for the following source domain controller as a replication partner for replication of the partial attribute set for the following directory partition.%n%nSource domain controller:%n%1%nDirectory partition:%n%2 |
| 0x400006AF | Internal event: The global catalog ignored a queue request for replication of the partial attribute set for the following directory partition from the following source domain controller. This operation is in progress.%n%nSource domain controller:%n%1%nDirectory partition:%n%1 |
Internal event: The global catalog ignored a queue request for replication of the partial attribute set for the following directory partition from the following source domain controller. This operation is in progress.%n%nSource domain controller:%n%1%nDirectory partition:%n%1 |
| 0x400006B1 | Internal event: An appropriate index to be used for virtual list views (VLV) sorted on an attribute was not found.%n%nAttribute:%n%1%n%nUser Action%nIf this event continues to occur, consider creating a new VLV containerized index. |
Internal event: An appropriate index to be used for virtual list views (VLV) sorted on an attribute was not found.%n%nAttribute:%n%1%n%nUser Action%nIf this event continues to occur, consider creating a new VLV containerized index. |
| 0x400006B2 | Internal event: The type of a group object was changed to universal. A member value was updated so that it will replicate to the global catalog.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4 |
Internal event: The type of a group object was changed to universal. A member value was updated so that it will replicate to the global catalog.%n%nObject:%n%1%nAttribute:%n%2%nAttribute value:%n%3%nDeletion time:%n%4 |
| 0x400006B4 | Internal event: Active Directory Lightweight Directory Services updated the following attribute value on the following object.%n%nObject:%n%2%nAttribute value:%n%1 |
Internal event: Active Directory Lightweight Directory Services updated the following attribute value on the following object.%n%nObject:%n%2%nAttribute value:%n%1 |
| 0x400006BA | Funksjonsnivået for NTDS-innstillingsobjektet for den lokale Active Directory Lightweight Directory Services-forekomsten er oppdatert.%n%nGammelt funksjonsnivå:%n%1%nNytt funksjonsnivå:%n%2 |
The functional level on the NTDS Settings object for the local Active Directory Lightweight Directory Services instance has been updated.%n%nOld functional level:%n%1%nNew functional level:%n%2 |
| 0x400006C2 | Katalogtjenesten er ikke lenger konfigurert til å være vert for følgende programkatalogpartisjon. Denne programkatalogpartisjonen blir ikke lenger replikert fra katalogtjenesten med følgende nettverksadresse.%n%nProgramkatalogpartisjon:%n%1%nKatalogtjeneste:%n%3%nNettverksadresse:%n%2 |
The directory service is no longer configured to host the following application directory partition. This application directory partition is no longer replicated from the directory service at the following network address.%n%nApplication directory partition:%n%1%nDirectory Service:%n%3%nNetwork address:%n%2 |
| 0x400006C3 | Katalogtjenesten blir ikke lenger konfigurert til å være vert for følgende programkatalogpartisjon. Det fører til at KCC (Knowledge Consistency Checker) forsøkte å stoppe replikering av denne programkatalogpartisjonen fra katalogtjenesten med følgende nettverksadresse, men forsøket mislyktes.%n%nProgramkatalogpartisjon:%n%1%nKatalogtjeneste:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt ved neste KCC-intervall.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The Directory Service is no longer configured to host the following application directory partition. As a result, the Knowledge Consistency Checker (KCC) attempted to stop replication of this application directory partition from the Directory Service at the following network address, but the attempt failed.%n%nApplication directory partition:%n%1%nDirectory Service:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again at the next KCC interval.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400006C4 | Katalogtjenesten er ikke lenger konfigurert til å være vert for følgende programkatalogpartisjon. Et forsøk på å overføre katalogtjenestens oppdateringer og driftsovervåkerroller (hvis tilgjengelig) til følgende katalogtjeneste var vellykket.%n%nProgramkatalogpartisjon:%n%1%nKatalogtjeneste:%n%2%n%nObjektene i denne katalogpartisjonen blir fjernet fra Active Directory Lightweight Directory Services-databasen for katalogtjenesten. |
The Directory Service is no longer configured to host the following application directory partition. An attempt to transmit its updates and transfer its operations master roles (if any) to the following Directory Service succeeded.%n%nApplication directory partition:%n%1%nDirectory Service:%n%2%n%nThe objects in this directory partition will be removed from the Active Directory Lightweight Directory Services database on the Directory Service. |
| 0x400006C5 | Katalogtjenesten er ikke lenger konfigurert til å være vert for følgende programkatalogpartisjon. Et forsøk på å overføre katalogtjenestens oppdateringer og driftsovervåkerroller (hvis tilgjengelig) til følgende katalogtjeneste mislyktes.%n%nProgramkatalogpartisjon:%n%1%nKatalogtjeneste:%n%2%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The Directory Service is no longer configured to host the following application directory partition. An attempt to transmit its updates and transfer its operations master roles (if any) to the following Directory Service failed.%n%nApplication directory partition:%n%1%nDirectory Service:%n%2%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x400006C6 | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivbar replika av følgende katalogpartisjon. Tidligere hadde den en skrivebeskyttet replika for denne katalogpartisjonen. Denne katalogpartisjonen replikerer ikke lenger fra domenekontrolleren med følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%3%nNettverksadresse:%n%2 |
The local domain controller is now configured to host a writeable replica of the following directory partition. It previously had a read-only replica of this directory partition. This directory partition will no longer replicate from the domain controller at the following at network address.%n%nDirectory partition:%n%1%ndomain controller:%n%3%nNetwork address:%n%2 |
| 0x400006C7 | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivbar replika av følgende katalogpartisjon. Et forsøk på å stoppe replikering av denne katalogpartisjonen fra domenekontrolleren med følgende nettverksadresse mislyktes.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt ved neste KCC-intervall (Knowledge Consistency Checker).%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The local domain controller is now configured to host a writeable replica of the following directory partition. An attempt to stop replication of this directory partition from the domain controller at the following network address failed.%n%nDirectory partition:%n%1%ndomain controller:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again at the next Knowledge Consistency Checker (KCC) interval.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400006C8 | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivbar replika av følgende katalogpartisjon. Tidligere hadde den en skrivebeskyttet replika for denne katalogpartisjonen.%n%nKatalogpartisjon:%n%1%n%nObjektene i den skrivebeskyttede replikaen for denne katalogpartisjonen fjernes fra den lokale domenekontrolleren. |
The local domain controller is now configured to host a writeable replica of the following directory partition. It previously had a read-only replica of this directory partition.%n%nDirectory partition:%n%1%n%nThe objects in the read-only replica of this directory partition will be removed from the local domain controller. |
| 0x400006C9 | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivbar replika av følgende katalogpartisjon. Tidligere hadde den en skrivebeskyttet replika for denne katalogpartisjonen. Et forsøk på å fjerne objektene i denne katalogpartisjonen fra den lokale domenekontrolleren mislyktes.%n%nKatalogpartisjon:%n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The local domain controller is now configured to host a writeable replica of the following directory partition. It previously had a read-only replica of this directory partition. An attempt to remove the objects in this directory partition from the local domain controller failed.%n%nDirectory partition:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0x400006CA | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivebeskyttet replika av følgende katalogpartisjon. Tidligere hadde den en skrivbar replika for denne katalogpartisjonen. Denne katalogpartisjonen replikerer ikke lenger fra domenekontrolleren med følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%3%nNettverksadresse:%n%2 |
The local domain controller is now configured to host a read-only replica of the following directory partition. It previously had a writeable replica of this directory partition. This directory partition will no longer be replicated from the domain controller at the following network address.%n%nDirectory partition:%n%1%ndomain controller:%n%3%nNetwork address:%n%2 |
| 0x400006CB | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivebeskyttet replika av følgende katalogpartisjon. Et forsøk på å stoppe replikering av denne katalogpartisjonen fra domenekontrolleren med følgende nettverksadresse mislyktes.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The local domain controller is now configured to host a read-only replica of the following directory partition. An attempt to stop replication of this directory partition from the domain controller at the following network address failed.%n%nDirectory partition:%n%1%ndomain controller:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400006CC | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivebeskyttet replika av følgende katalogpartisjon. Tidligere hadde den en skrivbar replika for denne katalogpartisjonen.%n%nKatalogpartisjon:%n%1%n%nObjektene i den skrivbare replikaen for denne katalogpartisjonen blir fjernet fra den lokale domenekontrolleren. |
The local domain controller is now configured to host a read-only replica of the following directory partition. It previously had a writeable replica of this directory partition.%n%nDirectory partition:%n%1%n%nThe objects in the writeable replica of this directory partition will be removed from the local domain controller. |
| 0x400006CD | Den lokale domenekontrolleren er nå konfigurert til å være vert for en skrivebeskyttet replika av følgende katalogpartisjon. Tidligere hadde den en skrivbar replika for denne katalogpartisjonen. Et forsøk på å fjerne objektene i denne katalogpartisjonen fra den lokale domenekontrolleren mislyktes.%n%nKatalogpartisjon:%n%1%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The local domain controller is now configured to host a read-only replica of the following directory partition. It previously had a writeable replica of this directory partition. An attempt to remove the objects in this directory partition from the local domain controller failed.%n%nDirectory partition:%n%1%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x400006CE | Den lokale domenekontrolleren er vert for en skrivbar replika for følgende katalogpartisjon. Kildedomenekontrolleren med følgende nettverksadresse er imidlertid vert for en skrivebeskyttet replika for denne katalogpartisjonen. Skrivbare replikaer for katalogpartisjoner kan ikke replikere fra skrivebeskyttede replikaer fordi skrivebeskyttede replikaer ikke inneholder alle attributtene som kreves for å fylle skrivbare replikaer.%n%nKatalogpartisjon:%n%1%nKildedomenekontroller:%n%4%nNettverksadresse:%n%2%n%nDet fører til at katalogpartisjonen ikke lenger replikeres fra denne kildedomenekontrolleren. |
The local domain controller hosts a writeable replica of the following directory partition; however, the source domain controller at the following network address hosts a read-only replica of this directory partition. Writeable replica directory partitions cannot replicate from read-only replicas because read-only replicas do not contain all of the attributes required to populate writeable replicas.%n%nDirectory partition:%n%1%nSource domain controller:%n%4%nNetwork address:%n%2%n%nAs a result, the directory partition will no longer be replicated from this source domain controller. |
| 0x400006CF | Den lokale domenekontrolleren er vert for en skrivbar replika for følgende katalogpartisjon. Kildedomenekontrolleren med følgende nettverksadresse er imidlertid vert for en skrivebeskyttet replika for denne katalogpartisjonen. Forsøket på å stoppe replikering av denne katalogpartisjonen fra denne domenekontrolleren mislyktes. Skrivbare replikaer for katalogpartisjoner kan ikke replikere fra skrivebeskyttede replikaer for katalogpartisjoner fordi skrivebeskyttede replikaer ikke inneholder alle attributtene som kreves for å fylle skrivbare replikakatalogpartisjoner.%n%nKatalogpartisjon:%n%1%nKildedomenekontroller:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The local domain controller hosts a writeable replica of the following directory partition; however, the source domain controller at the following network address hosts a read-only replica of this directory partition. The attempt to stop replication of this directory partition from this domain controller failed. Writeable replica directory partitions cannot replicate from read-only replica directory partitions because read-only replica directory partitions do not contain all of the attributes required to populate writeable replica directory partitions.%n%nDirectory partition:%n%1%nSource domain controller:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400006D0 | Den lokale domenekontrolleren er ikke lenger en global katalog. Det fører til at den delvise, skrivebeskyttede katalogpartisjonen for følgende domene fjernes fra den lokale domenekontrolleren.%n%nDomene:%n%1%n%nDen lokale domenekontrolleren kan ikke konfigureres på nytt til å bli en global katalog før denne delvise, skrivebeskyttede katalogpartisjonen er fullstendig fjernet. |
The local domain controller is no longer a global catalog. As a result, the partial, read-only directory partition of the following domain is being removed from the local domain controller.%n%nDomain:%n%1%n%nThe local domain controller cannot be reconfigured to become a global catalog until this partial, read-only directory partition is completely removed. |
| 0x400006D2 | Følgende domene har blitt fjernet fra skogen, og domeneobjektene blir fjernet fra den globale katalogen.%n%nDomene:%n%1 |
The following domain has been removed from the forest and the domain objects will be removed from the global catalog.%n%nDomain:%n%1 |
| 0x400006D6 | Følgende programkatalogpartisjon har blitt slettet.%n%nProgramkatalogpartisjon:%n%1%n%nObjektene i denne programkatalogpartisjonen blir fjernet fra denne katalogserveren. |
The following application directory partition has been deleted.%n%nApplication directory partition:%n%1%n%nThe objects in this application directory partition will be removed from this directory server. |
| 0x400006D7 | Følgende programkatalogpartisjon har blitt slettet. Et forsøk på å fjerne objektene fra denne katalogserveren mislyktes.%n%nProgramkatalogpartisjon:%n%1%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The following application directory partition has been deleted. An attempt to remove the objects from this directory server failed.%n%nApplication directory partition:%n%1%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x400006D8 | Følgende programkatalogpartisjon har blitt slettet og blir ikke lenger replikert fra katalogserveren med følgende nettverksadresse.%n%nProgramkatalogpartisjon:%n%1%nKatalogserver:%n%3%nNettverksadresse:%n%2 |
The following application directory partition has been deleted and is no longer replicated from the directory server at the following network address.%n%nApplication directory partition:%n%1%nDirectory server:%n%3%nNetwork address:%n%2 |
| 0x400006D9 | Følgende programkatalogpartisjon har blitt slettet. Et forsøk på å stoppe replikering av denne katalogpartisjonen fra katalogserveren med følgende nettverksadresse mislyktes.%n%nProgramkatalogpartisjon:%n%1%nKatalogserver:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The following application directory partition has been deleted. An attempt to stop replication of this directory partition from the directory server at the following network address failed.%n%nApplication directory partition:%n%1%nDirectory server:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400006DA | Følgende katalogpartisjon er ikke lenger konfigurert til å være vert for globale kataloger. Det fører til at denne katalogpartisjonen ikke lenger blir replikert fra domenekontrolleren med følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%3%nNettverksadresse:%n%2 |
The following directory partition is no longer configured for hosting by global catalogs. As a result, this directory partition is no longer replicated from the domain controller at the following network address.%n%nDirectory partition:%n%1%nDomain controller:%n%3%nNetwork address:%n%2 |
| 0x400006DB | Følgende katalogpartisjon er ikke lenger konfigurert til å være vert for globale kataloger. Forsøket på å stoppe replikering av denne katalogpartisjonen fra domenekontrolleren med følgende nettverksadresse mislyktes.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%4%nNettverksadresse:%n%2%n%nDenne operasjonen blir forsøkt på nytt ved neste KCC-intervall (Knowledge Consistency Checker).%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The following directory partition is no longer configured for hosting by global catalogs. The attempt to stop replication of this directory partition from the domain controller at the following network address failed.%n%nDirectory partition:%n%1%nDomain controller:%n%4%nNetwork address:%n%2%n%nThis operation will be tried again at the next Knowledge Consistency Checker (KCC) interval.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x400006DC | Følgende katalogpartisjon er ikke lenger konfigurert til å være vert for globale kataloger. Det fører til at den delvise, skrivebeskyttede replikaen for denne katalogpartisjonen fjernes fra den lokale domenekontrolleren.%n%nKatalogpartisjon:%n%1%n%nDenne katalogpartisjonen kan ikke konfigureres på nytt til å være vert for en global katalog før den er fullstendig fjernet. |
The following directory partition is no longer configured for hosting by global catalogs. As a result, the partial, read-only replica of this directory partition is being removed from the local domain controller.%n%nDirectory partition:%n%1%n%nThis directory partition cannot be reconfigured for hosting by a global catalog until it is completely removed. |
| 0x400006DD | Følgende katalogpartisjon er ikke lenger konfigurert til å være vert for globale kataloger, og forsøket på å fjerne den delvise, skrivebeskyttede replikaen for denne katalogpartisjonen fra den lokale domenekontrolleren mislyktes.%n%nKatalogpartisjon:%n%1%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The following directory partition is no longer configured for hosting by global catalogs and the attempt to remove the partial, read-only replica of this directory partition from the local domain controller failed.%n%nDirectory partition:%n%1%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x400006DE | Overfører driftsovervåkerroller som eies av denne Active Directory Lightweight Directory Services-forekomsten for katalogpartisjonen %1, til Active Directory Lightweight Directory Services-forekomsten %2 ... |
Transferring operations master roles owned by this Active Directory Lightweight Directory Services instance in directory partition %1 to Active Directory Lightweight Directory Services instance %2... |
| 0x400006DF | Fullfører renovering av domenenavnreferanse... |
Completing DN reference scavenging... |
| 0x400006E0 | Replikerer gjenstående oppdateringer i katalogpartisjonen %1 til Active Directory Lightweight Directory Services-forekomsten %2... |
Replicating remaining updates in directory partition %1 to Active Directory Lightweight Directory Services instance %2... |
| 0x400006E1 | Søker etter andre replikaer for katalogpartisjonen %1 på nettverket... |
Searching for other replicas of directory partition %1 on the network... |
| 0x400006E2 | Overfører gjenstående data i katalogpartisjonen %1 til Active Directory Lightweight Directory Services-forekomsten %2... |
Transferring remaining data in directory partition %1 to Active Directory Lightweight Directory Services instance %2... |
| 0x400006E3 | Active Directory Lightweight Directory Services kan ikke overføre de gjenstående dataene i katalogpartisjonen %1 tilActive Directory Lightweight Directory Services-forekomsten %2. |
Active Directory Lightweight Directory Services could not transfer the remaining data in directory partition %1 toActive Directory Lightweight Directory Services instance %2. |
| 0x400006E4 | Active Directory Lightweight Directory Services overførte de gjenstående dataene i katalogpartisjonen %1 til Active Directory Lightweight Directory Services-forekomsten %2. |
Active Directory Lightweight Directory Services successfully transferred the remaining data in directory partition %1 to Active Directory Lightweight Directory Services instance %2. |
| 0x400006E5 | Active Directory Lightweight Directory Services finner ikke en annen Active Directory Lightweight Directory Services-forekomst å overføre de gjenstående dataene i katalogpartisjonen %1 til. |
Active Directory Lightweight Directory Services could not find another Active Directory Lightweight Directory Services instance to transfer the remaining data in directory partition %1. |
| 0x400006E6 | Active Directory Lightweight Directory Services kan ikke opprette en indeks for språkattributtet med følgende ID for nasjonal innstilling.%n%nAttributtidentifikator:%n%1%nAttributtnavn:%n%2%nID for nasjonal innstilling:%n%3%n%nDenne operasjonen blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%4 %5 |
Active Directory Lightweight Directory Services could not create an index for the language attribute with the following localeID.%n%nAttribute ID:%n%1%nAttribute name:%n%2%nLocaleID:%n%3%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%4 %5 |
| 0x400006F0 | Internal event: The group membership cache task is starting. |
Internal event: The group membership cache task is starting. |
| 0x400006F1 | Internal event: The group membership cache task has finished. The completion status was%1, and the exit Internal ID was %2. |
Internal event: The group membership cache task has finished. The completion status was%1, and the exit Internal ID was %2. |
| 0x400006F2 | Internal event: The group membership cache task will run again in %1 minutes. |
Internal event: The group membership cache task will run again in %1 minutes. |
| 0x400006F3 | Internal event: The Global Catalog Domain Controller %1, in site %2, domain %3 will be used toupdate the group memberships. |
Internal event: The Global Catalog Domain Controller %1, in site %2, domain %3 will be used toupdate the group memberships. |
| 0x400006F4 | Internal event: No Global Catalog was located because %1. The group membership cache task is exitingand will reschedule itself. |
Internal event: No Global Catalog was located because %1. The group membership cache task is exitingand will reschedule itself. |
| 0x400006F5 | Internal event: By examining the published connectivity information, the group membership cachetask has determined site %1 is a site with a low network cost to contact. Thetask will schedule itself based on the schedule of network connectivity to thissite. |
Internal event: By examining the published connectivity information, the group membership cachetask has determined site %1 is a site with a low network cost to contact. Thetask will schedule itself based on the schedule of network connectivity to thissite. |
| 0x400006F6 | Internal event: By examining the published connectivity information, the group membership cachetask cannot find an efficient site to obtain group membershipinformation. The task will run using the Global Catalog that is closest, asdetermined by the NetLogon locator and will schedule itself based on a fixedperiod. |
Internal event: By examining the published connectivity information, the group membership cachetask cannot find an efficient site to obtain group membershipinformation. The task will run using the Global Catalog that is closest, asdetermined by the NetLogon locator and will schedule itself based on a fixedperiod. |
| 0x400006F7 | Internal event: The attempt to retrieve the group memberships for a batch of users failed. Theerror is %1. The attempt will be retried. |
Internal event: The attempt to retrieve the group memberships for a batch of users failed. Theerror is %1. The attempt will be retried. |
| 0x400006F8 | Internal event: The group membership cache task determined that site %1 does not have a Global Catalog. |
Internal event: The group membership cache task determined that site %1 does not have a Global Catalog. |
| 0x400006F9 | Internal event: Site %1 has a Global Catalog, but a valid schedule does not exist (error, %2). |
Internal event: Site %1 has a Global Catalog, but a valid schedule does not exist (error, %2). |
| 0x40000701 | Internal event: Task queue invoking function %1 with parameter %2. |
Internal event: Task queue invoking function %1 with parameter %2. |
| 0x40000702 | Internal event: Task queue completed function call %1 with parameter %2, error code = %3.Next call is scheduled at +%4 seconds, parameter %5. |
Internal event: Task queue completed function call %1 with parameter %2, error code = %3.Next call is scheduled at +%4 seconds, parameter %5. |
| 0x4000070A | Knowledge Consistency Checker konstruerer ikke topologienfor partisjonen %1 fordi kunnskapen om partisjonens objekt-GUIDennå ikke er replikert til denne katalogtjenesten. |
The Knowledge Consistency Checker will not construct the topologyfor partition %1 because knowledge of the partition's objectGuidhas not yet replicated to this directory service. |
| 0x4000070C | Overførte driftsovervåkerroller som eies av denne serveren i partisjon %1, til serveren %2. |
Transferred Operation Master roles owned by this server in partition %1 to server %2. |
| 0x4000070D | Replikerte gjenstående oppdateringer i partisjonen %1 til Active Directory Lightweight Directory Services-forekomsten %2. |
Replicated off remaining updates in partition %1 to Active Directory Lightweight Directory Services instance %2. |
| 0x4000070E | Replikerte skjemabeholderen. |
Replicated the schema container. |
| 0x4000070F | Replikerte konfigurasjonsbeholderen. |
Replicated the configuration container. |
| 0x40000710 | Replikerte de kritiske objektene i domenebeholderen. |
Replicated the critical objects in the domain container. |
| 0x40000711 | Den globale katalogen har ingen områdekilder for minst én partisjon.Replikering til den globale katalogen er begrenset til planlagt replikeringfra områdekilder. |
The Global Catalog has no intra-site sources for at least one partition.Replication to the Global Catalog is limited to scheduled replicationfrom inter-site sources. |
| 0x4000072C | Internal event: The Intersite Messaging service using the SMTP transport has found the following number of messages remaining in this SMTP mail drop folder.%n%nNumber of messages:%n%1%nSMTP mail drop folder:%n%2 |
Internal event: The Intersite Messaging service using the SMTP transport has found the following number of messages remaining in this SMTP mail drop folder.%n%nNumber of messages:%n%1%nSMTP mail drop folder:%n%2 |
| 0x40000730 | Internal event: Active Directory Lightweight Directory Services deleted the following unneeded substring index.%n%nSubstring index:%n%1%n%nAdditional Data%nAttributeID:%n%2 |
Internal event: Active Directory Lightweight Directory Services deleted the following unneeded substring index.%n%nSubstring index:%n%1%n%nAdditional Data%nAttributeID:%n%2 |
| 0x40000732 | Internal event: The following site link will be used to schedule the group membership cache refresh task.%n%nSite link:%n%1 |
Internal event: The following site link will be used to schedule the group membership cache refresh task.%n%nSite link:%n%1 |
| 0x40000736 | Internal event: Active Directory Lightweight Directory Services is ignoring the following deactivated schema object.%n%ndeactivated schema object:%n%1 (%2, %3) |
Internal event: Active Directory Lightweight Directory Services is ignoring the following deactivated schema object.%n%ndeactivated schema object:%n%1 (%2, %3) |
| 0x4000073F | Internal event: The following attribute for the following schema class has been reactivated because it is the rdnAttid attribute for the class.%n%nAttribute:%n%1 (%2, %3)%nClass:%n%4 (%5) |
Internal event: The following attribute for the following schema class has been reactivated because it is the rdnAttid attribute for the class.%n%nAttribute:%n%1 (%2, %3)%nClass:%n%4 (%5) |
| 0x40000741 | Active Directory Lightweight Directory Services kan ikke oppdatere skjemabufferen etter replikering av følgende katalogpartisjon fra denne eksterne Active Directory Lightweight Directory Services-forekomsten.%n%nKatalogpartisjon:%n%1%nEkstern katalogtjeneste:%n%2 |
Active Directory Lightweight Directory Services failed to update the schema cache after replicating the following directory partition from this remote Active Directory Lightweight Directory Services instance.%n%nDirectory partition:%n%1%nRemote directory service:%n%2 |
| 0x40000742 | Active Directory Lightweight Directory Services oppdaterte skjemabufferen. |
Active Directory Lightweight Directory Services updated the schema cache. |
| 0x40000744 | Internal event: The instanceType attribute of the following object has been set to the following value.%n%nObject:%n%1%nAttribute value:%n%2%n%nAdditional Data%nInternal ID:%n%3 |
Internal event: The instanceType attribute of the following object has been set to the following value.%n%nObject:%n%1%nAttribute value:%n%2%n%nAdditional Data%nInternal ID:%n%3 |
| 0x4000074C | Tilkoblingen til følgende globale katalog har blitt avsluttet fordi den globale katalogen befinner seg på et eksternt område.%n%nGlobal katalog:%n%1%n%nActive Directory Lightweight Directory Services bruker indikatortjenesten for domenekontrolleren til å finne en tilgjengelig global katalog på et nærmere område for neste operasjon som krever dette. |
The connection to the following global catalog has been closed because the global catalog is in a remote site.%n%nGlobal catalog:%n%1%n%nActive Directory Lightweight Directory Services will use the domain controller locator service to find an available global catalog in a closer site for the next operation that requires one. |
| 0x4000074D | Active Directory Lightweight Directory Services har funnet en global katalog på følgende område.%n%nGlobal katalog:%n%1%nOmråde:%n%2 |
Active Directory Lightweight Directory Services has located a global catalog in the following site.%n%nGlobal catalog:%n%1%nSite:%n%2 |
| 0x40000750 | Active Directory Lightweight Directory Services-replikering registrerte et manglende overordnet objekt for følgende utgående objekt for denne katalogpartisjonen. Det frittstående objektet ble flyttet til LostAndFound-beholderen.%n%nUtgående objekt:%n%1%nGUID for utgående objekt:%n%2%nKatalogpartisjon:%n%3%n%nDenne feilen oppstår når et overordnet objekt slettes og sendes til datasanering når det fortsatt har aktive underordnede objekter. Det fører til at det frittstående objektet flyttes til LostAndFound-beholderen. |
Active Directory Lightweight Directory Services replication detected a missing parent object for the following outgoing object in this directory partition. The orphaned object was moved to the LostAndFound container.%n%nOutgoing object:%n%1%nOutgoing object GUID:%n%2%nDirectory partition:%n%3%n%nThis erroneous condition occurs when a parent object is deleted and sent to garbage collection when it still has active child objects. As a result, the orphaned object is moved to the LostAndFound container. |
| 0x40000751 | Kopierer gjenopprettede Active Directory Lightweight Directory Services-filer fra %1 til %2... |
Copying restored Active Directory Lightweight Directory Services files from %1 to %2... |
| 0x4000075A | Active Directory Lightweight Directory Services avslutter systemet for å fullføre operasjonen med å gi nytt navn til domenet. |
Active Directory Lightweight Directory Services is shutting down the system to complete the domain rename operation. |
| 0x4000075C | Internal event: As part of running a script, Active Directory Lightweight Directory Services is checking the instanceType flag of the following object.%n%nOperation type: %n%1%nObject: %n%2%nMatch result: %n%3%n%nAdditional Data%nError value: %n%4 %5 |
Internal event: As part of running a script, Active Directory Lightweight Directory Services is checking the instanceType flag of the following object.%n%nOperation type: %n%1%nObject: %n%2%nMatch result: %n%3%n%nAdditional Data%nError value: %n%4 %5 |
| 0x4000075D | Internal event: As part of running a script, Active Directory Lightweight Directory Services is checking the cardinality (number of children) of the following object.%n%nObject: %n%1%nCardinality: %n%2%n%nAdditional Data%nError value: %n%3 %4 |
Internal event: As part of running a script, Active Directory Lightweight Directory Services is checking the cardinality (number of children) of the following object.%n%nObject: %n%1%nCardinality: %n%2%n%nAdditional Data%nError value: %n%3 %4 |
| 0x4000075E | Internal event: As part of running a script, Active Directory Lightweight Directory Services is comparing values of the following object.%n%nObject: %n%1%nResult of compare: %n%2%n%nAdditional Data%nError value: %n%3 |
Internal event: As part of running a script, Active Directory Lightweight Directory Services is comparing values of the following object.%n%nObject: %n%1%nResult of compare: %n%2%n%nAdditional Data%nError value: %n%3 |
| 0x4000075F | Internal event: As part of running a script, Active Directory Lightweight Directory Services is updating the values of the following object.%n%nObject: %n%1%n%nAdditional Data%nError value: %n%2 |
Internal event: As part of running a script, Active Directory Lightweight Directory Services is updating the values of the following object.%n%nObject: %n%1%n%nAdditional Data%nError value: %n%2 |
| 0x40000760 | Internal event: As part of running a script, Active Directory Lightweight Directory Services is moving the following object.%n%nSource object: %n%1%nDestination object: %n%2%n%nAdditional Data%nError value: %n%3 |
Internal event: As part of running a script, Active Directory Lightweight Directory Services is moving the following object.%n%nSource object: %n%1%nDestination object: %n%2%n%nAdditional Data%nError value: %n%3 |
| 0x40000761 | Internal event: As part of running a script, Active Directory Lightweight Directory Services is creating the following object.%n%nObject: %n%1%n%nAdditional Data%nError value: %n%2 |
Internal event: As part of running a script, Active Directory Lightweight Directory Services is creating the following object.%n%nObject: %n%1%n%nAdditional Data%nError value: %n%2 |
| 0x40000763 | Internal event: The crossRef object has a reference to a directory partition (nCName attribute) with the following conflicting name.%n%nCrossRef object: %n%1%nConflicting name: %n%2%nRenamed directory partition: %n%3%n%nThe directory partition previously holding this name has been removed. Active Directory Lightweight Directory Services has renamed the conflicting partition. |
Internal event: The crossRef object has a reference to a directory partition (nCName attribute) with the following conflicting name.%n%nCrossRef object: %n%1%nConflicting name: %n%2%nRenamed directory partition: %n%3%n%nThe directory partition previously holding this name has been removed. Active Directory Lightweight Directory Services has renamed the conflicting partition. |
| 0x40000767 | Internal event: A conflict occurred between two attributes for the same Attribute ID. The following attribute will be used.%n%nAttribute name:%n%1%nAttribute Internal ID:%n%2%nAttribute External ID:%n%3 |
Internal event: A conflict occurred between two attributes for the same Attribute ID. The following attribute will be used.%n%nAttribute name:%n%1%nAttribute Internal ID:%n%2%nAttribute External ID:%n%3 |
| 0x40000768 | Internal event: A conflict occurred between two attributes for the same LDAP display name. The following attribute will be used.%n%nAttribute name:%n%1%nAttribute Internal ID:%n%2%nAttribute External ID:%n%3 |
Internal event: A conflict occurred between two attributes for the same LDAP display name. The following attribute will be used.%n%nAttribute name:%n%1%nAttribute Internal ID:%n%2%nAttribute External ID:%n%3 |
| 0x40000769 | Internal event: A conflict occurred between two attributes for the same MAPI ID. The following attribute will be used.%n%nAttribute name:%n%1%nAttribute Internal ID:%n%2%nAttribute External ID:%n%3%nMAPI-ID: %n%4 |
Internal event: A conflict occurred between two attributes for the same MAPI ID. The following attribute will be used.%n%nAttribute name:%n%1%nAttribute Internal ID:%n%2%nAttribute External ID:%n%3%nMAPI-ID: %n%4 |
| 0x4000076A | Internal event: The following schema object was modified.%n%nSchema object: %n%1 |
Internal event: The following schema object was modified.%n%nSchema object: %n%1 |
| 0x4000076B | Internal event: The following schema object was added.%n%nSchema object: %n%1 |
Internal event: The following schema object was added.%n%nSchema object: %n%1 |
| 0x4000076E | Internal event: The Knowledge Consistency Checker (KCC) is using the Windows Server 2003 election algorithm for the intersite topology generator. |
Internal event: The Knowledge Consistency Checker (KCC) is using the Windows Server 2003 election algorithm for the intersite topology generator. |
| 0x4000076F | Active Directory Lightweight Directory Services la til en replikeringskobling for følgende skrivbare katalogpartisjon fra følgende katalogtjeneste.%n%nSkrivbar katalogpartisjon: %n%1%nKatalogtjeneste: %n%2 |
Active Directory Lightweight Directory Services added a replication link for the following writable directory partition from the following directory service.%n%nWritable directory partition: %n%1%ndirectory service: %n%2 |
| 0x40000770 | Internal event: The Knowledge Consistency Checker (KCC) is using the Windows Server 2003 intersite replication topology generator algorithm. |
Internal event: The Knowledge Consistency Checker (KCC) is using the Windows Server 2003 intersite replication topology generator algorithm. |
| 0x40000771 | Internal event: The following directory service no longer holds the intersite topology generator role. Either the directory service is no longer in the current site, or the directory service does not recognize application directory partitions.%n%nCurrent intersite topology generator: %n%1%n%nActive Directory Lightweight Directory Services will automatically elect a new directory service to hold the role of the intersite topology generator. |
Internal event: The following directory service no longer holds the intersite topology generator role. Either the directory service is no longer in the current site, or the directory service does not recognize application directory partitions.%n%nCurrent intersite topology generator: %n%1%n%nActive Directory Lightweight Directory Services will automatically elect a new directory service to hold the role of the intersite topology generator. |
| 0x40000772 | Internal event: The following directory service no longer holds the intersite topology generator role. This is because the local directory service has no entry in its up-to-dateness vector for this directory service.%n%nCurrent intersite topology generator: %n%1%n%nActive Directory Lightweight Directory Services will automatically elect a new directory service to hold the role of the intersite topology generator. |
Internal event: The following directory service no longer holds the intersite topology generator role. This is because the local directory service has no entry in its up-to-dateness vector for this directory service.%n%nCurrent intersite topology generator: %n%1%n%nActive Directory Lightweight Directory Services will automatically elect a new directory service to hold the role of the intersite topology generator. |
| 0x40000773 | Internal event: The following directory service holds the intersite topology generator role. Its claim is still valid because the last update is recent enough.%n%nCurrent intersite topology generator: %n%1%nLast update: %n%2 |
Internal event: The following directory service holds the intersite topology generator role. Its claim is still valid because the last update is recent enough.%n%nCurrent intersite topology generator: %n%1%nLast update: %n%2 |
| 0x40000774 | Internal event: The following directory service no longer holds the intersite topology generator role. The directory service is assumed to be unavailable because it has not responded since the last update, which invalidates its claim.%n%nCurrent intersite topology generator: %n%1%nLast update: %n%2 |
Internal event: The following directory service no longer holds the intersite topology generator role. The directory service is assumed to be unavailable because it has not responded since the last update, which invalidates its claim.%n%nCurrent intersite topology generator: %n%1%nLast update: %n%2 |
| 0x40000775 | Internal event: The intersite topology generator role will fail over to the following directory service.%n%ndirectory service: %n%1 |
Internal event: The intersite topology generator role will fail over to the following directory service.%n%ndirectory service: %n%1 |
| 0x4000077D | Sikkerhetskopieringen av Active Directory Lightweight Directory Services ved hjelp av skyggekopitjenesten var vellykket. |
The shadow copy backup for Active Directory Lightweight Directory Services was successful. |
| 0x40000780 | Gjenopprettingen av Active Directory Lightweight Directory Services ved hjelp av skyggekopitjenesten var vellykket. |
Active Directory Lightweight Directory Services shadow copy restore was successful. |
| 0x40000784 | Internal event: The Knowledge Consistency Checker (KCC) has added a replication link for a read-only directory partition from the following directory service.%n%nDirectory partition: %n%1%ndirectory service: %n%2 |
Internal event: The Knowledge Consistency Checker (KCC) has added a replication link for a read-only directory partition from the following directory service.%n%nDirectory partition: %n%1%ndirectory service: %n%2 |
| 0x40000787 | Den lokale domenekontrolleren har blitt valgt av indikatortjenesten for domenekontrolleren til å være en global katalog. Domenekontrolleren har imidlertid bare fullført en delvis synkronisering av følgende katalogpartisjon. En fullstendig synkronisering kreves for at domenekontrolleren kan være en global katalog.%n%nKatalogpartisjon: %n%1%nKildedomenekontroller: %n%2%nTransport: %n%3%nVellykket USN-synkronisering: %n%4%nForrige synkronisering ble utført den: %n%5%n%nActive Directory Lightweight Directory Services fortsetter å synkronisere katalogpartisjonen.%n%nEn forutsetning for å bli en global katalog er at hver katalogpartisjon som blir driftet av den lokale domenekontrolleren, må fullføre minst én fullstendig synkronisering. Hvis den lokale domenekontrolleren nylig ble en global katalog og fikk nivået senket, er det mulig at den forrige kopien av katalogpartisjonen er i ferd med å bli fjernet.%n%nTilleggsdata%nFeilverdi: %n6 %7 |
The local domain controller has been selected by the domain controller locator service to be a global catalog. However, the domain controller has only completed a partial synchronization of the following directory partition. A full synchronization is required for the domain controller to be a global catalog.%n%nDirectory partition: %n%1%nSource domain controller: %n%2%nTransport: %n%3%nSuccessful USN Sync: %n%4%nLast sync performed: %n%5%n%nActive Directory Lightweight Directory Services will continue to synchronize the directory partition.%n%nA precondition to become a global catalog is that every directory partition hosted by the local domain controller must complete at least one full synchronization. If the local domain controller was recently a global catalog and was demoted, it is possible that the previous copy of the directory partition is in the process of being removed.%n%nAdditional Data%nError value: %n6 %7 |
| 0x40000789 | RPC%0 |
RPC%0 |
| 0x4000078A | Domenekontrolleren har ikke fullført en første synkronisering av alle skrivebeskyttede partisjoner som den inneholder.%n%nDette kan forsinke nivåhevingsprosessen for den globale katalogen, men synkroniseringene fortsetter. |
The domain controller has not completed an initial synchronization of every read-only directory partition that it holds.%n%nThis could delay the global catalog promotion but the synchronizations will continue. |
| 0x4000078C | Internal event: The following directory partition was removed from the subRef attribute on its parent object.%n%nDirectory partition DN: %n%1%nDirectory partition GUID: %n%2%nCalling site: %n%3 |
Internal event: The following directory partition was removed from the subRef attribute on its parent object.%n%nDirectory partition DN: %n%1%nDirectory partition GUID: %n%2%nCalling site: %n%3 |
| 0x4000078D | Internal event: The following directory partition was added to the subRef attribute on its parent object.%n%nDirectory partition DN: %n%1%nDirectory partition GUID: %n%2%nCalling site: %n%3 |
Internal event: The following directory partition was added to the subRef attribute on its parent object.%n%nDirectory partition DN: %n%1%nDirectory partition GUID: %n%2%nCalling site: %n%3 |
| 0x4000078E | Internal event: The following crossRef object will be deleted. The directory partition is being processed as an automatic subordinate reference.%n%nCrossRef object: %n%1%nDirectory partition DN: %n%2%nDirectory partition GUID: %n%3%n%nAdditional Data%nError value: %n%4 |
Internal event: The following crossRef object will be deleted. The directory partition is being processed as an automatic subordinate reference.%n%nCrossRef object: %n%1%nDirectory partition DN: %n%2%nDirectory partition GUID: %n%3%n%nAdditional Data%nError value: %n%4 |
| 0x4000078F | Internal event: The following crossRef object will be added. The directory partition is being processed as an automatic subordinate reference.%n%nCrossRef object: %n%1%nDirectory partition DN: %n%2%nDirectory partition GUID: %n%3%n%nAdditional Data%nError value: %n%4 |
Internal event: The following crossRef object will be added. The directory partition is being processed as an automatic subordinate reference.%n%nCrossRef object: %n%1%nDirectory partition DN: %n%2%nDirectory partition GUID: %n%3%n%nAdditional Data%nError value: %n%4 |
| 0x40000790 | Internal event: Active Directory Lightweight Directory Services completed running the script.%n%nAdditional Data%nError value: %n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed running the script.%n%nAdditional Data%nError value: %n%1 %2 |
| 0x40000791 | Active Directory Lightweight Directory Services har begynt fjerningen av etterlatte objekter på den lokale domenekontrolleren. Alle objekter på denne domenekontrolleren får eksistensen bekreftet på følgende kildedomenekontroller.%n%nKildedomenekontroller: %n%1%n%nObjekter som har blitt slettet og datasanert på kildedomenekontrolleren, men som fortsatt eksisterer på denne domenekontrolleren, blir slettet. Påfølgende hendelsesloggoppføringer lister opp alle slettede objekter. |
Active Directory Lightweight Directory Services has begun the removal of lingering objects on the local domain controller. All objects on this domain controller will have their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%n%nObjects that have been deleted and garbage collected on the source domain controller yet still exist on this domain controller will be deleted. Subsequent event log entries will list all deleted objects. |
| 0x40000792 | Active Directory Lightweight Directory Services har begynt verifiseringen av etterlatte objekter i bekreftelsesmodus på den lokale domenekontrolleren. Alle objekter i denne domenekontrolleren får eksistensen bekreftet på følgende kildedomenekontroller.%n%nKildedomenekontroller: %n%1%n%nObjekter som har blitt slettet og datasanert på kildedomenekontrolleren, men som fortsatt eksisterer på denne domenekontrolleren, blir listet opp i påfølgende hendelsesloggoppføringer. Du sletter etterlatte objekter permanent ved å starte denne prosedyren på nytt uten å bruke bekreftelsesmodus. |
Active Directory Lightweight Directory Services has begun the verification of lingering objects in advisory mode on the local domain controller. All objects on this domain controller will have their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%n%nObjects that have been deleted and garbage collected on the source domain controller yet still exist on this domain controller will be listed in subsequent event log entries. To permanently delete the lingering objects, restart this procedure without using the advisory mode option. |
| 0x40000793 | Active Directory Lightweight Directory Services har fullført fjerningen av etterlatte objekter på den lokale domenekontrolleren. Alle objekter på denne domenekontrolleren har fått eksistensen bekreftet på følgende kildedomenekontroller.%n%nKildedomenekontroller: %n%1%nAntall etterlatte objekter som ble slettet: %n%2%n%nObjekter som har blitt slettet og datasanert på kildedomenekontrolleren, men som fortsatt eksisterer på denne domenekontrolleren, ble slettet fra den lokale domenekontrolleren. Tidligere hendelsesloggoppføringer lister opp disse slettede objektene. |
Active Directory Lightweight Directory Services has completed the removal of lingering objects on the local domain controller. All objects on this domain controller have had their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%nNumber of lingering objects deleted: %n%2%n%nObjects that were deleted and garbage collected on the source domain controller yet existed on the local domain controller were deleted from the local domain controller. Past event log entries list these deleted objects. |
| 0x40000794 | Internal event: Active Directory Lightweight Directory Services has completed the removal of a subset of lingering objects on the local domain controller. All objects in this subset on this domain controller have had their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%nNumber of objects deleted: %n%2%n%nThe subset of objects that were deleted and garbage collected on the source domain controller yet existed on the local domain controller were deleted. Past event log entries list these deleted objects.%n%nThe lingering object removal process will continue. |
Internal event: Active Directory Lightweight Directory Services has completed the removal of a subset of lingering objects on the local domain controller. All objects in this subset on this domain controller have had their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%nNumber of objects deleted: %n%2%n%nThe subset of objects that were deleted and garbage collected on the source domain controller yet existed on the local domain controller were deleted. Past event log entries list these deleted objects.%n%nThe lingering object removal process will continue. |
| 0x40000795 | Active Directory Lightweight Directory Services kan ikke fjerne alle objekter i dette delsettet av etterlatte objekter på den lokale domenekontrolleren. Alle objekter i dette delsettet på denne domenekontrolleren har fått eksistensen bekreftet på den følgende kildedomenekontrolleren.%n%nKildedomenekontroller: %n%1%nAntall objekter i delsettet som ikke ble slettet: %n%2%n%nFjerningen av etterlatte objekter fortsetter i neste delsett av objekter. Tidligere hendelsesloggoppføringer lister opp etterlatte objekter som ikke kunne slettes.%n%nTilleggsdata%nFeilverdi: %n%3 %4 |
Active Directory Lightweight Directory Services was unable to remove all objects in this subset of lingering objects on the local domain controller. All objects in this subset on this domain controller have had their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%nNumber of objects in this subset that were not deleted: %n%2%n%nThe lingering object removal process will continue on the next subset of objects. Past event log entries list the lingering objects that could not be deleted.%n%nAdditional Data%nError value: %n%3 %4 |
| 0x40000796 | Active Directory Lightweight Directory Services har fullført bekreftelsen av etterlatte objekter på den lokale domenekontrolleren i bekreftelsesmodus. Alle objekter på denne domenekontrolleren har fått eksistensen bekreftet på følgende kildedomenekontroller.%n%nKildedomenekontroller: %n%1%nAntall etterlatte objekter som ble undersøkt og bekreftet: %n%2%n%nObjekter som har blitt slettet og datasanert på kildedomenekontrolleren, men som fortsatt eksisterer på denne domenekontrolleren, har blitt listet opp i tidligere hendelsesloggoppføringer. Du sletter etterlatte objekter permanent ved å starte denne prosedyren på nytt uten å bruke bekreftelsesmodus. |
Active Directory Lightweight Directory Services has completed the verification of lingering objects on the local domain controller in advisory mode. All objects on this domain controller have had their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%nNumber of lingering objects examined and verified: %n%2%n%nObjects that have been deleted and garbage collected on the source domain controller yet still exist on this domain controller have been listed in past event log entries. To permanently delete the lingering objects, restart this procedure without using the advisory mode option. |
| 0x4000079A | Active Directory Lightweight Directory Services har identifisert følgende etterlatte objekt på den lokale domenekontrolleren i bekreftelsesmodus. Objektet hadde blitt slettet og datasanert på følgende kildedomenekontroller, men eksisterer fortsatt på den lokale domenekontrolleren.%n%nObjekt: %n%1%nObjekt-GUID: %n%2%nKildedomenekontroller: %n%3 |
Active Directory Lightweight Directory Services has identified the following lingering object on the local domain controller in advisory mode. The object had been deleted and garbage collected on the following source domain controller yet still exists on the local domain controller.%n%nObject: %n%1%nObject GUID: %n%2%nSource domain controller: %n%3 |
| 0x400007A0 | Internal event: Active Directory Lightweight Directory Services used connection object 2 instead of connection object 1.%n%nConnection object 1: %n%1%nConnection object 2: %n%2%n%nConnection object 1 was not prepared and, therefore, was superseded by connection object 2. |
Internal event: Active Directory Lightweight Directory Services used connection object 2 instead of connection object 1.%n%nConnection object 1: %n%1%nConnection object 2: %n%2%n%nConnection object 1 was not prepared and, therefore, was superseded by connection object 2. |
| 0x400007A1 | Overføringen av sikkerhetsbeskrivelsen har startet en fullstendig overføringsprosedyre |
The security descriptor propagator has started a full propagation pass |
| 0x400007A2 | Overføringen av sikkerhetsbeskrivelsen har fullført en fullstendig overføringsprosedyre. |
The security descriptor propagator has completed a full propagation pass. |
| 0x400007A3 | Det oppstod en skrivekonflikt i Active Directory Lightweight Directory Services under implementering av replikerte endringer for følgende objekt.%n%nObjekt: %n%1%nTid i sekunder: %n%2%nNye forsøk: %n%3%nret:%n%4%n%nHendelsesloggoppføringer som kommer før denne oppføringen, angir om oppdateringen ble godkjent eller ikke.%n%nEn skrivekonflikt kan forårsakes av samtidige endringer i det samme objektet eller samtidige endringer i andre objekter som har attributter som refererer til dette objektet. Dette skjer vanligvis når objektet representerer en stor gruppe med mange medlemmer, og funksjonsnivået for konfigurasjonssettet er satt til Windows 2000. Denne konflikten førte til at oppdateringen ble forsøkt flere ganger. Hvis operativsystemet jobber langsomt, kan det skyldes at replikering av disse endringene pågår.%n%nBrukerhandling%nBruk mindre grupper for denne operasjonen, eller hev funksjonsnivået for konfigurasjonssettet til Windows Server 2003. |
Active Directory Lightweight Directory Services encountered a write conflict when applying replicated changes to the following object.%n%nObject: %n%1%nTime in seconds: %n%2%nRetries: %n%3%nret:%n%4%n%nEvent log entries preceding this entry will indicate whether or not the update was accepted.%n%nA write conflict can be caused by simultaneous changes to the same object or simultaneous changes to other objects that have attributes referencing this object. This commonly occurs when the object represents a large group with many members, and the functional level of the configuration set is set to Windows 2000. This conflict triggered additional retries of the update. If the system appears slow, it could be because replication of these changes is occurring.%n%nUser Action%nUse smaller groups for this operation or raise the configuration set functional level to Windows Server 2003. |
| 0x400007A4 | Internal event: The following directory partition was deleted.%n%nDirectory partition DN: %n%1%nDirectory partition GUID: %n%2%nName changed (0 or 1): %n%3%nGarbage collect immediate (0 or 1): %n%4%n%nAdditional Data%nInternal ID: %n%5 |
Internal event: The following directory partition was deleted.%n%nDirectory partition DN: %n%1%nDirectory partition GUID: %n%2%nName changed (0 or 1): %n%3%nGarbage collect immediate (0 or 1): %n%4%n%nAdditional Data%nInternal ID: %n%5 |
| 0x400007A5 | Internal event: A GUID was added to the ncName attribute on a crossRef object.%n%nCrossRef object: %n%1%nPartition name: %n%2%nGUID: %n%3 |
Internal event: A GUID was added to the ncName attribute on a crossRef object.%n%nCrossRef object: %n%1%nPartition name: %n%2%nGUID: %n%3 |
| 0x400007AD | Active Directory Lightweight Directory Services initialiserer de gjenopprettede databasefilene. Dette kan ta noen minutter. |
Active Directory Lightweight Directory Services is initializing the restored database files. This might take several minutes. |
| 0x400007AE | Overføringen av sikkerhetsbeskrivelsen har fullført en fullstendig overføringsprosedyre.%n%nFordelt plass (MB): %n%1%nLedig plass (MB): %n%2%n%nDet finnes kanskje økt ledig plass i Active Directory Lightweight Directory Services-databasen.%n%nBrukerhandling%nVurder å defragmentere databasen frakoblet for å frigjøre ledig plass som kanskje er tilgjengelig i Active Directory Lightweight Directory Services-databasen. |
The security descriptor propagator has completed a full propagation pass.%n%nAllocated space (MB): %n%1%nFree space (MB): %n%2%n%nThis may have increased free space in the Active Directory Lightweight Directory Services database.%n%nUser Action%nConsider defragmenting the database offline to reclaim the free space that may be available in the Active Directory Lightweight Directory Services database. |
| 0x400007B0 | Active Directory Lightweight Directory Services har hevet funksjonsnivået for partisjonen for dette domenet slik at det blir kompatibelt med funksjonsnivået for gjeldende konfigurasjonssett.%n%n partisjon: %n%1%nFunksjonsnivå for gjeldende konfigurasjonssett: %n%3%nFunksjonsnivå for forrige partisjon: %n%2%nFunksjonsnivå for gjeldende partisjon: %n%3 |
Active Directory Lightweight Directory Services has raised the partition functional level for this domain to be compatible with the current configuration set functional level.%n%n partition: %n%1%nCurrent configuration set functional level: %n%3%nPrevious partition functional level: %n%2%nCurrent partition functional level: %n%3 |
| 0x400007B3 | Active Directory Lightweight Directory Services kan ikke tildele nok minne for å fjerne programkatalogpartisjonen %1. Forsøk å fjerne programkatalogpartisjonen manuelt. |
Active Directory Lightweight Directory Services could not allocate enough memory to remove the application directory partition %1. Try removing the application directory partition manually. |
| 0x400007B4 | Active Directory Lightweight Directory Services forsøkte å legge til et crossRef-objekt, men navnereferansen (nCName-attributt) for katalogpartisjonen er i konflikt med et annet objekt. Dette kan ha oppstått da crossRef-objektet ble lagt til eller slettet, eller når katalogpartisjonen ble slettet og crossRef-objektet ble lagt til på nytt.%n%nCrossRef-objekt: %n%1%nNavn på gammel katalogpartisjon: %n%2%nNavn på ny katalogpartisjon: %n%3%n%nActive Directory Lightweight Directory Services har endret navnet på katalogpartisjonsobjektet. |
Active Directory Lightweight Directory Services attempted to add a crossRef object, but the directory partition name reference (nCName attribute) conflicts with another object. This could have occurred when the crossRef object was added or deleted, the directory partition was deleted, and the crossRef object was added again.%n%nCrossRef object: %n%1%nOld directory partition name: %n%2%nNew directory partition name: %n%3%n%nActive Directory Lightweight Directory Services has successfully corrected the name of the directory partition object. |
| 0x400007B5 | Internal Event: The request for changes completed at the following destination directory service.%n%ndirectory service: %n%1%nDirectory partition: %n%2%nObject update USN: %n%3%nProperty update USN: %n%4%nFlags: %n%5%nExtended FSMO operation code: %n%6%n%nAdditional Data%nError value: %n%7 %8 |
Internal Event: The request for changes completed at the following destination directory service.%n%ndirectory service: %n%1%nDirectory partition: %n%2%nObject update USN: %n%3%nProperty update USN: %n%4%nFlags: %n%5%nExtended FSMO operation code: %n%6%n%nAdditional Data%nError value: %n%7 %8 |
| 0x400007B6 | Internal event: The Knowledge Consistency Checker (KCC) did not update the schedule for the following connection object because the connection has a user-defined schedule.%n%nConnection object: %n%1 |
Internal event: The Knowledge Consistency Checker (KCC) did not update the schedule for the following connection object because the connection has a user-defined schedule.%n%nConnection object: %n%1 |
| 0x400007B7 | Internal event: Schedule staggering is enabled in the following site. The Knowledge Consistency Checker (KCC) will automatically stagger the schedules for any intersite connections that replicate from this site.%n%nSite: %n%1 |
Internal event: Schedule staggering is enabled in the following site. The Knowledge Consistency Checker (KCC) will automatically stagger the schedules for any intersite connections that replicate from this site.%n%nSite: %n%1 |
| 0x400007B8 | Internal event: Random bridgehead selection is enabled in the following site. The Knowledge Consistency Checker (KCC) will randomly choose bridgehead servers for any new intersite connections that replicate to or from that site.%n%nSite: %n%1 |
Internal event: Random bridgehead selection is enabled in the following site. The Knowledge Consistency Checker (KCC) will randomly choose bridgehead servers for any new intersite connections that replicate to or from that site.%n%nSite: %n%1 |
| 0x400007C0 | Installasjonsveiviseren for Active Directory Lightweight Directory Services kan ikke hente bufringsinformasjon for programkatalogpartisjonene eller for partisjonenes crossRef-objekter fra AD LDS. Start denne Active Directory Lightweight Directory Services-forekomsten på nytt, og kjør veiviseren en gang til. |
The Active Directory Lightweight Directory Services Installation Wizard could not retrieve cached information of the application directory partitions or their crossRef objects from AD LDS. Restart this Active Directory Lightweight Directory Services instance and run the wizard again. |
| 0x400007C1 | Active Directory Lightweight Directory Services kan ikke slette crossRef-objektet %1 for katalogpartisjonen %2. |
Active Directory Lightweight Directory Services could not delete the crossRef object %1 for the directory partition %2. |
| 0x400007C2 | Den skrivbare katalogpartisjonen %1 må slettes selv om brukeren ikke valgte at den skulle slettes. Nivåsenkingen kan ikke fullføres så lenge denne katalogpartisjonen eksisterer. Slett katalogpartisjonen manuelt. |
The writable directory partition %1 must be deleted even though the user did not select it to be deleted. The existence of this directory partition prevents the demotion operation from completing. Delete the directory partition manually. |
| 0x400007C3 | Active Directory Lightweight Directory Services kan ikke fjernes på denne Active Directory Lightweight Directory Services-forekomsten fordi dette er den siste AD LDS-forekomsten i partisjonen, og domenet har den underordnede katalogpartisjonen %1. |
Active Directory Lightweight Directory Services could not be removed on this Active Directory Lightweight Directory Services instance because this is the last AD LDS instance in the partition, and the domain has a child directory partition %1. |
| 0x400007C5 | Active Directory Lightweight Directory Services kan ikke fjerne programkatalogpartisjonen %1 fordi denne partisjonen har én eller flere underordnede partisjoner eller kryssreferanser. Fjern alle underordnede partisjoner eller kryssreferanser først. |
Active Directory Lightweight Directory Services could not remove the application directory partition %1 because this partition has one or more child partitions or cross-refs. Remove the child partition or partitions or cross-refs first. |
| 0x400007C6 | Internal event: Notifications to the following directory service have been failing for a long period of time.%n%ndirectory service GUID: %n%1%nDirectory partition: %n%2%nFailure period in seconds: %n%3%n%nNotifications will no longer be sent to that directory service. |
Internal event: Notifications to the following directory service have been failing for a long period of time.%n%ndirectory service GUID: %n%1%nDirectory partition: %n%2%nFailure period in seconds: %n%3%n%nNotifications will no longer be sent to that directory service. |
| 0x400007C7 | Fjerner Active Directory Lightweight Directory Services-objekter fra navngivingsovervåkeren %1... |
Removing Active Directory Lightweight Directory Services objects from the naming master %1... |
| 0x400007CB | Internal event: Active Directory Lightweight Directory Services has begun using unique remote procedure call (RPC) associations to ensure correct security context information. |
Internal event: Active Directory Lightweight Directory Services has begun using unique remote procedure call (RPC) associations to ensure correct security context information. |
| 0x400007CC | Denne installasjonen av Active Directory Lightweight Directory Services krever endringer i domenekonfigurasjonen. Kjør kommandoen adprep /domainprep på Active Directory Lightweight Directory Services-forekomsten %1 for å utføre disse endringene, og fortsett deretter med installasjonen av AD LDS. |
This Active Directory Lightweight Directory Services installation requires domain configuration changes. Run the adprep /domainprep command on Active Directory Lightweight Directory Services instance %1 to make these changes and then proceed with the AD LDS installation. |
| 0x400007CD | Denne installasjonen av Active Directory Lightweight Directory Services krever endringer i domenekonfigurasjonen. Konfigurasjonsendringer har imidlertid ennå ikke blitt replikert til Active Directory Lightweight Directory Services-forekomsten %1. Etter at replikeringen er fullført, kjører du installasjonen av AD LDS på nytt. |
This Active Directory Lightweight Directory Services installation requires domain configuration changes. However, configuration changes have not yet replicated to the Active Directory Lightweight Directory Services instance %1. After replication has completed, try the AD LDS installation again. |
| 0x400007CE | Denne installasjonen av Active Directory Lightweight Directory Services må bekrefte at de nødvendige endringene i domenekonfigurasjonen har blitt utført, men installasjonsprogrammet kunne ikke kontakte Active Directory Lightweight Directory Services-forekomsten %1 for å fastslå om disse endringene har blitt utført. Installasjonsprosessen ble avsluttet. Denne feilen kan oppstå hvis infrastrukturovervåkerrollen blir tilordnet til et slettet objekt, hvis det oppstår nettverksproblemer, eller hvis du ikke har tilstrekkelige tillatelser til å lese nødvendige data i katalogen. %2. |
This Active Directory Lightweight Directory Services installation needs to verify that necessary domain configuration changes have occurred, but it could not contact Active Directory Lightweight Directory Services instance %1 to determine whether these changes have been made. The installation process has quit. This error can occur if the infrastructure master role is assigned to a deleted object, if there are networking issues, or if you do not have sufficient permissions to read the required data in the directory. %2. |
| 0x400007CF | Kildekatalogtjenesten har optimalisert oppdateringssekvensnummeret (USN) som angis av målkatalogtjenesten. Kilde- og målkatalogtjenestene har en felles replikeringspartner. Målkatalogtjenesten er oppdatert med den felles replikeringspartneren, og kildekatalogtjenesten ble installert ved hjelp av en sikkerhetskopi av denne partneren.%n%nID for målkatalogtjeneste: %n%1%nID for felles katalogtjeneste: %n%2%nUSN for felles egenskap:%n%3%n%nDet fører til at UpToDateness Vector for målkatalogtjenesten har blitt konfigurert med følgende innstillinger.%n%nUSN for forrige objekt:%n%4%nUSN for forrige egenskap:%n%5%nDatabase-GUID:%n%6%nObjekt-USN:%n%7%nEgenskaps-USN:%n%8 |
The source directory service has optimized the update sequence number (USN) presented by the destination directory service. The source and destination directory services have a common replication partner. The destination directory service is up to date with the common replication partner, and the source directory service was installed using a backup of this partner.%n%nDestination directory service ID: %n%1%nCommon directory service ID: %n%2%nCommon property USN:%n%3%n%nAs a result, the up-to-dateness vector of the destination directory service has been configured with the following settings.%n%nPrevious object USN:%n%4%nPrevious property USN:%n%5%nDatabase GUID:%n%6%nObject USN:%n%7%nProperty USN:%n%8 |
| 0x400007D0 | Standard NTFS-sikkerhetsinnstillinger har blitt tatt i bruk for Active Directory Lightweight Directory Services-mapper etter anmodning fra brukeren. |
The default NTFS security settings have been applied to Active Directory Lightweight Directory Services folders as requested by the user. |
| 0x400007D5 | Internal event: The following crossRef object is being added.%n%nCrossRef object: %n%1%nDirectory partition: %n%2%nDirectory partition GUID: %n%3%nParent directory partition: %n%4%n%nThe directory partition will be processed as an automatic subordinate reference The parent directory partition is a phantom, so no subRef value is required. |
Internal event: The following crossRef object is being added.%n%nCrossRef object: %n%1%nDirectory partition: %n%2%nDirectory partition GUID: %n%3%nParent directory partition: %n%4%n%nThe directory partition will be processed as an automatic subordinate reference The parent directory partition is a phantom, so no subRef value is required. |
| 0x400007D6 | Internal event: The security descriptor propagation task resumed the propagation task from the following container.%n%nContainer: %n%1%nNumber of objects processed so far: %n%2 |
Internal event: The security descriptor propagation task resumed the propagation task from the following container.%n%nContainer: %n%1%nNumber of objects processed so far: %n%2 |
| 0x400007D7 | Internal event: The security descriptor propagation task has reached the following container and will continue with the propagation.%n%nContainer: %n%1%nNumber of objects processed so far: %n%2 |
Internal event: The security descriptor propagation task has reached the following container and will continue with the propagation.%n%nContainer: %n%1%nNumber of objects processed so far: %n%2 |
| 0x400007DC | Du installerer en Active Directory Lightweight Directory Services-forekomst i dette Active Directory Lightweight Directory Services-konfigurasjonssettet ved først å klargjøre konfigurasjonssettet ved å oppgradere skjemaet slik at det samsvarer med den nye operativsystemversjonen. Se Hjelp for Active Directory Lightweight Directory Services hvis du vil ha mer informasjon. |
To install a Active Directory Lightweight Directory Services instance into this Active Directory Lightweight Directory Services configuration set, you must first prepare the configuration set by upgrading the schema to match the new Operating System version. See Active Directory Lightweight Directory Services help for more information. |
| 0x400007DD | Active Directory Lightweight Directory Services bygger følgende antall indekser på nytt som en del av initialiseringsprosessen.%n%nAntall indekser: %n%1%nIndekser: %n%2 |
Active Directory Lightweight Directory Services is rebuilding the following number of indices as part of the initialization process.%n%nNumber of indices: %n%1%nIndices: %n%2 |
| 0x400007DE | Active Directory Lightweight Directory Services fullførte bygging av følgende antall indekser på nytt.%n%nIndekser: %n%1 |
Active Directory Lightweight Directory Services successfully completed rebuilding the following number of indices.%n%nIndices: %n%1 |
| 0x400007E1 | Internal event: Active Directory Lightweight Directory Services received a request to compute the costs between a set of sites. Only the first seven destination sites are reported below.%n%nSource site: %n%1%nDestination sites:%n%2%n%3%n%4%n%5%n%6%n%7 |
Internal event: Active Directory Lightweight Directory Services received a request to compute the costs between a set of sites. Only the first seven destination sites are reported below.%n%nSource site: %n%1%nDestination sites:%n%2%n%3%n%4%n%5%n%6%n%7 |
| 0x400007E2 | Internal event: Active Directory Lightweight Directory Services completed the request to compute the costs between a set of sites.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to compute the costs between a set of sites.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x400007E4 | Internal event: Active Directory Lightweight Directory Services successfully created an object on a remote computer.%n%nComputer (blank = local computer): %n%1%nObject: %n%2%nObject GUID: %n%3%n%nAdditional Data%nInternal ID: %n%4 |
Internal event: Active Directory Lightweight Directory Services successfully created an object on a remote computer.%n%nComputer (blank = local computer): %n%1%nObject: %n%2%nObject GUID: %n%3%n%nAdditional Data%nInternal ID: %n%4 |
| 0x400007F5 | Internal event: While replicating a superior partition, a change to an inferior partition head wasdetected. The inferior partition head already exists locally. The change will not be applied sothat the partition head attributes may be replicated with that partition at a later time. However,the instance type and partition membership of the local inferior partition head have been adjusted.%n%nObject:%n%1%nOld Attribute value:%n%2%nNew Attribute value:%n%3%n%nAdditional Data%nInternal ID:%n%4 |
Internal event: While replicating a superior partition, a change to an inferior partition head wasdetected. The inferior partition head already exists locally. The change will not be applied sothat the partition head attributes may be replicated with that partition at a later time. However,the instance type and partition membership of the local inferior partition head have been adjusted.%n%nObject:%n%1%nOld Attribute value:%n%2%nNew Attribute value:%n%3%n%nAdditional Data%nInternal ID:%n%4 |
| 0x400007F6 | Internal event: A partition head has changed its SUBREF status. Its partition membership hasbeen adjusted.%n%nObject:%n%1%nOld partition DNT: %n%2%nNew partition DNT: %n%3%n%nAdditional Data%nInternal ID:%n%4 |
Internal event: A partition head has changed its SUBREF status. Its partition membership hasbeen adjusted.%n%nObject:%n%1%nOld partition DNT: %n%2%nNew partition DNT: %n%3%n%nAdditional Data%nInternal ID:%n%4 |
| 0x400007F7 | Funksjonsnivået for denne partisjonen har blitt oppdatert.%nDomene: %1%nFunksjonsnivå for ny partisjon:%2%n |
The functional level of this partition has been updated.%nDomain: %1%nNew partition functional level:%2%n |
| 0x400007F8 | Funksjonsnivået for dette konfigurasjonssettet har blitt oppdatert.%nFunksjonsnivå for nytt konfigurasjonssett:%1%n |
The functional level of this configuration set has been updated.%nNew configuration set functional level:%1%n |
| 0x400007F9 | Duplikate hendelsesloggoppføringer ble skjult.%n%nSe forrige hendelsesloggoppføring hvis du vil ha mer informasjon. En oppføring anses som duplikat hvishendelseskoden og alle innsettingsparameterne er identiske. Tidsperioden fordenne kjøringen av duplikater er fra tidspunktet for den forrige hendelsen til tidspunktet for denne hendelsen.%n%nHendelseskode:%n%1%nAntall duplikate oppføringer: %n%2 |
Duplicate event log entries were suppressed.%n%nSee the previous event log entry for details. An entry is considered a duplicate ifthe event code and all of its insertion parameters are identical. The time period forthis run of duplicates is from the time of the previous event to the time of this event.%n%nEvent Code:%n%1%nNumber of duplicate entries: %n%2 |
| 0x40000801 | Antallet tilkoblinger som ble forespurt, overskred den administrative grensen %1 ganger de siste fem minuttene. |
The number of connections requested exceeded the administrative limit %1 times in the last five minutes. |
| 0x40000802 | Active Directory Lightweight Directory Services kan ikke gjenopprettes fordi sikkerhetskopifilene ble tatt på en annen versjon av operativsystemet.%n%nBrukerhandling%nBruk en sikkerhetskopi som er tatt på samme versjon av operativsystemet, og prøv å gjenopprette på nytt.%n |
Active Directory Lightweight Directory Services could not be restored, because the backup files were taken on a different build of the operating system.%n%nUser Action%nUse a backup of the same build of the operating system and retry the restore operation.%n |
| 0x4000080B | Active Directory Lightweight Directory Services kan ikke løse navnekonflikten for SAM-kontoen for %1 på objektet %2. |
Active Directory Lightweight Directory Services could not resolve a SAM account name conflict for %1 on object %2. |
| 0x40000810 | Active Directory Lightweight Directory Services har registrert at kvotesporingstabellen mangler eller ikke er fullstendig bygget. Tabellen blir bygget på nytt i bakgrunnen (gjenopptar om mulig eventuelle tidligere nye bygginger). Kvotehåndhevelsen blir ikke tatt i bruk før tabellen er bygget på nytt. |
Active Directory Lightweight Directory Services has detected that the quota-tracking table is either missing or not completely built. The table will be rebuilt in the background (resuming the progress of any previous rebuild, if possible). Until it has completed, quota enforcement will not be in effect. |
| 0x40000811 | Active Directory Lightweight Directory Services har fullført ny bygging av kvotesporingstabellen. Kvotehåndhevelsen har nå trådt i kraft. |
Active Directory Lightweight Directory Services has completed rebuilding the quota-tracking table. Quota enforcement is now in effect. |
| 0x40000813 | Beholderen for NTDS-kvoter (%1) har blitt opprettet.%n |
The NTDS Quotas(%1) container has been created.%n |
| 0x40000819 | Oppretting av et objekt mislyktes fordi anmoderen overskred den tilordnede kvoten.%n%nObjekt:%n%1%n%nTilleggsdata:%nNCDNT: %2 |
Creation of an object failed due to the requestor exceeding assigned quota.%n%nObject:%n%1%n%nAdditional data:%nNCDNT: %2 |
| 0x4000081A | Endring i eierskapet av et objekt mislyktes fordi anmoderen overskred den tilordnede kvoten.%n%nObjekt:%n%1%n%nTilleggsdata:%nNCDNT: %2 |
Change-ownership of an object failed due to the requestor exceeding assigned quota.%n%nObject:%n%1%n%nAdditional data:%nNCDNT: %2 |
| 0x4000081B | Gjenoppretting av et objekt mislyktes fordi anmoderen overskred den tilordnede kvoten.%n%nObjekt:%n%1%n%nTilleggsdata:%nNCDNT: %2 |
Undelete of an object failed due to the requestor exceeding assigned quota.%n%nObject:%n%1%n%nAdditional data:%nNCDNT: %2 |
| 0x4000081C | Nivåhevingen mislyktes fordi navnet på den lokale datamaskinen er navnet på den forhåndsdefinerte sikkerhetsidentifikatoren. Gi nytt navn til datamaskinen. |
The promotion failed because the name of local computer is the name of a predefined security identifier. Please rename the computer. |
| 0x4000081D | Active Directory Lightweight Directory Services har registrert et manglende overordnet objekt eller en manglende løkke i en kjede for et overordnet objekt for følgende objekt. Objektet har blitt flyttet.%n%nObjekt-GUID:%n%1%nDomenenavn for nytt objekt:%n%2 |
Active Directory Lightweight Directory Services has detected a missing parent or a loop in parent chain for the following object. The object has been moved.%n%nObject GUID:%n%1%nNew object DN:%n%2 |
| 0x4000081E | Internal event: Connection object was retained because of the redundant servers topology.%n%nConnection object 1: %n%1%nConnection object 2: %n%2%n |
Internal event: Connection object was retained because of the redundant servers topology.%n%nConnection object 1: %n%1%nConnection object 2: %n%2%n |
| 0x4000081F | Internal event: Redundant server topology is enabled in the following site. The Knowledge Consistency Checker (KCC) will generate a redundant connection between alternate bridgeheads in the same site as the primary connection.%n%nSite: %n%1 |
Internal event: Redundant server topology is enabled in the following site. The Knowledge Consistency Checker (KCC) will generate a redundant connection between alternate bridgeheads in the same site as the primary connection.%n%nSite: %n%1 |
| 0x40000833 | Internal event: The following attribute value change was applied. A value key conflict was resolved.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5%nPresent:%n%6 |
Internal event: The following attribute value change was applied. A value key conflict was resolved.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%nAttribute value:%n%4%nAttribute value GUID:%n%5%nPresent:%n%6 |
| 0x4000083D | Skogens utløpstid/levetid har blitt satt til %1 dager. Dette påvirker levetiden tilsikkerhetskopieringer, og det påvirker også tiden som replikaer kan være frakoblet før de måinstalleres på nytt. |
The forest tombstone lifetime has been set to %1 days. This will affect the shelf-life ofyour backups and also affect the time that replicas can be disconnected before they mustbe reinstalled. |
| 0x4000083E | Internal event: Query processor is intersecting the following indexes to optimize a query.%n%nIndexes:%n%1 |
Internal event: Query processor is intersecting the following indexes to optimize a query.%n%nIndexes:%n%1 |
| 0x4000083F | Internal event: Call to index intersection returned %1. The approximate record count in intersect index is %2%n |
Internal event: Call to index intersection returned %1. The approximate record count in intersect index is %2%n |
| 0x40000840 | Internal event: NSPIBind operation completed with return code %1%nFollowing are the details of the bind operation:%nPeer Address: %2%nCode page: %3%nSid of the user: %4%nDNT of the GAL chosen: %5%nDNT of the Template chosen: %6%nBind Number: %7%n |
Internal event: NSPIBind operation completed with return code %1%nFollowing are the details of the bind operation:%nPeer Address: %2%nCode page: %3%nSid of the user: %4%nDNT of the GAL chosen: %5%nDNT of the Template chosen: %6%nBind Number: %7%n |
| 0x40000841 | Internal event: DS is creating a sort table with max table size set to %8.%nThe entries will be sorted on attribute %2 whose attribute syntax is %3%nThe index used to create the sort table is %1.%nThe locale used for sorting is %4.%nSort order is ascending: %5%nSort is Forward only sort: %6%nSort is for a VLV search: %7%n%n |
Internal event: DS is creating a sort table with max table size set to %8.%nThe entries will be sorted on attribute %2 whose attribute syntax is %3%nThe index used to create the sort table is %1.%nThe locale used for sorting is %4.%nSort order is ascending: %5%nSort is Forward only sort: %6%nSort is for a VLV search: %7%n%n |
| 0x40000842 | Internal event: Creating sort table returned with error %1.%nThere are %2 entries in the sort table.%n |
Internal event: Creating sort table returned with error %1.%nThere are %2 entries in the sort table.%n |
| 0x40000847 | Denne Active Directory Lightweight Directory Services-serveren støtter nå den valgfrie funksjonen Papirkurv. Når alle servere støtter denne valgfrie funksjonen, kan gjenoppretting av objekter utføres uten at data går tapt. |
This Active Directory Lightweight Directory Services server now supports the Recycle Bin optional feature. When all servers support the optional feature, objects may be undeleted without loss of data. |
| 0x40000848 | Denne Active Directory Lightweight Directory Services-serveren støtter ikke Papirkurv. Slettede objekter kan gjenopprettes, men når dette utføres, kan det hende noen av attributtene for det objektet går tapt. I tillegg kan det hende at attributter for andre objekter som refererer til det gjenopprettede objektet, også går tapt. |
This Active Directory Lightweight Directory Services server does not support the Recycle Bin. Deleted objects may be undeleted, however, when an object is undeleted, some attributes of that object may be lost. Additionally, attributes of other objects that refer to the object being undeleted may also be lost. |
| 0x40000849 | Denne Active Directory Lightweight Directory Services-serveren deaktiverer papirkurven. Slettede objekter kan ikke gjenopprettes på dette tidspunktet. |
This Active Directory Lightweight Directory Services server is disabling the Recycle Bin. Deleted objects may not be undeleted at this time. |
| 0x4000084C | Internal event: The DirRemove (recycle) operation was called with the following parameters.%n%nCaller type:%n%1%nObject:%n%2%n%nThis information is generally used for event tracing. |
Internal event: The DirRemove (recycle) operation was called with the following parameters.%n%nCaller type:%n%1%nObject:%n%2%n%nThis information is generally used for event tracing. |
| 0x4000084D | Internal event: The DirRemove (recycle) operation completed with the following status.%n%nStatus:%n1%n%nThis information is generally used for event tracing. |
Internal event: The DirRemove (recycle) operation completed with the following status.%n%nStatus:%n1%n%nThis information is generally used for event tracing. |
| 0x4000084E | Fantomobjektet %1 eksisterer i den lokale Active Directory Lightweight Directory Services-databasen, men eksisterer ikke i databasen for en annen GC. Dette kan angi at replikering ikke har blitt fullført, eller at den lokale AD_TERM-databasen inneholder et etterlatt fantom. Hvis denne tilstanden vedvarer, angir det et etterlatt fantom. |
The phantom object %1 exists in the local Active Directory Lightweight Directory Services database, but doesn't exist in the database of another GC. This may indicate that replication has not completed, or may indicate that the local AD_TERM database contains a lingering phantom. If this state persists, it indicates a lingering phantom. |
| 0x40000855 | Active Directory Lightweight Directory Services utførte et eksternt prosedyrekall (RPC) til følgende server for å bekrefte navnet på objekter som ikke eksisterer i den lokale Active Directory Lightweight Directory Services-databasen. Returverdien 0 angir at RPC-kallet var vellykket.%n%nServer:%n%1%nReturverdi:%n%2%n%nTilleggsdata%nIntern ID:%n%3 |
Active Directory Lightweight Directory Services made a remote procedure call (RPC) to the following server in order to verify the names of objects that do not exist in the local Active Directory Lightweight Directory Services database. A return value of 0 indicates the RPC call succeeded.%n%nServer:%n%1%nReturn value:%n%2%n%nAdditional Data%nInternal ID:%n%3 |
| 0x40000858 | Intern hendelse: En valgfri funksjon har blitt aktivert.%n%nNavn på valgfri funksjon:%n%1%nGUID for valgfri funksjon:%n%2%nOmfang av valgfri funksjon:%n%3 |
Internal event: An optional feature has been enabled.%n%nOptional feature name:%n%1%nOptional feature guid:%n%2%nScope of optional feature:%n%3 |
| 0x40000859 | Intern hendelse: En valgfri funksjon har blitt deaktivert.%n%nNavn på valgfri funksjon:%n%1%nGUID for valgfri funksjon:%n%2%nOmfang av valgfri funksjon:%n%3 |
Internal event: An optional feature has been disabled.%n%nOptional feature name:%n%1%nOptional feature guid:%n%2%nScope of optional feature:%n%3 |
| 0x4000085A | Intern behandling av Active Directory Lightweight Directory Services-databasen har ennå ikke fullstendig oppdatert Active Directory Lightweight Directory Services' sporing av tilstanden til slettede objekter. Inntil denne behandlingen er fullført, er det ikke sikkert at objekter kan gjenopprettes. I tillegg er det ikke sikkert at funksjonen Papirkurv kan aktiveres. Denne behandlingen fortsetter. |
Internal processing of the Active Directory Lightweight Directory Services database has not yet completely updated the Active Directory Lightweight Directory Services's tracking of the state of deleted objects. Until this processing completes successfully, objects may not be undeleted. Additionally, the Recycle Bin feature may not be enabled. This processing is continuing. |
| 0x4000085B | Intern behandling av Active Directory Lightweight Directory Services-databasen har fullført oppdateringen av Active Directory Lightweight Directory Services' sporing av tilstanden for slettede objekter. |
Internal processing of the Active Directory Lightweight Directory Services database has completed the update of the Active Directory Lightweight Directory Services's tracking of the state of deleted objects. |
| 0x40000864 | Internal event: The local Active Directory Lightweight Directory Services has found an object that conflicts with a reference to a directory partition (nCName attribute). The Active Directory Lightweight Directory Services has renamed the object to correct this problem.%n%nConflicting partition: %n%1%nObject: %n%2%nRenamed object name: %n%3 |
Internal event: The local Active Directory Lightweight Directory Services has found an object that conflicts with a reference to a directory partition (nCName attribute). The Active Directory Lightweight Directory Services has renamed the object to correct this problem.%n%nConflicting partition: %n%1%nObject: %n%2%nRenamed object name: %n%3 |
| 0x40000865 | Internal event: The local Active Directory Lightweight Directory Services has found a crossRef object whose directory partition name reference (ncName attribute) was renamed because it conflicted with a local object. Active Directory Lightweight Directory Services has successfully corrected the problem.%n%nFixed partition name: %n%1 |
Internal event: The local Active Directory Lightweight Directory Services has found a crossRef object whose directory partition name reference (ncName attribute) was renamed because it conflicted with a local object. Active Directory Lightweight Directory Services has successfully corrected the problem.%n%nFixed partition name: %n%1 |
| 0x40000870 | Den lokale Active Directory Lightweight Directory Services-forekomsten har funnet en konfigurasjonsfil for kloning av virtuell domenekontroller.%n%nKonfigurasjonsfilen for kloning av virtuell domenekontroller ble funnet på følgende plassering: %n%1%nEksistensen av en konfigurasjonsfil for kloning av virtuell domenekontroller angir at den lokale virtuelle domenekontrolleren er en kloning av en annen virtuell domenekontroller. Active Directory Lightweight Directory Services begynner å klone seg selv. |
The local Active Directory Lightweight Directory Services has found a virtual domain controller cloning configuration file.%n%nThe virtual domain controller cloning configuration file is found at: %n%1%nThe existence of the virtual domain controller cloning configuration file indicates that the local virtual domain controller is a clone of another virtual domain controller. The Active Directory Lightweight Directory Services will start to clone itself. |
| 0x40000871 | Den lokale Active Directory Lightweight Directory Services-forekomsten fant ikke konfigurasjonsfilen for kloning av virtuell domenekontroller. Den lokale maskinen er ikke en klonet domenekontroller. |
The local Active Directory Lightweight Directory Services did not find the virtual domain controller cloning configuration file. The local machine is not a cloned DC. |
| 0x40000873 | DsRoleSvc-tjenesten ble startet for å klone den lokale virtuelle domenekontrolleren. |
DsRoleSvc service was started to clone the local virtual domain controller. |
| 0x40000878 | Domenekontrolleren kjøres på en støttet hypervisor. Genererings-ID for virtuell maskin er funnet.%n%nGjeldende verdi for genererings-ID for virtuell maskin: %1 |
The DC is running on a supported hypervisor. VM Generation ID is detected.%n%nCurrent value of VM Generation ID: %1 |
| 0x40000879 | Finner ingen genererings-ID for virtuell maskin. Domenekontrolleren ligger på en fysisk maskin, en versjon på lavere versjon av Hyper-V eller en hypervisor som ikke støtter genererings-IDen for virtuell maskin.%n%nTilleggsdata%nFeilkode returnert under kontroll av genererings-ID for virtuell maskin:%n%1 |
There is no VM Generation ID detected. The DC is hosted on a physical machine, a down-level version of Hyper-V, or a hypervisor that does not support the VM Generation ID.%n%nAdditional Data%nFailure code returned when checking VM Generation ID:%n%1 |
| 0x4000087B | Finner ingen endring i genererings-ID.%n%nGenererings-ID bufret i DS (gammel verdi):%n%1%nGenererings-ID for øyeblikket i virtuell maskin (ny verdi):%n%2 |
No Generation ID change has been detected.%n%nGeneration ID cached in DS (old value):%n%1%nGeneration ID currently in VM (new value):%n%2 |
| 0x4000087C | Leste msDS-GenerationId-attributtet for domenekontrollerens datamaskinobjekt.%n%nVerdi for msDS-GenerationId-attributt:%n%1 |
Read the msDS-GenerationId attribute of the Domain Controller's computer object.%n%nmsDS-GenerationId attribute value:%n%1 |
| 0x4000087D | Kan ikke lese msDS-GenerationId-attributtet for domenekontrollerens datamaskinobjekt. Dette kan skyldes en feil under overføringen av databasen, eller at genererings-IDen ikke eksisterer i den lokale databasen. msDS-GenerationId-attributtet eksisterer ikke i den første omstarten etter dcpromo, eller domenekontrolleren er ikke en virtuell domenekontroller.%n%nTilleggsdata%nFeilkode:%n%1 |
Failed to read the msDS-GenerationId attribute of the Domain Controller's computer object. This may be caused by database transaction failure, or the generation id does not exist in the local database. The msDS-GenerationId does not exist during the first reboot after dcpromo or the DC is not a virtual domain controller.%n%nAdditional Data%nFailure code:%n%1 |
| 0x4000087E | Domenekontrolleren er verken en kloning av en virtuell domenekontroller eller et statisk utvalg av en gjenopprettet virtuell domenekontroller. |
The DC is neither a virtual domain controller clone nor a restored virtual domain controller snapshot. |
| 0x40000880 | Gav nytt navn til konfigurasjonsfilen for kloning av virtuell domenekontroller.%n%nTilleggsdata%nGammelt filnavn:%n%1%nNytt filnavn:%n%2 |
Renamed virtual domain controller clone configuration file.%n%nAdditional Data%nOld file name:%n%1%nNew file name:%n%2 |
| 0x40000882 | Registrerte en konfigurasjonsfil for kloning av virtuell domenekontroller, men genererings-IDen for VM har ikke blitt endret. Den lokale domenekontrolleren er kildedomenekontrolleren for kloningen. Gi nytt navn til konfigurasjonsfilen for kloningen. |
Detected virtual domain controller clone configuration file, but VM Generation ID has not been changed. The local DC is the clone source DC. Rename the clone configuration file. |
| 0x40000883 | msDS-GenerationId-attributtet for domenekontrollerens datamaskinobjekt har blitt satt til følgende parameter:%n%nGenerationID-attributt:%n%1 |
The msDS-GenerationId attribute of the Domain Controller's computer object has been set to the following parameter:%n%nGenerationID attribute:%n%1 |
| 0x40000885 | The transaction was aborted due to the virtual machine being reverted to a previous state. This occurs after the application of a virtual machine snapshot, after a virtual machine import operation, or after a live migration operation. |
The transaction was aborted due to the virtual machine being reverted to a previous state. This occurs after the application of a virtual machine snapshot, after a virtual machine import operation, or after a live migration operation. |
| 0x40000886 | Internal event: The Directory Service has been asked to clone a remote DSA%n%nAdditional data:%nClone Id: %1 |
Internal event: The Directory Service has been asked to clone a remote DSA%n%nAdditional data:%nClone Id: %1 |
| 0x40000887 | Internal event: Active Directory Lightweight Directory Services completed the request to clone the remote Directory System Agent.%n%nOriginal DC name:%n%3%nRequest clone DC name:%n%4%nRequest clone DC site:%n%5%nCreated clone DC name:%n%7%nCreated clone DC site:%n%8%n%nAdditional Data%nClone Id: %6%nError value:%n%1 %2%n%nPlease see http://go.microsoft.com/fwlink/?LinkId=286669 for more information. |
Internal event: Active Directory Lightweight Directory Services completed the request to clone the remote Directory System Agent.%n%nOriginal DC name:%n%3%nRequest clone DC name:%n%4%nRequest clone DC site:%n%5%nCreated clone DC name:%n%7%nCreated clone DC site:%n%8%n%nAdditional Data%nClone Id: %6%nError value:%n%1 %2%n%nPlease see http://go.microsoft.com/fwlink/?LinkId=286669 for more information. |
| 0x40000889 | Active Directory Lightweight Directory Services stoppet FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen.%n%nTjenestenavn:%n%1%nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-replikaen. Dette gjøres ved å stoppe FRS- eller DFSR-replikeringstjenesten som brukes til å replikere SYSVOL-mappen og deretter starte den på nytt med de relevante registernøklene og -verdiene for å utløse gjenopprettingen. Hendelse 2187 loggføres når FRS- eller DFSR-tjenesten startes på nytt. |
Active Directory Lightweight Directory Services stopped the FRS or DFSR service used to replicate the SYSVOL folder.%n%nService name:%n%1%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services must initialize a non-authoritative restore on the local SYSVOL replica. This is performed by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. Event 2187 will be logged when FRS or DFSR service is restarted. |
| 0x4000088B | Active Directory Lightweight Directory Services startet FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen.%n%nTjenestenavn:%n%1%nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-replikaen. Dette ble gjort ved å stoppe FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen og deretter starte den på nytt med de relevante registernøklene og -verdiene for å utløse gjenopprettingen. |
Active Directory Lightweight Directory Services started the FRS or DFSR service used to replicate the SYSVOL folder.%n%nService name:%n%1%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services needed to initialize a non-authoritative restore on the local SYSVOL replica. This was done by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. |
| 0x4000088D | Active Directory Lightweight Directory Services satte følgende registerverdier til å initialisere SYSVOL-replikaer i løpet av en ikke-autoritativ gjenoppretting:%n%nRegisternøkkel:%n%1%nRegisterverdi: %n%2%nRegisterverdidata: %n%3%nActive Directory registrerte at den virtuelle maskinen som er vert for domenekontrolleren, ble tilbakestilt til en tidligere tilstand. Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-replikaen. Dette gjøres ved å stoppe FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen, og starte den med riktige registernøkler og verdier for å starte gjenopprettingen. |
Active Directory Lightweight Directory Services set the following registry values to initialize SYSVOL replica during a non-authoritative restore:%n%nRegistry Key:%n%1%nRegistry Value: %n%2%nRegistry Value data: %n%3%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services needs to initialize a non-authoritative restore on the local SYSVOL replica. This is done by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. |
| 0x4000088F | Active Directory Lightweight Directory Services satte følgende registerverdi til å deaktivere DNS-oppdateringer.%n%nRegisternøkkel:%n%1%nRegisterverdi: %n%2%nRegisterverdidata: %n%3%nI løpet av kloningsprosessen kan det hende den lokale maskinen et kort øyeblikk har samme datamaskinnavn som klonekildemaskinen. DNS A- og AAAA-postregistrering deaktiveres i denne perioden slik at klienter ikke kan sende forespørsler til den lokale maskinen som blir klonet. Kloningsprosessen aktiverer DNS-oppdateringer på nytt etter at kloning er fullført. |
Active Directory Lightweight Directory Services set the following registry value to disable DNS updates.%n%nRegistry Key:%n%1%nRegistry Value: %n%2%nRegistry Value data: %n%3%nDuring the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. The cloning process will enable DNS updates again after cloning is completed. |
| 0x40000891 | Active Directory Lightweight Directory Services satte følgende registerverdi til å aktivere DNS-oppdateringer.%nRegisternøkkel:%n%1%nRegisterverdi: %n%2%nRegisterverdidata: %n%3%nI løpet av kloningsprosessen kan det hende den lokale maskinen et kort øyeblikk har samme datamaskinnavn som klonekildemaskinen. DNS A- og AAAA-postregistrering deaktiveres i denne perioden slik at klienter ikke kan sende forespørsler til den lokale maskinen som blir klonet. |
Active Directory Lightweight Directory Services set the following registry value to enable DNS updates.%nRegistry Key:%n%1%nRegistry Value: %n%2%nRegistry Value data: %n%3%nDuring the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. |
| 0x40000898 | %nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services initialiserer replikering for å oppdatere domenekontrolleren. Hendelse 2201 loggføres når replikeringen er fullført.%n |
%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services initializes replication to bring the domain controller current. Event 2201 will be logged when the replication is finished.%n |
| 0x40000899 | %nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services har fullført replikering for å oppdatere domenekontrolleren.%n |
%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services has finished replication to bring the domain controller current.%n |
| 0x4000089C | Active Directory Lightweight Directory Services har oppdaget en endring av generasjons-ID for virtuell maskin. Endringen betyr at den virtuelle domenekontrolleren er gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services vil utføre følgende operasjoner for å beskytte den gjenopprettede domenekontrolleren mot mulige dataavvik og opprettelsen av sikkerhetskontohaver med dupliserte SIDer:%nOpprette en ny aktiverings-ID%nGjøre gjeldende RID-utvalg ugyldig%nEierskap til FSMO-roller bekreftes ved neste innkommende replikering. Hvis domenekontrolleren hadde en FSMO-rolle i dette tidsrommet, vil den rollen være utilgjengelig.%nStarte gjenopprettingsoperasjon for SYSVOL-replikeringstjenesten.%nStarte replikering for å oppdatere den gjenopprettede domenekontrolleren til den mest oppdaterte tilstanden.%nForespørre et nytt RID-utvalg. |
Active Directory Lightweight Directory Services has detected a change of virtual machine generation ID. The change means that the virtual domain controller has been reverted to a previous state. Active Directory Lightweight Directory Services will perform the following operations to protect the reverted domain controller against possible data divergence and to protect creation of security principals with duplicate SIDs:%nCreate a new invocation ID%nInvalidate current RID pool%nOwnership of the FSMO roles will be validated at next inbound replication. During this window if the domain controller held a FSMO role, that role will be unavailable.%nStart SYSVOL replication service restore operation.%nStart replication to bring the reverted domain controller to the most current state.%nRequest a new RID pool. |
| 0x4000089D | Active Directory Lightweight Directory Services gjorde gjeldende RID-utvalg ugyldig etter at den virtuelle domenekontrolleren ble gjenopprettet til en tidligere tilstand. |
Active Directory Lightweight Directory Services invalidated current RID pool after virtual domain controller was reverted to previous state. |
| 0x400008A0 | Active Directory Lightweight Directory Services slettet DFSR-databaser for å initialisere SYSVOL-replika under en ikke-autoritativ gjenoppretting.%nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-replikaen. For DFSR gjøres dette ved å stoppe DFSR-tjenesten, slette DFSR-databaser og starte tjenesten på nytt. Når DFSR startes på nytt, vil databasene gjenoppbygges og den innledende synkroniseringen startes. |
Active Directory Lightweight Directory Services deleted DFSR databases to initialize SYSVOL replica during a non-authoritative restore.%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services needs to initialize a non-authoritative restore on the local SYSVOL replica. For DFSR, this is done by stopping the DFSR service, deleting DFSR databases, and re-starting the service. Upon restarting DFSR will rebuild the databases and start the initial sync. |
| 0x400008A3 | Active Directory Lightweight Directory Services har opprettet objekter for klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %3%nNavn på klonedomenekontroller: %1%nForsøksløkke: %2 |
Active Directory Lightweight Directory Services has created objects for clone domain controller.%n%nAdditional data:%nClone Id: %3%nClone domain controller name: %1%nRetry loop: %2 |
| 0x400008A4 | Active Directory Lightweight Directory Services startet oppretting av objekter for klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nKlonenavn: %2%nKloneområde: %3%nKlone-RODC: %4 |
Active Directory Lightweight Directory Services started to create objects for the clone domain controller.%n%nAdditional data:%nClone Id: %1%nClone name: %2%nClone site: %3%nClone RODC: %4 |
| 0x400008A5 | Active Directory Lightweight Directory Services opprettet et nytt KrbTgt-objekt for kloning av skrivebeskyttet domenekontroller.%n%nTilleggsdata:%nKlone-ID: %1%nNy KrbTgt-objekt-GUID: %2 |
Active Directory Lightweight Directory Services created a new KrbTgt object for Read-Only domain controller cloning.%n%nAdditional data:%nClone Id: %1%nNew KrbTgt Object Guid: %2 |
| 0x400008A6 | Active Directory Lightweight Directory Services oppretter et datamaskinobjekt for klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nOpprinnelig domenekontroller: %2%nKlonedomenekontroller: %3 |
Active Directory Lightweight Directory Services will create a computer object for the clone domain controller.%n%nAdditional data:%nClone Id: %1%nOriginal domain controller: %2%nClone domain controller: %3 |
| 0x400008A7 | Active Directory Lightweight Directory Services legger til klonedomenekontrolleren i følgende område.%n%nTilleggsdata:%nKlone-ID: %1%nOmråde: %2 |
Active Directory Lightweight Directory Services will add the clone domain controller in the following site.%n%nAdditional data:%nClone Id: %1%nSite: %2 |
| 0x400008A8 | Active Directory Lightweight Directory Services oppretter en serverbeholder for klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nServerbeholder: %2 |
Active Directory Lightweight Directory Services will create a servers container for the clone domain controller.%n%nAdditional data:%nClone Id: %1%nServers Container: %2 |
| 0x400008A9 | Active Directory Lightweight Directory Services oppretter et serverobjekt for klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nServerobjekt: %2 |
Active Directory Lightweight Directory Services will create a server object for the clone domain controller.%n%nAdditional data:%nClone Id: %1%nServer Object: %2 |
| 0x400008AA | Active Directory Lightweight Directory Services oppretter et NTDS Settings-objekt for klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nObjekt: %2 |
Active Directory Lightweight Directory Services will create a NTDS Settings object for the clone domain controller.%n%nAdditional data:%nClone Id: %1%nObject: %2 |
| 0x400008AB | Active Directory Lightweight Directory Services oppretter tilkoblingsobjekter for den skrivebeskyttede klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1 |
Active Directory Lightweight Directory Services will create connection objects for the clone Read-Only domain controller.%n%nAdditional data:%nClone Id: %1 |
| 0x400008AC | Active Directory Lightweight Directory Services oppretter SYSVOL-objekter for den skrivebeskyttede klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1 |
Active Directory Lightweight Directory Services will create SYSVOL objects for the clone Read-Only domain controller.%n%nAdditional data:%nClone Id: %1 |
| 0x400008AF | Active Directory Lightweight Directory Services angav maskinkontopassord for klonedomenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nNavn på klonedomenekontroller: %2%nTotalt antall nye forsøk: %3 |
Active Directory Lightweight Directory Services successfully set machine account password for the cloned domain controller.%n%nAdditional data:%nClone Id: %1%nClone domain controller name: %2%nTotal retry times: %3 |
| 0x400008B1 | De hurtigbufrede hemmelighetene for følgende sikkerhetskontohaver ble fjernet fra lokal domenekontroller:%n%1%nNår du har klonet en skrivebeskyttet domenekontroller, blir hemmeligheter som tidligere ble hurtigbufret på den skrivebeskyttede domenekontrolleren for kloningskilde, fjernet på den klonede domenekontrolleren. |
The cached secrets of the following security principal have been successfully removed from local domain controller:%n%1%nAfter cloning a read-only domain controller, secrets which were previously cached on the cloning source read-only domain controller will be removed on the cloned domain controller. |
| 0x40000961 | Internal event: Active Directory Lightweight Directory Services removed the following expired link history value:%n%nSource Object:%n%2%nTarget Object:%n%1 |
Internal event: Active Directory Lightweight Directory Services removed the following expired link history value:%n%nSource Object:%n%2%nTarget Object:%n%1 |
| 0x40000964 | Denne Active Directory Lightweight Directory Services-serveren støtter nå den valgfrie funksjonen %1. |
This Active Directory Lightweight Directory Services server now supports the \"%1\" optional feature. |
| 0x40000965 | Denne Active Directory Lightweight Directory Services-serveren støtter ikke den valgfrie funksjonen %1. |
This Active Directory Lightweight Directory Services server does not support the \"%1\" optional feature. |
| 0x40000966 | Denne Active Directory Lightweight Directory Services-serveren deaktiverer støtte for den valgfrie funksjonen %1. |
This Active Directory Lightweight Directory Services server is disabling support for the \"%1\" optional feature. |
| 0x400009C8 | Active Directory Lightweight Directory Services har opprettet tilgangskontrollnøkkelen for VSS slik atsikkerhetskopieringstjenestene for skyggekopien blir riktig registrert.%n%nBrukerhandling:%nIngen kreves.%nHvis brukeren avinstallerer alle tjenester som krever en registerverdi fordenne nøkkelen, kan registernøkkelen trygt fjernes.%n%nTilleggsdata:%nNøkkelnavn:%n%1 |
Active Directory Lightweight Directory Services has successfully created the VSS's Access Control key, to allow theshadow copy backup services to be properly registered.%n%nUser Action:%nNone required.%nIf the user uninstalls all services that require a registry value underthis key, then the registry key may be safely removed.%n%nAdditional Data:%nKey Name:%n%1 |
| 0x400009CA | Active Directory Lightweight Directory Services klarte å legge til seg selv i registernøkkelen for VSS-tilgangskontrollen.%n%nBrukerhandling:%nIngen kreves.%nHvis brukeren avinstallerer alle tjenester som krever at denne tjenestekontoen må ha sikkerhetskopieringstjenester forskyggekopien, kan registerverdien trygt fjernes.%n%nTilleggsdata:%nRegisternøkkel:%n%1%n%nNavn på registerverdi:%n%2 |
Active Directory Lightweight Directory Services succeeded in adding itself to the VSS Access Control registry key.%n%nUser Action:%nNone required.%nIf the user uninstalls all services that require this service account to haveshadow copy backup services, this registry value may be safely removed.%n%nAdditional Data:%nRegistry Key:%n%1%n%nRegistry Value Name:%n%2 |
| 0x400009CF | Følgende hovednavn for tjeneste, som passer til gjensidig godkjenning, ble opprettet for følgende katalogtjeneste.%n%nHovednavn for tjeneste: %n%2%nDSA: %n%1%n |
The following service principal name, which is suitable for mutual authentication, was created for the following Directory Service.%n%nService Principal Name: %n%2%nDSA: %n%1%n |
| 0x400009D5 | Denne DSAen skrev hovednavnene for tjenesten for følgende konto, og disse navnene kreves for at gjensidig godkjenning skal fungere på inngåendetilkoblinger.%n%nKonto:%n%1 |
This DSA successfully wrote the service principal names for the following account which are needed for mutual authentication to succeed on inboundconnections.%n%nAccount:%n%1 |
| 0x400009E0 | Katalogserveren har registrert at tjenestekontoen som ble brukt til å kjøre denne tjenesten, er endret.Katalogserveren har oppdatert den interne strukturen i henhold til dette.%n%nDet er ikke sikkert at denne katalogserveren kan replikere endringer fra andre forekomster før endringen påtjenestekontoen er ferdigreplikert.%n%nBrukerhandling%nHvis gjensidig godkjenning kreves for replikering i dette konfigurasjonssettet, kan det være nødvendig åavregistrere hovednavnene for tjenesten fra den gamle tjenestekontoen og deretter registrere hovednavnene for tjenesten for den nye tjenestekontoen. |
The directory server has detected that the service account used to run this service has been changed.The directory server has updated the internal structures accordingly.%n%nThis directory server may be unable to replicate in changes from other instances, until the serviceaccount change is replicated around.%n%nUser Action%nIf mutual authentication is required for replication in this configuration set, then it may be necessary tounregister the SPNs from the old service account, and register the SPNs for the new service account. |
| 0x400009E1 | Katalogserveren har registrert at vertsnavnet og/eller portene er endret. Hvis dette er den enestekatalogserveren i konfigurasjonssettet, blir denne informasjonen oppdatert i den lokale databasen. Ellers blir denne informasjonenoppdatert på en ekstern katalogserver. Denne meldingen gjentas til endringen er replikert på den lokalekatalogserveren.%n%nTilleggsdata%nGammelt DNS-vertsnavn: %1%nGjeldende DNS-vertsnavn: %2%nGammelt NetBIOS-navn: %3%nGjeldende NetBIOS-navn: %4%nGammel LDAP-port: %5%nGjeldende LDAP-port: %6%nGammel SSL-port: %7%nGjeldende SSL-port: %8 |
The directory server has detected that the host name and/or ports have been changed. If this is the onlydirectory server in the configuration set, then this information will be updated in the local database. Otherwise, this informationwill be updated on a remote directory server. This message will repeat until this change is replicated to the localdirectory server.%n%nAdditional Data%nOld DNS host name: %1%nCurrent DNS host name: %2%nOld NetBIOS name: %3%nCurrent NetBIOS name: %4%nOld LDAP port: %5%nCurrent LDAP port: %6%nOld SSL port: %7%nCurrent SSL port: %8 |
| 0x400009E2 | Katalogserveren har oppdatert informasjonen for vertsnavnet og/eller portene for denne tjenesten på følgende eksterneserver. Andre katalogservere i dette konfigurasjonssettet kan ikke replikere endringer fra dennekatalogserveren før endringen er replikert på disse katalogserverne.%n%nTilleggsdata%nMål-DSA-objekt: %1 |
The directory server has successfully updated the host name and/or ports information for this service on the following remoteserver. Other directory servers in this configuration set (if any) will be unable to replicate changes from thisdirectory server until this change is replicated to them.%n%nAdditional Data%nTarget DSA object: %1 |
| 0x400009E4 | Katalogserveren har oppdatert informasjonen for vertsnavnet og/eller portene for denne tjenesten i den lokale databasen. |
The directory server has successfully updated the host name and/or ports information for this service in the local database. |
| 0x400009E6 | Katalogserveren har oppdatert AD LDS serviceConnectionPoint-objektet i Active Directory Lightweight Directory Services.%n%nTilleggsdata%nDomenenavn for SCP-objekt:%n%1 |
The directory server has successfully updated the AD LDS serviceConnectionPoint object in Active Directory Lightweight Directory Services.%n%nAdditional Data%nSCP object DN:%n%1 |
| 0x400009E7 | Katalogserveren har opprettet AD LDS serviceConnectionPoint-objektet i Active Directory Lightweight Directory Services.%n%nTilleggsdata%nDomenenavn for SCP-objekt:%n%1 |
The directory server has successfully created the AD LDS serviceConnectionPoint object in Active Directory Lightweight Directory Services.%n%nAdditional Data%nSCP object DN:%n%1 |
| 0x400009FC | Samler inn informasjon om denne Active Directory Lightweight Directory Services-forekomsten for avinstallasjon ... |
Collecting information about this Active Directory Lightweight Directory Services instance for uninstall ... |
| 0x400009FD | Avinstallerer Active Directory Lightweight Directory Services... |
Uninstalling Active Directory Lightweight Directory Services... |
| 0x400009FE | Internal event: Active Directory Lightweight Directory Services received a request to begin the removal process.%n%nFlags:%n%1 |
Internal event: Active Directory Lightweight Directory Services received a request to begin the removal process.%n%nFlags:%n%1 |
| 0x400009FF | Internal event: Active Directory Lightweight Directory Services completed the request to initialize the removal process.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to initialize the removal process.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x40000A00 | Internal event: Active Directory Lightweight Directory Services received a request to begin inbound replication with the following parameters.%n%nDirectory partition:%n%1%nFlags:%n%2%nHelper DSA GUID:%n%3 |
Internal event: Active Directory Lightweight Directory Services received a request to begin inbound replication with the following parameters.%n%nDirectory partition:%n%1%nFlags:%n%2%nHelper DSA GUID:%n%3 |
| 0x40000A01 | Internal event: Active Directory Lightweight Directory Services completed the request to remove the local replica of this directory partition.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: Active Directory Lightweight Directory Services completed the request to remove the local replica of this directory partition.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x40000A04 | Internal event: Active Directory Lightweight Directory Services received a request to begin inbound replication with the following parameters.%n%nFlags:%n%1%nHelper DSA GUID:%n%2 |
Internal event: Active Directory Lightweight Directory Services received a request to begin inbound replication with the following parameters.%n%nFlags:%n%1%nHelper DSA GUID:%n%2 |
| 0x40000A07 | Internal event: Active Directory Lightweight Directory Services completed the request to uninstall this instance.%n%nAdditional Data%nOperations Done: %1%nFailed Operation: %2%nError value:%n%3 %4 |
Internal event: Active Directory Lightweight Directory Services completed the request to uninstall this instance.%n%nAdditional Data%nOperations Done: %1%nFailed Operation: %2%nError value:%n%3 %4 |
| 0x40000A0E | Katalogtjenesten har startet avinstallasjonen.%nBrukerhandling:%nHvis denne katalogtjenesten forblir i tjenestekontrollbehandlingen eller hendelsesloggen, forsøker du å kjøre adamuninstall med alternativet /force. |
The directory service has begun an uninstall.%nUser Action:%nIf this directory service remains in the Service Control Manager or the Event Log, try running adamuninstall with the /force option. |
| 0x40000A0F | Katalogtjenesten har begynt å avinstallere databasen. Denne katalogtjenesten kan ikke lenger startes på nytt.%nBrukerhandling:%nHvis denne katalogtjenesten forblir i tjenestekontrollbehandlingen eller hendelsesloggen, forsøker du å kjøre adamuninstall med alternativet /force. |
The directory service has committed the uninstall to the database. This directory service will not be able to start up again.%nUser Action:%nIf this directory service remains in the Service Control Manager or the Event Log, try running adamuninstall with the /force option. |
| 0x40000A11 | Denne katalogtjenesten har fjernet sine servermetadata fra konfigurasjonssettet.%n%nTilleggsdata:Domenenavn for DSA: %1%n |
The directory service has removed its server metadata from the configuration set%n%nAdditional Data:DSA DN: %1%n |
| 0x40000A12 | Avinstallasjonen kan ikke lese tjenesteinnstillingene fra registret for tjenesten: %1!S!. |
Uninstall could not read the service settings from the registry for the service: %1!S!. |
| 0x40000A13 | Avinstallasjonen kan ikke koble til Active Directory Lightweight Directory Services på %1. Avinstallasjonen kan ikke fortsette uten informasjon fra AD LDS. Start AD LDS på nytt, eller kjør ADAMUnInstall /force. |
Uninstall cannot connect to the Active Directory Lightweight Directory Services at %1. Uninstall cannot continue without information from the AD LDS. Please either restart the AD LDS or run ADAMUnInstall /force. |
| 0x40000A14 | Klargjør avinstallasjon av Active Directory Lightweight Directory Services-forekomsten ... |
Preparing the Active Directory Lightweight Directory Services instance for uninstall ... |
| 0x40000A15 | Avinstallasjonen kan ikke kontakte navngivingsovervåkeren (%1) for å fjerne uønskede katalogpartisjoner og kryssreferanser.%nFeil: %2!d!%nHvis du hopper over dette trinnet, blir metadata (kryssreferanser) for katalogpartisjonen værende i konfigurasjonssettet. |
Uninstall could not contact the Naming Master (%1) to remove unwanted directory partitions and cross references.%nError: %2!d!%nSkipping this step will leave directory partition meta data (cross-refs) in the configuration set. |
| 0x40000A16 | Sletter metadataene for katalogpartisjonen %1. |
Deleting the metadata for the directory partition %1. |
| 0x40000A17 | Active Directory Lightweight Directory Services kan ikke fjerne programkatalogpartisjonen %1 fordi denne partisjonen har én eller flere underordnede partisjoner eller kryssreferanser. Fjern den underordnede partisjonen eller kryssreferansene først, og prøv deretter på nytt. Dsmgmt.exe kan brukes til å fjerne partisjonsmetadata.%nHvis du hopper over dette trinnet, genereres det et uopprettelig katalogpartisjonshierarki for dette konfigurasjonssettet. |
Active Directory Lightweight Directory Services could not remove the application directory partition %1 because this partition has one or more child partitions or cross-refs. Remove the child partition or cross-refs first and retry. Dsmgmt.exe can be used to remove partition metadata.%nSkipping this step will result in an irreparable directory partition hierarchy for this configuration set. |
| 0x40000A18 | Active Directory Lightweight Directory Services kan ikke fjerne programkatalogpartisjonen %1 på grunn av følgende feil: %2!d!.%nAdvarsel: Hvis du hopper over dette trinnet, genereres det et uopprettelig katalogpartisjonshierarki for dette konfigurasjonssettet hvis katalogpartisjonen har underordnede katalogpartisjoner. |
Active Directory Lightweight Directory Services could not remove the application directory partition %1 because of the following error %2!d!.%nWarning: Skipping this step will result in an irreparable directory partition hierarchy for this configuration set if the directory partition has child directory partitions. |
| 0x40000A19 | Overfører gjenstående data i katalogpartisjonen %1 til en annen Active Directory Lightweight Directory Services-forekomst... |
Transferring the data remaining in the directory partition %1 to another Active Directory Lightweight Directory Services instance... |
| 0x40000A1A | Active Directory Lightweight Directory Services kan ikke overføre gjenstående data i katalogpartisjonen %1 til en annen Active Directory Lightweight Directory Services-forekomst på grunn av følgende feil: %2!d!. |
Active Directory Lightweight Directory Services could not transfer the data remaining in the directory partition %1 to another Active Directory Lightweight Directory Services instance because of the following error: %2!d!. |
| 0x40000A1B | Kritisk feil under forsøk på å hente brukerinndata. |
Critical failure attempting to get user input. |
| 0x40000A1C | Active Directory Lightweight Directory Services kan ikke koble til Active Directory Lightweight Directory Services-forekomsten %1. Hvis du hopper over dette trinnet, kan ikke avinstallasjonen lagre nylige dataendringer på en annen replika, og metadata blir ikke fjernet fra konfigurasjonssettet. Dette anbefales ikke. Tilkoblingen mislyktes med følgende feil:%nFeil: %2!d! |
Active Directory Lightweight Directory Services could not connect to the Active Directory Lightweight Directory Services instance %1. Skipping this step will cause uninstall to not save recent data changes to another replica, and metadata will not be removed from the configuration set. This is not suggested. The connection failed with the following error:%nError %2!d! |
| 0x40000A1D | Koblet til versjon %1 av Active Directory Lightweight Directory Services. |
Connected to version %1 of Active Directory Lightweight Directory Services. |
| 0x40000A1E | Kobler til serveren %1 som %2\\%3 |
Connecting to server %1 as %2\\%3 |
| 0x40000A1F | Kobler til serveren %1 som pålogget bruker. |
Connecting to the server %1 as the logged on user. |
| 0x40000A20 | Hoppet over sletting av metadataene for katalogpartisjonen %1. |
Skipped deleting the metadata for directory partition %1. |
| 0x40000A21 | Slett metadata/kryssreferanse for katalogpartisjonen %1. |
Delete the metadata/cross-ref for directory partition %1. |
| 0x40000A22 | Slettet kryssreferansen (metadata) %2 for katalogpartisjonen %1. |
Successfully deleted the cross-ref (metadata) %2 for the directory partition %1. |
| 0x40000A23 | Startet avinstallasjonen av databasen. Denne Active Directory Lightweight Directory Services-forekomsten (%1!S!) kan ikke lenger startes på nytt. |
Successfully committed the uninstall to the database; this Active Directory Lightweight Directory Services (%1!S!) will not start again. |
| 0x40000A24 | Slettet DSA-objektet %1 |
Successfully deleted the DSA Object: %1 |
| 0x40000A25 | Slettet alle tjenestetilkoblingspunkter (SCPer) for denne Active Directory Lightweight Directory Services-forekomsten (%1). |
Successfully deleted all SCPs for this Active Directory Lightweight Directory Services (%1). |
| 0x40000A26 | Slettet alle SPNer for denne Active Directory Lightweight Directory Services-forekomsten (%1). |
Successfully deleted all SPNs for this Active Directory Lightweight Directory Services (%1). |
| 0x40000A27 | Hoppet over den lokale operasjonen. |
Skipped the local commit. |
| 0x40000A28 | Hoppet over sletting av forekomstmetadataene: DSA-objekt: %1. |
Skipped deleting the instance metadata: DSA Object: %1. |
| 0x40000A29 | Bruk dsmgmt.exe til å slette serverens metadata (%1). |
Use dsmgmt.exe to delete the server's metadata (%1). |
| 0x40000A2A | Hoppet over sletting av tjenestetilkoblingspunkter (SCPer) i domenet som denne tjenestekontoen hører til. Tjeneste: %1!S! |
Skipped deleting the service connection points (SCPs) in the domain this service account belongs to. Service: %1!S! |
| 0x40000A2B | Finn tjenestetilkoblingspunktene (SCPene) under tjenestekontoobjektet som har et nøkkelord som samsvarer med %1, og slett dem. |
Find the Service Connection Points (SCPs) under the service account object that have a keyword matching \"%1\", and delete them. |
| 0x40000A2C | Hoppet over sletting av hovednavnene for tjenesten (SPNene) fra tjenestekontoobjektet. |
Skipped deleting the service principal names (SPNs) from the service account object. |
| 0x40000A2D | Få en domeneadministrator til å kjøre SPN-skriptene i katalogen %1. |
Have a domain administrator run the SPN scripts in the directory %1. |
| 0x40000A2E | Active Directory Lightweight Directory Services overførte de gjenstående dataene i katalogpartisjonen %1 til en annen Active Directory Lightweight Directory Services-forekomst. |
Active Directory Lightweight Directory Services successfully transferred the remaining data in directory partition %1 to another Active Directory Lightweight Directory Services instance. |
| 0x40000A2F | Avinstallasjonen hoppet over ureplikerte endringer for katalogpartisjonen %1 etter forespørsel. Alle tidligere ureplikerte endringer for denne katalogpartisjonen har gått tapt. |
Uninstall skipped saving unreplicated changes to the directory partition %1 as requested. All previously unreplicated changes for this directory partition are lost. |
| 0x40000A30 | Henter alle kryssreferanser i konfigurasjonssettet ... |
Retrieving all cross-refs in the configuration set ... |
| 0x40000A33 | Active Directory Lightweight Directory Services kan ikke koble til en assisterende Active Directory Lightweight Directory Services-forekomst i forbindelse med fjerning. |
Active Directory Lightweight Directory Services could not connect to a helper Active Directory Lightweight Directory Services instance for removal purposes. |
| 0x40000A34 | Fullfører fjerning av Active Directory Lightweight Directory Services... |
Completing removal of Active Directory Lightweight Directory Services... |
| 0x40000AF0 | Anroperen sendte en forespørsel om replikering og bufring for en sikkerhetskontohaver i den skrivbare katalogpartisjonen som har blitt avvist.%n%nKatalogpartisjon: %n%1%nAnmodet sikkerhetskontohaver: %n%2%n%nTilleggsdata%nFeilverdi:%n%4 %3%n |
The caller made a replication-caching request for a security principal in the writable directory partition that has been denied.%n%nDirectory partition: %n%1%nSecurity Principal requested: %n%2%n%nAdditional Data%nError value:%n%4 %3%n |
| 0x40000AF1 | Finner ikke en LH-skrivbar PDC for domenet. |
Couldn't find a LH writable PDC for the domain. |
| 0x40000AF2 | Konfigurasjonsinnstillingene angir at denne skrivebeskyttede domenekontrolleren skal installeres på området %1, men dette området inneholder ikke et områdeinnstillingsobjekt. |
Configuration settings indicate that this Read-only Domain Controller should be installed in site %1, but this site doesn't contain a site settings object. |
| 0x40000AF3 | Under nivåhevingen av en skrivebeskyttet domenekontroller mislyktes angivelsen av alternativer for områdeobjektet %1. |
During read only DC promotion setting options on site object %1 failed. |
| 0x40000AF4 | Oppretter tilstandsobjekter for skrivebeskyttede domenekontrollere. |
Creating state objects for Read-only Domain Controller. |
| 0x40000AF5 | Replikerer hemmeligheter for skrivebeskyttede domenekontrollere. |
Replicating secrets for Read-only Domain Controller. |
| 0x40000AF6 | Kan ikke opprette tilstandsobjekter under nivåhevingen av skrivebeskyttede domenekontrollere. |
While promoting Read-only Domain Controller, failed to create the state objects. |
| 0x40000AF7 | Kan ikke oppdatere hovednavnene for tjenesten (SPNene) for datamaskinobjektet under nivåhevingen av skrivebeskyttede domenekontrollere. |
While promoting Read-only Domain Controller, failed to update the SPNs on the computer object. |
| 0x40000AF8 | Kan ikke opprette sekundær krbtgt-konto under nivåhevingen av skrivebeskyttede domenekontrollere. |
While promoting Read-only Domain Controller, failed to create secondary krbtgt account. |
| 0x40000AF9 | Kan ikke opprette krbtgt-kobling under nivåhevingen av skrivebeskyttede domenekontrollere. |
While promoting Read-only Domain Controller, failed to create krbtgt link. |
| 0x40000AFA | Kan ikke replikere hemmelighetene fra den assisterende AD LDS-forekomsten under nivåhevingen av skrivebeskyttede domenekontrollere. |
While promoting Read-only Domain Controller, failed to replicate the secrets from the helper AD LDS instance. |
| 0x40000AFB | Kan ikke bufre en skrivereferanseliste for skrivebeskyttede domenekontrollere.Feilverdi: %n %1 %2 |
Failed to cache a write referral list on Read Only DC.Error Value: %n %1 %2 |
| 0x40000AFC | En skriveforespørsel ble mottatt av den skrivebeskyttede domenekontrolleren. Kan ikke generere en skriveforespørsel til en skrivbar domenekontroller.Skriveforespørsel mottatt fra klienten %3Feilverdi: %n %1 %2 |
A write request was received at the Read Only DC. Failed to generate write referral to a writable DC.Write request received from client %3Error Value: %n %1 %2 |
| 0x40000AFD | En skriveforespørsel ble mottatt av den skrivebeskyttede domenekontrolleren. Den skrivebeskyttede domenekontrolleren har generert en referanse til den skrivbare domenekontrolleren %1.Skriveforespørsel mottatt fra klienten %2 for objektet %3. Skriveforespørselen ble sendt av brukeren %4. |
A write request was received at the Read Only DC. The Read Only DC has generated a referral to writable DC %1.Write request received from client %2 for object %3. The write request was made by the user %4. |
| 0x40000AFE | Kan ikke replikere enkeltobjekter fra PDC til den assisterende Active Directory Lightweight Directory Services-forekomsten |
Failed to replicate single object from PDC to Helper Active Directory Lightweight Directory Services instance |
| 0x40000AFF | Kan ikke replikere en hemmelighet for enkeltobjekter fra PDC til den assisterende Active Directory Lightweight Directory Services-forekomsten |
Failed to replicate single object secret from PDC to Helper Active Directory Lightweight Directory Services instance |
| 0x40000B00 | Kan ikke bufre en skrivereferanseliste for PDC på en skrivebeskyttet domenekontroller.%n%nTilleggsdata%nFeilverdi:%n%1 (%2)%nDatabasefeilkode: %3 |
Failed to cache a write referral list for PDC on Read Only DC.%n%nAdditional Data%nError Value:%n%1 (%2)%nDatabase error code: %3 |
| 0x40000B01 | Katalogtjenesten har åpnet et UDP-endepunkt.%nPortnummer:%n%1%nIP-adresse%n %2 |
The Directory Service has successfully opened an UDP endpoint.%nPort number:%n%1%nIP Address%n %2 |
| 0x40000B03 | Validering av maksimal tilkoblingsgrense for NSPI mislyktes.%n%nFeilverdi:%n%1%nBruker: %n%2 |
Validating NSPI Max connection limit failed.%n%nError Value:%n%1%nUser: %n%2 |
| 0x40000B04 | Maksimal tilkoblingsgrense for NSPI for brukeren er nådd.Du må oppheve binding av gamle tilkoblinger for NSPI før du kan opprette nye tilkoblinger.%n%n Tilleggsdata%n Maksimalt antall NSPI-tilkoblinger per bruker: %n%1%n Bruker: %n%2 |
NSPI max connection limit for the user has reached.You need to do NSPI unbind on old connections before making new connections.%n%n Additional Data%n Max NSPI connections per user: %n%1%n User: %n%2 |
| 0x40000B05 | Startet vurdering av transitivt filter.%n%n Tilleggsdata%n ID for basiskobling: %n%1%n Koblingstype:%n%2%n Attributt:%n%3 |
Started evaluating transitive filter.%n%n Additional Data%n Base link id: %n%1%n Link type:%n%2%n Attribute:%n%3 |
| 0x40000B06 | Avsluttet vurdering av transitivt filter.%n%n Tilleggsdata%n Vurderte objekter: %n%1 |
Finished evaluating transitive filter.%n%n Additional Data%n Objects visited: %n%1 |
| 0x40000B07 | Kan ikke angi grupper for visning etter behov og/eller grupper for ingen visning under nivåhevingen av skrivebeskyttede domenekontrollere. |
While promoting Read-only Domain Controller, failed to set the reveal on demand and/or never reveal groups. |
| 0x40000B08 | Kontrollerer tilstandsobjekter for skrivebeskyttede domenekontrollere. |
Checking state objects for Read-only Domain Controller. |
| 0x40000B09 | Fant ikke det forventede serverobjektet for denne Active Directory Lightweight Directory Services-forekomsten. |
The expected server object for this Active Directory Lightweight Directory Services instance could not be found. |
| 0x40000B0A | Fant ikke det forventede NTDS-innstillingsobjektet for denne Active Directory Lightweight Directory Services-forekomsten. |
The expected NTDS Settings object for this Active Directory Lightweight Directory Services instance could not be found. |
| 0x40000B0B | Active Directory Lightweight Directory Services-forekomsten fant ikke NTDS-innstillingsobjektet for denne AD LDS-forekomsten (%1) på den eksterne AD LDS-forekomsten (%2). |
Active Directory Lightweight Directory Services instance could not find the NTDS Settings object for this AD LDS instance %1 on the remote AD LDS instance %2. |
| 0x40000B0D | Fant ikke de forventede tilstandsobjektene under nivåhevingen av skrivebeskyttede domenekontrollere. |
While promoting Read-only Domain Controller, the expected state objects could not be found. |
| 0x40000B0E | Kan ikke oppdatere aktiverings-IDen for NTDS-innstillingsobjektet. |
The invocation ID on the NTDS Settings object could not be refreshed. |
| 0x40000B0F | Katalogtjenesten er ikke lenger konfigurert til å være vert for følgende skrivebeskyttede programkatalogpartisjon. Et forsøk på å fjerne partisjonen mislyktes.%n%nProgramkatalogpartisjon:%n%1%n%nDenne operasjonen vil blir prøvd på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Directory Service is no longer configured to host the following read-only application directory partition. An attempt to remove the partition failed.%n%nApplication directory partition:%n%1%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%3 %2 |
| 0x40000B10 | Katalogtjenesten er ikke lenger konfigurert til å være vert for følgende skrivebeskyttede programkatalogpartisjon.%n%nProgramkatalogpartisjon:%n%1%n%nObjektene i denne katalogpartisjonen blir fjernet fra Active Directory Lightweight Directory Services-databasen i katalogtjenesten. |
The Directory Service is no longer configured to host the following read-only application directory partition.%n%nApplication directory partition:%n%1%n%nThe objects in this directory partition will be removed from the Active Directory Lightweight Directory Services database on the Directory Service. |
| 0x40000B11 | Oversatt fonetisk indeks for visningsnavn eksisterer.%n%n Tilleggsdata%n Indeksnavn: %n%1 |
Localized phonetic displayname index exists.%n%n Additional Data%n Index name: %n%1 |
| 0x40000B15 | Kan ikke oppdatere DNS-vertsnavnet for serverobjektet under nivåhevingen av en skrivebeskyttet domenekontroller. |
While promoting a Read-only Domain Controller, failed to update the DNS hostname on the server object. |
| 0x40000B16 | Kan ikke oppdatere informasjonen om operativsystemversjonen for datamaskinobjektet under nivåhevingen av en skrivebeskyttet domenekontroller. |
While promoting a Read-only Domain Controller, failed to update the OS version information on the computer object. |
| 0x40000B1E | Knowledge Consistency Checker fant en replikeringstilkobling for den lokale skrivebeskyttede katalogtjenesten, men tilkoblingens plan er ikke nøyaktig. En ny plan ble funnet hos en gjeldende replikeringspartner. Planen oppdateres i skogen.%n%nTilleggsdata%nTilkobling: %n%1%nGjeldende partnertilkobling: %n%2%n |
The Knowledge Consistency Checker located a replication connection for the local read-only directory service, but the connection's schedule is not accurate. A new schedule was found from a current replication partner. It will be updated in the forest.%n%nAdditional Data%nConnection: %n%1%nCurrent Partner Connection: %n%2%n |
| 0x40000B42 | Active Directory Lightweight Directory Services kan ikke konfigurere replikeringsvarslinger for katalogpartisjonen %1 i den eksterne Active Directory Lightweight Directory Services-forekomsten %2. |
Active Directory Lightweight Directory Services could not setup replication notifications for the directory partition %1 on the remote Active Directory Lightweight Directory Services instance %2. |
| 0x40000B48 | %nI løpet av den forrige 24-timersperioden forsøkte noen klienter å utføre LDAP-bindinger som enten var:%n(1) En SASL LDAP-binding (Negotiate, Kerberos, NTLM eller Digest) som ikke krever signatur (integritetsvalidering), eller%n(2) En enkel LDAP-binding som ble utført for en klarteksttilkobling (ikke-SSL/TLS-kryptert)%n%nDenne katalogserveren er konfigurert til å avslå slike bindinger. Dette er den anbefalte konfigurasjonsinnstillingen, og denforbedrer sikkerheten på denne serveren betraktelig. Se http://go.microsoft.com/fwlink/?LinkID=87923 hvis du vil ha mer informasjon.%n%nNedenfor vises kort informasjon om hvor mange slike bindinger som ble mottatt de siste 24 timene.%n%nDu kan aktivere tilleggslogging for å logge en hendelse hver gang en klient genererer en slik binding, inkludertinformasjon om hvilken klient som genererer bindingen. Dette gjør du ved å heve nivået for innstillingen for hendelsesloggkategorien \"LDAP Interface Events\"til nivå 2 eller høyere.%n%nAntall enkle bindinger som ble utført uten SSL/TLS: %1%nAntall Negotiate/Kerberos/NTLM/Digest-bindinger som ble utført uten signatur: %2 |
%nDuring the previous 24 hour period, some clients attempted to perform LDAP binds that were either:%n(1) A SASL (Negotiate, Kerberos, NTLM, or Digest) LDAP bind that did not request signing (integrity validation), or%n(2) A LDAP simple bind that was performed on a clear text (non-SSL/TLS-encrypted) connection%n%nThis directory server is configured to reject such binds. This is the recommend configuration setting, and significantlyenhances the security of this server. For more details, please see http://go.microsoft.com/fwlink/?LinkID=87923.%n%nSummary information on the number of such binds received within the past 24 hours is below.%n%nYou can enable additional logging to log an event each time a client makes such a bind, including informationon which client made the bind. To do so, please raise the setting for the \"LDAP Interface Events\" event logging categoryto level 2 or higher.%n%nNumber of simple binds rejected because they were performed without SSL/TLS: %1%nNumber of Negotiate/Kerberos/NTLM/Digest binds rejected because they were performed without signing: %2 |
| 0x40000B49 | Klienten nedenfor opprettet en SASL LDAP-binding (Forhandle/Kerberos/NTLM/Sammendrag) uten å be omsignering (integritetskontroll), eller opprettet en enkel binding via en LDAP-tilkobling av typen ren tekst(ikke SSL-/TLS-kryptert).%n%nIP-adresse for klient:%n%1%nIDen klienten prøve å godkjennes som:%n%2%nBindingstype:%n%3 |
The following client performed a SASL (Negotiate/Kerberos/NTLM/Digest) LDAP bind without requestingsigning (integrity verification), or performed a simple bind over a clear text (non-SSL/TLS-encrypted)LDAP connection.%n%nClient IP address:%n%1%nIdentity the client attempted to authenticate as:%n%2%nBinding Type:%n%3 |
| 0x40000B4B | Active Directory Lightweight Directory Services har mottatt en forespørsel om å oppdatere hovednavnene på tjenesten (SPNene). Denne forespørselen kan ikke utføres på denne skrivebeskyttede domenekontrolleren og ble videresendt til en skrivbar domenekontroller. Operasjonen ble fullført på den skrivbare domenekontrolleren, og endringen har blitt replikert til denne skrivebeskyttede domenekontrolleren.%n%nKonto:%n%1%nOperasjon:%n%2%nAntall SPNer:%n%3%nFlagg:%n%4%nEkstern domenekontroller:%n%5 |
Active Directory Lightweight Directory Services has received a request to update SPNs. The request could not be accomplished on this read-only domain controller, and was forwarded to a writable domain controller. The operation was finished successfully on the writable domain controller, and the change has been replicated to this read-only domain controller.%n%nAccount:%n%1%nOperation:%n%2%nNumber of SPNs:%n%3%nFlags:%n%4%nRemote domain controller:%n%5 |
| 0x40000B4C | Active Directory Lightweight Directory Services har mottatt en forespørsel om å oppdatere hovednavnene på tjenesten (SPNene). Denne forespørselen kan ikke utføres på denne skrivebeskyttede domenekontrolleren og ble videresendt til en skrivbar domenekontroller. Operasjonen mislyktes på den skrivbare domenekontrolleren.%n%nKonto:%n%1%nOperasjon:%n%2%nAntall SPNer:%n%3%nFlagg:%n%4%nEkstern domenekontroller:%n%5%nFeilverdi: %n%6 %7 |
Active Directory Lightweight Directory Services has received a request to update SPNs. The request could not be accomplished on this read-only domain controller, and was forwarded to a writable domain controller. The operation failed on the writable domain controller.%n%nAccount:%n%1%nOperation:%n%2%nNumber of SPNs:%n%3%nFlags:%n%4%nRemote domain controller:%n%5%nError value: %n%6 %7 |
| 0x40000B4D | Active Directory Lightweight Directory Services har mottatt en forespørsel om å oppdatere hovednavnene på tjenesten (SPNene). Denne forespørselen kan ikke utføres på denne skrivebeskyttede domenekontrolleren og ble videresendt til en skrivbar domenekontroller. Operasjonen ble fullført på den skrivbare domenekontrolleren. Endringen ble imidlertid ikke replikert til denne skrivebeskyttede domenekontrolleren. Endringen blir replikert til denne skrivebeskyttede domenekontrolleren under neste vellykkede replikering med en skrivbar domenekontroller.%n%nKonto:%n%1%nOperasjon:%n%2%nAntall SPNer:%n%3%nFlagg:%n%4%nEkstern domenekontroller:%n%5%nFeilverdi: %n%6 %7 |
Active Directory Lightweight Directory Services has received a request to update SPNs. The request could not be accomplished on this read-only domain controller, and was forwarded to a writable domain controller. The operation was finished successfully on the writable domain controller. However, the change failed to replicate to this read-only domain controller. The change will be replicated to this read-only domain controller during the next successful replication with a writable domain controller.%n%nAccount:%n%1%nOperation:%n%2%nNumber of SPNs:%n%3%nFlags:%n%4%nRemote domain controller:%n%5%nError value: %n%6 %7 |
| 0x40000B4E | The destination Active Directory Lightweight Directory Services instance logging this event processed a link value update on the source object below. The change was not applied because the source object is in the recycled state on the destination Active Directory Lightweight Directory Services instance.%nTo correct this condition, the destination Active Directory Lightweight Directory Services instance will re-request a re-ordered list of updates from the source Active Directory Lightweight Directory Services instance.%n%nSource Object GUID:%n%1%nAttribute:%n%2%nTarget Object DN:%n%3%n |
The destination Active Directory Lightweight Directory Services instance logging this event processed a link value update on the source object below. The change was not applied because the source object is in the recycled state on the destination Active Directory Lightweight Directory Services instance.%nTo correct this condition, the destination Active Directory Lightweight Directory Services instance will re-request a re-ordered list of updates from the source Active Directory Lightweight Directory Services instance.%n%nSource Object GUID:%n%1%nAttribute:%n%2%nTarget Object DN:%n%3%n |
| 0x40000B51 | Periodiske replikeringssynkroniseringer blir ikke startet fordi de første synkroniseringene ennå ikke er fullført. |
Periodic replication synchronizations are not being started since initial synchronizations have not finished yet. |
| 0x40000B52 | Internal event: The LDAP server has reached the limit of the number of page tokens it will cache for a single LDAP connection. Each page token in this cache corresponds to an on going LDAP page search on this connection. The oldest page token will be discarded and the corresponding LDAP paged search will not be able to continue.%n%nMaximum number of Result Sets allowed per LDAP connection: %n%1%nCurrent number of Result Sets for this LDAP connection: %n%2%n%nUser Action%nPlease use multiple LDAP Connections to conduct paged searches or increase the limit for Maximum Result Sets per Connection. Please refer to this web page for more inforamtion: http://go.microsoft.com/fwlink/?LinkId=389591 |
Internal event: The LDAP server has reached the limit of the number of page tokens it will cache for a single LDAP connection. Each page token in this cache corresponds to an on going LDAP page search on this connection. The oldest page token will be discarded and the corresponding LDAP paged search will not be able to continue.%n%nMaximum number of Result Sets allowed per LDAP connection: %n%1%nCurrent number of Result Sets for this LDAP connection: %n%2%n%nUser Action%nPlease use multiple LDAP Connections to conduct paged searches or increase the limit for Maximum Result Sets per Connection. Please refer to this web page for more inforamtion: http://go.microsoft.com/fwlink/?LinkId=389591 |
| 0x40000B53 | Internal event: The LDAP server page token cache size has exceeded the maximum limit. Each page token in this cache corresponds to an ongoing LDAP page search. The oldest page token will be discarded and the corresponding LDAP paged search will not be able to continue.%n%nNumber of result sets currently stored: %n%1%nCurrent Result Set Size: %n%2%nMaximum Result Set Size: %n%3%nSize of single Result Set being discarded: %n%4%n%nUser Action%nIncreasing the Maximum Result Set Size will allow LDAP server to expand the page token cache. Please refer to this web page for more inforamtion: http://go.microsoft.com/fwlink/?LinkId=389591 |
Internal event: The LDAP server page token cache size has exceeded the maximum limit. Each page token in this cache corresponds to an ongoing LDAP page search. The oldest page token will be discarded and the corresponding LDAP paged search will not be able to continue.%n%nNumber of result sets currently stored: %n%1%nCurrent Result Set Size: %n%2%nMaximum Result Set Size: %n%3%nSize of single Result Set being discarded: %n%4%n%nUser Action%nIncreasing the Maximum Result Set Size will allow LDAP server to expand the page token cache. Please refer to this web page for more inforamtion: http://go.microsoft.com/fwlink/?LinkId=389591 |
| 0x40000B54 | Et kontinuerlig sidevekslet LDAP-søk har andre søkeargumenter enn den opprinnelige forespørselen om sidevekslede søk.%n%nKlient:%n%1%nStartnode:%n%2%nFilter:%n%3%nSøkeomfang:%n%4%nAttributtutvalg:%n%5%nServerkontroller:%n%6%nKontroll av strengt sidevekslet søkeargument ble deaktivert: %n%7 |
A continued LDAP paged search has different search argument than the initial paged search request.%n%nClient:%n%1%nStarting node:%n%2%nFilter:%n%3%nSearch scope:%n%4%nAttribute selection:%n%5%nServer controls:%n%6%nStrict paged search argument check disabled: %n%7 |
| 0x40000B57 | Active Directory Lightweight Directory Services identifiserte feilaktig følgende objekt på den lokale Active Directory Lightweight Directory Services-forekomsten som et etterlatt objekt. Objektets metadata ble ikke funnet i UpToDateness Vector og måtte kontrolleres manuelt for å bekrefte eksistensen. Resultatet viste atobjektet eksisterte på Active Directory Lightweight Directory Services-kildeforekomsten.%n%nObjekt: %n%1%nObjekt-GUID: %n%2%nKildeforekomst at Active Directory Lightweight Directory Services: %n%3%n%nFjerningen av etterlatte objekter fortsetter, men dette objektet blir ikke slettet. |
Active Directory Lightweight Directory Services incorrectly identified the following object on the local Active Directory Lightweight Directory Services instance as lingering. The objects metadata was not found in the up-to-dateness vector and had to be manually checked for existence. It wasfound to exist on the source Active Directory Lightweight Directory Services instance.%n%nObject: %n%1%nObject GUID: %n%2%nSource Active Directory Lightweight Directory Services instance: %n%3%n%nThe lingering object removal process will continue, this object will not be deleted. |
| 0x40000B5A | Objektet ble gjenopprettet lokalt, og det ble resirkulert på kildeforekomsten av Active Directory Lightweight Directory Services. Det gjenopprettede objektet blir resirkulert.%n%nNavn på resirkulert objekt: %n%1%nObjekt-GUID: %n%2 |
The object was undeleted locally, and recycled on the source Active Directory Lightweight Directory Services instance. The undeleted object is being recycled.%n%nRecycled object name: %n%1%nObject GUID: %n%2 |
| 0x40000B61 | Målforekomsten av Active Directory Lightweight Directory Services som logget denne hendelsen, behandlet en oppdatering av koblingsverdien for kildeobjektet nedenfor. Koblingsverdien refererer til et målobjekt som er i resirkulert tilstand på målforekomsten av Active Directory Lightweight Directory Services.%nDu løser dette problemet ved at målforekomsten av Active Directory Lightweight Directory Services sender en ny forespørsel om en bestilt liste med oppdateringer fra kildeforekomsten av Active Directory Lightweight Directory Services. Hvis denne operasjonen mislykkes, logges hendelsen [Task Category: Replication, EventId: 2914]. Denne hendelsen refererer til samme domenenavn og GUIDer for kilde- og målobjekt som nedenfor.%n%nDomenenavn for kildeobjekt:%n%1%nGUID for kildeobjekt:%n%2%nAttributt:%n%3%nDomenenavn for målobjekt:%n%4%nGUID for målobjekt:%n%5%nKildeforekomst av Active Directory Lightweight Directory Services:%n%6%n |
The destination Active Directory Lightweight Directory Services instance logging this event processed a link value update on the source object below. The link value refers to a target object that is in the recycled state on the destination Active Directory Lightweight Directory Services instance.%nTo correct this condition, the destination Active Directory Lightweight Directory Services instance will re-request a re-ordered list of updates from the source Active Directory Lightweight Directory Services instance. If this corrective step fails, event [Task Category: Replication, EventId: 2914] will be logged, referencing the same source and target object DN's and GUIDS's as below.%n%nSource Object DN:%n%1%nSource Object GUID:%n%2%nAttribute:%n%3%nTarget Object DN:%n%4%nTarget Object GUID:%n%5%nSource Active Directory Lightweight Directory Services instance:%n%6%n |
| 0x40000B66 | Intern hendelse: Katalogtjenesten resirkulerte det utløpte, slettede objektet %1 fra databasen. |
Internal event: The Directory Service recycled the expired, deleted object %1 from the database. |
| 0x40000B67 | Active Directory Lightweight Directory Services registrerer et stort antall objekter under behandling av slettede objekter. Dette er ikke en feil, men kan forsinke fullføringen av datasaneringsoppgaven. |
Active Directory Lightweight Directory Services is encountering a large number of objects while processing deleted-objects. This is not an error condition, but may delay the completion of the garbage collection task. |
| 0x40000B6F | Active Directory Lightweight Directory Services har behandlet alle Påstandstyper.Du finner sammendragsinformasjon nedenfor.%n%nBehandlede Påstandstyper: %1%n%nObs! Påstandstyper behandles under oppstart av Active Directory Lightweight Directory Services og underførste loggføring etter en endring av Påstandstype.%n |
Active Directory Lightweight Directory Services successfully processed all Claim Types.Summary information is below.%n%nClaim Types processed: %1%n%nNOTE: Claim Types are processed during Active Directory Lightweight Directory Services startup and duringthe first log on following any Claim Type changes.%n |
| 0x40000B80 | Alle indeksendringer som er tilknyttet en skjemaendring, utsettes. |
Any index changes that are associated with a schema change are being deferred. |
| 0x40000B82 | En oppkaller hentet passordet til en gruppeadministrert tjenestekonto.%n%nGruppeadministrert tjenestekontoobjekt: %n%1%nOppkaller-SID: %n%2%nOppkaller-IP: %n%3 |
A caller successfully fetched the password of a group managed service account.%n%nGroup Managed Service Account Object: %n%1%nCaller SID: %n%2%nCaller IP: %n%3 |
| 0x40000B87 | Den kjente beholderen for DS-navnet som vises nedenfor, er feilkonfigurert eller mangler. Be administrator om å konfigurere eller opprette beholderen på nytt.%n%nDS-navn: %n%1%nStatus: %n%2 |
The well-known container for the DS name shown below is misconfigured or missing. Please have an administrator reconfigure or recreate the container.%n%nDS Name: %n%1%nStatus: %n%2 |
| 0x40000B88 | Active Directory Lightweight Directory Services prøver å slette registernøkkelen %1 rekursivt (DeleteRoot=%2). |
Active Directory Lightweight Directory Services is attempting to recursively delete the %1 registry key (DeleteRoot=%2). |
| 0x40000B89 | Active Directory Lightweight Directory Services slettet registernøkkelen %1 (DeleteRoot=%2). |
Active Directory Lightweight Directory Services successfully deleted the %1 registry key (DeleteRoot=%2). |
| 0x40000B91 | Oppretter %1 valgfrie systemindekser.%n |
Creating %1 optional system indices.%n |
| 0x40000B92 | Opprettet %1 valgfrie systemindekser. |
Created %1 optional system indices. |
| 0x40000B94 | Følgende objekt ble oppdatert med SPNene nedenfor:%nObjektnavn:%n%1%nSPNer:%n%2%nIntern ID (DSID):%n%3 |
The following object was updated with the following SPNs:%nObject Name:%n%1%nSPNs:%n%2%nInternal ID (DSID):%n%3 |
| 0x40000B99 | Active Directory Lightweight Directory Services leste og tok i bruk en replikeringspolicy.%n%nReplikeringspolicy: %1%nPolicyinnstillinger: %2 |
Active Directory Lightweight Directory Services successfully read and applied a replication policy.%n%nReplication Policy: %1%nPolicy Settings: %2 |
| 0x40000B9A | Active Directory Lightweight Directory Services fant en ugyldig replikeringspolicy.%n%nReplikeringspolicy: %1 |
Active Directory Lightweight Directory Services found an invalid replication policy.%n%nReplication Policy: %1 |
| 0x40000B9B | Replikeringen kunne ikke bruke en replikeringspakke på grunn av et umiddelbart overordnet element, et overordnet element eller et koblingsmål som mangler. Replikeringspolicyen er definert til å bruke det overordnede flagget for resten av replikeringssyklusen.%n%nObjekt: %1 |
Replication failed to apply a replication packet because of a missing parent, ancestor or link target. Replication policy has been defined to use the ancestors flag for the rest of the replication cycle.%n%nObject: %1 |
| 0x40000B9C | En replikering med manglende umiddelbare overordnede elementer er fullført. Ytterligere replikeringssykluser vil ikke fremtvinge henting av overordnede.%n |
A replication cycle with missing parents has completed. Further replication cycles won't force to get ancestors.%n |
| 0x40000B9D | Et objekt ble ikke opprettet fordi objektets umiddelbare overordnede manglet.%n%nObjekt: %1%nDenne operasjonen blir forsøkt på nytt senere. Objektene ordnes på nytt for å øke sjansen for at dette objektet tas med i pakken. |
An object was not created because the object's parent was missing.%n%nObject: %1%nThis operation will be tried again later. Objects will be reordered to increase the chance that this object will be included in the packet. |
| 0x40000B9F | LDAP tar i bruk en ny QOS-policy.Policy-ID for QOS: %1LdapQosPolicyTrigger: %2LdapQosPolicyMaxCpu: %3IsReplicationPolicy: %4%n |
LDAP will apply new QOS policy.QOS Policy ID: %1LdapQosPolicyTrigger: %2LdapQosPolicyMaxCpu: %3IsReplicationPolicy: %4%n |
| 0x40000BA0 | LDAP tar i bruk en oppdatert QOS-policy.Policy-ID for QOS: %1LdapQosPolicyTrigger: %2LdapQosPolicyMaxCpu: %3IsReplicationPolicy: %4%n |
LDAP will apply updated QOS policy.QOS Policy ID: %1LdapQosPolicyTrigger: %2LdapQosPolicyMaxCpu: %3IsReplicationPolicy: %4%n |
| 0x40000BA1 | LDAP bruker ikke lenger en QOS-policy.Policy-ID for QOS: %1IsReplicationPolicy: %4%n |
LDAP will no longer apply QOS policy.QOS Policy ID: %1IsReplicationPolicy: %4%n |
| 0x40000BA4 | Opprettingen av den sammensatte indeksen var vellykket.Primært attributt: %1IndexName: %2%n |
Compound index creation succeeded.Primary Attribute: %1IndexName: %2%n |
| 0x40000BA5 | Sletting av den sammensatte indeksen var vellykket.IndexName: %1%n |
Compound index deletion suceeded.IndexName: %1%n |
| 0x40000BA9 | Endringer i den sammensatte indeksen som er knyttet til en skjemaendring, blir utsatt. |
Any compound index changes that are associated with a schema change are being deferred. |
| 0x40000BAA | Internal event: This directory service applied changes in a packet with the following information.%n%nNaming Context:%n%1%nTotal number of objects:%n%2%nTotal number of links:%n%3%nreturn::%n%4%nExtended return:%n%5%nTime Taken (msec):%n%6 |
Internal event: This directory service applied changes in a packet with the following information.%n%nNaming Context:%n%1%nTotal number of objects:%n%2%nTotal number of links:%n%3%nreturn::%n%4%nExtended return:%n%5%nTime Taken (msec):%n%6 |
| 0x40000BAB | Internal event: This directory service applied object changes in a packet with the following information.%n%nNaming Context:%n%1%nTotal number of threads:%n%2%nTotal number of objects:%n%3%nreturn::%n%4%nMissing parent retries%n%5%nBusy retries%n%6 |
Internal event: This directory service applied object changes in a packet with the following information.%n%nNaming Context:%n%1%nTotal number of threads:%n%2%nTotal number of objects:%n%3%nreturn::%n%4%nMissing parent retries%n%5%nBusy retries%n%6 |
| 0x40000BAC | Internal event: This directory service applied link changes in a packet with the following information.%n%nNaming Context:%n%1%nTotal number of threads:%n%2%nTotal number of links:%n%3%nreturn::%n%4 |
Internal event: This directory service applied link changes in a packet with the following information.%n%nNaming Context:%n%1%nTotal number of threads:%n%2%nTotal number of links:%n%3%nreturn::%n%4 |
| 0x40000BAF | Internal event: A new column was created in link table for the following new attribute.%n%nDatabase column:%n%1%nAttribute identifier:%n%2%nAttribute name:%n%3%nTable type:%n%3 |
Internal event: A new column was created in link table for the following new attribute.%n%nDatabase column:%n%1%nAttribute identifier:%n%2%nAttribute name:%n%3%nTable type:%n%3 |
| 0x40000BB2 | Dirsync-oppretting fullført.IndexName: %1%n |
Dirsync index creation succeeded.IndexName: %1%n |
| 0x40000BB4 | Active Directory Lightweight Directory Services-replikering oppdaget et mangler overordnet objekt for det overordnede objektet i denne mappepartisjonen. Det foreldreløse objektet ble flyttet til LostAndFound-beholderen.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nOverordnet objekt-GUID:%n%3%n%nDenne feilaktige tilstanden inntreffer når et overordnet objekt mangler for det underordnede objektet i innkommende replikering. Som et resultat blir det frittstående underordnede objektet flyttet til LostAndFound-beholderen. |
Active Directory Lightweight Directory Services replication detected a missing parent object for the parent object in this directory partition. The orphaned object was moved to the LostAndFound container.%n%nobject:%n%1%nobject GUID:%n%2%nParent object GUID:%n%3%n%nThis erroneous condition occurs when a parent object is missing for the child object in the inbound replication. As a result, the orphaned child object is moved to the LostAndFound container. |
| 0x40002737 | Internal event: The DirSearch operation was called with the following parameters.%n%nCaller type:%n%1%nCaller provided correlation ID:%n%2%n%nThis information is generally used for event tracing. |
Internal event: The DirSearch operation was called with the following parameters.%n%nCaller type:%n%1%nCaller provided correlation ID:%n%2%n%nThis information is generally used for event tracing. |
| 0x800003F6 | Replikeringstopologien for den lokale katalogtjenesten ble ikke oppdatert i Knowledge Consistency Checker (KCC). Det vil bli gjort et nytt forsøk på å oppdatere replikeringstopologien i KCC med de planlagte intervallene nedenfor.%n%nKCC-oppdateringsintervall:%n%4%n%nOppdateringer forekommer som standard hvert 15. minutt.%n%nBrukerhandling%nHvis dette vedvarer, starter du katalogtjenesten på nytt.%n%nTilleggsdata%nFeilverdi:%n%3 %1%nIntern ID:%n%2 |
The Knowledge Consistency Checker (KCC) failed to update the replication topology for the local directory service. The KCC will attempt to update the replication topology at the following scheduled interval.%n%nKCC update interval:%n%4%n%nBy default, updates occur every 15 minutes.%n%nUser Action%nIf this continues to occur, restart the directory service.%n%nAdditional Data%nError value:%n%3 %1%nInternal ID:%n%2 |
| 0x80000425 | Internal event: The directory replication agent request returned the following status.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: The directory replication agent request returned the following status.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x80000429 | Domenekontrolleren vil ikke lenger replikere katalogpartisjonen nedenfor fra domenekontrolleren på den angitte nettverksadressen. Dette skyldes at det ikke finnes noe tilkoblingsobjekt for innkommende replikering for domenekontrolleren nedenfor.%n%nKatalogpartisjon:%n%1%nDomenekontroller:%n%4%nNettverksadresse:%n%2 |
The domain controller will no longer replicate the following directory partition from the domain controller at the following network address. This is because no Connection object exists for inbound replication for the following domain controller.%n%nDirectory partition:%n%1%nDomain controller:%n%4%nNetwork address:%n%2 |
| 0x80000432 | Internal event: The directory service could not assemble a replication update reply message for another site.%n%nThis operation will be tried again later.%n%nUser Action%nIf this condition continues to occur, restart the directory service.%n%nAdditional Data%nError value:%n%2 %1 |
Internal event: The directory service could not assemble a replication update reply message for another site.%n%nThis operation will be tried again later.%n%nUser Action%nIf this condition continues to occur, restart the directory service.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x80000433 | Internal event: The directory service could not assemble a replication update request message for another site.%n%nThis operation will be tried again later.%n%nUser Action%nIf this condition continues to occur, restart the directory service.%n%nAdditional Data%nError value:%n%2 %1 |
Internal event: The directory service could not assemble a replication update request message for another site.%n%nThis operation will be tried again later.%n%nUser Action%nIf this condition continues to occur, restart the directory service.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x80000437 | Internal event: Active Directory Lightweight Directory Services could not allocate enough memory to process replication tasks. Replication might be affected until more memory is available.%n%nUser Action%nIncrease the amount of physical memory or virtual memory and restart the local computer. |
Internal event: Active Directory Lightweight Directory Services could not allocate enough memory to process replication tasks. Replication might be affected until more memory is available.%n%nUser Action%nIncrease the amount of physical memory or virtual memory and restart the local computer. |
| 0x80000438 | Internal event: Active Directory Lightweight Directory Services could not notify the directory service at the following network address about changes to the directory partition.%n%nDirectory partition:%n%2%nNetwork address:%n%1%n%nAdditional Data%nError value:%n%4 %3 |
Internal event: Active Directory Lightweight Directory Services could not notify the directory service at the following network address about changes to the directory partition.%n%nDirectory partition:%n%2%nNetwork address:%n%1%n%nAdditional Data%nError value:%n%4 %3 |
| 0x80000439 | Internal event: Active Directory Lightweight Directory Services could not send the following directory partition changes to the directory service at the following network address.%n%nDirectory partition:%n%1%nNetwork address:%n%2%n%nAdditional Data%nError value:%n%4 %3 |
Internal event: Active Directory Lightweight Directory Services could not send the following directory partition changes to the directory service at the following network address.%n%nDirectory partition:%n%1%nNetwork address:%n%2%n%nAdditional Data%nError value:%n%4 %3 |
| 0x8000043A | Internal event: Active Directory Lightweight Directory Services could not send a message requesting changes in the following directory partition to the directory service at the following network address.%n%nDirectory partition:%n%1%nNetwork address:%n%2%n%nThis operation will be tried again at next scheduled replication.%n%nAdditional Data%nError value:%n%4 %3 |
Internal event: Active Directory Lightweight Directory Services could not send a message requesting changes in the following directory partition to the directory service at the following network address.%n%nDirectory partition:%n%1%nNetwork address:%n%2%n%nThis operation will be tried again at next scheduled replication.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x8000043B | Kan ikke oppdatere objektet nedenfor i Active Directory Lightweight Directory Services med endringer som er mottatt fra katalogtjenesten på den angitte nettverksadressen fordi Active Directory Lightweight Directory Services var opptatt med informasjonsbehandling.%n%nObjekt:%n%1%nNettverksadresse:%n%2%n%nDenne operasjonen vil bli prøvd på nytt senere. |
Active Directory Lightweight Directory Services could not update the following object with changes received from the directory service at the following network address because Active Directory Lightweight Directory Services was busy processing information.%n%nObject:%n%1%nNetwork address:%n%2%n%nThis operation will be tried again later. |
| 0x8000043D | Internal event: Active Directory Lightweight Directory Services could not synchronize the following directory partition with the directory service at the following network address.%n%nDirectory partition:%n%1%nNetwork address:%n%2%n%nIf this error continues, the Knowledge Consistency Checker (KCC) will reconfigure the replication links and bypass the directory service.%n%nUser Action%nVerify that the network address can be resolved with a DNS query.%n%nAdditional Data%nError value:%n%4 %3 |
Internal event: Active Directory Lightweight Directory Services could not synchronize the following directory partition with the directory service at the following network address.%n%nDirectory partition:%n%1%nNetwork address:%n%2%n%nIf this error continues, the Knowledge Consistency Checker (KCC) will reconfigure the replication links and bypass the directory service.%n%nUser Action%nVerify that the network address can be resolved with a DNS query.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x80000440 | Internal event: The following tombstone lifetime registry value is too low or incompatible with the following garbage collection interval specified in the Active Directory Lightweight Directory Services Configuration object. As a result, the following default registry values for the tombstone lifetime and garbage collection will be used.%n%nCurrent tombstone lifetime (days):%n%1%nCurrent garbage collection interval (hours):%n%2%nDefault tombstone lifetime (days):%n%3%nDefault garbage collection interval (hours):%n%4 |
Internal event: The following tombstone lifetime registry value is too low or incompatible with the following garbage collection interval specified in the Active Directory Lightweight Directory Services Configuration object. As a result, the following default registry values for the tombstone lifetime and garbage collection will be used.%n%nCurrent tombstone lifetime (days):%n%1%nCurrent garbage collection interval (hours):%n%2%nDefault tombstone lifetime (days):%n%3%nDefault garbage collection interval (hours):%n%4 |
| 0x80000443 | Tilkoblingsobjektet nedenfor i den lokale katalogtjenesten er konfigurert for replikering fra seg selv. Resultatet er at tilkoblingsobjektet ikke kunne replikeres i Active Directory Lightweight Directory Services.%n%nTilkoblingsobjekt:%n%1%n%nDette er en ugyldig konfigurasjon, og den vil bli ignorert. |
The following Connection object on the local directory service is configured to replicate from itself. As a result, Active Directory Lightweight Directory Services could not replicate the Connection object.%n%nConnection object:%n%1%n%nThis is an invalid configuration, and it will be ignored. |
| 0x80000444 | Kan ikke oppdatere objektet nedenfor i Active Directory Lightweight Directory Services med attributtendringer fordi de innkommende endringene førte til at objektet overskred den maksimale størrelsen for objektposter. Det ble gjort forsøk på trekke tilbake eller tilbakeføre de mislykkede innkommende attributtendringene i Active Directory Lightweight Directory Services etter tur.%n%nObject:%n%1%nObjekt-GUID:%n%2%n%nAlle kandidater for attributtfjerning er nå forsøkt i Active Directory Lightweight Directory Services fra oppdateringen. Denne oppdateringen var mislykket, og replikering med kildekatalogtjenesten er blokkert til problemet er løst.%n%nReplikering med kildekatalogtjenesten vil bli forsøkt på nytt ved neste planlagte replikering.%n%nBrukerhandling%nUndersøk objektet i den lokale katalogpartisjonen, og kontroller om det er noen attributter med mange verdier. Reduser antallet verdier, eller fjern attributtet. |
Active Directory Lightweight Directory Services could not update the following object with attribute changes because the incoming changes caused the object to exceed the maximum object record size. Active Directory Lightweight Directory Services attempted to back out or reverse the failed incoming attribute changes one at a time.%n%nObject:%n%1%nObject GUID:%n%2%n%nAt this time, Active Directory Lightweight Directory Services has exhausted all candidates for attribute removal from the update. This update has failed and replication with the source directory service is blocked until the problem is corrected.%n%nReplication with the source directory service will be tried again at the next scheduled replication.%n%nUser Action%nExamine the object on the local directory partition and verify if there are any attributes with a large number of values. Reduce the number of values or remove the attribute. |
| 0x80000445 | Kan ikke oppdatere objektet nedenfor i Active Directory Lightweight Directory Services med attributtendringer fordi den innkommende endringen førte til at objektet overskred den maksimale størrelsen for objektposter. Den innkommende endringen av attributtet nedenfor vil bli tilbakeført i et forsøk på å fullføre oppdateringen.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nAttributt:%n%3%n%nDen gjeldende verdien (uten endringer) for attributtet i den lokale katalogpartisjonen vil bli replikert til alle andre katalogtjenester. Dette vil motvirke endringen i resten av katalogtjenestene. Tilbakeføringsverdier kan gjenkjennes som følger:%nVersjon:%n%4%nEndringstidspunkt:%n%5%nOppdateringssekvensnummer:%n%6 |
Active Directory Lightweight Directory Services could not update the following object with attribute changes because the incoming change caused the object to exceed the maximum object record size. The incoming change to the following attribute will be reversed in an attempt to complete the update.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%n%nThe current value (without changes) of the attribute on the local directory partition will replicate to all other directory services. This will counteract the change to the rest of the directory services. The reversal values may be recognized as follows:%nVersion:%n%4%nTime of change:%n%5%nUpdate sequence number:%n%6 |
| 0x80000448 | Internal event: Active Directory Lightweight Directory Services received an incorrectly formatted or corrupted update-replica message during intersite replication.%n%nUser Action%nIf this condition continues, restart this directory service.%n%nAdditional Data%nError value:%n%2 %1 |
Internal event: Active Directory Lightweight Directory Services received an incorrectly formatted or corrupted update-replica message during intersite replication.%n%nUser Action%nIf this condition continues, restart this directory service.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x80000449 | Internal event: Active Directory Lightweight Directory Services received an update-request message for an invalid directory partition from the following directory services during intersite replication.%n%nDirectory partition:%n%1%nDomain controller:%n%2 |
Internal event: Active Directory Lightweight Directory Services received an update-request message for an invalid directory partition from the following directory services during intersite replication.%n%nDirectory partition:%n%1%nDomain controller:%n%2 |
| 0x8000044A | Internal event: Active Directory Lightweight Directory Services received an invalid update-replica message for the following directory partition during intersite replication. The local directory service does not contain this directory partition.%n%nDirectory partition:%n%1%nSource domain controller:%n%2 |
Internal event: Active Directory Lightweight Directory Services received an invalid update-replica message for the following directory partition during intersite replication. The local directory service does not contain this directory partition.%n%nDirectory partition:%n%1%nSource domain controller:%n%2 |
| 0x8000044C | Internal event: Active Directory Lightweight Directory Services received an invalid update-replica message for the following directory partition during intersite replication. The directory service cannot replicate from the following directory service.%n%nDirectory partition:%n%1%nDirectory service:%n%2 |
Internal event: Active Directory Lightweight Directory Services received an invalid update-replica message for the following directory partition during intersite replication. The directory service cannot replicate from the following directory service.%n%nDirectory partition:%n%1%nDirectory service:%n%2 |
| 0x80000451 | Det ble gjort et forsøk på å avslutte endringsvarslene nedenfor i Knowledge Consistency Checker (KCC).%n%nKatalogpartisjon:%n%1%nMåladresse for katalogtjenesteagent:%n%2%nMålrettet unikt navn for katalogtjenesteagent (hvis tilgjengelig):%n%4%n%nDenne advarselen kan forekomme hvis denne katalogtjenesten eller målkatalogtjenesten er flyttet til et annet område.%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
The Knowledge Consistency Checker (KCC) attempted to terminate the following change notifications.%n%nDirectory partition:%n%1%nDestination directory service agent address:%n%2%nDestination directory service agent distinguished name (if available):%n%4%n%nThis warning can occur if either this directory service or the destination directory service has been moved to another site.%n%nAdditional Data%nError value:%n%5 %3 |
| 0x80000459 | Innkommende replikering er deaktivert av brukeren. |
Inbound replication has been disabled by the user. |
| 0x8000045B | Utgående replikering er deaktivert av brukeren. |
Outbound replication has been disabled by the user. |
| 0x8000045D | Alle tilkoblinger for innkommende replikering for partisjonen %1 er deaktivert. Innkommende replikering for denne partisjonen kan ikke utføres. |
All inbound replication connections for the partition %1 are disabled. Inbound replication of this partition cannot be performed. |
| 0x8000046E | Tilkoblingsobjektene nedenfor er konfigurert for samme kilde- og målkatalogtjenester. Resultatet er at ett tilkoblingsobjekt vil bli ignorert.%n%nIgnorert tilkoblingsobjekt:%n%1%nTilkoblingsobjekt:%n%2%n%nBrukerhandling%nSlett ett av disse tilkoblingsobjektene. |
The following Connection objects are configured for the same source and destination directory services. As a result, one Connection object will be ignored.%n%nIgnored Connection object:%n%1%nConnection object:%n%2%n%nUser Action%nDelete one of these Connection objects. |
| 0x8000047A | Internal event: The following structural class is derived from the following class that is defined by multiple inheritance. Multiple inheritance, where both parent classes are structural, is not supported by Active Directory Lightweight Directory Services.%n%nStructural class identifier:%n%1%nStructural class name:%n%2%nClass identifier:%n%3%nClass name:%n%4%n%nThis error was ignored and the inheritance was processed anyway. |
Internal event: The following structural class is derived from the following class that is defined by multiple inheritance. Multiple inheritance, where both parent classes are structural, is not supported by Active Directory Lightweight Directory Services.%n%nStructural class identifier:%n%1%nStructural class name:%n%2%nClass identifier:%n%3%nClass name:%n%4%n%nThis error was ignored and the inheritance was processed anyway. |
| 0x8000047B | Internal event: The following attribute does not contain an attribute identifier.%n%nAttribute:%n%1%n%nThe attribute will be ignored. |
Internal event: The following attribute does not contain an attribute identifier.%n%nAttribute:%n%1%n%nThe attribute will be ignored. |
| 0x8000047C | Internal event: The search for objects in the schema directory partition returned the following unexpected attribute.%n%nAttribute:%n%1%n%nThe attribute will be ignored. |
Internal event: The search for objects in the schema directory partition returned the following unexpected attribute.%n%nAttribute:%n%1%n%nThe attribute will be ignored. |
| 0x8000047D | Internal event: Active Directory Lightweight Directory Services is in the process of creating a new database column for the following new attribute.%n%nAttribute identifier:%n%1%nAttribute name:%n%2 |
Internal event: Active Directory Lightweight Directory Services is in the process of creating a new database column for the following new attribute.%n%nAttribute identifier:%n%1%nAttribute name:%n%2 |
| 0x80000480 | Internal event: The following schema class is part of a class hierarchy that results in an inheritance loop. This class references itself as either a superclass or an auxiliary class.%n%nClass identifier:%n%1%nClass name:%n%2%n%nInheritance was ignored. |
Internal event: The following schema class is part of a class hierarchy that results in an inheritance loop. This class references itself as either a superclass or an auxiliary class.%n%nClass identifier:%n%1%nClass name:%n%2%n%nInheritance was ignored. |
| 0x80000481 | Internal event: The following schema class has a superclass that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nSuperclass identifier:%n%3%n%nInheritance was ignored. |
Internal event: The following schema class has a superclass that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nSuperclass identifier:%n%3%n%nInheritance was ignored. |
| 0x80000482 | Internal event: The following schema class has a relative distinguished name (RDN) attribute identifier that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nRDN attribute identifier:%n%3%n%nThe class definition was ignored. |
Internal event: The following schema class has a relative distinguished name (RDN) attribute identifier that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nRDN attribute identifier:%n%3%n%nThe class definition was ignored. |
| 0x80000483 | Internal event: The following schema class has a mandatory attribute that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nMandatory attribute:%n%3%n%nThe attribute was ignored. |
Internal event: The following schema class has a mandatory attribute that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nMandatory attribute:%n%3%n%nThe attribute was ignored. |
| 0x80000484 | Internal event: The following schema class has an optional attribute that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nOptional attribute:%n%3%n%nThe attribute was ignored. |
Internal event: The following schema class has an optional attribute that is not valid.%n%nClass identifier:%n%1%nClass name:%n%2%nOptional attribute:%n%3%n%nThe attribute was ignored. |
| 0x80000485 | Internal event: Active Directory Lightweight Directory Services is in the process of creating a new index for the following attribute.%n%nAttribute name:%n%2%nAttribute identifier:%n%1 |
Internal event: Active Directory Lightweight Directory Services is in the process of creating a new index for the following attribute.%n%nAttribute name:%n%2%nAttribute identifier:%n%1 |
| 0x8000048B | Internal event: While rebuilding the Address Book hierarchy table, Active Directory Lightweight Directory Services failed to allocate the requested memory for this task.%n%nMemory requested (bytes):%n%1%n%nUser Action%nIncrease the amount of available physical or virtual memory. |
Internal event: While rebuilding the Address Book hierarchy table, Active Directory Lightweight Directory Services failed to allocate the requested memory for this task.%n%nMemory requested (bytes):%n%1%n%nUser Action%nIncrease the amount of available physical or virtual memory. |
| 0x8000048C | Antallet overstyringer overskred den maksimale overstyringsverdien under behandling av overstyringer av hendelseslogging for Active Directory Lightweight Directory Services.%n%nMaksimal overstyringsverdi for hendelseslogging:%n%1%n%nBare overstyringsverdier for hendelseslogging opptil den maksimale overstyringsverdien vil bli behandlet i Active Directory Lightweight Directory Services. |
While processing Active Directory Lightweight Directory Services event logging overrides, the number of overrides located exceeded the maximum override value.%n%nMaximum event logging override value:%n%1%n%nActive Directory Lightweight Directory Services will only process event logging override values up to the maximum override value. |
| 0x80000493 | Internal event: Active Directory Lightweight Directory Services could not shut down successfully and quit with threads still active.%n%nUser Action%nRestart the directory service and confirm that the Active Directory Lightweight Directory Services database recovered successfully. |
Internal event: Active Directory Lightweight Directory Services could not shut down successfully and quit with threads still active.%n%nUser Action%nRestart the directory service and confirm that the Active Directory Lightweight Directory Services database recovered successfully. |
| 0x80000495 | Internal event: Active Directory Lightweight Directory Services has encountered the following exception and associated parameters.%n%nException:%n%1%nParameter:%n%3%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%4 |
Internal event: Active Directory Lightweight Directory Services has encountered the following exception and associated parameters.%n%nException:%n%1%nParameter:%n%3%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%4 |
| 0x8000049A | Internal event: The following language identifier is not valid on this domain controller. The registry key that specifies this language identifier might not be configured properly or the language support for this language identifier is not installed.%n%nLanguage identifier:%n%1%nRegistry key:%n%2%n%nLocalized language indices will not be created for this language identifier. |
Internal event: The following language identifier is not valid on this domain controller. The registry key that specifies this language identifier might not be configured properly or the language support for this language identifier is not installed.%n%nLanguage identifier:%n%1%nRegistry key:%n%2%n%nLocalized language indices will not be created for this language identifier. |
| 0x8000049B | Internal event: The following codepage is not installed on this directory server.%n%nCodepage:%n%1%n%nAs a result, the user could not log on to the local directory server. |
Internal event: The following codepage is not installed on this directory server.%n%nCodepage:%n%1%n%nAs a result, the user could not log on to the local directory server. |
| 0x800004A0 | Kan ikke slette indeksen for attributtet nedenfor i Active Directory Lightweight Directory Services.%n%nAttributtnavn:%n%1%nAttributt-ID:%n%2%n%nDenne indeksen er ikke lenger nødvendig.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
Active Directory Lightweight Directory Services was unable to delete the index for the following attribute.%n%nAttribute name:%n%1%nAttribute ID:%n%2%n%nThis index is no longer needed.%n%nAdditional Data%nError value:%n%3 %4 |
| 0x800004A2 | Den lokale domenekontrolleren mottok en melding for replikering mellom områder som hadde et inkompatibelt meldingsversjonsnummer.%n%nMeldingen vil bli ignorert.%n%nBrukerhandling%nKontroller at domenekontrollerne kjører samme versjon av operativsystemet. |
The local domain controller received an intersite replication message with an incompatible message version number.%n%nThe message will be ignored.%n%nUser Action%nVerify that the domain controllers are running the same version of the operating system. |
| 0x800004A3 | Internal event: The local domain controller received a compressed intersite replication message with an incompatible compression version number.%n%nThis message will be ignored.%n%nUser Action%nVerify that the domain controllers are running the same version of the operating system. |
Internal event: The local domain controller received a compressed intersite replication message with an incompatible compression version number.%n%nThis message will be ignored.%n%nUser Action%nVerify that the domain controllers are running the same version of the operating system. |
| 0x800004A4 | En tråd i Active Directory Lightweight Directory Services venter på at et eksternt prosedyrekall til katalogtjenesten nedenfor skal fullføres.%n%nKatalogtjeneste:%n%1%nOperasjon:%n%3%nTråd-ID:%n%2%nTidsavbruddsperiode (minutter):%n%4%n%nDet er gjort et forsøk på å avbryte kallet og gjenopprette denne tråden i Active Directory Lightweight Directory Services.%n%nBrukerhandling%nHvis dette vedvarer, starter du katalogtjenesten på nytt. |
A thread in Active Directory Lightweight Directory Services is waiting for the completion of a RPC made to the following directory service.%n%nDirectory service:%n%1%nOperation:%n%3%nThread ID:%n%2%nTimeout period (minutes):%n%4%n%nActive Directory Lightweight Directory Services has attempted to cancel the call and recover this thread.%n%nUser Action%nIf this condition continues, restart the directory service. |
| 0x800004B3 | Katalogtjenesten kan ikke replikere objektet nedenfor fra kildekatalogtjenesten på den angitte nettverksadressen på grunn av manglende samsvar for skjemaet i Active Directory Lightweight Directory Services.%n%nObjekt:%n%1%nNettverksadresse:%n%2%n%nDet vil bli gjort et forsøk i Active Directory Lightweight Directory Services på å synkronisere skjemaet før forsøket på å synkronisere katalogpartisjonen nedenfor.%nKatalogpartisjon:%n%3 |
The directory service could not replicate the following object from the source directory service at the following network address because of an Active Directory Lightweight Directory Services schema mismatch.%n%nObject:%n%1%nNetwork address:%n%2%n%nActive Directory Lightweight Directory Services will attempt to synchronize the schema before attempting to synchronize the following directory partition.%nDirectory partition:%n%3 |
| 0x800004BE | Oppgaven for overføring av sikkerhetsbeskrivelse fant en sikkerhetsbeskrivelse med verdien NULL eller som var skadet, i objektet nedenfor, ogbrukte en standard sikkerhetsbeskrivelse.%n%nObjekt:%n%1%n%nResultatet er at sikkerheten for dette objektet i den lokale katalogtjenesten kan være forskjellig fra i andre katalogtjenester.%n%nBrukerhandling%nLegg til den riktige sikkerhetsbeskrivelsen for dette objektet for å sikre at den er enhetlig, slik at den replikeres til andre katalogservere.%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The security descriptor propagation task found a NULL or corrupt security descriptor on the following object andapplied a default security descriptor.%n%nObject:%n%1%n%nAs a result, the security for this object on the local directory service might be different than on other directory services.%n%nUser Action%nTo ensure uniformity, add the correct security descriptor for this object so that it is replicated to other directory servers.%n%nAdditional Data%nError value:%n%2 %3 |
| 0x800004C0 | Internal event: An LDAP client connection was closed because of an error.%n%nClient IP:%n%3%n%nAdditional Data%nError value:%n%1 %4%nInternal ID:%n%2 |
Internal event: An LDAP client connection was closed because of an error.%n%nClient IP:%n%3%n%nAdditional Data%nError value:%n%1 %4%nInternal ID:%n%2 |
| 0x800004C1 | Kan ikke initialisere NTLM-godkjenning i Active Directory Lightweight Directory Services.%n%nResultatet er at NTLM ikke vil bli brukt som metode for sikkerhetsgodkjenning. |
Active Directory Lightweight Directory Services was unable to initialize NTLM authentication.%n%nAs a result, NTLM will not be used as a security authentication method. |
| 0x800004C2 | Kan ikke initialisere SPNEGO-godkjenning (Simple Protected Negotiation) i Active Directory Lightweight Directory Services.%n%nResultatet er at SPNEGO-godkjenningsbindinger mot dette LDAP-grensesnittet ikke vil støttes. |
Active Directory Lightweight Directory Services was unable to initialize Simple Protected Negotiation (SPNEGO) authentication.%n%nAs a result, SPNEGO authentication binds against this LDAP interface will not be supported. |
| 0x800004C3 | Kan ikke initialisere godkjenning av enkel binding i Active Directory Lightweight Directory Services.%n%nResultatet er at godkjenning av enkel binding mot dette LDAP-grensesnittet vil føre til binding som ikke-godkjent bruker. |
Active Directory Lightweight Directory Services was unable to initialize simple bind authentication.%n%nAs a result, simple bind authentication against this LDAP interface will result in binding as an unauthenticated user. |
| 0x800004C4 | LDAP over Secure Sockets Layer (SSL) vil være utilgjengelig nå fordi et sertifikat ikke kunne hentes på serveren.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
LDAP over Secure Sockets Layer (SSL) will be unavailable at this time because the server was unable to obtain a certificate.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x800004C8 | Et forsøk fra den lokale domenekontrolleren på å oppdatere informasjon automatisk på ett eller flere av datamaskinobjektet, innstillingsobjektet eller serverobjektet mislyktes.%n%nDenne operasjonen vil bli forsøkt på nytt med intervallet nedenfor.%n%nIntervall (minutter):%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %4%n%5%nIntern ID:%n%2 |
An attempt by the local domain controller to automatically update information on one or more of the Computer object, the Settings object, or the Server object failed.%n%nThis operation will be tried again at the following interval.%n%nInterval (minutes):%n%1%n%nAdditional Data%nError value:%n%3 %4%n%5%nInternal ID:%n%2 |
| 0x800004D0 | Det ble gjort et forsøk på å utføre et eksternt prosedyrekall (RPC) i Active Directory Lightweight Directory Services til serverennedenfor. Kallet ble tidsavbrutt og ble avbrutt.%n%nServer:%n%2%nTidsavbrudd for kall (min.):%n%3%nTråd-ID:%n%1%n%nTilleggsdata%nIntern ID:%n%4 |
Active Directory Lightweight Directory Services attempted to perform a remote procedure call (RPC) to the followingserver. The call timed out and was cancelled.%n%nServer:%n%2%nCall Timeout (Mins):%n%3%nThread ID:%n%1%n%nAdditional Data%nInternal ID:%n%4 |
| 0x800004F1 | Et forsøk i Knowledge Consistency Checker (KCC) på å legge til en replikeringsavtale for katalogpartisjonen og kildekatalogtjenesten nedenfor mislyktes.%n%nKatalogpartisjon:%n%1%nKildekatalogtjeneste:%n%4%nNettverksadresse:%n%2%nTransport mellom områder (eventuelt):%n%5%n%nDenne operasjonen vil bli forsøkt på nytt ved neste KCC-oppdatering.%n%nTilleggsdata%nFeilverdi:%n%6 %3 |
An attempt by the Knowledge Consistency Checker (KCC) to add a replication agreement for the following directory partition and source directory service failed.%n%nDirectory partition:%n%1%nSource directory service:%n%4%nNetwork address:%n%2%nIntersite transport (if any):%n%5%n%nThis operation will be tried again at the next KCC update.%n%nAdditional Data%nError value:%n%6 %3 |
| 0x8000051B | Knowledge Consistency Checker (KCC) har oppdaget at forsøk på å opprette en replikeringskobling med katalogtjenesten nedenfor konsekvent mislykkes.%n%nForsøk:%n%1%nKatalogtjeneste:%n%2%nTidsperiode (minutter):%n%3%n%nTilkoblingsobjektet for denne katalogtjenesten vil bli ignorert, og en ny midlertidig tilkobling vil bli opprettet for å sikre at replikering fortsetter. Når replikering med denne katalogtjenesten gjenopptas, vil den midlertidige tilkoblingen bli fjernet.%n%nTilleggsdata%nFeilverdi:%n%5 %4 |
The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.%n%nAttempts:%n%1%nDirectory service:%n%2%nPeriod of time (minutes):%n%3%n%nThe Connection object for this directory service will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this directory service resumes, the temporary connection will be removed.%n%nAdditional Data%nError value:%n%5 %4 |
| 0x8000051C | Knowledge Consistency Checker (KCC) har oppdaget at gjentatte forsøk på å replikere med katalogtjenesten nedenfor konsekvent har mislykkes.%n%nForsøk:%n%1%nKatalogtjeneste:%n%2%nTidsperiode (minutter):%n%3%n%nTilkoblingsobjektet for denne katalogtjenesten vil bli ignorert, og en ny midlertidig tilkobling vil bli opprettet for å sikre at replikering fortsetter. Når replikering med denne katalogtjenesten gjenopptas, vil den midlertidige tilkoblingen bli fjernet.%n%nTilleggsdata%nFeilverdi:%n%5 %4 |
The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed.%n%nAttempts:%n%1%nDirectory service:%n%2%nPeriod of time (minutes):%n%3%n%nThe Connection object for this directory service will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this directory service resumes, the temporary connection will be removed.%n%nAdditional Data%nError value:%n%5 %4 |
| 0x8000051E | Kan ikke bruke RPC-protokollsekvensen nedenfor i Active Directory Lightweight Directory Services.%n%nRPC-protokollsekvens:%n%1%n%nSelv om RPC-protokollsekvensen ser ut til å være installert, kan den ikke brukes til kommunikasjon i Active Directory Lightweight Directory Services.%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
Active Directory Lightweight Directory Services could not use the following RPC protocol sequence.%n%nRPC protocol sequence:%n%1%n%nAlthough the RPC protocol sequence appears to be installed, Active Directory Lightweight Directory Services cannot use this protocol sequence for communication.%n%nAdditional Data%nError value:%n%2 %3 |
| 0x80000521 | Den gjeldende registerkonfigurasjonsparameteren er angitt for lavt og vil bli ignorert.%n%nRegisterkonfigurasjonsparameter:%n%1%nGjeldende verdi:%n%2%nLaveste verdi:%n%3%n%nDen laveste verdien vil bli brukt i stedet. |
The current registry configuration parameter is set too low and will be ignored.%n%nRegistry configuration parameter:%n%1%nCurrent value:%n%2%nLowest value:%n%3%n%nThe lowest value will be used instead. |
| 0x80000522 | Den gjeldende registerkonfigurasjonsparameteren er angitt for høyt og vil bli ignorert.%n%nRegisterkonfigurasjonsparameter:%n%1%nGjeldende verdi:%n%2%nHøyeste verdi:%n%3%n%nDen høyeste verdien vil bli brukt i stedet. |
The current registry configuration parameter is set too high and will be ignored.%n%nRegistry configuration parameter:%n%1%nCurrent value:%n%2%nHighest value:%n%3%n%nThe highest value will be used instead. |
| 0x80000558 | Forespørselen fra Intersite Messaging-tjenesten om et LDAP-basissøk mislyktes.%n%nObjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service request for an LDAP base search failed.%n%nObject:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0x80000559 | Forespørselen fra Intersite Messaging-tjenesten bad om et LDAP-søk på ett nivå med start i beholderobjektet nedenfor. Operasjonen mislyktes.%n%nBeholderobjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service requested an LDAP one-level search starting at the following container object. The operation failed.%n%nContainer object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0x8000055B | Et forsøk fra Intersite Messaging-tjenesten på å sende data til en tjeneste på den angitte nettverksadressen via transporten nedenfor mislyktes.%n%nData (byte):%n%1%nTjeneste:%n%2%nNettverksadresse:%n%3%nTransport:%n%4%n%nTilleggsdata%nFeilverdi:%n%6 %5 |
An attempt by the Intersite Messaging service to send data to a service at the following network address through the following transport failed.%n%nData (bytes):%n%1%nService:%n%2%nNetwork address:%n%3%nTransport:%n%4%n%nAdditional Data%nError value:%n%6 %5 |
| 0x80000564 | Oppgaven som overvåker Active Directory Lightweight Directory Services for endringer i objekter for transport mellom områder, mislyktes.%n%nResultatet er at Intersite Messaging-tjenesten ikke vil gjenkjenne tillegg, slettinger og endringer i objekter for transport mellom områder.%n%nBrukerhandling%nStart Intersite Messaging-tjenesten på nytt, eller start den lokale domenekontrolleren på nytt.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The task that monitors Active Directory Lightweight Directory Services for changes to intersite transport objects failed.%n%nAs a result, the Intersite Messaging service will not recognize additions, deletions, and modifications of intersite transport objects.%n%nUser Action%nRestart the Intersite Messaging service or restart the local domain controller.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x80000581 | Intersite Messaging-tjenesten kan ikke sende en SMTP-melding fordi SMTP-tjenesten ikke er installert.%n%nDet vil bli gjort et nytt forsøk på å sende meldingen senere.%n%nBrukerhandling%nInstaller SMTP-tjenesten. |
The Intersite Messaging service could not send a SMTP message because the SMTP service is not installed.%n%nAn attempt to send the message will be tried again later.%n%nUser Action%nInstall the SMTP service. |
| 0x80000591 | Under installasjonen av denne replikaen kunne ikke katalogtjenestenfremtvinge en replikeringssyklus med RID FSMO-datamaskinen %1. Hvis RID FSMO harvært utilgjengelig over tid, kan det hende denne replikaen ikke kan opprettesikkerhetskontohavere umiddelbart. Dette kan løses ved å oppdatere katalogtjenesten manueltpå RID FSMO-datamaskinen. |
During the installation of this replica, the Directory Service was unable toforce a replication cycle with the RID FSMO computer %1. If the RID FSMO hasbeen unavailable for some time, this replica may not be able to create securityprincipals immediately. This can be remedied by manually bringing the Directory Serviceon the RID FSMO computer up to date. |
| 0x8000059B | Det oppstod en uventet feil i Knowledge Consistency Checker (KCC) under utføring av en Active Directory Lightweight Directory Services-operasjon.%n%nOperasjonstype:%n%1%nUnikt navn for objekt:%n%2%n%nOperasjonen vil bli forsøkt på nytt ved neste KCC-intervall.%n%nTilleggsdata%nFeilverdi:%n%3 %5%nIntern ID:%n%4 |
The Knowledge Consistency Checker (KCC) encountered an unexpected error while performing an Active Directory Lightweight Directory Services operation.%n%nOperation type:%n%1%nObject distinguished name:%n%2%n%nThe operation will be retried at the next KCC interval.%n%nAdditional Data%nError value:%n%3 %5%nInternal ID:%n%4 |
| 0x8000059C | Intersite Messaging-tjenesten kan ikke behandle objektet nedenfor.%n%nObjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service could not process the following object.%n%nObject:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0x8000059D | Active Directory Lightweight Directory Services mangler viktig informasjon etter installasjonen og kan ikke fortsette. Hvis dette er en replikaforekomst av Active Directory Lightweight Directory Services, kobler du denne serveren til partisjonen på nytt. |
Active Directory Lightweight Directory Services is missing critical information after installation and cannot continue. If this is a replica Active Directory Lightweight Directory Services instance, rejoin this server to the partition. |
| 0x8000059E | Navnet %1 er allerede brukt for et standard Active Directory Lightweight Directory Services-objekt. Angi et annet navn for dette objektet. |
The name %1 is already used for a default Active Directory Lightweight Directory Services object. Specify another name for this object. |
| 0x8000059F | Kan ikke legge til en replika av katalogpartisjonen nedenfor i Knowledge Consistency Checker (KCC) ved hjelp av den angitte transporten fordi det transportspesifikke adresseattributtet mangler i kildekatalogtjenesten eller den lokale katalogtjenesten.%n%nKatalogpartisjon:%n%1%nKildekatalogtjeneste:%n%2%nTransport:%n%3 |
The Knowledge Consistency Checker (KCC) could not add a replica of the following directory partition using the following transport because the transport-specific address attribute is missing on either the source directory service or the local directory service.%n%nDirectory partition:%n%1%nSource directory service:%n%2%nTransport:%n%3 |
| 0x800005B7 | Noen indekser som kanskje er skadet, ble funnet og slettet som en del av initialiseringen i Active Directory Lightweight Directory Services.%n%nDisse slettede indeksene vil bli bygd på nytt. |
Active Directory Lightweight Directory Services has detected and deleted some possibly corrupted indices as part of initialization.%n%nThese deleted indices will be rebuilt. |
| 0x800005B9 | Oppgaven som overvåker Active Directory Lightweight Directory Services for endringer i områdetopologien, mislyktes for det angitte objektet for transport mellom områder.%n%nObjekt for transport mellom områder:%n%1%n%nTillegg, slettinger og endringer av objekter for transport mellom områder vil ikke bli gjenkjent i Intersite Messaging-tjenesten før denne tjenesten er stoppet og startet på nytt.%n%nBrukerhandling%nStart Intersite Messaging-tjenesten eller denne domenekontrolleren på nytt.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The task that monitors Active Directory Lightweight Directory Services for changes in site topology failed for the following intersite transport object.%n%nIntersite transport object:%n%1%n%nAdditions, deletions, and modifications of intersite transport objects will not be recognized by the Intersite Messaging service until this service is stopped and then restarted.%n%nUser Action%nRestart the Intersite Messaging service or this domain controller.%n%nAdditional Data%nError value:%n%3 %2 |
| 0x800005BF | Intersite Messaging-tjenesten som bruker SMTP-transporten, kan ikke konfigurere en mappe for levering av e-post for den lokale domenekontrolleren.%n%nBrukerhandling%nKontroller at mappen som inneholder loggfilene for Active Directory Lightweight Directory Services, er tilgjengelig.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The Intersite Messaging service using the SMTP transport could not configure a mail drop folder for the local domain controller.%n%nUser Action%nVerify that the folder containing the Active Directory Lightweight Directory Services log files is accessible.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x800005C1 | Intersite Messaging-tjenesten kan ikke lese objektene for transport mellom områder fra Active Directory Lightweight Directory Services.%n%nResultatet er at Intersite Messaging-tjenesten er stoppet. Knowledge Consistency Checker (KCC) kan ikke beregne topologi mellom områder uten denne tjenesten.%n%nBrukerhandling%nKontroller at LDAP-spørringene fungerer som de skal på denne maskinen.%n%nStart Intersite Messaging-tjenesten på nytt for å fortsette kommunikasjonen mellom områder.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The Intersite Messaging service could not read the intersite transport objects from Active Directory Lightweight Directory Services.%n%nAs a result, the Intersite Messaging service has stopped. The Knowledge Consistency Checker (KCC) will be unable to calculate intersite topology without this service.%n%nUser Action%nVerify that LDAP queries function properly on this machine.%n%nRestart the Intersite Messaging service to continue intersite communication.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x800005C2 | Internal event: A viable bridgehead server could not be found to transport data to the following site for the following directory partition.%n%nSite:%n%1%nDirectory partition:%n%3%nTransport method:%n%2%n%nIf preferred bridgehead servers have been specified, then only those directory servers will be considered viable; otherwise, all directory servers in the site will be considered viable.%n%nTo set a viable preferred bridgehead server, the following requirements must be met.%n%n- The transport object must be configured for that directory server by verifying the transport-specific address attribute.%n%n- The directory partition must be instantiated on the directory server, and it must be writeable when constructing a normal topology. If constructing a global catalog topology, the directory partition can be either read-only or writeable. |
Internal event: A viable bridgehead server could not be found to transport data to the following site for the following directory partition.%n%nSite:%n%1%nDirectory partition:%n%3%nTransport method:%n%2%n%nIf preferred bridgehead servers have been specified, then only those directory servers will be considered viable; otherwise, all directory servers in the site will be considered viable.%n%nTo set a viable preferred bridgehead server, the following requirements must be met.%n%n- The transport object must be configured for that directory server by verifying the transport-specific address attribute.%n%n- The directory partition must be instantiated on the directory server, and it must be writeable when constructing a normal topology. If constructing a global catalog topology, the directory partition can be either read-only or writeable. |
| 0x800005C3 | Internal event: The attempt to delete outdated Active Directory Lightweight Directory Services performance counters failed.%n%nThis operation will be tried again later.%n%nAdditional Data%nFailed operation:%n%3%nError value:%n%2 %1 |
Internal event: The attempt to delete outdated Active Directory Lightweight Directory Services performance counters failed.%n%nThis operation will be tried again later.%n%nAdditional Data%nFailed operation:%n%3%nError value:%n%2 %1 |
| 0x800005C4 | Forsøket på å registrere ytelsestellerne for Active Directory Lightweight Directory Services mislyktes.%n%nDenne operasjonen vil bli forsøkt på nytt med intervallet nedenfor.%n%nIntervall (minutter):%n%2%n%nTilleggsdata%nMislykket operasjon:%n%4%nFeilverdi:%n%3 %1 |
The attempt to register the Active Directory Lightweight Directory Services performance counters failed.%n%nThis operation will be tried again at the following interval.%n%nInterval (minutes):%n%2%n%nAdditional Data%nFailed operation:%n%4%nError value:%n%3 %1 |
| 0x800005F0 | Internal event: Active Directory Lightweight Directory Services could not remove the following deleted object that has expired from the Active Directory Lightweight Directory Services database.%n%nObject:%n%1%n%nUser Action%nIf this error continues to occur, perform a semantic analysis check on the database.%n%nAdditional Data%nError value:%n%2 %4%nInternal ID:%n%3 |
Internal event: Active Directory Lightweight Directory Services could not remove the following deleted object that has expired from the Active Directory Lightweight Directory Services database.%n%nObject:%n%1%n%nUser Action%nIf this error continues to occur, perform a semantic analysis check on the database.%n%nAdditional Data%nError value:%n%2 %4%nInternal ID:%n%3 |
| 0x800005F1 | Internal event: An index needed by the MAPI address book for the following language was not created.%n%nLanguage:%n%1%n%nThis language will not be supported through the MAPI interface. |
Internal event: An index needed by the MAPI address book for the following language was not created.%n%nLanguage:%n%1%n%nThis language will not be supported through the MAPI interface. |
| 0x800005F9 | Internal event: During intersite replication, the local domain controller received a message with an unrecognized message type.%n%nMessage type:%n%1%n%nAs a result, this message will be ignored. |
Internal event: During intersite replication, the local domain controller received a message with an unrecognized message type.%n%nMessage type:%n%1%n%nAs a result, this message will be ignored. |
| 0x800005FB | Internal event: During intersite replication, the local domain controller encountered an error while receiving a message from the Intersite Messaging service.%n%nThis operation will be tried again at the following interval.%n%nInterval (minutes):%n%2%n%nAdditional Data%nError value:%n%3 %1 |
Internal event: During intersite replication, the local domain controller encountered an error while receiving a message from the Intersite Messaging service.%n%nThis operation will be tried again at the following interval.%n%nInterval (minutes):%n%2%n%nAdditional Data%nError value:%n%3 %1 |
| 0x800005FC | Internal event; During intersite replication, the local domain controller encountered an error while sending a message using the Intersite Messaging service.%n%nDestination domain controller:%n%2%nTransport:%n%3%nMessage description:%n%4%n%nThe operation will be tried again at the next replication interval according to the schedule on the Connection object.%n%nAdditional Data%nError value:%n%5 %1 |
Internal event; During intersite replication, the local domain controller encountered an error while sending a message using the Intersite Messaging service.%n%nDestination domain controller:%n%2%nTransport:%n%3%nMessage description:%n%4%n%nThe operation will be tried again at the next replication interval according to the schedule on the Connection object.%n%nAdditional Data%nError value:%n%5 %1 |
| 0x800005FE | Den lokale domenekontrolleren er overvåkeren av domenenavngiving, men den er ikke en global katalog. Overvåkeren av domenenavngiving må være en global katalog.%n%nBrukerhandling%nKonfigurer denne katalogserveren som en global katalog, eller overfør rollen som driftsovervåker for navngiving til en katalogserver som er en global katalog. |
The local domain controller is the domain naming master; however, it is not a global catalog. The domain naming master must be a global catalog.%n%nUser Action%nConfigure this directory server as a global catalog, or transfer the naming operations master role to a directory server that is a global catalog. |
| 0x80000602 | Det ble gjort et forsøk på å gjenopprette Active Directory Lightweight Directory Services fra sikkerhetskopieringsmediet fordi det oppstod en feil under generering av en ny database-GUID for Active Directory Lightweight Directory Services.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
An attempt to restore Active Directory Lightweight Directory Services from backup media failed because an error was encountered while generating a new Active Directory Lightweight Directory Services database GUID.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x80000603 | Active Directory Lightweight Directory Services kan ikke deaktivere den programvarebaserte hurtigbufferen for diskskriving på harddisken nedenfor.%n%nHarddisk:%n%1%n%nData kan gå tapt under systemfeil. |
Active Directory Lightweight Directory Services could not disable the software-based disk write cache on the following hard disk.%n%nHard disk:%n%1%n%nData might be lost during system failures. |
| 0x80000609 | Internal event: An Active Directory Lightweight Directory Services schema mismatch was encountered while replicating the directory partition from the following directory service.%n%nDirectory partition:%n%1%nDirectory Service:%n%2%n%nAs a result, a schema update will be performed. An attempt to replicate the directory partition will be tried again after the schema update. |
Internal event: An Active Directory Lightweight Directory Services schema mismatch was encountered while replicating the directory partition from the following directory service.%n%nDirectory partition:%n%1%nDirectory Service:%n%2%n%nAs a result, a schema update will be performed. An attempt to replicate the directory partition will be tried again after the schema update. |
| 0x80000612 | Internal event: This directory service is not making progress performing an initial synchronization of the following directory partition.%n%nDirectory partition:%n%1%n%nAn attempt to perform an initial synchronization will be tried again later. |
Internal event: This directory service is not making progress performing an initial synchronization of the following directory partition.%n%nDirectory partition:%n%1%n%nAn attempt to perform an initial synchronization will be tried again later. |
| 0x8000061D | Kunne ikke fullføre synkronisering av alle katalogpartisjonene på den lokale domenekontrolleren før den ble en global katalog. Registernøkkelen er angitt for overstyring av dette kravet, og den maksimale tidsgrensen som tillates av administratoren, er nådd.%n%nRegisternøkkel:%nHKLM\\System\\CurrentControlSet\\Services\\NTDS\\Parameters%nRegisterverdi (sekunder):%nAnnonsering av forsinkelse for global katalog%nMaksimal tidsgrense (minutter og sekunder):%n%1 %2%n%nResultatet er at kanskje ikke alle nødvendige katalogpartisjoner er lagt til på denne domenekontrolleren. |
The local domain controller could not complete full synchronization of all its directory partitions prior to becoming a global catalog. The following registry key has been set to override this requirement, and the maximum time limit allowed by the administrator has been reached.%n%nRegistry Key:%nHKLM\\System\\CurrentControlSet\\Services\\NTDS\\Parameters%nRegistry value (seconds):%nGlobal Catalog Delay Advertisement%nMaximum time limit (minutes and seconds):%n%1 %2%n%nAs a result, this domain controller might not have added all the necessary directory partitions. |
| 0x8000061E | Alle katalogservere på området nedenfor som kan replikere katalogpartisjonen via denne transporten, er for øyeblikket utilgjengelige.%n%nOmråde:%n%1%nKatalogpartisjon:%n%3%nTransport:%n%2 |
All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.%n%nSite:%n%1%nDirectory partition:%n%3%nTransport:%n%2 |
| 0x80000626 | Internal event: Inbound replication was delayed for the following time period due to contention of resources with the security descriptor propagation task.%n%nTime period (minutes and seconds):%n%1 %2%n%nThis condition might be transient. An attempt to replicate will be tried again later. |
Internal event: Inbound replication was delayed for the following time period due to contention of resources with the security descriptor propagation task.%n%nTime period (minutes and seconds):%n%1 %2%n%nThis condition might be transient. An attempt to replicate will be tried again later. |
| 0x8000062B | Replikeringen i Active Directory Lightweight Directory Services ble forsinket i tidsperioden nedenfor på grunn av en konflikt med sertifikattjenester for ressurser.%n%nMinutter og sekunder:%n%1 %2%n%nResultatet er at klargjøring av en asynkron replikeringsmelding for overføring tok lengre tid enn forventet. Dette problemet er antakelig forbigående. |
Due to contention with Certificate Services for resources, Active Directory Lightweight Directory Services replication was delayed for the following period of time.%n%nMinutes and seconds:%n%1 %2%n%nAs a result, preparation of an asynchronous replication message for transmission took longer than expected. This condition is probably transient. |
| 0x8000062D | Internal event: Active Directory Lightweight Directory Services could not resolve the following DNS host name to an IP address.%n%nDNS host name:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
Internal event: Active Directory Lightweight Directory Services could not resolve the following DNS host name to an IP address.%n%nDNS host name:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0x8000062F | Denne Active Directory Lightweight Directory Services-forekomsten er den siste AD LDS-forekomsten i domenet. |
This Active Directory Lightweight Directory Services instance is the last AD LDS instance in the domain. |
| 0x80000630 | Denne Active Directory Lightweight Directory Services-forekomsten er ikke den siste AD LDS-forekomsten i domenet. |
This Active Directory Lightweight Directory Services instance is not the last AD LDS instance in the domain. |
| 0x80000632 | Kontrollpunktet for replikering for Windows NT 4.0 eller tidligere i PDC-emulatorovervåkeren var mislykket.%n%nEn fullstendig synkronisering av SAM-database (Security Accounts Manager) til domenekontrollere som kjører Windows NT 4.0 og tidligere, kan finne sted hvis rollen som PDC-emulatorovervåker overføres til den lokale domenekontrolleren før neste vellykkede kontrollpunkt.%n%nKontrollpunktprosessen vil bli forsøkt på nytt om fire timer.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was unsuccessful.%n%nA full synchronization of the security accounts manager (SAM) database to domain controllers running Windows NT 4.0 and earlier might take place if the PDC emulator master role is transferred to the local domain controller before the next successful checkpoint.%n%nThe checkpoint process will be tried again in four hours.%n%nAdditional Data%nError value:%n%2 %1 |
| 0x80000634 | Det slettede objektet nedenfor har ikke den riktige verdien for det angitte attributtet.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nAttributt:%n%3%n%nDet blir vanligvis gjort et forsøk på å opprettholde attributtverdiene for slettede objekter, selv når innkommende endringer er nyere. I dette tilfellet var imidlertid ikke attributtverdien for det slettede objektet en riktig verdi. Resultatet er at den innkommende attributtendringen ble brukt. |
The following deleted object does not have the proper value for the following attribute.%n%nObject:%n%1%nObject GUID:%n%2%nAttribute:%n%3%n%nAn attempt is usually made to preserve the attribute values of deleted objects, even when incoming changes are more recent. However, in this case, the attribute value of the deleted object was not a proper value. As a result, the incoming attribute change was applied. |
| 0x8000066F | Active Directory Lightweight Directory Services kunne ikke skrive skjemaversjonsinformasjon på skjemakatalogpartisjonen under innkommende replikering eller under en overføring av skjemaovervåkerrollen.%n%nBrukerhandling%nHvis et manglende samsvar for skjema vedvarer under replikeringsforsøk, synkroniserer du skjemakatalogpartisjonen på nytt for å fremtvinge en oppdatering av skjemaversjonsinformasjonen.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services failed to write schema version information on the schema directory partition during inbound replication or during a schema master role transfer.%n%nUser Action%nIf a schema mismatch continues to occur during replication attempts, synchronize the schema directory partition again to force an update of the schema version information.%n%nAdditional Data%nError value:%n%1 %2 |
| 0x80000676 | Internal event: The Intersite Messaging service requested an LDAP search in the following container. The search failed with the following result.%n%nContainer object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
Internal event: The Intersite Messaging service requested an LDAP search in the following container. The search failed with the following result.%n%nContainer object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0x80000677 | Det ble gjort et forsøk i Active Directory Lightweight Directory Services på å kommunisere med den globale katalogen nedenfor, og forsøkene var mislykkede.%n%nGlobal katalog:%n%1%n%nOperasjonen som pågår, kan kanskje ikke fortsette. Domenekontrollerlokatoren vil bli brukt i Active Directory Lightweight Directory Services for å prøve å finne en tilgjengelig global katalogserver.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
Active Directory Lightweight Directory Services attempted to communicate with the following global catalog and the attempts were unsuccessful.%n%nGlobal catalog:%n%1%n%nThe operation in progress might be unable to continue. Active Directory Lightweight Directory Services will use the domain controller locator to try to find an available global catalog server.%n%nAdditional Data%nError value:%n%3 %2 |
| 0x80000679 | Intersite Messaging-tjenesten bad om en ADSI-operasjon for henting av objekt for navneområdeobjektet nedenfor, og operasjonen mislyktes.%n%nNavneområdeobjekt:%n%1%n%nBrukerhandling%n- Kontroller at tjenesten som er knyttet til navneområdeobjektet, er installert og kjører. Hvis navneområdet for eksempel er Internet Information Service (IIS), kontrollerer du at IIS-tjenesten kjører.%n%n- Kontroller at DLL-komponenten som er knyttet til navneområdeobjektet, ikke mangler eller er skadet.%n%nHvis dette problemet vedvarer, bør du kanskje installere Windows-komponenten som inneholder tjenesten, på nytt.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service requested an ADSI Get Object operation for the following namespace object and the operation failed.%n%nNamespace object:%n%1%n%nUser Action%n- Verify that the service associated with the namespace object is installed and running. For example, if the namespace is Internet Information Service (IIS), verify that the IIS service is running.%n%n- Verify that the DLL component associated with the namespace object is not missing or corrupt.%n%nIf this problem continues, you might want to reinstall the Windows component that contains the service.%n%nAdditional Data%nError value:%n%3 %2 |
| 0x8000067F | Hurtigbufferen for konfigurasjon ble ikke initialisert i Knowledge Consistency Checker (KCC).%n%nDenne operasjonen vil bli forsøkt på nytt senere.%n%nBrukerhandling%nHvis dette forholdet vedvarer, starter du katalogtjenesten på nytt.%n%nTilleggsdata%nIntern ID:%n%1 |
The Knowledge Consistency Checker (KCC) did not initialize its configuration cache.%n%nThis operation will be tried again later.%n%nUser Action%nIf this condition continues, restart the directory service.%n%nAdditional Data%nInternal ID:%n%1 |
| 0x80000683 | Oppgaven for oppdatering av hurtigbufferen for gruppemedlemskap oppdaget at området nedenfor som inneholdt en global katalog, ikke er et av de billigste områdene, som angitt av den publiserte koblingsinformasjonen for området.%n%nOmråde:%n%1%n%nDenne hendelsesloggmeldingen kan skyldes midlertidige nettverksbrudd.%n%nBrukerhandling%nHvis dette forholdet vedvarer, kontrollerer du replikeringsplanene og nøyaktigheten for områdekoblinger. |
The group membership cache refresh task detected that the following site in which a global catalog was found is not one of the cheapest sites, as indicated by the published site link information.%n%nSite:%n%1%n%nThis event log message could be caused by temporary network outages.%n%nUser Action%nIf this condition continues, verify replication schedules and accuracy of site links. |
| 0x80000684 | Oppgaven for oppdatering av hurtigbufferen for gruppemedlemskap fant ingen global katalog på det foretrukne området, men fant en global katalog på det tilgjengelige området nedenfor.%n%nForetrukket område:%n%1%nTilgjengelig område:%n%2%n%nDenne hendelsesloggmeldingen kan skyldes midlertidige nettverksbrudd.%n%nBrukerhandling%nHvis dette forholdet vedvarer, kontrollerer du at planleggingsinformasjonen er riktig, eller vurderer å konfigurere det foretrukne området for global katalog på nytt. |
The group membership cache refresh task did not locate a global catalog in the preferred site, but was able to find a global catalog in the following available site.%n%nPreferred site:%n%1%nAvailable site:%n%2%n%nThis event log message could be caused by temporary network outages.%n%nUser Action%nIf this condition continues, verify that the scheduling information is correct or consider reconfiguring the preferred global catalog site. |
| 0x80000685 | Oppgaven for oppdatering av hurtigbufferen for gruppemedlemskap har nådd det maksimale antallet brukere for den lokale domenekontrolleren.%n%nMaksimalt antall brukere:%n%1%n%nBrukerhandling%nVurder å øke den maksimale grensen ved å endre følgende registerverdi:%n%nHKLM\\System\\CurrentControlSet\\Services\\NTDS\\Parameters\\ |
The group membership cache refresh task has reached the maximum number of users for the local domain controller.%n%nMaximum number of users:%n%1%n%nUser Action%nConsider increasing the maximum limit by changing the following registry value:%n%nHKLM\\System\\CurrentControlSet\\Services\\NTDS\\Parameters\\ |
| 0x80000686 | Oppgaven for oppdatering av hurtigbufferen for gruppemedlemskap ligger bak tidsplanen.%n%nBrukerhandling%nVurder fremtvinging av oppdatering av hurtigbufferen for gruppemedlemskap. |
The group membership cache refresh task is behind schedule.%n%nUser Action%nConsider forcing a group membership cache update. |
| 0x80000687 | Oppgaven for oppdatering av hurtigbufferen for gruppemedlemskap fant ikke neste tilgjengelige tidsluke for tilkobling til området nedenfor.%n%nOmråde:%n%1%n%nDenne operasjonen vil bli forsøkt på nytt med intervallet nedenfor.%n%nIntervall (timer):%n%2 |
The group membership cache refresh task was unable to find the next available time slot of connectivity to the following site.%n%nSite:%n%1%n%nThis operation will be tried again at the following interval.%n%nInterval (hours):%n%2 |
| 0x80000688 | Oppgaven for hurtigbuffer for gruppemedlemskap kan ikke hente en tilkoblingsplan til det foretrukne området nedenfor.%n%nForetrukket område:%n%1%n%nBrukerhandling%nBruk Active Directory-områder og -tjenester til å kontrollere innstillingene for områdetilkobling. |
The group membership cache task was unable to obtain a connection schedule to the following preferred site.%n%nPreferred site:%n%1%n%nUser Action%nUse Active Directory Sites and Services to check the site connectivity settings. |
| 0x800006A2 | Internal event: Active Directory Lightweight Directory Services encountered an error while attempting to remove the following expired, deleted attribute value from the following object.%n%nObject:%n%2%nAttribute value:%n%1%n%nAdditional Data%nError value:%n%3 %5%nInternal ID:%n%4 |
Internal event: Active Directory Lightweight Directory Services encountered an error while attempting to remove the following expired, deleted attribute value from the following object.%n%nObject:%n%2%nAttribute value:%n%1%n%nAdditional Data%nError value:%n%3 %5%nInternal ID:%n%4 |
| 0x800006AE | Den globale katalogen fant ingen kildedomenekontroller for replikering av det delvise attributtsettet for katalogpartisjonen nedenfor.%n%nKatalogpartisjon:%n%1%n%nDenne operasjonen vil bli forsøkt på nytt ved neste planlagte replikering. Dette er en spesiell replikeringssyklus som skyldes at ett eller flere attributter er lagt til i det delvise attributtsettet.%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The global catalog failed to locate any source domain controller to replicate the partial attribute set for the following directory partition.%n%nDirectory partition:%n%1%n%nThis operation will be tried again at the next scheduled replication. This is a special replication cycle due to the addition of one or more attributes to the partial attribute set.%n%nAdditional Data%nError value:%n%2 %3 |
| 0x800006B3 | Oppgaven som oppdaterer koblingsverdier, sluttet med en feil.%n%nDenne operasjonen vil bli forsøkt på nytt senere.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du denne katalogtjenesten på nytt.%n%nTilleggsdata%nFeilverdi:%n%3 %1%nIntern ID:%n%2 |
The task that updates link values ended with an error.%n%nThis operation will be tried again later.%n%nUser Action%nIf this event continues to occur, restart this directory service.%n%nAdditional Data%nError value:%n%3 %1%nInternal ID:%n%2 |
| 0x800006BB | Kan ikke oppdatere funksjonsnivået for konfigurasjonssettet i Active Directory Lightweight Directory Services fordi Active Directory Lightweight Directory Services-forekomsten nedenfor er på et lavere funksjonsnivå enn det forespurte nye funksjonsnivået for konfigurasjonssettet.%n%nObjekt:%n%1%nNTDS-innstillingsobjektet for Active Directory Lightweight Directory Services-forekomsten:%n%2 |
Active Directory Lightweight Directory Services failed to update the functional level of the configuration set because the following Active Directory Lightweight Directory Services instance is at a lower functional level than the requested new functional level of the configuration set.%n%nObject:%n%1%nNTDS Settings object of Active Directory Lightweight Directory Services instance:%n%2 |
| 0x800006BC | Kan ikke oppdatere funksjonsnivået for partisjonen nedenfor i Active Directory Lightweight Directory Services fordi partisjonen er i blandet modus.%n%n partisjon:%n%1%n%nBrukerhandling%nEndre partisjonen til enhetlig modus, og prøv operasjonen på nytt. |
Active Directory Lightweight Directory Services could not update the functional level of the following partition because the partition is in mixed mode.%n%n partition:%n%1%n%nUser Action%nChange the partition to native mode and try the operation again. |
| 0x800006BD | Forespørselen om å legge til et nytt NTDS-innstillingsobjekt ble avslått fordi det høyeste funksjonsnivået som støttes i operativsystemet, var lavere enn funksjonsnivået for konfigurasjonssettet.%n%nHøyeste funksjonsnivå i operativsystemet:%n%1%n funksjonsnivå for konfigurasjonssett:%n%2%n%nBrukerhandling%nInstaller det riktige operativsystemet. |
The request to add a new NTDS Settings object was denied because the highest functional level supported by the operating system was lower than the functional level of the configuration set.%n%nHighest functional level of the operating system:%n%1%n configuration set functional level:%n%2%n%nUser Action%nInstall the correct operating system. |
| 0x800006D1 | Den lokale domenekontrolleren er ikke lenger en global katalog, og forsøket på å fjerne den delvise, skrivebeskyttede replikakatalogpartisjonen for domenet nedenfor fra denne domenekontrolleren mislyktes.%n%nDomene:%n%1%n%nDenne operasjonen vil bli forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The local domain controller is no longer a global catalog and the attempt to remove the partial, read-only replica directory partition of the following domain from this domain controller failed.%n%nDomain:%n%1%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x800006D3 | Domenet nedenfor er fjernet fra skogen, og forsøket på å fjerne objektene fra den globale katalogen mislyktes.%n%nDomene:%n%1%n%nDenne operasjonen vil bli forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The following domain has been removed from the forest and the attempt to remove the objects from the global catalog failed.%n%nDomain:%n%1%n%nThis operation will be tried again later.%n%nAdditional Data%nError value:%n%4 %3 |
| 0x800006D4 | Den lokale katalogserveren er ikke lenger konfigurert som vert for programkatalogpartisjonen nedenfor. Et forsøk på å overføre de tilhørende oppdateringene og eventuelle driftsovervåkerroller til en annen katalogserver mislyktes fordi ingen annen katalogserver er konfigurert som vert for en replika av denne programkatalogpartisjonen.%n%nProgramkatalogpartisjon:%n%1%n%nDenne operasjonen vil bli forsøkt på nytt senere.%n%nBrukerhandling%nBruk kommandolinjeverktøyet dsmgmt til å gjøre ett av følgende:%n%n- Hvis du vil fjerne partisjonen for godt, bruker du alternativet Slett NC til å slette crossRef-objektet for denne katalogpartisjonen.%n- Hvis du vil beholde partisjonen på denne katalogserveren, bruker du alternativet Legg til NC-replika til å konfigurere denne katalogserveren på nytt som vert for denne katalogpartisjonen.%n- Hvis du vil flytte replikaen for denne katalogpartisjonen til en annen katalogserver, bruker du alternativet Legg til NC-replika til å konfigurere denne katalogserveren på nytt som vert for denne katalogpartisjonen (slik at den kan fungere som replikeringskilde), og til å konfigurere den nye katalogserveren som vert for katalogpartisjonen. Når den første replikeringen er fullført på den nye katalogserveren, bruker du alternativet Fjern NC-replika til å fjerne katalogpartisjonen fra den lokale katalogserveren. |
The local directory server is no longer configured to host the following application directory partition. An attempt to transmit its updates and transfer its operations master roles (if any) to another directory server failed because no other directory server is configured to host a replica of this application directory partition.%n%nApplication directory partition:%n%1%n%nThis operation will be tried again later.%n%nUser Action%nUse the dsmgmt command-line tool to do one of the following:%n%n- To remove the partition permanently, use the Delete NC option to delete the crossRef object for this directory partition.%n- To keep the partition on this directory server, use the Add NC Replica option to reconfigure this directory server to host this directory partition.%n- To move the replica of this directory partition to another directory server, use the Add NC Replica option to reconfigure this directory server to host the directory partition (so it can act as a replication source) and to configure the new directory server to host the directory partition. Once the new directory server has completed its initial replication, use the Remove NC Replica option to remove the directory partition from the local directory server. |
| 0x800006D5 | Denne katalogserveren er ikke lenger konfigurert som vert for programkatalogpartisjonen nedenfor. Et forsøk på å overføre de tilhørende oppdateringene og eventuelle driftsovervåkerroller til en annen katalogserver mislyktes fordi det ikke finnes noen annen katalogserver som er vert for programkatalogpartisjonen.%n%nProgramkatalogpartisjon:%n%1%n%nÉn eller flere katalogservere er for øyeblikket konfigurert som vert for programkatalogpartisjonen, men finner ingen replika av programkatalogpartisjonen.%n%nDenne operasjonen vil bli forsøkt på nytt senere.%n%nDenne advarselen kan forekomme som et resultat av en av følgende situasjoner:%n%n- Katalogserverne som er konfigurert som vert for denne programkatalogpartisjonen, er frakoblet.%n- Den første replikeringen av programkatalogpartisjonen er ennå ikke fullført på katalogserverne som er konfigurert som vert for denne programkatalogpartisjonen.%n- Denne katalogserveren finner ikke katalogserverne på grunn av en nettverksfeil eller DNS-oppslagsfeil. |
This directory server is no longer configured to host the following application directory partition. An attempt to transmit its updates and transfer its operations master roles (if any) to another directory server failed because no other directory server that hosts the application directory partition could be found.%n%nApplication directory partition:%n%1%n%nOne or more directory servers are currently configured to host the application directory partition, but no replica of the application directory partition could be located.%n%nThis operation will be tried again later.%n%nThis warning can occur as a result of one of the following situations:%n%n- The directory servers configured to host this application directory partition are offline.%n- The directory servers configured to host this application directory partition have not yet completed their initial replication of the application directory partition.%n- This directory server cannot find the directory servers due to a network or DNS lookup failure. |
| 0x800006EC | Kan ikke tildele tilstrekkelig minne til å behandle en innkommende forespørsel i Active Directory Lightweight Directory Services. Denne feilen har forekommet det angitte antallet ganger i tidsperioden nedenfor.%n%nAntall forekomster:%n%1%nTidsperiode (minutter):%n%2%n%nHvis denne hendelsen vedvarer, er det lite minne på denne katalogtjenesten.%n%nBrukerhandling%nØk mengden tilgjengelig fysisk minne, størrelsen på sidevekslingsfilen eller virtuelt adresseområde på denne datamaskinen. |
Active Directory Lightweight Directory Services was unable to allocate sufficient memory to process an incoming request. This error has occurred the following number of times in the following time period.%n%nNumber of times occurred:%n%1%nTime period (minutes):%n%2%n%nIf this event continues to occur, a low memory condition on this directory service exists.%n%nUser Action%nIncrease the amount of available physical memory, pagefile size, or virtual address space on this computer. |
| 0x800006EF | Kan ikke initialisere godkjenningspakken for LDAP-meldingssammendrag 5 (MD5) i Active Directory Lightweight Directory Services med statuskoden nedenfor.%n%nStatuskode:%n%1%n%nMD5-godkjenningsbindinger mot LDAP-grensesnittet støttes ikke. |
Active Directory Lightweight Directory Services failed to initialize the LDAP Message Digest 5 (MD5) authentication package with the following status code.%n%nStatus code:%n%1%n%nMD5 authentication binds against the LDAP interface will not be supported. |
| 0x800006FA | Objektet %1 for områdekoblinger inneholder mindre enn to områder.Områdekoblingen vil bli ignorert. |
The site link object %1 contains fewer than two sites.The site link will be ignored. |
| 0x80000700 | En transaksjon varer %1 minutter og %2 sekunder, som er mye lenger enn forventet. (Oppkalleren er %3.) Langvarige transaksjoner bidrar til at versjonslageret utarmes. Når versjonslageret er brukt opp, vil alle katalogoperasjoner mislykkes. Kontakt Microsoft Product Support Services for å få hjelp. |
A transaction lasts %1 minutes and %2 seconds, much longer than expected. (The caller is %3.) Long-running transactions contribute to the depletion of version store. When version store is exhausted all directory operations will fail. Please contact Microsoft Product Support Services for assistance. |
| 0x80000703 | Tilkoblingen %1 har den ukjente transportType %2. Den vil bli slettet. |
Connection %1 has unknown transportType %2. It will be deleted. |
| 0x80000704 | Trådprioriteten kunne ikke endres i oppgaven for oppdatering av replikeringstopologi.Feilmeldingen er:%n%n%1%nOppdateringsoppgaven vil fortsette med den eksisterende prioriteten. |
The replication topology update task failed to change its thread priority.The error message is:%n%n%1%nThe update task will proceed at the existing priority. |
| 0x80000705 | KCC forsøkte å opprette en duplisert tilkobling, men denne operasjonenble forhindret. Den eksisterende tilkoblingen er%n%n%1%n%nHvis dette problemet vedvarer, kontakter du Microsoft Product SupportServices for å få hjelp. |
The KCC attempted to make a duplicate connection, but this operationwas successfully prevented. The existing connection is%n%n%1%n%nIf this issue persists, please contact Microsoft Product SupportServices for assistance. |
| 0x80000707 | KCC finner ikke DSA-målobjektet for tilkoblingen%1. Den mest sannsynlige årsaken er en katalogoppdatering mens KCC blekjørt. Gjeldende KCC-kjøring vil bli avbrutt. |
The KCC could not find the destination DSA object for connection%1. The most likely cause is a directory update while the KCC wasexecuting. The current KCC run will be aborted. |
| 0x80000708 | En delvis replika av partisjonen %1 har området %2 som vert, menfinner ingen skrivbare kilder for denne partisjonen. |
A partial replica of partition %1 is hosted at site %2, but nowriteable sources could be found for this partition. |
| 0x80000709 | Partisjonen %1 skal ha området %2 som vert, men er ikkestartet ennå. KCC finner imidlertid ingen verter somdenne partisjonen kan replikeres fra. |
The partition %1 should be hosted at site %2, but has not beeninstantiated yet. However, the KCC could not find any hosts fromwhich to replicate this partition. |
| 0x8000070B | Intersite Messaging-tjenesten sendte en ugyldig tidsplan tilKCC. Denne tidsplanen er for bruk mellom områdene %1 og %2. Entidsplan der replikasjon alltid er tilgjengelig, vil bli brukt i stedetfor den ugyldige tidsplanen. |
The Intersite Messaging Service passed an invalid schedule tothe KCC. This schedule is for use between sites %1 and %2. Aschedule where replication is always available will be used insteadof the invalid schedule. |
| 0x8000071E | Intersite Messaging-tjenesten stoppet ikkeRPC-serveren.%nFeilmeldingen er som følger:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to stop theRPC server.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0x80000722 | Et viktig attributt for området %1 ble ikke lest i IntersiteMessaging-tjenesten. Området blir ignorert. |
The Inter-Site Messaging Service failed to read a critical attribute forsite %1. The site is being ignored. |
| 0x80000723 | Et viktig attributt for transporten %1 ble ikke lest i IntersiteMessaging-tjenesten. Transporten blir ignorert. |
The Inter-Site Messaging Service failed to read a critical attribute fortransport %1. The transport is being ignored. |
| 0x80000724 | Knowledge Consistency Checker (KCC) la ikke til en kobling med parametere på grunn av en tidligere feil under tillegging av en kobling fra denne kildekatalogtjenesten.%n%nPartisjon:%n%1%nUnikt navn for DSA for kilde:%n%4%nDSA-adresse for kilde:%n%2%nTransport mellom områder (hvis noen):%n%5%n%nDen tidligere feilstatusen var:%n%n%3%n%nDenne operasjonen vil bli forsøkt på nytt.%n%nTilleggsdata%nFeilverdi:%n%4 |
The Knowledge Consistency Checker (KCC) didn't add a link with parameters due to a previous failure while adding a link from this source directory service.%n%nPartition:%n%1%nSource DSA DN:%n%4%nSource DSA Address:%n%2%nInter-site Transport (if any):%n%5%n%nThe previous error status was:%n%n%3%n%nThis operation will be retried.%n%nAdditional data%nError value:%n%4 |
| 0x80000729 | Intersite Messaging-tjenesten kan ikke slette SMTP-domeneobjektet nedenfor for Internet Information Services (IIS).%n%nDomeneobjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service failed to delete the following Internet Information Services (IIS) SMTP domain object.%n%nDomain object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0x8000072B | Intersite Messaging-tjenesten kan ikke lagre endringer i SMTP-domeneobjektet nedenfor for Internet Information Services (IIS).%n%nDomeneobjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service failed to commit changes to the following Internet Information Services (IIS) SMTP domain object.%n%nDomain object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0x8000072D | Et forsøk på å overføre driftsovervåkerrollen som er representert av objektet nedenfor, mislyktes.%n%nObjekt:%n%1%nGjeldende driftsovervåkerrolle:%n%2%nForeslått driftsovervåkerrolle:%n%3%n%nTilleggsdata%nFeilverdi:%n%4 |
An attempt to transfer the operations master role represented by the following object failed.%n%nObject:%n%1%nCurrent operations master role:%n%2%nProposed operations master role:%n%3%n%nAdditional Data%nError value:%n%4 |
| 0x8000072E | En replikeringsoperasjon som startet på starttidspunktet nedenfor, har tatt lengre tid enn forventet å fullføre. Resultatet er at det angitte antallet operasjoner venter i replikeringskøen.%n%nStarttidspunkt:%n%1%nAntall ventende operasjoner:%n%2%n%nDette skjer vanligvis hvis en ny katalogpartisjon blir replikert til denne katalogserveren, eller hvis denne katalogserveren nylig har fått nivået hevet til en global katalog. |
A replication operation that began at the following start time has been taking longer than expected to complete. As a result, the following number of operations is waiting in the replication queue.%n%nStart time:%n%1%nNumber of waiting operations:%n%2%n%nThis condition is typical if a new directory partition is being replicated to this directory server or this directory server has recently been promoted to a global catalog. |
| 0x8000072F | Det angitte antallet operasjoner venter i replikeringskøen. Den eldste operasjonen har ventet siden tidspunktet nedenfor.%n%nTidspunkt:%n%1%nAntall ventende operasjoner:%n%2%n%nDette kan skje hvis den samlede replikeringsbelastningen i denne katalogtjenesten er for stor, eller hvis replikeringsintervallet er for lite. |
The following number of operations is waiting in the replication queue. The oldest operation has been waiting since the following time.%n%nTime:%n%1%nNumber of waiting operations:%n%2%n%nThis condition can occur if the overall replication workload on this directory service is too large or the replication interval is too small. |
| 0x80000731 | Internal event: Active Directory Lightweight Directory Services could not delete the following unneeded substring index.%n%nSubstring index:%n%1%n%nAdditional Data%nError value:%n%3 %4%nInternal ID:%n%2 |
Internal event: Active Directory Lightweight Directory Services could not delete the following unneeded substring index.%n%nSubstring index:%n%1%n%nAdditional Data%nError value:%n%3 %4%nInternal ID:%n%2 |
| 0x80000733 | En forespørsel om å slette det viktige systemobjektet nedenfor ble funnet under replikering av endringer fra en kildekatalogtjeneste. Denne slettingen vil bli tilbakeført. Objektet kom fra katalogserveren nedenfor.%n%nViktig systemobjekt:%n%1%nOpprinnelig katalogserver:%n%2%nOpprinnelig tidsstempel:%n%3%n%nActive Directory Lightweight Directory Services vil ikke slette objektet, men objektet vil bli merket som autoritativ i den lokale databasen. Dette objektet vil deretter fortsette å replikere til andre katalogservere.%n%nDet er usikkert om endringer i objektet like før slettingen vil være beholdt. Enkelte referanser for unikt navn til eller fra det slettede objektet er kanskje ikke gjenopprettet.%n%nBrukerhandling%nUndersøk innholdet i dette objektet på de andre katalogserverne for eventuelle inkonsekvenser. |
While replicating changes from a source directory service, a request to delete the following critical system object was detected. This deletion will be reversed. The object originated at the following directory server.%n%nCritical system object:%n%1%nOriginating directory server:%n%2%nOriginating timestamp:%n%3%n%nActive Directory Lightweight Directory Services will not delete the object, but the object will be marked as authoritative on the local database. This object will then continue to replicate to other directory servers.%n%nChanges made to the object just before the deletion operation may or may not have been preserved. Some distinguished name references to or from the deleted object may not have been restored.%n%nUser Action%nInspect the contents of this object on the other directory servers for any inconsistencies. |
| 0x80000734 | Den lokale domenekontrolleren kan ikke koble til domenekontrolleren nedenfor som er vert for den angitte katalogpartisjonen, for løsing av unike navn.%n%nDomenekontroller:%n%5%nKatalogpartisjon:%n%1%n%nTilleggsdata%nFeilverdi:%n%2 %4%nIntern ID:%n%3 |
The local domain controller could not connect with the following domain controller hosting the following directory partition to resolve distinguished names.%n%nDomain controller:%n%5%nDirectory partition:%n%1%n%nAdditional Data%nError value:%n%2 %4%nInternal ID:%n%3 |
| 0x80000735 | Verdien for governsID-attributtet for skjemaklassen nedenfor dupliserer governsID-verdien for en eksisterende klasse.%n%nKlasse:%n%1 (%2)%nEksisterende klasse:%n%3%n%nBegge klassene regnes som deaktivert (som om verdien for attributtet isDefunct var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The governsID attribute value for the following schema class duplicates the governsID value for an existing class.%n%nClass:%n%1 (%2)%nExisting class:%n%3%n%nBoth classes are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x80000737 | Verdien for governsID-attributtet for skjemaklassen nedenfor dupliserer AttributeID-verdien for et eksisterende attributt.%n%nKlasse:%n%1 (%2)%nEksisterende attributt:%n%3 (%4, %5)%n%nBegge attributtene regnes som deaktivert (som om verdien for attributtet isDefunct var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The governsID attribute value for the following schema class duplicates the AttributeID value for an existing attribute.%n%nClass:%n%1 (%2)%nExisting attribute:%n%3 (%4, %5)%n%nThe class and the attribute are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x80000738 | Verdien for attributtet schemaIdGuid for skjemaklassen nedenfor dupliserer verdien for schemaIdGuid for en eksisterende klasse.%n%nKlasse:%n%1 (%2)%nEksisterende klasse:%n%3 (%4)%n%nBegge klassene regnes som deaktivert (som om verdien for attributtet isDefunct var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The schemaIdGuid attribute value for the following schema class duplicates the schemaIdGuid value for an existing class.%n%nClass:%n%1 (%2)%nExisting class:%n%3 (%4)%n%nBoth classes are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x80000739 | Verdien for attributtet IdapDisplayName for skjemaklassen nedenfor dupliserer verdien for IdapDisplayName for en eksisterende klasse.%n%nKlasse:%n%1 (%2)%nEksisterende klasse:%n%3 (%4)%n%nBegge klassene regnes som deaktivert (som om verdien for attributtet isDefunct var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The ldapDisplayName attribute value for the following schema class duplicates the ldapDisplayName value for an existing class.%n%nClass:%n%1 (%2)%nExisting class:%n%3 (%4)%n%nBoth classes are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x8000073A | Verdien for attributtet IdapDisplayName for skjemaklassen nedenfor dupliserer IdapDisplayName-verdien for et eksisterende attributt.%n%nKlasse:%n%1 (%2)%nEksisterende attributt:%n%3 (%4, %5)%n%nBegge attributtene regnes som deaktivert (som om verdien for attributtet isDefunct var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The ldapDisplayName attribute value for the following schema class duplicates the ldapDisplayName value for an existing attribute.%n%nClass:%n%1 (%2)%nExisting attribute:%n%3 (%4, %5)%n%nThe class and the attribute are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x8000073B | AttributeID-verdien for attributtet nedenfor dupliserer AttributeID-verdien for det angitte eksisterende attributtet.%n%nAttributt:%n%1 (%2, %3)%nEksisterende attributt:%n%4 (%5, %6)%n%nBegge attributtene regnes som deaktivert (som om verdien for isDefunct-attributtet var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The AttributeID value for the following attribute duplicates the AttributeID value for the following existing attribute.%n%nAttribute:%n%1 (%2, %3)%nExisting attribute:%n%4 (%5, %6)%n%nBoth attributes are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x8000073C | Verdien for schemaIdGuid for attributtet nedenfor dupliserer verdien for schemaIdGuid for et eksisterende attributt.%n%nAttributt:%n%1 (%2, %3)%nEksisterende attributt:%n%4 (%5, %6)%n%nBegge attributtene regnes som deaktivert (som om verdien for isDefunct-attributtet var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The schemaIdGuid value for the following attribute duplicates the schemaIdGuid value for an existing attribute.%n%nAttribute:%n%1 (%2, %3)%nExisting attribute:%n%4 (%5, %6)%n%nBoth attributes are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x8000073D | mapiID-verdien for attributtet nedenfor dupliserer mapiID-verdien for et eksisterende attributt.%n%nAttributt:%n%1 (%2, %3)%nEksisterende attributt:%n%4 (%5, %6)%n%nBegge attributtene regnes som deaktivert (som om verdien for isDefunct-attributtet var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The mapiID value for the following attribute duplicates the mapiID value for an existing attribute.%n%nAttribute:%n%1 (%2, %3)%nExisting attribute:%n%4 (%5, %6)%n%nBoth attributes are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x8000073E | Verdien for IdapDisplayName for attributtet nedenfor dupliserer verdien for IdapDisplayNamefor et eksisterende attributt.%n%nAttributt:%n%1 (%2, %3)%nEksisterende attributt:%n%4 (%5, %6)%n%nBegge attributtene regnes som deaktivert (som om verdien for isDefunct-attributtet var TRUE). Forholdet vil løse seg selv når skjemakatalogpartisjonen er replikert.%n%nBrukerhandling%nHvis denne hendelsen vedvarer, starter du en replikeringssyklus med alle replikeringspartnerne for den lokale katalogtjenesten. Hvis forholdet vedvarer, deaktiverer du en av klassene ovenfor ved å sette isDefunct-verdien til TRUE. |
The ldapDisplayName value for the following attribute duplicates the ldapDisplayName value for an existing attribute.%n%nAttribute:%n%1 (%2, %3)%nExisting attribute:%n%4 (%5, %6)%n%nBoth attributes are considered deactivated (as if the isDefunct attribute value were TRUE). The condition will resolve itself after the schema directory partition has replicated successfully.%n%nUser Action%nIf this event continues to occur, initiate a replication cycle with all replication partners of the local directory service. If the condition persists, deactivate one of the above classes by setting the isDefunct value to TRUE. |
| 0x80000743 | Internal event: The current garbage collection interval is larger than the maximum value.%n%nCurrent garbage collection interval (hours):%n%1%nMaximum value:%n%2%nNew value:%n%3%n%nAs a result, the garbage collection interval has been set to a new value. |
Internal event: The current garbage collection interval is larger than the maximum value.%n%nCurrent garbage collection interval (hours):%n%1%nMaximum value:%n%2%nNew value:%n%3%n%nAs a result, the garbage collection interval has been set to a new value. |
| 0x80000746 | Dette er replikeringsstatusen for katalogpartisjonen nedenfor på denne katalogserveren.%n%nKatalogpartisjon:%n%1%n%nDenne katalogserveren har ikke mottatt replikeringsinformasjon fra flere katalogservere på andre områder i det konfigurerte ventetidsintervallet.%n%nAntall katalogservere:%n%2%nVentetidsintervall (timer):%n%3%n%nVentetidsintervallet kan endres med registernøkkelen nedenfor.%n%nRegisternøkkel: %nHKLM\\%4\\Intervall for feil i ventetid for replikator (timer)%n%nHvis du vil identifisere katalogserverne med navn, bruker du verktøyet Dcdiag.exe.%nDu kan også bruke støtteverktøyet Repadmin.exe til å vise ventetidene for replikering for katalogserverne. Kommandoen er \"repadmin /showvector /latency \". |
This is the replication status for the following directory partition on this directory server.%n%nDirectory partition:%n%1%n%nThis directory server has not received replication information from a number of directory servers in other sites within the configured latency interval.%n%nNumber of directory servers:%n%2%nLatency Interval (Hours):%n%3%n%nThe latency interval can be modified with the following registry key.%n%nRegistry Key: %nHKLM\\%4\\Replicator latency error interval (hours)%n%nTo identify the directory servers by name, use the dcdiag.exe tool.%nYou can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is \"repadmin /showvector /latency \". |
| 0x80000749 | Knowledge Consistency Checker (KCC) kan ikke danne topologi for et fullstendig spredt trenettverk. Resultatet er at listen over områder nedenfor ikke kan nås fra det lokale området.%n%nOmråder:%n%1%n%2%n%3%n%4%n%5%n%6%n%7%n%8 |
The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.%n%nSites:%n%1%n%2%n%3%n%4%n%5%n%6%n%7%n%8 |
| 0x8000074B | Kan ikke starte oppgaven som overvåker Active Directory Lightweight Directory Services for endringer i områdetopologien for det angitte objektet for transport mellom områder.%n%nObjekt for transport mellom områder:%n%1%n%nProblemet kan ha vært en midlertidig mangel på ressurser. Oppgaven vil bli startet på nytt.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The task that monitors Active Directory Lightweight Directory Services for changes in the site topology for the following Intersite Transport object could not be started.%n%nIntersite Transport object:%n%1%n%nThe problem may have been caused by a temporary resource shortage. The task will be restarted.%n%nAdditional Data%nError value:%n%3 %2 |
| 0x8000074E | Katalogpartisjonen nedenfor på den lokale katalogtjenesten har det angitte antallet replikeringspartnere, som overskrider den anbefalte grensen for replikeringspartnere for en katalogpartisjon.%n%nKatalogpartisjon:%n%2%nReplikeringspartnere:%n%1%nAnbefalt grense for replikeringspartnere:%n%3%n%nBrukerhandling%nKonfigurer nettverkstopologien for Active Directory Lightweight Directory Services for å redusere antallet replikeringspartnere i denne katalogtjenesten. |
The following directory partition on the local directory service has the following number of replication partners, which exceed the recommended limit of replication partners for a directory partition.%n%nDirectory partition:%n%2%nReplication partners:%n%1%nRecommended replication partner limit:%n%3%n%nUser Action%nConfigure the Active Directory Lightweight Directory Services network topology to reduce the number of replication partners at this directory service. |
| 0x80000753 | Active Directory Lightweight Directory Services har funnet ut at replikeringsepoken (som angitt i attributtet msDS-ReplicationEpoch for objektet nedenfor) for den lokale domenekontrolleren er endret. Dette skjer vanligvis som en del av prosessen med å gi nytt navn til domenet.%n%nObjekt: %n%1%nGammel replikeringsepoke: %n%2%nNy replikeringsepoke: %n%3%n%nResultatet er at replikering mellom denne domenekontrolleren og domenekontrollerne som bruker den gamle replikeringsepoken, ikke lenger er tillatt. Replikering kan bare forekomme hvis disse domenekontrollerne bruker den nye replikeringsepoken. |
Active Directory Lightweight Directory Services has detected that the replication epoch (as indicated by the msDS-ReplicationEpoch attribute of the following object) of the local domain controller has been changed. This typically occurs as part of the domain rename process.%n%nObject: %n%1%nOld replication epoch: %n%2%nNew replication epoch: %n%3%n%nAs a result, replication between this domain controller and domain controllers that are using the old replication epoch is no longer allowed. Replication can occur only with those domain controllers using the new replication epoch. |
| 0x80000754 | Den lokale domenekontrolleren kan ikke replikere med den eksterne domenekontrolleren nedenfor på grunn av manglende samsvar i replikeringsepoker (msDS-ReplicationEpoch). Dette forekommer vanligvis som en del av prosessen med å gi nytt navn til domenet.%n%nEkstern domenekontroller: %n%1%nReplikeringsepoke for ekstern domenekontroller: %n%2%nReplikeringsepoke for lokal domenekontroller: %n%3%n%nDomenekontrollere som får nytt domenenavn, kan ikke kommunisere med domenekontrollere som ennå ikke har fått nytt navn. Når alle domenekontrollere har fått nytt domenenavn, vil replikering bli tillatt på nytt. |
The local domain controller cannot replicate with the following remote domain controller because of a mismatched replication epoch (msDS-ReplicationEpoch). This typically occurs as part of the domain rename process.%n%nRemote domain controller: %n%1%nRemote domain controller replication epoch: %n%2%nLocal domain controller replication epoch: %n%3%n%nDomain controllers undergoing a domain rename are not allowed to communicate with those domain controllers that have not yet undergone the domain rename. When all domain controllers have completed the domain rename, replication will once again be allowed. |
| 0x8000076D | Kan ikke slette den automatisk registreringsoppføringen for sertifikattjenester i Active Directory Lightweight Directory Services.%n%nDenne domenekontrolleren vil kanskje fortsette å be om et domenekontrollersertifikat. |
Active Directory Lightweight Directory Services could not delete the auto enrollment entry for Certificate Services.%n%nThis domain controller may continue to request a domain controller certificate. |
| 0x80000777 | Perioden for replikering mellom områder for dette området overskrider rollevalgperioden for generering av topologi mellom områder. Dette kan føre til at rollen for generering av topologi mellom områder får en unødvendig failover til en annen katalogtjeneste på dette området.%n%nOmråde: %n%1%nUtilgjengelighetsperiode: %n%2%nAnbefalt periode i minutter: %n%3%n%nBrukerhandling%nDu kan løse dette problemet ved å sette tidsplanen for replikering mellom områder til standardverdien, eller ved å justere attributtet interSiteTopologyFailover for områdets innstillingsobjekt for NTDS-område til den anbefalte perioden i minutter, som øker valgperioden for generering mellom områder. |
The intrasite replication period for this site exceeds the intersite topology generator role election period. This may cause the intersite topology generator role to unnecessarily failover to another directory service in this site.%n%nSite: %n%1%nUnavailability period: %n%2%nRecommended period in minutes: %n%3%n%nUser Action%nTo repair this problem, either set the intrasite replication schedule to its default value, or adjust the interSiteTopologyFailover attribute on this site's NTDS Site Settings object to the recommended period in minutes, which increases the intersite generator election period. |
| 0x80000781 | Tjenesten for sikkerhetskopiering og gjenoppretting i Active Directory Lightweight Directory Services støtte på en uventet feil under lesing på en katalogtjeneste.%n%nObjektlesing: %n%1%n%nSikkerhetskopiering og gjenoppretting mislyktes.%n%nTilleggsdata%nFeilverdi: %n%2 %3%nIntern ID: %n%4 |
The Active Directory Lightweight Directory Services backup and restore service encountered a unexpected error while performing a directory service read operation.%n%nObject read: %n%1%n%nThe backup and restore operation was unsuccessful.%n%nAdditional Data%nError value: %n%2 %3%nInternal ID: %n%4 |
| 0x80000782 | Under degraderingen av den lokale domenekontrolleren var det umulig å tilbakestille datamaskinkontoen for Active Directory Lightweight Directory Services til den opprinnelige statusen før forfremmingen.%n%nNavn på datamaskinkonto: %n%1%nBane til opprinnelig datamaskinkonto: %n%3%n%nBrukerhandling%nFlytt datamaskinkontoen som ble funnet i beholderen for domenekontrollere, tilbake til banen for den opprinnelige datamaskinkontoen, og sett attributtet userAccountControl til 4096.%n%nTilleggsdata%nFeilverdi: %n%4 %2 |
During the demotion of the local domain controller, Active Directory Lightweight Directory Services was unable to move its computer account back to its original state prior to its promotion.%n%nComputer account name: %n%1%nOriginal computer account path: %n%3%n%nUser Action%nManually move the computer account found under the Domain Controllers container to the original computer account path and set its userAccountControl attribute to 4096.%n%nAdditional Data%nError value: %n%4 %2 |
| 0x80000783 | Veiviseren for installasjon av Active Directory Lightweight Directory Services (Dcpromo.exe) kan ikke konvertere datamaskinkontoen %1 til forekomstkontoen for Active Directory Lightweight Directory Services.%nKontroller at brukeren som kjører Dcpromo.exe, får brukerrettigheten Gjør det mulig for datamaskin og brukerkontoer å bli klarert for delegering i standardpolicyen for domenekontrollere.%nHvis du vil ha mer informasjon, kan du se delen om oppløsning på http://go.microsoft.com/fwlink/?LinkId=178406.%nFeilen var: |
The Active Directory Lightweight Directory Services Installation Wizard (Dcpromo.exe) was unable to convert the computer account %1 to an Active Directory Lightweight Directory Services instance account.%nVerify that the user running Dcpromo.exe is granted the \"Enable computer and user accounts to be trusted for delegation\" user right in the Default Domain Controllers Policy.%nFor more information, see the resolution section of http://go.microsoft.com/fwlink/?LinkId=178406.%nThe error was: |
| 0x80000785 | Forsøket på å opprette en replikeringskobling for den skrivbare katalogpartisjonen nedenfor mislyktes.%n%nKatalogpartisjon: %n%1%nKildekatalogtjeneste: %n%4%nAdresse til kildekatalogtjeneste: %n%2%nTransport mellom områder (hvis noen): %n%5%n%nDenne katalogtjenesten kan ikke replikere med kildekatalogtjenesten før problemet er løst.%n%nBrukerhandling%nKontroller om kildekatalogtjenesten og nettverkstilkobling er tilgjengelig.%n%nTilleggsdata%nFeilverdi: %n%6 %3 |
The attempt to establish a replication link for the following writable directory partition failed.%n%nDirectory partition: %n%1%nSource directory service: %n%4%nSource directory service address: %n%2%nIntersite transport (if any): %n%5%n%nThis directory service will be unable to replicate with the source directory service until this problem is corrected.%n%nUser Action%nVerify if the source directory service is accessible or network connectivity is available.%n%nAdditional Data%nError value: %n%6 %3 |
| 0x80000786 | Forsøket på å opprette en replikeringskobling til en skrivebeskyttet katalogpartisjon med parameterne nedenfor mislyktes.%n%nKatalogpartisjon: %n%1%nKildedomenekontroller: %n%4%nAdresse til kildedomenekontroller: %n%2%nTransport mellom områder (hvis noen): %n%5%n%nTilleggsdata%nFeilverdi: %n%6 %3 |
The attempt to establish a replication link to a read-only directory partition with the following parameters failed.%n%nDirectory partition: %n%1%nSource domain controller: %n%4%nSource domain controller address: %n%2%nIntersite transport (if any): %n%5%n%nAdditional Data%nError value: %n%6 %3 |
| 0x80000788 | Den lokale domenekontrolleren har blitt valgt som global katalog i tjenesten for søk etter domenekontroller. Domenekontrolleren har imidlertid aldri fullført en fullstendig synkronisering av katalogpartisjonen nedenfor. Det siste synkroniseringsforsøket mislyktes.%n%nKatalogpartisjon: %n%1%nKildedomenekontroller: %n%2%nBrukt transport: %n%3%nSiste forsøk: %n%5%nEtterfølgende feil: %n%6%n%nDet vil jevnlig bli gjort forsøk på en fullstendig synkronisering av denne katalogpartisjonen i Active Directory Lightweight Directory Services.%n%nEn forhåndsbetingelse for å bli global katalog er at alle katalogpartisjoner som den lokale domenekontrolleren er vert for, må fullføre minst én fullstendig synkronisering. Hvis den lokale domenekontroller nylig var en global katalog og ble nivåsenket, er det mulig at den forrige kopien av katalogpartisjonen er i ferd med å fjernes.%n%nTilleggsdata%nFeilverdi: %n%8 %7 |
The local domain controller has been selected by the domain controller locator service to be a global catalog. However, the domain controller has never completed a full synchronization of the following directory partition. The last synchronization attempt failed.%n%nDirectory partition: %n%1%nSource domain controller: %n%2%nTransport used: %n%3%nLast attempt: %n%5%nConsecutive failures: %n%6%n%nActive Directory Lightweight Directory Services will attempt to complete a full synchronization of this directory partition periodically.%n%nA precondition to become a global catalog is that every directory partition hosted by the local domain controller must complete at least one full synchronization. If the local domain controller was recently a global catalog and was demoted, it is possible that the previous copy of the directory partition is in the process of being removed.%n%nAdditional data%nError value: %n%8 %7 |
| 0x80000799 | Active Directory Lightweight Directory Services vil fjerne det etterlatte objektet på den lokale domenekontrolleren fordi det ble slettet og data sanert på kildedomenekontrolleren uten at det ble slettet på denne domenekontrolleren.%n%nObjekt: %n%1%nObjekt-GUID: %n%2%nKildedomenekontroller: %n%3 |
Active Directory Lightweight Directory Services will remove the following lingering object on the local domain controller because it had been deleted and garbage collected on the source domain controller without being deleted on this domain controller.%n%nObject: %n%1%nObject GUID: %n%2%nSource domain controller: %n%3 |
| 0x8000079F | Det ble gjort et forsøk på å bygge hurtigbufferen for crossRef-objekter på nytt i Active Directory Lightweight Directory Services, men det mislyktes.%n%nIntervall mellom forsøk (minutter): %n%3%n%nDet vil bli gjort et forsøk på å bygge hurtigbufferen på nytt ved neste planlagte replikering.%n%nBrukerhandling%nHvis denne operasjonen fortsetter å mislykkes, starter du den lokale datamaskinen på nytt.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
Active Directory Lightweight Directory Services attempted to rebuild the cache of crossRef objects but failed.%n%nRetry interval (minutes): %n%3%n%nAn attempt to rebuild the cache operation will be tried again at the next scheduled replication.%n%nUser Action%nIf this operation continues to fail, restart the local computer.%n%nAdditional Data%nError value: %n%1 %2 |
| 0x800007A7 | Kunne ikke fjerne leveringsmappen i Intersite Messaging-tjenesten som bruker SMTP-transport. Det er kanskje filer i mappen som ikke kan fjernes i tjenesten, eller selve mappen kan være beskyttet mot fjerning.%n%nBane til leveringsbane: %n%1%n%nUønskede filer vil bli værende i leveringsmappen til de fjernes manuelt. |
The Intersite Messaging service using the SMTP transport was not able to remove the drop folder. There may be files within the folder that cannot be removed by this service, or the folder itself may be protected against removal.%n%nDrop folder path: %n%1%n%nUnwanted files will remain in the drop folder until manually removed. |
| 0x800007AF | Det oppstod en feil i Active Directory Lightweight Directory Services under et forsøk på å bufre gruppemedlemskap.%n%nBufringen av gruppemedlemskap ble ikke fullført. Dette vil imidlertid ikke ha innvirkning på brukere som logger på. Det vil bli gjort et forsøk på å bufre gruppemedlemskap i Active Directory Lightweight Directory Services senere.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
Active Directory Lightweight Directory Services encountered an error while attempting to cache group memberships.%n%nThe group membership cache task did not complete. However, this will not affect users from logging on. Active Directory Lightweight Directory Services will attempt to cache group memberships in the future.%n%nAdditional Data%nError value: %n%1 %2 |
| 0x800007B1 | Det ble gjort et forsøk på å legge til et crossRef-objekt i Active Directory Lightweight Directory Services, men navnereferansen for katalogpartisjonen (nCName-attributtet) er i konflikt med et annet objekt fordi det er to katalogpartisjoner med samme nCName. Dette kan ha oppstått da crossRef-objektet ble lagt til eller slettet, partisjonen ble slettet og crossRef-objektet ble lagt til på nytt.%n%nCrossRef-objekt: %n%1%nNavn på gammel katalogpartisjon: %n%2%nNavn på ny katalogpartisjon: %n%3%n%nDet blir vanligvis gjort forsøk i Active Directory Lightweight Directory Services på å korrigere denne navnereferansekonflikten automatisk, men det finnes en annen katalogpartisjon med dette navnet.%n%nBrukerhandling%nSlett manuelt det crossRef-objektet som tilsvarer katalogpartisjonen som ikke skal bli værende i konfigurasjonssettet. Hvis du velger å beholde crossRef-objektet med navnekonflikten, må du kjøre semantikkanalysen Dsdbutil for å korrigere navnereferansen.%n%nTilleggsdata%nFeilverdi: %n%4 %5 |
Active Directory Lightweight Directory Services attempted to add a crossRef object, but the directory partition name reference (nCName attribute) conflicts with another object because there are two directory partitions with the same nCName. This could have occurred when the crossRef object was added or deleted, the partition was deleted, and the crossRef object was added again.%n%nCrossRef object: %n%1%nOld directory partition name: %n%2%nNew directory partition name: %n%3%n%nActive Directory Lightweight Directory Services usually attempts to automatically correct this conflicting name reference, but another directory partition that has this name exists.%n%nUser Action%nManually delete one of the crossRef objects corresponding to the directory partition that should not remain in the configuration set. If you chose to keep the crossRef object with the conflicting name, you must run Dsdbutil semantic analysis to correct the name reference.%n%nAdditional Data%nError value: %n%4 %5 |
| 0x800007B2 | Det ble gjort et forsøk på å legge til et crossRef-objekt i Active Directory Lightweight Directory Services, men navnereferansen for katalogpartisjonen (nCName-attributtet) er i konflikt med et annet objekt. Dette kan ha oppstått da crossRef-objektet ble lagt til eller slettet, katalogpartisjonen ble slettet og crossRef-objektet ble lagt til på nytt.%n%nCrossRef-objekt: %n%1%nNavn på gammel katalogpartisjon: %n%2%nNavn på ny katalogpartisjon: %n%3%n%nDet ble gjort et forsøk på å korrigere navnereferansen i Active Directory Lightweight Directory Services, men operasjonen mislyktes.%n%nBrukerhandling%nKontroller partisjonsbeholderen for å se om det finnes flere crossRef-objekter som refererer til samme katalogpartisjonsnavn. I så fall fjerner du ett av crossRef-objektene. Hvis det gjenværende crossRef-objektet har konfliktformatet, må du kjøre semantikkdatabaseanalysen Dsdbutil for å korrigere navnereferansen.%n%nTilleggsdata%nFeilverdi: %n%4 %5 |
Active Directory Lightweight Directory Services attempted to add a crossRef object, but the directory partition name reference (nCName attribute) conflicts with another object. This could have occurred when the crossRef object was added or deleted, the directory partition was deleted, and the crossRef object was added again.%n%nCrossRef object: %n%1%nOld directory partition name: %n%2%nNew directory partition name: %n%3%n%nActive Directory Lightweight Directory Services attempted to correct the name reference, but the operation failed.%n%nUser Action%nCheck the Partitions container to see if there is more than one crossRef object referring to the same directory partition name. If so, remove one of the crossRef objects. If the remaining crossRef object is in the conflicted form, it will be necessary to run Dsdbutil semantic database analysis to correct the name reference.%n%nAdditional Data%nError value: %n%4 %5 |
| 0x800007BC | Standardtilgangskontrollisten (ACL) i objektklasseobjektet Domain-DNS nedenfor er fjernet tidligere.%n%nAlle senere opprettede domene- og programkatalogpartisjoner vil tillate usikret tilgang.%n%nBrukerhandling%nHvis du vil sikre tilgangen til domene- og programkatalogpartisjoner senere, tilbakestiller du standardsikkerhetsbeskrivelsen for objektklassen Domain-DNS i skjemaet til standardinnstillingen. |
The default access control list (ACL) on the following Domain-DNS object class has been previously removed.%n%nAll subsequently created domain and application directory partitions will permit insecure access.%n%nUser Action%nTo secure access to domain and application directory partitions created in the future, revert the default security descriptor on the Domain-DNS object class in the schema back to the default setting. |
| 0x800007C9 | Internal event: Active Directory Lightweight Directory Services cancelled a remote procedure call (RPC) to the following directory service because of an impending shutdown.%n%ndirectory service: %n%2%nThread ID: %n%1%n%nUser Action%nWait for the directory service to shut down and perform the operation again.%n%nAdditional Data%nInternal ID:%n%3 |
Internal event: Active Directory Lightweight Directory Services cancelled a remote procedure call (RPC) to the following directory service because of an impending shutdown.%n%ndirectory service: %n%2%nThread ID: %n%1%n%nUser Action%nWait for the directory service to shut down and perform the operation again.%n%nAdditional Data%nInternal ID:%n%3 |
| 0x800007D9 | Internal event: The security descriptor propagation task failed to process the objects starting from the following container.%n%nStarting container:%n%3%nObjects processed:%n%4%n%nThe propagation task will be tried again in thirty minutes or when a security descriptor on any object changes, whichever comes first.%n%nAdditional Data%nError value: %n%1 %2 |
Internal event: The security descriptor propagation task failed to process the objects starting from the following container.%n%nStarting container:%n%3%nObjects processed:%n%4%n%nThe propagation task will be tried again in thirty minutes or when a security descriptor on any object changes, whichever comes first.%n%nAdditional Data%nError value: %n%1 %2 |
| 0x800007DA | Internal event: The security descriptor propagation task has completed the propagation starting from the following container. However, it was unable to propagate to some objects in the subtree.%n%nThe propagations starting from these objects will be tried again in thirty minutes or when a security descriptor on any object changes, whichever comes first.%n%nStarting container:%n%1%nObjects processed:%n%2%nPropagations waiting in queue:%n%3 |
Internal event: The security descriptor propagation task has completed the propagation starting from the following container. However, it was unable to propagate to some objects in the subtree.%n%nThe propagations starting from these objects will be tried again in thirty minutes or when a security descriptor on any object changes, whichever comes first.%n%nStarting container:%n%1%nObjects processed:%n%2%nPropagations waiting in queue:%n%3 |
| 0x800007DF | Kan ikke bygge det angitte antallet indekser i Active Directory Lightweight Directory Services på grunn av lite diskplass i arbeidskatalogen. Prosessen med å bygge indeksen på nytt starter på nytt med den nye bunkestørrelsen nedenfor for å redusere bruk av midlertidig diskplass.%n%nIndekser: %n%1%nNy bunkestørrelse: %n%2 |
Active Directory Lightweight Directory Services was unable to rebuild the following number of indices due to low disk space in the working directory. To reduce temporary disk space usage during this process, the index rebuild process is restarting with the following new batch size.%n%nIndices: %n%1%nNew batch size: %n%2 |
| 0x800007E3 | Tilkoblingsobjektet nedenfor hadde ikke en gyldig verdi for transportType-attributtet. Denne verdien vil bli fjernet fra tilkoblingsobjektet. Prosessen vil fortsette.%n%nUnikt navn for tilkoblingsobjekt:%n%1%nUgyldig transportType-verdi:%n%2 |
The following connection object did not have a valid transportType attribute value. This value will be removed from the connection object. The process will continue.%n%nConnection object DN:%n%1%nInvalid transportType value:%n%2 |
| 0x800007E8 | Internal event: Active Directory Lightweight Directory Services was unable to replicate the following object from the following remote directory server.%n%nObject: %n%2%nRemote directory server: %n%1%n%nThis directory server will try another method for retrieving and replicating the desired object.%n%nUser Action%nEnsure that replication can succeed between these two directory servers.%n%nAdditional Data%nError value: %n%3%nExtended error value: %n%4 |
Internal event: Active Directory Lightweight Directory Services was unable to replicate the following object from the following remote directory server.%n%nObject: %n%2%nRemote directory server: %n%1%n%nThis directory server will try another method for retrieving and replicating the desired object.%n%nUser Action%nEnsure that replication can succeed between these two directory servers.%n%nAdditional Data%nError value: %n%3%nExtended error value: %n%4 |
| 0x800007ED | Et sertifikat som ble funnet i lokal Active Directory Lightweight Directory Services, hevdes å være fra en domenekontroller med datamaskinkontoen nedenfor. Denne datamaskinen samsvarer ikke med IDen for den lokale domenekontrolleren. Resultatet er at sertifikatet ikke ble godkjent.%n%nObjekt-GUID for datamaskinkonto:%n%1%n%nBrukerhandling%nRegistrer den lokale datamaskinen ved hjelp av det nyeste sertifikatet. I sertifiseringsinstansen bruker du snapin-modulen for sertifikatmaler til å heve malversjonen i sertifikatene for e-postreplikering og domenegodkjenning. Bruk deretter snapin-modulen for sertifikater på den lokale datamaskinen til å fremtvinge ny registrering av det nye domenekontrollersertifikatet. |
A certificate found in the local Active Directory Lightweight Directory Services claims to be from a domain controller with the following computer account. This computer does not match the identity of the local domain controller. As a result, the certificate was not authenticated.%n%nComputer account object GUID:%n%1%n%nUser Action%nHave the local computer enroll using the latest certificate. First, on the certificate authority, use the certificate template snapin to raise the template version on the email replication and domain authentication certificates. Second, on the local computer, use the certificate snapin to force the re-enrollment of the new domain controller certificate. |
| 0x800007EE | Fant ikke nummeret for oppdateringssekvens under sikkerhetskopieringen. Databasen vil bli lest i Active Directory Lightweight Directory Services i et forsøk på å finne det beste nummeret for oppdateringssekvens.%n |
The USN at the time of backup was not found. Active Directory Lightweight Directory Services will read the database to attempt to locate the best USN to use.%n |
| 0x800007F2 | Internal Event: Another directory server has attempted to replicate into this directory server an object which is not present in the local Active Directory Lightweight Directory Services database. This object was not identified as a lingering object.%n%n%nThe attribute set included in the update request is not sufficient to create the object. The object will be re-requested with a full attribute set and created on this directory server.%n%n%nSource directory server (Transport-specific network address):%n%4%nObject:%n%1%nObject GUID:%n%2%nDirectory partition:%n%3%nDestination highest property USN:%n%5 |
Internal Event: Another directory server has attempted to replicate into this directory server an object which is not present in the local Active Directory Lightweight Directory Services database. This object was not identified as a lingering object.%n%n%nThe attribute set included in the update request is not sufficient to create the object. The object will be re-requested with a full attribute set and created on this directory server.%n%n%nSource directory server (Transport-specific network address):%n%4%nObject:%n%1%nObject GUID:%n%2%nDirectory partition:%n%3%nDestination highest property USN:%n%5 |
| 0x800007F3 | Kan ikke bruke RPC-protokollsekvensen nedenfor i Active Directory Lightweight Directory Services.%n%nRPC-protokollsekvens: %n%1%n%nDenne RPC-protokollsekvensen ser ikke ut til å være installert. Det ble gjort et mislykket forsøk i Active Directory Lightweight Directory Services på å registreres i RPCved hjelp av denne protokollsekvensen, og protokollsekvensen kan derfor ikke brukes til kommunikasjon.%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
Active Directory Lightweight Directory Services could not use the following RPC protocol sequence.%n%nRPC protocol sequence:%n%1%n%nThis RPC protocol sequence does not appear to be installed. Active Directory Lightweight Directory Services unsuccessfully attempted to register with RPCusing this protocol sequence, and therefore cannot use this protocol sequence for communication.%n%nAdditional Data%nError value:%n%2 %3 |
| 0x800007F4 | Kan ikke bruke den brukerdefinerte TCP-porten i Active Directory Lightweight Directory Services på grunn av minnebegrensninger. En dynamisk valgt RPC-port vil bli brukti stedet.%n |
Active Directory Lightweight Directory Services cannot use the user defined TCP port because of memory constraints. A dynamic RPC chosen port will be usedinstead.%n |
| 0x800007FC | Alle Unicode-indekser er slettet i Active Directory Lightweight Directory Services som en del av initialiseringen.%n%nDisse slettede indeksene vil bli bygd på nytt. |
Active Directory Lightweight Directory Services has deleted all Unicode indices as part of initialization.%n%nThese deleted indices will be rebuilt. |
| 0x800007FE | Alle LDAP-sendekøene i Active Directory Lightweight Directory Services er fulle. Dette kan skyldes atklienter fortsetter å sende forespørsler raskere enn de behandlerresultatene. For å forhindre at serveren slutter å svare, er resultatetav dette forholdet at %1 tilkoblinger som ikke er bundet som administratorer, har blitt lukket i Active Directory LightweightDirectory Services. Tilkoblinger vil fortsatt bli lukket i Active Directory Lightweight Directory Servicestil det er nok køplass til normal bruk. |
All of Active Directory Lightweight Directory Services's LDAP send queues are full. This can be caused byclients that continue to send requests faster than they are processing theresults. In order to prevent the server from becoming unresponsive as a resultof this condition Active Directory Lightweight Directory Services has closed %1 connections that are notbound as Administrators. Active Directory Lightweight Directory Services will continue to close connectionsuntil enough send queue space has been recovered to operate normally. |
| 0x80000803 | Knowledge Consistency Checker har funnet en potensiell tilkoblingsoscillasjon.Tilkoblingen nedenfor (eller lignende tilkoblinger) er opprettet og slettet gjentatte ganger.Tilkoblingen blir nå holdt tilbake i den angitte tidsperioden og vil ikke bli slettetpå nytt før perioden er over.%n%nTilkoblingsobjekt: %n%1%nGUID for mål-DSA: %n%2%nKilde-DSA: %n%3%nGUID for kilde-DSA: %n%4%nAlternativer: %n%5%nTilbakeholdingsperiode (sek.): %n%6%nToleranse for gjentatt sletting: %n%7%nIntern ID for slettepunkt: %n%8%n%nBrukerhandling:%n%nGjentatt oppretting og sletting av failover-tilkobling kan være et tegn på ustabilt brohode.Kontroller om det er tilkoblings- eller replikeringsproblemer i brohodene. Failover-policy kan også justeresved hjelp av registret. |
The Knowledge Consistency Checker has detected a potential connection oscillation. Thefollowing connection (or ones like it) has been repeatedly created and deleted. Theconnection is now being retained for the time period indicated and will not be deletedagain until that time period has elapsed.%n%nConnection object: %n%1%nDestination DSA Guid: %n%2%nSource DSA: %n%3%nSource DSA Guid: %n%4%nOptions: %n%5%nRetention Period (secs): %n%6%nRepeated Deletion Tolerance: %n%7%nDeletion Point Internal ID: %n%8%n%nUser action:%n%nFrequent failover connection creation and deletion may be a sign of bridgehead instability. Pleasecheck bridgeheads for connectivity or replication problems. Failover policy may also be adjustedusing the registry. |
| 0x80000804 | Det er opprettet en ny tilkobling for å løse tilkoblingsproblemer i lokale brohoder.%n%nSelv om det finnes én eller flere tilkoblinger mellom de to områdene nedenfor, regnes de som ikke valgbare fordi brohodene ikke svarer. Brohodene kan være nede, eller replikering med disse brohodene mislykkes.%n%nDet opprettes en ny failover-tilkobling for brohode i et forsøk på å gjenopprette tilkoblingen i topologien. Disse midlertidige tilkoblingene vil bli fjernet når brohodene fungerer igjen. Dette er et vanlig svar for å korrigere topologien.%n%nDet ble opprettet en replikeringstilkobling fra kildekatalogserveren nedenfor til denne katalogserveren.%n%nKildekatalogserver:%n%1%nLokal katalogserver:%n%2%n%nTilleggsdata:%nÅrsakskode:%n0x%3%nIntern ID for opprettingspunkt:%n%4%n%nBrukerhandling%nSe etter tidligere brohodefeil. Kontroller at brohodene svarer. Se etter og korriger replikeringsfeil i brohoder ved hjelp av overvåkingsverktøy som Repadmin.exe eller Dcdiag.exe. Hvis denne failoveren ikke er ønsket, justerer du registernøklene som styrer failoverpolicyen. Hyppig failover kan være et tegn på en midlertidig brohodetilkobling eller ustabile brohoder.%n |
A new connection has been created to address local bridgehead connectivity issues.%n%nAlthough one or more connections exist between the following two sites, they are considered ineligible because their bridgeheads are not responding. The bridgeheads may be down, or replication with these bridgeheads is failing.%n%nA new bridgehead failover connection is being created in an attempt to reestablish connectivity in the topology. These temporary connections will be removed once the bridgeheads are functioning again. This is a normal response to correct the topology.%n%nA replication connection was created from the following source directory server to this directory server.%n%nSource directory server:%n%1%nLocal directory server:%n%2%n%nAdditional data:%nReason Code:%n0x%3%nCreation Point Internal ID:%n%4%n%nUser Action%nCheck for previous bridgehead errors. Verify that bridgeheads are responding. Check for and correct replication errors on bridgeheads using monitoring tools such as repadmin.exe or dcdiag.exe. If this failover is not desired, please adjust the registry keys controlling failover policy. Frequent failover may be a sign of intermittent bridgehead connectivity or bridgehead instability.%n |
| 0x80000805 | Det er opprettet en ny tilkobling for å løse tilkoblingsproblemer for områder.%n%nEtt eller flere områder kan ikke nås i topologien. Områdene kan være utilgjengelige på grunn av konfigurasjonsfeil i områdekoblingen, eller fordi brohoder i disse områdene har feil. Knowledge Consistency Checker (KCC) prøver å danne topologien på nytt ved å utelate disse områdene. Den nye tilkoblingen hopper over områder som er nede.%n%nDet opprettes en ny failover-tilkobling i et forsøk på å opprette tilkobling på nytt i topologien. Disse midlertidige tilkoblingene vil bli fjernet når områdene fungerer igjen. Dette er et vanlig svar for å korrigere topologien.%n%nDet ble opprettet en replikeringstilkobling fra kildekatalogserveren nedenfor til den lokale katalogserveren.%n%nKildekatalogserver:%n%1%nLokal katalogserver:%n%2%n%nTilleggsdata:%nÅrsakskode:%n0x%3%nIntern ID for opprettingspunkt:%n%4%n%nBrukerhandling%nSe etter tidligere område- eller brohodefeil. Kontroller at områdekoblingene er riktig konfigurert. Kontroller at brohodene svarer. Se etter og korriger replikeringsfeil i brohoder ved hjelp av overvåkingsverktøy som Repadmin.exe eller Dcdiag.exe. Hvis denne failoveren ikke er ønsket, justerer du registernøklene som styrer failoverpolicyen. Hyppig failover kan være et tegn på en midlertidig brohodetilkobling eller ustabile brohoder.%n |
A new connection has been created to address site connectivity issues.%n%nOne or more sites are unreachable in the topology. The sites may be unreachable due to site link configuration errors, or by bridgeheads in those sites having errors. The Knowledge Consistency Checker (KCC) is attempting to reform the topology by excluding those sites. This new connection bypasses sites that are down.%n%nA new failover connection is being created in an attempt to reestablish connectivity in the topology. These temporary connections will be removed once the sites are functioning again. This is a normal response to correct the topology.%n%nA replication connection was created from the following source directory server to the local directory server.%n%nSource directory server:%n%1%nLocal directory server:%n%2%n%nAdditional data:%nReason Code:%n0x%3%nCreation Point Internal ID:%n%4%n%nUser Action%nCheck for previous site or bridgehead errors. Verify that site links are configured correctly. Verify that bridgeheads are responding. Check for and correct replication errors on bridgeheads using monitoring tools such as repadmin.exe or dcdiag.exe. If this failover is not desired, please adjust the registry keys controlling failover policy. Frequent failover may be a sign of intermittent bridgehead connectivity or bridgehead instability.%n |
| 0x80000806 | KCC (Knowledge Consistency Checker) opprettet en ny failover-brohodetilkobling fordi følgende brohoder som ble brukt av eksisterende områdetilkoblinger, ikke svarte eller replikerte.%n%nServere:%n%1%n%2%n%3%n%4%n%5%n%6%n%7%n%8 |
The Knowledge Consistency Checker (KCC) created a new bridgehead failover connection because the following bridgeheads used by existing site connections were not responding or replicating.%n%nServers:%n%1%n%2%n%3%n%4%n%5%n%6%n%7%n%8 |
| 0x80000809 | Active Directory Lightweight Directory Services kan ikke slette følgende registernøkkel. Standardverdien for dennenøkkelen har blitt endret fordi funksjonsnivået for konfigurasjonssettet har blitt satt til Windows Server 2003 eller nyere.Active Directory Lightweight Directory Services forsøkte å slette den eksisterende nøkkelen og bruke den nye standardverdien.%n%nRegisternøkkel: %1\\%2%nGjeldende verdi: %3%nNy standardverdi:%4%n%n%nBrukerhandling%nHvis du vil at Active Directory Lightweight Directory Services skal bruke den nye standardverdien, sletter du nøkkelen ovenformanuelt fra registret.%n%nTilleggsdata%nFeilverdi: %n%5 %6 |
Active Directory Lightweight Directory Services could not delete the following registry key. The default value of thiskey has changed because the configuration set functional level has been set to Windows Server 2003 or greater.Active Directory Lightweight Directory Services attempted to delete the existing key and use the new default value.%n%nRegistry key: %1\\%2%nCurrent value: %3%nNew default value:%4%n%n%nUser Action%nIf you would like Active Directory Lightweight Directory Services to use the new default value, manually delete the abovekey from the registry.%n%nAdditional Data%nError value: %n%5 %6 |
| 0x8000080A | Standardverdien for følgende registernøkkel har blitt endret fordi konfigurasjonssettetsfunksjonsnivå har blitt satt til Windows Server 2003 eller nyere. Active Directory Lightweight Directory Services kan imidlertid ikke bruke den nyestandardverdien fordi nøkkelen allerede har en verdi.%n%nRegisternøkkel: %1\\%2%nGjeldende verdi: %3%nNy standardverdi: %4%n%nBrukerhandling:%nHvis du vil at Active Directory Lightweight Directory Services skal bruke den nye standardverdien, sletter du nøkkelen ovenformanuelt fra registret. Hvis du vil beholde gjeldende verdi, krever det ingen handling. |
The default value of the following registry key has changed because the configuration set functionallevel has been set to Windows Server 2003 or greater. However Active Directory Lightweight Directory Services cannot use the new defaultvalue because the key already has a value.%n%nRegistry key: %1\\%2%nCurrent value: %3%nNew default value: %4%n%nUser Action:%nIf you would like Active Directory Lightweight Directory Services to use the new default value, manually delete the abovekey from the registry. If you want to retain the current value, there is no action required. |
| 0x8000080D | Active Directory Lightweight Directory Services kunne ikke endre tilstanden til databasen i løpet av en sikkerhetskopiering. Ved neste omstart vil det føre til at denne katalogtjenesten unødvendig endrer aktiverings-IDen.%n%nBrukerhandling%nHvis denne hendelsen forekommer regelmessig, kan det føre til at Uptodateness Vector i denne katalogtjenesten raskt øker i størrelse.%n%nTilleggsdata%nFeilverdi: %1 %2 |
During a backup operation, Active Directory Lightweight Directory Services could not change the state of the database. As a result, on the next reboot, this directory service will unnecessarily change its invocation ID.%n%nUser Action%nIf this event occurs frequently, it could cause the Uptodateness Vector on this directory service to rapidly increase in size.%n%nAdditional Data%nError value: %1 %2 |
| 0x80000812 | Active Directory Lightweight Directory Services registrerte en feil under forsøk på å bygge kvotesporingstabellen på nytt i bakgrunnen. Et nytt forsøk på å gjenoppta byggingen av kvotesporingstabellen vil bli utført om %4 sekunder.%n%nTilleggsdata:%nFeilverdi:%n%1 (0x%2)%n%3 |
Active Directory Lightweight Directory Services encountered a failure while attempting to rebuild the quota-tracking table in the background. Another attempt to resume rebuilding of the quota-tracking table will be made in %4 seconds.%n%nAdditional data:%nError value:%n%1 (0x%2)%n%3 |
| 0x80000824 | Directory Service Agent har registrert et objekt med en NULL GUID ogoppdaterte GUIDen med følgende verdi.%n%nTilleggsdata%nObjektnavn:%n%1%nTilordnet GUID:%n%2 |
The Directory Service Agent has detected an object with a NULL GUID andupdated the GUID with the following value.%n%nAdditional Data%nObject name:%n%1%nAssigned GUID:%n%2 |
| 0x80000825 | Internal event: An LDAP over Secure Sockets Layer (SSL) connection could not be established with a client.%n%nClient network address:%n%3%nProtocol:%n%4%n%nAdditional Data%nError value:%n%1 %5%nInternal ID:%n%2 |
Internal event: An LDAP over Secure Sockets Layer (SSL) connection could not be established with a client.%n%nClient network address:%n%3%nProtocol:%n%4%n%nAdditional Data%nError value:%n%1 %5%nInternal ID:%n%2 |
| 0x80000828 | Active Directory Lightweight Directory Services kan ikke bruke DNS til å løse IP-adressen forkildedomenekontrolleren som er oppført nedenfor. Konsekvensen beholdes forsikkerhetsgrupper, gruppepolicy, brukere og datamaskiner og deres passordved at Active Directory Lightweight Directory Services replikeres ved hjelp av NetBIOS eller et fullstendig kvalifisertdatamaskinnavn for kildedomenekontrolleren.%n%nUgyldig DNS-konfigurasjon kan påvirke andre viktige operasjoner påmedlemsdatamaskiner, domenekontrollere eller programservere i denne Active Directory Lightweight Directory Services-skogen, inkludert påloggingsgodkjenning eller tilgang til nettverksressurser.%n%nDu bør imidlertid løse denne DNS-konfigurasjonsfeilen slik at dennedomenekontrolleren kan løse IP-adressen for kildedomenekontrolleren ved hjelp avDNS.%n%nAlternativt servernavn:%n %1%nUgyldig navn på DNS-vert:%n %2%n%nObs! Som standard vises bare opptil ti DNS-feil for en periodepå tolv timer, selv om det forekommer mer enn ti feil. Du logger alle individuellefeilhendelser ved å sette følgende diagnoseregisterverdi til 1:%n%nRegisterbane:%nHKLM\\%5\\%6%n%nBrukerhandling:%n%n 1) Hvis kildedomenekontrolleren ikke lenger fungerer eller kontrollerensoperativsystem har blitt installert på nytt med et annet datamaskinnavn eller en annen GUIDfor NTDSDSA-objektet, fjerner du kildedomenekontrollerens metadata med Ntdsutil.EXE ved hjelp avfremgangsmåten som beskrives i MSKB-artikkel 216498.%n%n 2) Bekreft at kildedomenekontrolleren kjører Active Directory Lightweight Directory Services oger tilgjengelig på nettverket ved å skrive inn \"net view \\\\\" eller\"ping \".%n%n 3) Bekreft at kildedomenekontrolleren bruker en gyldig DNS-server forDNS-tjenester, og at kildedomenekontrollerens vertspost ogCNAME-post er registrert på riktig måte ved hjelp av DNS Enhanced-versjonenfor DCDIAG.EXE, som er tilgjengelig på http://www.microsoft.com/dns%n%n dcdiag /test:dns%n%n 4) Bekreft at denne måldomenekontrolleren bruker en gyldigDNS-server for DNS-tjenester ved å kjøre DNS Enhanced-versjonen for DCDIAG.EXE-kommandoen på konsollen for måldomenekontrolleren, på følgende måte:%n%n dcdiag /test:dns%n%n 5) Se KB 824449 hvis du vil ha ytterligere analyse av DNS-feil:%n http://support.microsoft.com/?kbid=824449%n%nTilleggsdata%nFeilverdi:%n %3 %4%n |
Active Directory Lightweight Directory Services could not use DNS to resolve the IP address of thesource domain controller listed below. To maintain the consistency ofSecurity groups, group policy, users and computers and their passwords,Active Directory Lightweight Directory Services successfully replicated using the NetBIOS or fully qualifiedcomputer name of the source domain controller.%n%nInvalid DNS configuration may be affecting other essential operations on membercomputers, domain controllers or application servers in this Active Directory Lightweight Directory Servicesforest, including logon authentication or access to network resources.%n%nYou should immediately resolve this DNS configuration error so that thisdomain controller can resolve the IP address of the source domain controller usingDNS.%n%nAlternate server name:%n %1%nFailing DNS host name:%n %2%n%nNOTE: By default, only up to 10 DNS failures are shown for any given 12 hourperiod, even if more than 10 failures occur. To log all individual failureevents, set the following diagnostics registry value to 1:%n%nRegistry Path:%nHKLM\\%5\\%6%n%nUser Action:%n%n 1) If the source domain controller is no longer functioning or its operatingsystem has been reinstalled with a different computer name or NTDSDSA objectGUID, remove the source domain controller's metadata with ntdsutil.exe, usingthe steps outlined in MSKB article 216498.%n%n 2) Confirm that the source domain controller is running Active Directory Lightweight Directory Services andis accessible on the network by typing \"net view \\\\\" or\"ping \".%n%n 3) Verify that the source domain controller is using a valid DNS server forDNS services, and that the source domain controller's host record and CNAMErecord are correctly registered, using the DNS Enhanced versionof DCDIAG.EXE available on http://www.microsoft.com/dns%n%n dcdiag /test:dns%n%n 4) Verify that this destination domain controller is using a valid DNSserver for DNS services, by running the DNS Enhanced version of DCDIAG.EXEcommand on the console of the destination domain controller, as follows:%n%n dcdiag /test:dns%n%n 5) For further analysis of DNS error failures see KB 824449:%n http://support.microsoft.com/?kbid=824449%n%nAdditional Data%nError value:%n %3 %4%n |
| 0x80000829 | Denne katalogpartisjonen har ikke blitt sikkerhetskopiert siden følgende antall dager.%n%nKatalogpartisjon:%n%1%n%n'Intervall for sikkerhetskopieringsventetid' (dager):%n%2%n%nDet anbefales at du sikkerhetskopierer så ofte som mulig for å gjenopprette systemet frautilsiktet tap av data. Hvis du imidlertid ikke har sikkerhetskopiert siden minst antall dager i'intervall for sikkerhetskopieringsventetid', logges denne meldingen hver dag til det utføres en sikkerhetskopiering. Du kansikkerhetskopiere alle kopier som inneholder denne partisjonen.%n%nSom standard settes 'intervall for sikkerhetskopieringsventetid' til halvparten av 'intervallet for utløpstid/levetid'. Hvisdu vil endre standardverdien for 'intervall for sikkerhetskopieringsventetid', legger du tilfølgende registernøkkel.%n%nRegisternøkkel for 'intervall for sikkerhetskopieringsventetid' (dager):%n%3\\%4%n |
This directory partition has not been backed up since at least the following number of days.%n%nDirectory partition:%n%1%n%n'Backup latency interval' (days):%n%2%n%nIt is recommended that you take a backup as often as possible to recover from accidentalloss of data. However if you haven't taken a backup since at least the 'backup latency interval'number of days, this message will be logged every day until a backup is taken. You can takea backup of any replica that holds this partition.%n%nBy default the 'Backup latency interval' is set to half the 'Tombstone Lifetime Interval'. Ifyou want to change the default 'Backup latency interval', you could do so by adding thefollowing registry key.%n%n'Backup latency interval' (days) registry key:%n%3\\%4%n |
| 0x8000082A | %nEierskap av følgende FSMO-rolle er ikke angitt, eller kunne ikke leses.%n%nOperasjoner som krever at en FSMO-operasjonsansvarlig kontaktes, mislykkes inntil dette problemetløses.%n%nFSMO-rolle: %1%n%nBrukerhandling:%n%n1. Fastslå hvilken server som bør inneholde den aktuelle rollen.%n2. Fastslå om rollen er angitt på riktig måte på FSMO-rolleserveren. Hvis rollen ikke er angitt, bruker du NTDSUTIL.EXE til å overføre rollen. Dette kan gjøres ved å bruke fremgangsmåten som beskrives i KB-artikkel 255504 og 324801 på http://support.microsoft.com.%n3. Bekreft at replikering av FSMO-partisjonen mellomFSMO-rolleserveren og denne serveren er vellykket. |
%nOwnership of the following FSMO role is not set or could not be read.%n%nOperations which require contacting a FSMO operation master will fail until this condition iscorrected.%n%nFSMO Role: %1%n%nUser Action:%n%n1. Determine which server should hold the role in question.%n2. Determine whether the role is set properly on the FSMO role holder server. If the role is not set, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.%n3. Verify that replication of the FSMO partition between theFSMO role holder server and this server is occurring successfully. |
| 0x8000082B | %nEierskap av følgende FSMO-rolle er satt til en server som er slettet eller som ikke finnes.%n%nOperasjoner som krever at en FSMO-operasjonsansvarlig kontaktes, mislykkes inntil dette problemetløses.%n%nFSMO-rolle: %1%nDomenenavn for FSMO-server: %2%n%nBrukerhandling:%n%n1. Fastslå hvilken server som bør inneholde den aktuelle rollen.%n2. Konfigurasjonsvisningen kan være utdatert. Hvis nivået til den aktuelle serveren nylig har blitt hevet,må du bekrefte at konfigurasjonspartisjonen nylig har blittreplikert fra den nye serveren. Hvis nivået til den aktuelle serveren nylig har blitt senket ogrollen har blitt overført, bekrefter du at denne serveren har replikert partisjonen (som inneholder det nyesterolleeierskapet) i det siste.%n3. Fastslå om rollen er angitt riktig på FSMO-rolleserveren. Hvis rollen ikke er angitt, bruker du NTDSUTIL.EXE til å overføre rollen. Dette kan gjøres ved å bruke fremgangsmåten som beskrives i KB-artikkel 255504 og 324801 på http://support.microsoft.com.%n4. Bekreft at replikering av FSMO-partisjonen mellomFSMO-rolleserveren og denne serveren er vellykket.%n%nFølgende operasjoner kan bli påvirket:%nSkjema: Du kan ikke lenger endre skjemaet for denne skogen.%nNavneendring av domene: Du kan ikke lenger legge til eller fjerne domener fra denne skogen.%nPDC: Du kan ikke lenger utføre primære operasjoner på domenekontrolleren, for eksempel oppdateringer av gruppepolicy og tilbakestilling av passord for ikke-Active Directory Lightweight Directory Services-kontoer.%nRID: Du kan ikke lenger tildele nye sikkerhetsidentifikatorer for nye brukerkontoer, datamaskinkontoer eller sikkerhetsgrupper.%nInfrastruktur: Navnereferanser mellom domener, for eksempel universelle gruppemedlemskap, oppdateres ikke på riktig måte hvis domenenes målobjekt flyttes eller får nytt navn. |
%nOwnership of the following FSMO role is set to a server which is deleted or does not exist.%n%nOperations which require contacting a FSMO operation master will fail until this condition iscorrected.%n%nFSMO Role: %1%nFSMO Server DN: %2%n%nUser Action:%n%n1. Determine which server should hold the role in question.%n2. Configuration view may be out of date. If the server in question has been promoted recently,verify that the Configuration partition hasreplicated from the new server recently. If the server in question has been demoted recently and therole transferred, verify that this server has replicated the partition (containing the latest roleownership) lately.%n3. Determine whether the role is set properly on the FSMO role holder server. If the role is not set, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.%n4. Verify that replication of the FSMO partition between theFSMO role holder server and this server is occurring successfully.%n%nThe following operations may be impacted:%nSchema: You will no longer be able to modify the schema for this forest.%nDomain Naming: You will no longer be able to add or remove domains from this forest.%nPDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Lightweight Directory Services accounts.%nRID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.%nInfrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed. |
| 0x8000082C | %nDenne serveren er eier av følgende FSMO-rolle, men anser den ikke som gyldig. Når det gjelderpartisjonen som inneholder FSMO, har ikke denne serveren replikert vellykket med noen av sinepartnere siden forrige gang serveren ble startet på nytt. Replikeringsfeil hindrer validering avdenne rollen.%n%nOperasjoner som krever at en FSMO-operasjonsansvarlig kontaktes, mislykkes inntil dette problemetløses.%n%nFSMO-rolle: %1%n%nBrukerhandling:%n%n1. Første synkronisering er de første tidligere replikeringene som utføres av et system når det starter. Mangel på første synkronisering forklarer kanskje hvorfor en FSMO-rolle ikke kan valideres. Denne prosessen beskrives i KB-artikkel 305476.%n2. Denne serveren har én eller flere replikeringspartnere, og replikering mislykkes for allepartnerne. Bruk kommandoen repadmin /showrepl til å vise replikeringsfeilene. Korriger den aktuellefeilen. Det kan for eksempel være feil med IP-tilkoblingen, DNS-navneløsningen ellersikkerhetsgodkjenningen som hindrer vellykket replikering.%n3. I den svært sjeldne situasjonen der det forventes at alle replikeringspartnerne er frakoblet (for eksempel på grunn av vedlikehold eller gjenoppretting etter en alvorlig feil), kan du fremtvinge validering av rollen. Dette kan du gjøre ved å bruke NTDSUTIL.EXE til å overføre rollen til den samme serveren. Dette kan du gjøre ved å følge fremgangsmåten som beskrives i KB-artikkel 255504 og 324801 på http://support.microsoft.com.%n%nFølgende operasjoner kan bli påvirket:%nSkjema: Du kan ikke lenger endre skjemaet for denne skogen.%nNavneendring av domene: Du kan ikke lenger legge til eller fjerne domener fra denne skogen.%nPDC: Du kan ikke lenger utføre primære operasjoner på domenekontrolleren, for eksempel oppdateringer av gruppepolicy og tilbakestilling av passord for ikke-Active Directory Lightweight Directory Services-kontoer.%nRID: Du kan ikke lenger tildele nye sikkerhetsidentifikatorer for nye brukerkontoer, datamaskinkontoer eller sikkerhetsgrupper.%nInfrastruktur: Navnereferanser mellom domener, for eksempel universelle gruppemedlemskap, oppdateres ikke på riktig måte hvis domenenes målobjekt flyttes eller får nytt navn. |
%nThis server is the owner of the following FSMO role, but does not consider it valid. For thepartition which contains the FSMO, this server has not replicated successfully with any of itspartners since this server has been restarted. Replication errors are preventing validation ofthis role.%n%nOperations which require contacting a FSMO operation master will fail until this condition iscorrected.%n%nFSMO Role: %1%n%nUser Action:%n%n1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476.%n2. This server has one or more replication partners, and replication is failing for all of thesepartners. Use the command repadmin /showrepl to display the replication errors. Correct the errorin question. For example there maybe problems with IP connectivity, DNS name resolution, orsecurity authentication that are preventing successful replication.%n3. In the rare event that all replication partners are expected to be offline (for example, because of maintenance or disaster recovery), you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.%n%nThe following operations may be impacted:%nSchema: You will no longer be able to modify the schema for this forest.%nDomain Naming: You will no longer be able to add or remove domains from this forest.%nPDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Lightweight Directory Services accounts.%nRID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.%nInfrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed. |
| 0x8000082D | %nDen eksterne serveren som er eier av en FSMO-rolle, svarer ikke. Denne serveren har ikkereplikert med FSMO-rolleeieren i det siste.%n%nOperasjoner som krever at en FSMO-operasjonsansvarlig kontaktes, mislykkes inntil dette problemetløses.%n%nFSMO-rolle: %1%nDomenenavn for FSMO-server: %2%nVenteterskel (timer): %3%nTid siden forrige vellykkede replikering (timer): %4%n%nBrukerhandling:%n%nDenne serveren har ikke replikert vellykket med FSMO-rolleserveren.%n1. FSMO-rolleserveren kan være nede eller svarer ikke. Løs problemet meddenne serveren.%n2. Fastslå om rollen er riktig angitt på FSMO-rolleserveren. Hvis rollen må justeres, bruker du NTDSUTIL.EXE til å overføre rollen. Dette kan gjøres ved å bruke fremgangsmåten som beskrives i KB-artikkel 255504 og 324801 på http://support.microsoft.com.%n3. Hvis FSMO-rolleserveren tidligere var en domenekontroller, men ikke fikk nivået senket på riktig måte,finnes objektene somrepresenterer den serveren, fortsatt i skogen. Dette kan forekomme hvis en domenekontroller fåroperativsystemet installert på nytt, eller hvis det utføres en tvunget fjerning. Disse etterlatte tilstandsobjektenebør fjernes ved hjelp av oppryddingsfunksjonen for metadata i NTDSUTIL.EXE.%n4. FSMO-rolleinnehaveren er kanskje ikke en direkte replikeringspartner. Hvis han/hun er en indirekte ellertransitiv partner, må replikeringsdataene flyte gjennom én eller fleremellomliggende replikeringspartnere. Den totale replikeringsventetiden bør være mindre ennterskelen for replikeringsventetid, ellers kan det hende denne advarselen vises for tidlig.%n5. Replikering blokkeres et sted mellom FSMO-rolleserverenog denne serveren. Studer skogtopologiplanen for å finne den sannsynlige ruten forreplikering mellom disse serverne. Kontroller replikeringsstatusen ved hjelp av repadmin /showrepl påhver av disse serverne.%n%nFølgende operasjoner kan bli påvirket:%nSkjema: Du kan ikke lenger endre skjemaet for denne skogen.%nNavneendring av domene: Du kan ikke lenger legge til eller fjerne domener fra denne skogen.%nPDC: Du kan ikke lenger utføre primære operasjoner på domenekontrolleren, for eksempel oppdateringer av gruppepolicy og tilbakestilling av passord for ikke-Active Directory Lightweight Directory Services-kontoer.%nRID: Du kan ikke lenger tildele nye sikkerhetsidentifikatorer for nye brukerkontoer, datamaskinkontoer eller sikkerhetsgrupper.%nInfrastruktur: Navnereferanser mellom domener, for eksempel universelle gruppemedlemskap, oppdateres ikke på riktig måte hvis domenenes målobjekt flyttes eller får nytt navn. |
%nThe remote server which is the owner of a FSMO role is not responding. This server has notreplicated with the FSMO role owner recently.%n%nOperations which require contacting a FSMO operation master will fail until this condition iscorrected.%n%nFSMO Role: %1%nFSMO Server DN: %2%nLatency threshold (hours): %3%nElapsed time since last successful replication (hours): %4%n%nUser Action:%n%nThis server has not replicated successfully with the FSMO role holder server.%n1. The FSMO role holder server may be down or not responding. Please address the problem withthis server.%n2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.%n3. If the FSMO role holder server used to be a domain controller, but was not demoted successfully,then the objectsrepresenting that server are still in the forest. This can occur if a domain controller has itsoperating system reinstalled or if a forced removal is performed. These lingering state objectsshould be removed using the NTDSUTIL.EXE metadata cleanup function.%n4. The FSMO role holder may not be a direct replication partner. If it is an indirect ortransitive partner, then there are one or more intermediate replication partners through whichreplication data must flow. The total end to end replication latency should be smaller than thereplication latency threshold, or else this warning may be reported prematurely.%n5. Replication is blocked somewhere along the path of servers between the FSMO role holderserver and this server. Consult your forest topology plan to determine the likely route forreplication between these servers. Check the status of replication using repadmin /showrepl ateach of these servers.%n%nThe following operations may be impacted:%nSchema: You will no longer be able to modify the schema for this forest.%nDomain Naming: You will no longer be able to add or remove domains from this forest.%nPDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Lightweight Directory Services accounts.%nRID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.%nInfrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed. |
| 0x8000082E | Ytelsesadvarsel: replikering ble forsinket mens endringer ble utført i følgende objekt. Hvis dennemeldingen forekommer regelmessig, angir det at replikeringen foregår langsomt, og at serverenkanskje har vanskeligheter med å holde tritt med endringene.%nDomenenavn for objekt: %1%n%nObjekt-GUID: %2%n%nDomenenavn for partisjon: %3%n%nServer: %4%n%nBrukt tid (sek): %5%n%n%nBrukerhandling%n%nEn vanlig årsak til at denne forsinkelsen oppstår, er at dette objektet er spesielt stort, enten i størrelsenpå verdiene, eller i antall verdier. Du bør først vurdere om programmet kanendres slik at mengden data som lagres i objektet, eller antall verdier, reduseres. Hvis dette eren stor gruppe eller distribusjonsliste, bør du kanskje vurdere å heve funksjonsnivået for konfigurasjonssettet til Windows Server2003 eller nyere, noe som vil føre til at replikering fungerer mer effektivt. Du bør vurdere omserverplattformen gir tilstrekkelig ytelse når det gjelder minne og behandlingseffekt. Til slutt børdu kanskje vurdere å justere Active Directory Lightweight Directory Services-databasen ved å flytte databasen og loggene til atskiltediskpartisjoner.%n%nHvis du vil endre advarselsgrensen, finnes registernøkkelen nedenfor. Verdien nulldeaktiverer kontrollen.%n%nTilleggsdata%n%nAdvarselsgrense (sek): %6%n%nRegisternøkkel for grense: %7%n |
Performance warning: replication was delayed while applying changes to the following object. If thismessage occurs frequently, it indicates that the replication is occurring slowly and that the servermay have difficulty keeping up with changes.%nObject DN: %1%n%nObject GUID: %2%n%nPartition DN: %3%n%nServer: %4%n%nElapsed Time (secs): %5%n%n%nUser Action%n%nA common reason for seeing this delay is that this object is especially large, either in the sizeof its values, or in the number of values. You should first consider whether the application canbe changed to reduce the amount of data stored on the object, or the number of values. If this isa large group or distribution list, you might consider raising the configuration set functional level to Windows Server2003 or greater, since this will enable replication to work more efficiently. You should evaluate whether theserver platform provides sufficient performance in terms of memory and processing power. Finally, youmay want to consider tuning the Active Directory Lightweight Directory Services database by moving the database and logs to separatedisk partitions.%n%nIf you wish to change the warning limit, the registry key is included below. A value of zero willdisable the check.%n%nAdditional Data%n%nWarning Limit (secs): %6%n%nLimit Registry Key: %7%n |
| 0x80000843 | Funksjonsnivået for konfigurasjonssettet er ikke høyt nok til å fullføre tillegg av programkatalogpartisjonerunder installasjonen av katalogen. Derfor blir ikke de angitte programkatalogpartisjonene lagt til i denne Active Directory Lightweight Directory Services-forekomsten i løpet av installasjonen.%nHvis du vil gjøre denne serveren til en kopi av en programkatalogpartisjon, kan du legge til denne programpartisjonen på nytt etter at installasjonen er fullført.%n%n%nIntern ID:%n%1%n%n |
The configuration set functional level is not high enough to complete addition of application directorypartitions during installation of the directory. Therefore specified application directory partitions will not be added to this Active Directory Lightweight Directory Services instance during installation.%nIf you would like to make this server a replica of an application directory partition, you could re-add these application partition after the installation is complete.%n%n%nInternal ID:%n%1%n%n |
| 0x8000084F | Internal event: The local Active Directory Lightweight Directory Services was unable to verify or update the state of the phantom object 1 (error %2). The phantom will be checked at a later time. |
Internal event: The local Active Directory Lightweight Directory Services was unable to verify or update the state of the phantom object 1 (error %2). The phantom will be checked at a later time. |
| 0x80000850 | Internal event: The local Active Directory Lightweight Directory Services was unable to delete the obsolete column %1 because the column is in use in an index. If this situation persists after the Active Directory Lightweight Directory Services is restarted, it may indicate a database consistency problem. |
Internal event: The local Active Directory Lightweight Directory Services was unable to delete the obsolete column %1 because the column is in use in an index. If this situation persists after the Active Directory Lightweight Directory Services is restarted, it may indicate a database consistency problem. |
| 0x80000856 | Intern hendelse: Det gjeldende intervallet for datasaneringen er mindre enn minimumsverdien.%n%nGjeldende intervall for datasanering (timer):%n%1%nMinimumsverdi:%n%2%nNy verdi:%n%3%n%nDette fører til at intervallet for datasaneringen har blitt satt til en ny verdi. |
Internal event: The current garbage collection interval is smaller than the minimum value.%n%nCurrent garbage collection interval (hours):%n%1%nMinimum value:%n%2%nNew value:%n%3%n%nAs a result, the garbage collection interval has been set to a new value. |
| 0x80000857 | Internal event: An attempt to add the following value to the following attribute was detected. This value already exists on some object in the local Active Directory Lightweight Directory Services database. Active Directory Lightweight Directory Services does not prevent such duplicate values. Duplicate values of this attribute in the Active Directory Lightweight Directory Services database may lead to error conditions in applications that rely on this attribute. The attempt to add the duplicate value may have succeeded.%n%nAttribute name:%n%1%nAttribute value:%n%2 |
Internal event: An attempt to add the following value to the following attribute was detected. This value already exists on some object in the local Active Directory Lightweight Directory Services database. Active Directory Lightweight Directory Services does not prevent such duplicate values. Duplicate values of this attribute in the Active Directory Lightweight Directory Services database may lead to error conditions in applications that rely on this attribute. The attempt to add the duplicate value may have succeeded.%n%nAttribute name:%n%1%nAttribute value:%n%2 |
| 0x8000085F | En valgfri funksjon er aktivert på denne domenekontrolleren. Funksjonsnivået for konfigurasjonssettet er imidlertid ikke kompatibelt med den fullstendige virkemåten for denne valgfrie funksjonen.%n%nDette kan skyldes en forsinkelse i replikeringen til denne Active Directory Lightweight Directory Services-forekomsten av en endring i funksjonsnivået for konfigurasjonssettet, og korrigeres kanskje automatisk. Hvis dette problemet vedvarer, kan det bli nødvendig med en manuell operasjon.%n%nBrukerhandling%nHev funksjonsnivået for konfigurasjonssettet til minste påkrevde funksjonsnivå.%n%nValgfri funksjon: %1%nMinste funksjonsnivå som kreves: %2%nGjeldende funksjonsnivå: %3%n |
An optional feature is enabled on this DC. However, the functional level of the configuration set is incompatible with the complete behavior of this optional feature.%n%nThis condition could be due to a delay in replication to this Active Directory Lightweight Directory Services instance of a change to the functional level of the configuration set, and may correct itself automatically. If this condition persists, manual intervention may be necessary.%n%nUser Action%nRaise the functional level of the configuration set to at least the minimum required functional level.%n%nOptional feature: %1%nMinimum required functional level: %2%nCurrent functional level: %3%n |
| 0x80000860 | Den lokale domenekontrolleren forstyrret replikering med følgende eksterne domenekontroller fordi den registrerte en endring i en koblingsverdi, der koblingsverdien nå skal datasaneres. Hvis denne replikeringen ble utført, ville det ført til en etterlatt koblingsverdi. Den lokale domenekontrolleren starter en umiddelbar datasaneringssyklus.%nReplikering med den eksterne domenekontrolleren kan ikke fortsette før objektet har blitt datasanert lokalt.%n%nEkstern domenekontroller: %n%2%nLokalt objekt som inneholder koblingsverdien som skal datasaneres: %n%1%n%nBrukerhandling%nHvis dette problemet vedvarer, ser du hendelsesloggen for mulige feil i systemet eller datasanseringen. |
The local domain controller interrupted replication with the following remote domain controller because it identified a change to a link value where the link value is to be garbage collected now. If this replication took place, it could cause a lingering linked value. The local domain controller will initiate an immediate garbage collection cycle.%nReplication with the remote domain controller cannot continue until the object has been successfully garbage collected locally.%n%nRemote domain controller: %n%2%nLocal object holding the link value to be garbage collected: %n%1%n%nUser Action%nIf this condition persists, check the event log for possible system or garbage collection errors. |
| 0x80000861 | Den lokale domenekontrolleren forstyrret replikering med følgende eksterne domenekontroller fordi den registrerte en endring i et objekt, der objektet nå skal datasaneres. Hvis denne replikeringen ble utført, ville det ført til et etterlatt objekt. Den lokale domenekontrolleren starter en umiddelbar datasaneringssyklus.%nReplikering med den eksterne domenekontrolleren kan ikke fortsette før objektet har blitt datasanert lokalt.%n%nEkstern domenekontroller: %n%2%nLokalt objekt som skal datasaneres: %n%1%n%nBrukerhandling%nHvis dette problemet vedvarer, ser du hendelsesloggen for mulige feil i systemet eller datasanseringen. |
The local domain controller interrupted replication with the following remote domain controller because it identified a change to an object where the object is to be garbage collected now. If this replication took place, it could cause a lingering object. The local domain controller will initiate an immediate garbage collection cycle.%nReplication with the remote domain controller cannot continue until the object has been successfully garbage collected locally.%n%nRemote domain controller: %n%2%nLocal object to be garbage collected: %n%1%n%nUser Action%nIf this condition persists, check the event log for possible system or garbage collection errors. |
| 0x80000863 | Internal event: The local Active Directory Lightweight Directory Services tried to detect and fix any renamed ncName attribute in crossRef objects. But Active Directory Lightweight Directory Services failed when processing a crossRef (error %2). The crossRef will be checked again at later time.%n%nCrossRef object: %n%1%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
Internal event: The local Active Directory Lightweight Directory Services tried to detect and fix any renamed ncName attribute in crossRef objects. But Active Directory Lightweight Directory Services failed when processing a crossRef (error %2). The crossRef will be checked again at later time.%n%nCrossRef object: %n%1%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
| 0x8000087A | Det ble registrert en endring i genererings-IDen.%n%nGenererings-IDen ble bufret i katalogtjenesten (gammel verdi):%n%1%nGenererings-IDen finnes for øyeblikket i VM (ny verdi):%n%2%n%nEndringen i genererings-IDen forekommer etter bruk av et statisk utvalg fra en virtuell maskin, etter en import på en virtuell maskin eller etter en live overføringsoperasjon. Active Directory Lightweight Directory Services oppretter en ny aktiverings-ID for å gjenopprette domenekontrolleren. Virtuelle domenekontrollere bør ikke gjenopprettes ved hjelp av statiske utvalg for virtuelle maskiner. Den støttede metoden for å gjenopprette eller rulle tilbake innholdet i en Active Directory Domain Services-database, skal gjenopprette en sikkerhetskopi av systemtilstand som ble utført med et kompatibelt sikkerhetskopieringsprogram for Active Directory Domain Services. |
A Generation ID change has been detected.%n%nGeneration ID cached in DS (old value):%n%1%nGeneration ID currently in VM (new value):%n%2%n%nThe Generation ID change occurs after the application of a virtual machine snapshot, after a virtual machine import operation or after a live migration operation. Active Directory Lightweight Directory Services will create a new invocation ID to recover the domain controller. Virtualized domain controllers should not be restored using virtual machine snapshots. The supported method to restore or rollback the content of an Active Directory Domain Services database is to restore a system state backup made with an Active Directory Domain Services aware backup application. |
| 0x80000884 | Feil ved angivelse av attributtet msDS-GenerationId for domenekontrollerens datamaskinobjekt.%n%nEkstra data%nFeilkode:%n%1 |
Failed to set the msDS-GenerationId attribute of the Domain Controller's computer object.%n%nAdditional Data%nFailure code:%n%1 |
| 0x8000089B | Siste kloning av virtuell domenekontroller mislyktes. Dette er den første omstarten siden da, så dette bør være et nytt forsøk på kloning. Konfigurasjonsfil for kloning av virtuell domenekontroller finnes ikke. Active Directory Lightweight Directory Services startes opp på vanlig måte. Tilstanden til den gjenopprettede domenekontrolleren kan ikke garanteres.%n%nHvis kloningen av virtuell domenekontroller mislyktes, er tilstanden til den mislykkede domenekontrolleren usikker. Det anbefales at du prøver å klone på nytt eller forkaster den mislykkede avbildningen. |
Last virtual domain controller cloning failed. This is the first reboot since then so this should be a re-try of the cloning. However, virtual domain controller clone configuration file does not exist. Active Directory Lightweight Directory Services will boot up normally. The state of the restored domain controller is not guaranteed.%n%nIf virtual domain controller cloning failed, the state of the failed domain controller is uncertain. It's recommended to either retry the cloning or discard the failed image. |
| 0x80000962 | Internal event: Active Directory Lightweight Directory Services encountered an error while attempting to remove the following expired link history value:%n%nSource Object:%n%2%nTarget Object:%n%1%n%nAdditional Data%nError value:%n%3 %5%nInternal ID:%n%4 |
Internal event: Active Directory Lightweight Directory Services encountered an error while attempting to remove the following expired link history value:%n%nSource Object:%n%2%nTarget Object:%n%1%n%nAdditional Data%nError value:%n%3 %5%nInternal ID:%n%4 |
| 0x80000967 | Denne Active Directory Lightweight Directory Services-serveren fant ikke objektet for den valgfrie funksjonen %1. Ingen indikasjon på at den valgfrie funksjonen %1 vil bli lagret. Opprett objektet for den valgfrie funksjonen %1. |
This Active Directory Lightweight Directory Services server was unable to locate the \"%1\" optional feature object. No indication that the \"%1\" optional feature is will be saved. Create the \"%1\" optional feature object. |
| 0x800009CD | Katalogtjenesten kunne ikke åpne en TCP-port for eksklusiv bruk.%n%nTilleggsdata:%nPortnummer:%n%1%nFeilverdi:%n%2 %3 |
The Directory Service failed to open a TCP port for exclusive use.%n%nAdditional Data:%nPort number:%n%1%nError Value:%n%2 %3 |
| 0x800009D0 | En gjensidig godkjent tilkobling kan ikke opprettes til følgende server. Denne tilkoblingen vil bli prøvd på nyttpå et lavere godkjenningsnivå.%nDSA:%n%1%nHovednavn for tjeneste:%n%5%n%nTilleggsdata:%nFeilverdi:%n%3 %2%n%nBrukerhandling:%nGjensidig godkjenning kan utføres ved å oppdatere følgende registernøkkel i AD LSD og/eller angiriktig verdi for msDS-ReplAuthenticationMode på konfigurasjonspartisjonen.%nRegisternøkkel:%n%6%nIntern informasjon:%n%4 |
A mutually authenticated connection could not be established to the following server. This connection will beretried at a lower authentication level.%nDSA:%n%1%nService Principal Name:%n%5%n%nAdditional Data:%nError value:%n%3 %2%n%nUser Action:%nMutual authentication can be enforced by updating the following registry key and/or in AD LDS by settingthe appropriate msDS-ReplAuthenticationMode value on the configuration partition.%nRegistry Key:%n%6%nInternal Info:%n%4 |
| 0x800009D7 | Et skript er tilgjengelig på følgende plassering for å oppdatere hovednavnene for tjeneste for følgende konto, som kreves for at gjensidig godkjenning skal lykkes for innkommendetilkoblinger.%n%nPlassering:%n%2%nKonto:%n%1%n%nBrukerhandling:%nDette skriptet må kjøres av en domeneadministrator for den aktuelle kontoen. |
A script is available at the following location to update the service principal names for the following account which are needed for mutual authentication to succeed on inboundconnections.%n%nLocation:%n%2%nAccount:%n%1%n%nUser Action:%nThis script must be run by a domain administrator for the account in question. |
| 0x800009D9 | Active Directory Lightweight Directory Services kan ikke initialisere overvåking av sikkerhetssystemet. Det kjøres med overvåking deaktivert.Ingen sikkerhetsovervåkinger genereres.%n%nTilleggsdata:%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services was unable to initialize auditing security system. It will run with auditing disabled.No security audits will be generated.%n%nAdditional Data:%nError value:%n%1 %2 |
| 0x800009E8 | Katalogserveren kan ikke oppdatere serviceConnectionPoint-objektet for AD LDS i Active Directory Lightweight Directory Services.Denne operasjonen vil blir prøvd på nytt.%n%nTilleggsdata%nDomenenavn for SCP-objekt:%n%1%nFeilverdi:%n%2 %3%nServerfeil:%n%4%nIntern ID:%n%5%nTjenestekonto for AD LDS:%n%6%n%nBrukerhandling%nHvis AD LDS kjører på en lokal tjenestekonto, kan ikke programmet oppdatere dataene i Active Directory Lightweight Directory Services.Vurder å endre tjenestekontoen for AD LDS til NetworkService eller en domenekonto.%n%nHvis AD LDS kjører på en domenebrukerkonto, må du sørge for at denne kontoen har tilstrekkelige rettigheter til å oppdatereserviceConnectionPoint-objektet.%n%nPublisering av ServiceConnectionPoint-objektet kan deaktiveres for denne forekomsten ved å angi attributtetfor msDS-DisableForInstances for konfigurasjonsobjektet for SCP-publiseringen. |
The directory server has failed to update the AD LDS serviceConnectionPoint object in Active Directory Lightweight Directory Services.This operation will be retried.%n%nAdditional Data%nSCP object DN:%n%1%nError value:%n%2 %3%nServer error:%n%4%nInternal ID:%n%5%nAD LDS service account:%n%6%n%nUser Action%nIf AD LDS is running under a local service account, it will be unable to update the data in Active Directory Lightweight Directory Services.Consider changing the AD LDS service account to either NetworkService or a domain account.%n%nIf AD LDS is running under a domain user account, make sure this account has sufficient rights to update theserviceConnectionPoint object.%n%nServiceConnectionPoint object publication can be disabled for this instance by setting msDS-DisableForInstancesattribute on the SCP publication configuration object. |
| 0x800009E9 | Katalogserveren kan ikke opprette serviceConnectionPoint-objektet for AD LDS i Active Directory Lightweight Directory Services.Denne operasjonen vil bli prøvd på nytt.%n%nTilleggsdata%nDomenenavn for SCP-objekt:%n%1%nFeilverdi:%n%2 %3%nServerfeil:%n%4%nIntern ID:%n%5%nTjenestekonto for AD LDS:%n%6%n%nBrukerhandling%nHvis AD LDS kjører på en lokal tjenestekonto, kan ikke programmet oppdatere dataene i Active Directory Lightweight Directory Services.Vurder å endre tjenestekontoen for AD LDS til NetworkService eller en domenekonto.%n%nHvis AD LDS kjører på en domenebrukerkonto, må du sørge for at denne kontoen har tilstrekkelige rettigheter til å oppretteserviceConnectionPoint-objektet.%n%nPublisering av ServiceConnectionPoint-objektet kan deaktiveres for denne forekomsten ved å angi attributtetfor angimsDS-DisableForInstances for SCP-publiseringens konfigurasjonsobjekt. |
The directory server has failed to create the AD LDS serviceConnectionPoint object in Active Directory Lightweight Directory Services.This operation will be retried.%n%nAdditional Data%nSCP object DN:%n%1%nError value:%n%2 %3%nServer error:%n%4%nInternal ID:%n%5%nAD LDS service account:%n%6%n%nUser Action%nIf AD LDS is running under a local service account, it will be unable to update the data in Active Directory Lightweight Directory Services.Consider changing the AD LDS service account to either NetworkService or a domain account.%n%nIf AD LDS is running under a domain user account, make sure this account has sufficient rights to create theserviceConnectionPoint object.%n%nServiceConnectionPoint object publication can be disabled for this instance by setting msDS-DisableForInstancesattribute on the SCP publication configuration object. |
| 0x800009EA | Katalogserveren har registrert at tjenestekontoen som ble brukt til å kjøre denne tjenesten, er endret.%n%nReplikeringsfeil kan oppstå hvis to eller flere Active Directory Lightweight Directory Services-forekomster i samme konfigurasjonssett samtidig endrer tjenestekontoene som disse forekomstene kjører under.%n%nTilleggsdata%nGammel tjenestekonto:%n%1%nNy tjenestekonto:%n%2%n%nBrukerhandling%nHvis du vil ha mer informasjon om disse mulige replikeringsfeilene og hvordan du korrigerer dem hvis de oppstår, kan du se http://go.microsoft.com/fwlink/?LinkId=92860. |
The directory server has detected that the service account used to run this service has been changed.%n%nReplication failures may occur if two or more Active Directory Lightweight Directory Services instances in the same configuration set simultaneously change the service accounts under which those instances are running.%n%nAdditional Data%nOld service account:%n%1%nNew service account:%n%2%n%nUser Action%nFor more information on these potential replication failures and how to correct them if they occur, please see http://go.microsoft.com/fwlink/?LinkId=92860. |
| 0x800009F1 | Du har valgt en systemtjenestekonto for denne Active Directory Lightweight Directory Services-forekomsten. Denne datamaskinen er ikke medlem av et domene, og derfor kan ikke denne forekomsten replikere data med AD LDS-forekomsten på andre datamaskiner mens denne tjenestekontoen brukes. |
You have selected a system service account for this Active Directory Lightweight Directory Services instance. Because this computer is not a member of a domain, this instance will not be able to replicate data with AD LDS instance on other computers while using this service account. |
| 0x80000A10 | Katalogtjenesten har rullet tilbake fjerningen. Det tar kanskje flere minutter før denne katalogtjenesten kan brukes med full kapasitet.%n%nBrukerhandling:%nStopp og start tjenesten på nytt. |
The directory service has rolled back the removal. This directory service might take several minutes to become fully operational.%n%nUser Action:%nStop and restart the service. |
| 0x80000B02 | Katalogtjenesten kan ikke åpne en UDP-port for eksklusiv bruk.%n%nTilleggsdata:%nPortnummer:%n%1%nFeilverdi:%n%2 %3%nIP-adresse%n %4 |
The Directory Service failed to open a UDP port for exclusive use.%n%nAdditional Data:%nPort number:%n%1%nError Value:%n%2 %3%nIP Address%n %4 |
| 0x80000B0C | Datamaskinkontoen %1 er ikke en Active Directory Lightweight Directory Services-forekomstkonto. |
The computer account %1 is not an Active Directory Lightweight Directory Services instance account. |
| 0x80000B13 | Den lokale katalogtjenesten har registrert en ugyldig serverReference-verdi for følgende serverobjekt.%n%nServerobjekt:%n%1%nForventet verdi:%n%2 |
The local directory service has detected an incorrect serverReference value on the following server object.%n%nServer object:%n%1%nExpected value:%n%2 |
| 0x80000B14 | ledig melding. |
unused message. |
| 0x80000B19 | Sikkerhetskopieringen av Active Directory Lightweight Directory Services mislykkes fordi brukeren bad om en stopp av Active Directory Lightweight Directory Services under sikkerhetskopieringen. Aktiverings-IDen kan være endret for oppstart av AD LDS.%n%nBrukerhandling%nSørg for at dette ikke skjer regelmessig. Kontroller at skriptene ikke kjører en sikkerhetskopiering av systemtilstanden samtidig med at AD LDS-tjenesten stoppes.%n |
The Active Directory Lightweight Directory Services backup will be failed, because the user requested the Active Directory Lightweight Directory Services stop during the backup process. The invocation ID may be changed on AD LDS startup.%n%nUser Action%nEnsure this does not regularly occur. Check that scripts are not running an system state backup concurrently with stopping the AD LDS service.%n |
| 0x80000B1C | Knowledge Consistency Checker fant en replikeringstilkobling for den lokale, skrivebeskyttede katalogtjenesten, men kildeserveren svarer eller replikerer ikke. En ny kildeserver blir valgt, og en skrivbar katalogtjenesteforekomst blir oppdatert.%n%nTilleggsdata%nTilkobling: %n%1%nKildeserver: %n%2%n |
The Knowledge Consistency Checker located a replication connection for the local read-only directory service, but the source server is not responsive or not replicating. A new source server will be chosen and a writable directory service instance will be updated.%n%nAdditional Data%nConnection: %n%1%nSource Server: %n%2%n |
| 0x80000B24 | LDAP VLV sender forespørsel om sortering for å bruke PHABVIEW-indeksen. Indeksen finnes ikke.%n |
LDAP VLV sort request to use PHABVIEW index. Index does not exist.%n |
| 0x80000B33 | Internal event: Failed building Address Book hierarchy table. Exceeded Address book nesting limit of 50. |
Internal event: Failed building Address Book hierarchy table. Exceeded Address book nesting limit of 50. |
| 0x80000B36 | Katalogtjenesten kan ikke opprette endringsovervåking i sertifikatlageret for LDAPS-tilkoblinger.%n%nTilleggsdata:%nFeilverdi:%n%1%nSertifikatlager:%n%2%n |
The Directory Service could not establish change monitoring on the certificate store for LDAPS connections.%n%nAdditional data:%nError value:%n%1%nCertificate store:%n%2%n |
| 0x80000B37 | Katalogtjenesten kan ikke opprette endringsovervåking i sertifikatlageret for LDAPS-tilkoblinger.Sertifikatlageret %2 kan ikke åpnes og finnes kanskje ikke.%n%nTilleggsdata:%nFeilverdi:%n%1%n |
The Directory Service could not establish change monitoring on the certificate store for LDAPS connections.The %2 certificate store could not be opened, and may not exist.%n%nAdditional data:%nError value:%n%1%n |
| 0x80000B3D | I løpet av en Active Directory Lightweight Directory Services-replikeringssyklus angav den angitte eksterne domenekontrolleren atUpToDateness Vector, som er angitt av den lokale domenekontrolleren i en replikeringsforespørsel, var ugyldig.Den lokale domenekontrollerens UpToDateness Vector ble imidlertid bekreftet som gyldig.%n%nEkstern domenekontroller:%n%1%nPartisjon:%n%2%n |
During an Active Directory Lightweight Directory Services replication cycle, the specified remote domain controller (DC) indicated that theup-to-dateness vector specified by the local DC in a replication request was invalid.However, the local DC's up-to-dateness vector was verified to be valid.%n%nRemote DC:%n%1%nPartition:%n%2%n |
| 0x80000B3E | I løpet av en Active Directory Lightweight Directory Services-replikeringsforespørsel registrerte den lokale domenekontrolleren enugyldig lokal UpToDateness Vector for den angitte partisjonen.%n%nHvis ikke dette problemet løses umiddelbart, fører det til inkonsekvenser i Active Directory Lightweight Directory Services-databasenefor denne domenekontrolleren.%nBrukeren har valgt å ignorere dette problemet på egen risiko.%nBrukerhandlinger:%nSenke nivået på domenekontrolleren.%n%nPartisjon:%n%1%n |
During an Active Directory Lightweight Directory Services replication request, the local domain controller (DC) detected an invalid localup-to-dateness vector for the specified partition.%n%nIf not resolved immediately, this scenario will result in inconsistencies in the Active Directory Lightweight Directory Services databasesof this DC.%nThe user has chosen to ignore this problem at their own peril.%nUser Actions:%nForcibly demote the DC.%n%nPartition:%n%1%n |
| 0x80000B46 | Sikkerheten for denne katalogserveren kan forbedres betydelig ved å konfigurere serveren til å avvise SASL LDAP-bindinger (Negotiate,Kerberos, NTLM eller Digest) som ikke ber om signatur (integritetsbekreftelse) og enkle LDAP-bindinger somutføres i en klarteksttilkobling (ikke-SSL/TLS-kryptert). Selv om ingen klienter bruker slike bindinger, vil konfigurasjonav serveren for å avvise dem forbedre sikkerheten på denne serveren.%n%nNoen klienter bruker kanskje for øyeblikket usignerte SASL-bindinger eller enkle LDAP-bindinger med en ikke-SSL/TLS-tilkobling,og disse klientene vil ikke fungere hvis denne konfigurasjonsendringen utføres. Hvis slike bindinger forekommer, kommer denne katalogtjenesten til å logge en sammendragshendelse hvert døgnfor å bidra til å identifisere disse klientene, og det vil bli angitt hvor mange slike bindingersom forekom. Du oppfordres til å konfigurere disse klientene til ikke å bruke slike bindinger. Når ingen slike hendelser oppståri en lengre periode, anbefales det at du konfigurerer serveren til å avvise slike bindinger.%n%nHvis du vil ha flere detaljer og informasjon om hvordan du foretar denne konfigurasjonsendringen på serveren, se http://go.microsoft.com/fwlink/?LinkID=87923.%n%nDu kan aktivere ytterligere logging for å logge en hendelse hver gang en klient oppretter en slik binding, inkludertinformasjon om hvilken klient som opprettet bindingen. Dette gjør du ved å øke innstillingen for hendelsesloggkategorien for LDAP-grensesnitthendelsertil nivå 2 eller høyere. |
The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate,Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds thatare performed on a clear text (non-SSL/TLS-encrypted) connection. Even if no clients are using such binds,configuring the server to reject them will improve the security of this server.%n%nSome clients may currently be relying on unsigned SASL binds or LDAP simple binds over a non-SSL/TLS connection,and will stop working if this configuration change is made. To assist in identifying these clients, if such binds occur thisdirectory server will log a summary event once every 24 hours indicating how many such bindsoccurred. You are encouraged to configure those clients to not use such binds. Once no such events are observedfor an extended period, it is recommended that you configure the server to reject such binds.%n%nFor more details and information on how to make this configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923.%n%nYou can enable additional logging to log an event each time a client makes such a bind, includinginformation on which client made the bind. To do so, please raise the setting for the \"LDAP Interface Events\" event logging categoryto level 2 or higher. |
| 0x80000B47 | %nI løpet av den forrige 24-timersperioden forsøkte noen klienter å utføre LDAP-bindinger som enten var:%n(1) En SASL (Negotiate, Kerberos, NTLM eller Digest) LDAP-binding som ikke bad om signatur (integritetsvalidering), eller%n(2) En enkel LDAP-binding som ble utført for en klarteksttilkobling (ikke-SSL/TLS-kryptert)%n%nDenne katalogserveren er ikke for øyeblikket konfigurert til å avvise slike bindinger. Sikkerheten for denne katalogtjenesten kanforbedres betydelig ved å konfigurere serveren til å avvise slike bindinger. Hvis du vil ha flere detaljer og mer informasjon om hvordan du utførerdenne konfigurasjonsendringen på serveren, kan du se http://go.microsoft.com/fwlink/?LinkID=87923.%n%nNedenfor vises det sammendragsinformasjon om hvor mange slike bindinger som ble mottatt de siste 24 timene.%n%nDu kan aktivere tilleggslogging for å logge en hendelse hver gang en klient genererer en slik binding, inkludertinformasjon om hvilken klient som genererer bindingen. Dette gjør du ved å heve nivået til innstillingen for hendelsesloggkategorien \"LDAP Interface Events\"til nivå 2 eller høyere.%n%nAntallet enkle bindinger som ble utført uten SSL/TLS: %1%nAntallet Negotiate/Kerberos/NTLM/Digest-bindinger som ble utført uten signatur: %2 |
%nDuring the previous 24 hour period, some clients attempted to perform LDAP binds that were either:%n(1) A SASL (Negotiate, Kerberos, NTLM, or Digest) LDAP bind that did not request signing (integrity validation), or%n(2) A LDAP simple bind that was performed on a clear text (non-SSL/TLS-encrypted) connection%n%nThis directory server is not currently configured to reject such binds. The security of this directory server can besignificantly enhanced by configuring the server to reject such binds. For more details and information on how to makethis configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923.%n%nSummary information on the number of these binds received within the past 24 hours is below.%n%nYou can enable additional logging to log an event each time a client makes such a bind, including informationon which client made the bind. To do so, please raise the setting for the \"LDAP Interface Events\" event logging categoryto level 2 or higher.%n%nNumber of simple binds performed without SSL/TLS: %1%nNumber of Negotiate/Kerberos/NTLM/Digest binds performed without signing: %2 |
| 0x80000B55 | KCC (Knowledge Consistency Checker) slettet ikke følgende Connection-objekt.%n%nObjekt:%n%1%n%nBrukerhandling%nKCC slettet ikke dette Connection-objektet for å hindre etterlatte tilkoblingsobjekter i andre Active Directory Lightweight Directory Services-forekomster. Dette Connection-objektet bør slettes manuelt i en skrivbar Active Directory Lightweight Directory Services-forekomst. |
The Knowledge Consistency Checker (KCC) did not delete the following Connection object.%n%nObject:%n%1%n%nUser Action%nThe KCC did not delete this Connection object to prevent lingering connection objects on other Active Directory Lightweight Directory Services instances. This Connection object should be manually deleted on a writable Active Directory Lightweight Directory Services instance. |
| 0x80000B56 | Mislykket forsøk på å skrive en indikator for innkommende synkroniseringssuksess for følgende partisjon. Hvis den lokale Active Directory Lightweight Directory Services-forekomsten inneholder en FSMO-rolle, kan det hende valideringen og bruken av rollen blokkeres til denne feilen er løst.%n%nPartisjon:%n%1%n%nTilleggsdata%nFeilverdi:%n %2 %3 |
An attempt to write a marker for inbound synchronization success for the following partition failed. If the local Active Directory Lightweight Directory Services instance holds a FSMO role, the validation and use of the role may be blocked until this error is resolved.%n%nPartition:%n%1%n%nAdditional Data%nError value:%n %2 %3 |
| 0x80000B5B | Maksimalt antall Active Directory Lightweight Directory Services-databaseøkter ble nådd, noe som genererte en forespørsel til tjenesten om å avbryte. Dette er vanligvis et tegn på høy belastning på serveren. Det kan føre til sporadiske feil i programmer som bruker Active Directory Lightweight Directory Services.%n%nBrukerhandling%n(1) Sjekk at en overdreven aktivitetsbelastning ikke forekommer.%n(2) Øk om nødvendig antallet tildelte økter per tråd ved å øke verdien på registerparameteren Maximum Allocated EDB Sessions per Thread. Dermed kan Active Directory Lightweight Directory Services bruke mer minne. |
The maximum number of Active Directory Lightweight Directory Services database sessions was reached, causing a request to the service to fail. This is generally a symptom of high load on the server. It can result in sporadic errors in applications that use Active Directory Lightweight Directory Services.%n%nUser Action%n(1) Check that an excessive activity load is not being performed.%n(2) If necessary, increase the number of allocated sessions per thread by increasing the 'Maximum Allocated EDB Sessions per Thread' registry parameter. This will result in Active Directory Lightweight Directory Services using more memory. |
| 0x80000B5D | Active Directory Lightweight Directory Services kan ikke oppdatere funksjonsnivået for partisjonen fordi følgende Active Directory Lightweight Directory Services-forekomst har et lavere funksjonsnivå enn det forespurte nye funksjonsnivået for partisjonen.%n%nObjekt:%n%1%nNTDS-innstillingsobjekt for Active Directory Lightweight Directory Services-forekomst:%n%2 |
Active Directory Lightweight Directory Services failed to update the functional level of the partition because the following Active Directory Lightweight Directory Services instance is at a lower functional level than the requested new functional level of the partition.%n%nObject:%n%1%nNTDS Settings object of Active Directory Lightweight Directory Services instance:%n%2 |
| 0x80000B5E | Forespørselen om å legge til et nytt NTDS-innstillingsobjekt ble avslått fordi det høyeste funksjonsnivået som støttes av operativsystemet, var lavere enn funksjonsnivået for partisjonen.%n%nHøyeste funksjonsnivå for operativsystemet:%n%1%n funksjonsnivå for partisjon:%n%2%n%nBrukerhandling%nInstaller et operativsystem som er kompatibelt med funksjonsnivået for partisjonen på den lokale Active Directory Lightweight Directory Services-forekomsten, eller oppdater funksjonsnivået for partisjonen slik at det er kompatibelt med funksjonsnivået som støttes av dette operativsystemet. |
The request to add a new NTDS Settings object was denied because the highest functional level supported by the operating system was lower than the functional level of the partition.%n%nHighest functional level of the operating system:%n%1%n partition functional level:%n%2%n%nUser Action%nInstall an operating system compatible with the functional level of the partition on the local Active Directory Lightweight Directory Services instance or update the functional level of the partition to be compatible with the functional level supported by this operating system. |
| 0x80000B62 | Målforekomsten av Active Directory Lightweight Directory Services som logget denne hendelsen, behandlet en oppdatering av koblingsverdien for kildeobjektet nedenfor. Koblingsverdien refererer til et målobjekt som finnes i resirkulert tilstand i målforekomsten av Active Directory Lightweight Directory Services.%nDenne hendelsen angir at korrigeringer ikke klarte å replikere målobjektet i ønsket rekkefølge fra kildeforekomsten av Active Directory Lightweight Directory Services til denne målforekomsten av Active Directory Lightweight Directory Services. Oppdaterte binærfiler for kildeforekomsten av Active Directory Lightweight Directory Services løser dette problemet for fremtidige tilfeller.%nHvis målobjektet ikke nylig har blitt gjenopprettet i kildeforekomsten av Active Directory Lightweight Directory Services, kan du ignorere denne hendelsen.%nHvis målobjektet nylig ble gjenopprettet for kildeforekomsten av Active Directory Lightweight Directory Services, finnes koblingsverdien i kildeforekomsten av Active Directory Lightweight Directory Services, men ikke i målforekomsten av Active Directory Lightweight Directory Services og dens transitive replikeringspartnere i konfigurasjonssettet, før en administrator utfører korrigeringer.%n%nDomenenavn for kildeobjekt:%n%1%nGUID for kildeobjekt:%n%2%nAttributt:%n%3%nDomenenavn for målobjekt:%n%4%nGUID for målobjekt:%n%5%nKildeforekomst av Active Directory Lightweight Directory Services:%n%6%n%nGjenta den samme gjenopprettingsoperasjonen for den samme gjenopprettede Active Directory Lightweight Directory Services-forekomsten. Gjenopprett spesifikt undertreet som inneholder målobjektet, eller gjenopprett det bestemte målobjektet som nevnes i denne hendelsen. |
The destination Active Directory Lightweight Directory Services instance logging this event processed a link value update on the source object below. The link value refers to a target object that is in the recycled state on the destination Active Directory Lightweight Directory Services instance.%nThis event indicates that corrective steps failed to replicate the target object in the desired order from the source Active Directory Lightweight Directory Services instance to this destination Active Directory Lightweight Directory Services instance. Updated binaries on the source Active Directory Lightweight Directory Services instance will resolve this condition for future occurrences.%nIf the target object has not been recently authoritatively restored on the source Active Directory Lightweight Directory Services instance, you can ignore this event.%nIf the target object was recently authoritatively restored on the source Active Directory Lightweight Directory Services instance, then the link value will exist on the source Active Directory Lightweight Directory Services instance but not on the destination Active Directory Lightweight Directory Services instance and its transitive replication partners in the configuration set until an administrator takes corrective steps.%n%nSource Object DN:%n%1%nSource Object GUID:%n%2%nAttribute:%n%3%nTarget Object DN:%n%4%nTarget Object GUID:%n%5%nSource Active Directory Lightweight Directory Services instance:%n%6%n%nRepeat the same authoritative restore operation on the same restored Active Directory Lightweight Directory Services instance. Specifically, authoritatively restore the subtree containing the target object or authoritatively restore the specific target object cited in this event. |
| 0x80000B65 | Intern hendelse: Active Directory Lightweight Directory Services kan ikke resirkulere følgende slettede objekt som har utløpt fra Active Directory Lightweight Directory Services-databasen.%n%nObjekt:%n%1%n%nBrukerhandling%nHvis denne feilen vedvarer, utfører du en semantisk analysekontroll i databasen.%n%nTilleggsdata%nFeilverdi:%n%2 %4%nIntern ID:%n%3 |
Internal event: Active Directory Lightweight Directory Services could not recycle the following deleted object that has expired from the Active Directory Lightweight Directory Services database.%n%nObject:%n%1%n%nUser Action%nIf this error continues to occur, perform a semantic analysis check on the database.%n%nAdditional Data%nError value:%n%2 %4%nInternal ID:%n%3 |
| 0x80000B68 | Active Directory Lightweight Directory Services kan ikke åpne en UDP-port for eksklusiv bruk. Dette kan skyldes at UDP-porten var reservert av en annen tjeneste. Hvis du vil ha informasjon om hvordan du reserverer en port for bruk av Active Directory Lightweight Directory Services, kan du se KB-artikkel 959215 på http://go.microsoft.com/fwlink/?LinkId=145140 .%n%nTilleggsdata:%nPortnummer:%n%1%nFeilverdi:%n%2 %3%nIP-adresse%n %4 |
Active Directory Lightweight Directory Services was unable to open a UDP port for exclusive use. This can be caused by the UDP port being reserved by another service. For information on how to reserve a port for Active Directory Lightweight Directory Services use, please refer to KB Article 959215 at http://go.microsoft.com/fwlink/?LinkId=145140 .%n%nAdditional Data:%nPort number:%n%1%nError Value:%n%2 %3%nIP Address%n %4 |
| 0x80000B6E | Kravene nedenfor for den angitte brukeren ble droppet i Active Directory Lightweight Directory Services fordi de er ugyldige i den gjeldende skogen.%n%nBruker: %n%1%nKrav: %n%2%nGå til http://go.microsoft.com/fwlink/?LinkId=285865 for mer hjelp til å feilsøke problemet. |
Active Directory Lightweight Directory Services dropped the following claim[s] for the given user because they are invalid in the current forest.%n%nUser: %n%1%nClaim[s]: %n%2%nPlease visit http://go.microsoft.com/fwlink/?LinkId=285865 for additional help troubleshooting the issue. |
| 0x80000B81 | Indeksendringer knyttet til en tidligere skjemaendring venter fortsatt. Dette skyldes at dSHeuristics-flaggetfDisableAutoIndexingOnSchemaUpdate for hele konfigurasjonssettet er angitt. Når dette flagget er angitt, deaktiveres automatisk indeksering av eksisterendeattributter i skjemaoppdatering.%nHvis du vil sikre optimal ytelse fra denne AD LDS-forekomsten, må du fremtvinge en indeksoppretting. Hvis fDisableAutoIndexingOnSchemaUpdate er satttil 1, utfører du en endring av rootDSE-attributtet i schemaUpdateNow og setter det til 1. Hvis fDisableAutoIndexingOnSchemaUpdate istedet er satt til 2, utfører du en endring av rootDSE-attributtet i schemaUpdateIndicesNow og setter det til 1. Denne virkemåten kan ogsådeaktiveres ved å tilbakestille flagget fDisableAutoIndexingOnSchemaUpdate i dsHeuristics til 0. AD LDS-forekomster vilautomatisk gjenoppbygge indekser etter hvert som de mottar denne endringen. |
Index changes associated with a previous schema change are still pending. This is because the configuration set-widedSHeuristics flag fDisableAutoIndexingOnSchemaUpdate is set. This flag, when set, disables automatic indexing of existingattributes on schema update.%nTo ensure optimal performance from this AD LDS instance, force an index creation. If fDisableAutoIndexingOnSchemaUpdate is setto 1, perform a rootDSE attribute modification on schemaUpdateNow and set it to 1. If fDisableAutoIndexingOnSchemaUpdate isinstead set to 2, perform a rootDSE attribute modification on schemaUpdateIndicesNow and set it to 1. This behavior can alsobe turned off by resetting the fDisableAutoIndexingOnSchemaUpdate flag in dsHeuristics to 0; AD LDS instances willautomatically rebuild indices as they receive this change. |
| 0x80000B83 | Et forsøk på å hente passordet til en gruppeadministrert tjenestekonto mislyktes.%n%nGruppeadministrert tjenestekontoobjekt: %n%1%nOppkaller-SID: %n%2%nOppkaller-IP: %n%3%nFeil: %n%4 |
An attempt to fetch the password of a group managed service account failed.%n%nGroup Managed Service Account Object: %n%1%nCaller SID: %n%2%nCaller IP: %n%3%nError: %n%4 |
| 0x80000B84 | De ugyldige kravene nedenfor for den angitte brukeren ble droppet i Active Directory Lightweight Directory Services.%n%nBruker: %n%1%nKrav: %n%2 |
Active Directory Lightweight Directory Services dropped the following invalid claim[s] for the given user.%n%nUser: %n%1%nClaim[s]: %n%2 |
| 0x80000B96 | Et LDAP-søk overskred de administrativt konfigurerte minnegrensene og ble utført uten optimalisering.%nVurder å forenkle operasjonen eller heve LDAP-minnegrensene ved hjelp av LDAP-policyer.Se http://go.microsoft.com/fwlink/?LinkId=272160 hvis du vil ha mer informasjon om denne policyen. |
An LDAP search exceeded the administratively configured memory limits and was executed without optimization.%nConsider simplifying the operation or raising the LDAP memory limits using LDAP policies.See http://go.microsoft.com/fwlink/?LinkId=272160 for more details on this policy. |
| 0x80000B97 | Eventuelle valgfrie endringer i systemindeks blir utsatt. |
Any optional system index changes are being deferred. |
| 0x80000B98 | Valgfrie endringer i systemindeks som er tilknyttet en tidligere oppgradering, venter fremdeles. Dette skjer fordi det konfigurertedSHeuristics-flagget fDisableAutoIndexingOnSchemaUpdate er angitt. Dette flagget deaktiverer automatisk indeksering av valgfrie systemindekser når det er angitt.%nHvis du vil sikre optimal ytelse fra denne AD LDS-forekomsten, kan du fremtvinge oppretting av en indeks. Hvis fDisableAutoIndexingOnSchemaUpdate er satttil 1, utfører du en endring av rootDSE-attributtet på schemaUpdateNow og setter det til 1. Hvis fDisableAutoIndexingOnSchemaUpdatei stedet settes til 2, utfører du en endring av rootDSE-attributtet på schemaUpdateIndicesNow og setter det til 1. Denne virkemåten kan ogsådeaktiveres ved å tilbakestille flagget fDisableAutoIndexingOnSchemaUpdate i dsHeuristics til 0. AD LDS-forekomster vil automatiskbygge nye indekser når de mottar denne endringen. |
Optional system index changes associated with a previous upgrade are still pending. This is because the configuration set-widedSHeuristics flag fDisableAutoIndexingOnSchemaUpdate is set. This flag, when set, disables automatic indexing of optional system indices.%nTo ensure optimal performance from this AD LDS instance, force an index creation. If fDisableAutoIndexingOnSchemaUpdate is setto 1, perform a rootDSE attribute modification on schemaUpdateNow and set it to 1. If fDisableAutoIndexingOnSchemaUpdate isinstead set to 2, perform a rootDSE attribute modification on schemaUpdateIndicesNow and set it to 1. This behavior can alsobe turned off by resetting the fDisableAutoIndexingOnSchemaUpdate flag in dsHeuristics to 0; AD LDS instances willautomatically rebuild indices as they receive this change. |
| 0x80000BA6 | Den sammensatte indeksen inneholder en ukjent OID.Attributt: %1IndexName: %2Plassering for uløst OID: %3%n |
Compound index contains an unknown OID.Attribute: %1IndexName: %2Location of unresolved OID: %3%n |
| 0x80000BA7 | Den sammensatte indeksen inneholder et ustøttet attributt.Attributt: %1IndexName: %2Ustøttet attributt: %3%n |
Compound index contains an unsupported attribute.Attribute: %1IndexName: %2Unsupported Attribute: %3%n |
| 0x80000BA8 | Indeksendringer som er knyttet til en tidligere skjemaendring, venter fortsatt. Dette skyldes at dSHeuristics-flaggetfDisableAutoIndexingOnSchemaUpdate for hele konfigurasjonssettet er angitt. Når dette flagget er angitt, deaktiveres indeksering av eksisterendeattributter automatisk i skjemaoppdateringen.%nHvis du vil sikre optimal ytelse fra denne AD LDS-forekomsten, må du fremtvinge en indeksoppretting. Hvis fDisableAutoIndexingOnSchemaUpdate er satttil 1, endrer du rootDSE-attributtet i schemaUpdateNow og setter det til 1. Hvis fDisableAutoIndexingOnSchemaUpdate istedet er satt til 2, endrer du rootDSE-attributtet i schemaUpdateIndicesNow og setter det til 1. Denne virkemåten kan ogsådeaktiveres ved å tilbakestille flagget fDisableAutoIndexingOnSchemaUpdate i dsHeuristics til 0. AD LDS-forekomster vilautomatisk gjenoppbygge indekser etter hvert som de mottar denne endringen. |
Compound index changes associated with a previous schema change are still pending. This is because the configuration set-widedSHeuristics flag fDisableAutoIndexingOnSchemaUpdate is set. This flag, when set, disables automatic indexing of existingattributes on schema update.%nTo ensure optimal performance from this AD LDS instance, force an index creation. If fDisableAutoIndexingOnSchemaUpdate is setto 1, perform a rootDSE attribute modification on schemaUpdateNow and set it to 1. If fDisableAutoIndexingOnSchemaUpdate isinstead set to 2, perform a rootDSE attribute modification on schemaUpdateIndicesNow and set it to 1. This behavior can alsobe turned off by resetting the fDisableAutoIndexingOnSchemaUpdate flag in dsHeuristics to 0; AD LDS instances willautomatically rebuild indices as they receive this change. |
| 0x80000BAD | Internal event: Active Directory Lightweight Directory Services is in the process of creating a new link table column for the following DirSyncSet attribute.%n%nAttribute identifier:%n%1%nAttribute name:%n%2%nTable type:%n%3 |
Internal event: Active Directory Lightweight Directory Services is in the process of creating a new link table column for the following DirSyncSet attribute.%n%nAttribute identifier:%n%1%nAttribute name:%n%2%nTable type:%n%3 |
| 0x80000BB0 | DirSync-Indeksendringer som er knyttet til en tidligere skjemaendring, venter fortsatt. Dette skyldes at dSHeuristics-flaggetfDisableAutoIndexingOnSchemaUpdate for hele konfigurasjonssettet er angitt. Når dette flagget er angitt, deaktiveres indeksering av eksisterendeattributter automatisk i skjemaoppdateringen.%nHvis du vil sikre optimal ytelse fra denne AD LDS-forekomsten, må du fremtvinge en indeksoppretting. Hvis fDisableAutoIndexingOnSchemaUpdate er satttil 1, endrer du rootDSE-attributtet i schemaUpdateNow og setter det til 1. Hvis fDisableAutoIndexingOnSchemaUpdate istedet er satt til 2, endrer du rootDSE-attributtet i schemaUpdateIndicesNow og setter det til 1. Denne virkemåten kan ogsådeaktiveres ved å tilbakestille flagget fDisableAutoIndexingOnSchemaUpdate i dsHeuristics til 0. AD LDS-forekomster vilautomatisk gjenoppbygge indekser etter hvert som de mottar denne endringen. |
DirSync index changes associated with a previous schema change are still pending. This is because the configuration set-widedSHeuristics flag fDisableAutoIndexingOnSchemaUpdate is set. This flag, when set, disables automatic indexing of existingattributes on schema update.%nTo ensure optimal performance from this AD LDS instance, force an index creation. If fDisableAutoIndexingOnSchemaUpdate is setto 1, perform a rootDSE attribute modification on schemaUpdateNow and set it to 1. If fDisableAutoIndexingOnSchemaUpdate isinstead set to 2, perform a rootDSE attribute modification on schemaUpdateIndicesNow and set it to 1. This behavior can alsobe turned off by resetting the fDisableAutoIndexingOnSchemaUpdate flag in dsHeuristics to 0; AD LDS instances willautomatically rebuild indices as they receive this change. |
| 0xC00003EB | Active Directory Lightweight Directory Services kan ikke initialiseres.%n%nKatalogtjenesten kan ikke gjenopprettes fra denne feilen.%n%nBrukerhandling%nGjenopprett den lokale katalogtjenesten fra sikkerhetskopieringsmediet.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services could not be initialized.%n%nThe directory service cannot recover from this error.%n%nUser Action%nRestore the local directory service from backup media.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00003F0 | KCC (Knowledge Consistency Checker) ble ikke initialisert. Konsekvensoppdateringer av replikeringstopologien for katalogtjenesten har blitt deaktivert. Den forrige replikeringstopologien brukes til katalogtjenesten har blitt startet på nytt.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
The Knowledge Consistency Checker (KCC) did not initialize. Consistency updates to the replication topology for the directory service have been disabled. The previous replication topology will be used until the directory service is restarted.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00003F2 | Det er ikke nok minne til å behandle overstyringer av logging. Et forsøk på å tildele følende mengde minne mislyktes.%n%nMinnetildeling (byte):%n%1%n%nDermed vil ingen overstyringer bli behandlet.%n%nBrukerhandling%nDu kan gjenoppta behandlingen ved å øke den tilgjengelige mengden fysisk eller virtuelt minne. |
There is not enough memory to process logging overrides. An attempt to allocate the following amount of memory failed.%n%nMemory allocation (bytes):%n%1%n%nAs a result, no overrides will be processed.%n%nUser Action%nTo resume processing, increase the available amount of physical or virtual memory. |
| 0xC00003F8 | Active Directory Lightweight Directory Services kan ikke initialiseres fordi skjemaet ikke ble lastet.%n%nBrukerhandling%nStart katalogtjenesten på nytt og prøv denne oppgaven en gang til. Hvis denne feilen vedvarer, gjenoppretter du katalogtjenesten fra sikkerhetskopieringsmediet. |
Active Directory Lightweight Directory Services could not be initialized because the schema could not be loaded.%n%nUser Action%nRestart the directory service and try this task again. If this error continues to occur, restore the directory service from backup media. |
| 0xC00003F9 | Prefikstilordningen kan ikke leses under skjemainitialiseringen.%n%nDette kan skyldes skade på eller inkonsekvens i databasen.%n%nBrukerhandling%nHvis denne feilen vedvarer, gjenoppretter du katalogtjenesten fra sikkerhetskopieringsmediet.%n%nTilleggsdata%nFeilverdi:%n%1 |
The prefix map could not be read during schema initialization.%n%nThis may be due to corruption or inconsistency of the database.%n%nUser Action%nIf this error continues to occur, restore the directory service from backup media.%n%nAdditional Data%nError value:%n%1 |
| 0xC00003FA | Konfigurasjonsinformasjon for Active Directory Lightweight Directory Services mangler fra følgende registerplassering.%n%nRegisternøkkel:%n%1%n%nBrukerhandling%nForsøk å gjenopprette registerinformasjonen. Hvis denne feilen vedvarer, gjenoppretter du katalogtjenesten fra sikkerhetskopieringsmediet. |
Active Directory Lightweight Directory Services configuration information is missing from the following registry location.%n%nRegistry key:%n%1%n%nUser Action%nAttempt to restore the registry information. If this error continues to occur, restore the directory service from backup media. |
| 0xC00003FB | Internal error: Unable to remove attribute for the schema cache. Stop and restart the directory service and try again. |
Internal error: Unable to remove attribute for the schema cache. Stop and restart the directory service and try again. |
| 0xC00003FD | Internal error: Some internal configuration information could not be set. Reinstall Active Directory Lightweight Directory Services. |
Internal error: Some internal configuration information could not be set. Reinstall Active Directory Lightweight Directory Services. |
| 0xC00003FE | Internal event: There is not enough memory to create a cache for objects. The performance of Active Directory Lightweight Directory Services will decrease considerably because this cache is ignored.%n%nUser Action%nIf this error continues to occur, restart the directory service. |
Internal event: There is not enough memory to create a cache for objects. The performance of Active Directory Lightweight Directory Services will decrease considerably because this cache is ignored.%n%nUser Action%nIf this error continues to occur, restart the directory service. |
| 0xC00003FF | Internal error: Active Directory Lightweight Directory Services could not retrieve or process data.%n%nUser Action%nRestart the directory service and try this task again.%n%nAdditional Data%nContext value:%n%1%nInternal ID:%n%2 |
Internal error: Active Directory Lightweight Directory Services could not retrieve or process data.%n%nUser Action%nRestart the directory service and try this task again.%n%nAdditional Data%nContext value:%n%1%nInternal ID:%n%2 |
| 0xC0000400 | KCC (Knowledge Consistency Checker) klarte ikke å stoppe etter at katalogtjenesten ble avsluttet eller startet på nytt.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
The Knowledge Consistency Checker (KCC) failed to stop after the directory service was shut down or restarted.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC0000401 | Internal error: Active Directory Lightweight Directory Services could not retrieve the distinguished name for the following queried object.%n%nObject:%n%1%n%nUser Action%nRestart the directory service and try this task again. If this error continues to occur, rename the object.%n%nAdditional Data%nError value:%n%2 |
Internal error: Active Directory Lightweight Directory Services could not retrieve the distinguished name for the following queried object.%n%nObject:%n%1%n%nUser Action%nRestart the directory service and try this task again. If this error continues to occur, rename the object.%n%nAdditional Data%nError value:%n%2 |
| 0xC0000403 | Internal error: Active Directory Lightweight Directory Services could not retrieve the instanceType attribute for the following queried object.%n%nObject:%n%1%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
Internal error: Active Directory Lightweight Directory Services could not retrieve the instanceType attribute for the following queried object.%n%nObject:%n%1%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
| 0xC0000404 | Internal error: Active Directory Lightweight Directory Services could not retrieve the child object information for the following queried object.%n%nBase object:%n%1%n%nAdditional Data%nError value:%n%2 |
Internal error: Active Directory Lightweight Directory Services could not retrieve the child object information for the following queried object.%n%nBase object:%n%1%n%nAdditional Data%nError value:%n%2 |
| 0xC0000406 | Internal error: Active Directory Lightweight Directory Services could not add an attribute to an object because either the syntax defined for the attribute is incorrect or the object does not exist.%n%nSyntax:%n%1%nAttribute OID:%n%2%nAttribute name:%n%3%n%nUser Action%nRestart the directory service and try this task again.%n%nAdditional Data%nInternal ID:%n%4 |
Internal error: Active Directory Lightweight Directory Services could not add an attribute to an object because either the syntax defined for the attribute is incorrect or the object does not exist.%n%nSyntax:%n%1%nAttribute OID:%n%2%nAttribute name:%n%3%n%nUser Action%nRestart the directory service and try this task again.%n%nAdditional Data%nInternal ID:%n%4 |
| 0xC0000408 | Internal event: Active Directory Lightweight Directory Services could not find the governsID attribute for the following schema class.%n%nSchema class:%n%1%n%nUser Action%nRestart the directory service and try this task again. |
Internal event: Active Directory Lightweight Directory Services could not find the governsID attribute for the following schema class.%n%nSchema class:%n%1%n%nUser Action%nRestart the directory service and try this task again. |
| 0xC0000409 | Internal error: Active Directory Lightweight Directory Services could not store schema class information to the cache. This local computer might have a memory allocation problem.%n%nUser Action%nIncrease physical memory or virtual memory. If this continues to occur, restart this local computer. |
Internal error: Active Directory Lightweight Directory Services could not store schema class information to the cache. This local computer might have a memory allocation problem.%n%nUser Action%nIncrease physical memory or virtual memory. If this continues to occur, restart this local computer. |
| 0xC000040A | Internal error: Active Directory Lightweight Directory Services could not remove the following class from the schema cache.%n%nClass:%n%2%n%nUser Action%nRestart the directory service and try this task again.%n%nAdditional Data%nInternal ID:%n%1 |
Internal error: Active Directory Lightweight Directory Services could not remove the following class from the schema cache.%n%nClass:%n%2%n%nUser Action%nRestart the directory service and try this task again.%n%nAdditional Data%nInternal ID:%n%1 |
| 0xC000040B | Internal error: Active Directory Lightweight Directory Services could not find the attributeID attribute for the following schema object.%n%nSchema object:%n%1%n%nUser Action%nIf this error continues to occur, restore the directory service from backup media. |
Internal error: Active Directory Lightweight Directory Services could not find the attributeID attribute for the following schema object.%n%nSchema object:%n%1%n%nUser Action%nIf this error continues to occur, restore the directory service from backup media. |
| 0xC000040C | Internal error: Active Directory Lightweight Directory Services could not find the attributeSyntax attribute for the following schema object.%n%nSchema object:%n%1%n%nUser Action%nIf this continues to occur, restore the directory service from backup media. |
Internal error: Active Directory Lightweight Directory Services could not find the attributeSyntax attribute for the following schema object.%n%nSchema object:%n%1%n%nUser Action%nIf this continues to occur, restore the directory service from backup media. |
| 0xC000040D | Internal error: Active Directory Lightweight Directory Services could not find the following attribute for the queried object.%n%nAttribute:%n%1%nObject:%n%2 |
Internal error: Active Directory Lightweight Directory Services could not find the following attribute for the queried object.%n%nAttribute:%n%1%nObject:%n%2 |
| 0xC000040E | Active Directory Lightweight Directory Services finner ikke NTDS-innstillingsobjektet som representerer denne forekomsten av katalogtjenesten.%n%n%nNTDS-innstillingsobjekt:%n%1%n%n%nActive Directory Lightweight Directory Services forsøker å fortsette.%n%n%nBrukerhandling%nHvis denne feilen vedvarer, gjenoppretter du katalogtjenesten fra sikkerhetskopieringsmediet.%n%n%nTilleggsinformasjon%nIntern ID:%n%2 |
Active Directory Lightweight Directory Services could not find the NTDS Settings object representing this instance of the directory service.%n%n%nNTDS Settings object:%n%1%n%n%nActive Directory Lightweight Directory Services will attempt to continue.%n%n%nUser Action%nIf this error continues to occur, restore the directory service from backup media.%n%n%nAdditional Information%nInternal ID:%n%2 |
| 0xC000040F | Internal event: Active Directory Lightweight Directory Services could not process the following object.%n%nObject:%n%1%n%nUser Action%nIncrease physical memory or virtual memory. If this error continues to occur, restart the local computer.%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
Internal event: Active Directory Lightweight Directory Services could not process the following object.%n%nObject:%n%1%n%nUser Action%nIncrease physical memory or virtual memory. If this error continues to occur, restart the local computer.%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
| 0xC0000410 | Internal error: Active Directory Lightweight Directory Services could not find the directory partition for the following object in the internal cache.%n%nObject:%n%1%n%nUser Action%nIf this continues to occur, restart the directory service. |
Internal error: Active Directory Lightweight Directory Services could not find the directory partition for the following object in the internal cache.%n%nObject:%n%1%n%nUser Action%nIf this continues to occur, restart the directory service. |
| 0xC0000411 | Internal error: Active Directory Lightweight Directory Services could not find the following directory partition.%n%nDirectory partition:%n%1 |
Internal error: Active Directory Lightweight Directory Services could not find the following directory partition.%n%nDirectory partition:%n%1 |
| 0xC0000413 | Internal event: Active Directory Lightweight Directory Services could not find the following directory system agent object for the directory service.%n%nDirectory system agent object:%n%1%n%nUser Action%nRestore the directory service from backup media.%n%nAdditional Data%nInternal ID:%n%2 |
Internal event: Active Directory Lightweight Directory Services could not find the following directory system agent object for the directory service.%n%nDirectory system agent object:%n%1%n%nUser Action%nRestore the directory service from backup media.%n%nAdditional Data%nInternal ID:%n%2 |
| 0xC0000414 | Internal event: Active Directory Lightweight Directory Services could not determine the computer name for this computer.%n%n%nUser Action%nIf this error continues to occur, restore the directory service from backup media.%n%n%nAdditional Data%nError value:%n%1%nInternal ID:%n%2 |
Internal event: Active Directory Lightweight Directory Services could not determine the computer name for this computer.%n%n%nUser Action%nIf this error continues to occur, restore the directory service from backup media.%n%n%nAdditional Data%nError value:%n%1%nInternal ID:%n%2 |
| 0xC0000416 | Internal error: The Active Directory Lightweight Directory Services database engine caused an exception with the following parameters.%n%nException:%n0x%1%nAddress:%n0x%2%nError value (if available):%n%3%n%nActive Directory Lightweight Directory Services cannot recover from this error.%n%nUser Action%nRestore the directory service from backup media. |
Internal error: The Active Directory Lightweight Directory Services database engine caused an exception with the following parameters.%n%nException:%n0x%1%nAddress:%n0x%2%nError value (if available):%n%3%n%nActive Directory Lightweight Directory Services cannot recover from this error.%n%nUser Action%nRestore the directory service from backup media. |
| 0xC0000419 | Et forsøk på å generere en referanse basert på den overordnede referansen mislyktes for følgende domenenavn.Active Directory Lightweight Directory Services finner ikke attributtet superiorDNSRoot for den angitte partisjonenskryssreferanseobjekt. Et forsøk på å generere en referanse automatisk mislyktes også.%n%nDomenenavn for objekt:%n%1%nDomenenavn for overordnet partisjon for DNS-rotkryssreferanse:%n%2 |
An attempt to generate a referral based on the superior reference failed for the following DN.Active Directory Lightweight Directory Services could not find the superiorDNSRoot attribute for the specified partition'scross-reference object. An attempt to generate a referral automatically has also failed.%n%nObject DN:%n%1%nSuperior DNS root cross-reference partition DN:%n%2 |
| 0xC000041C | Internal error: Active Directory Lightweight Directory Services could not find the masterDSA attribute for the following subordinate-reference object.%n%nSubordinate-reference object:%n%1%n%nUser Action%nRestart the directory service. |
Internal error: Active Directory Lightweight Directory Services could not find the masterDSA attribute for the following subordinate-reference object.%n%nSubordinate-reference object:%n%1%n%nUser Action%nRestart the directory service. |
| 0xC000041D | Internal error: Active Directory Lightweight Directory Services could not read the definition of an attribute becausethe system is out of memory.%n%nUser Action%nIncrease physical memory or virtual memory. If this continues to occur, restart the local computer. |
Internal error: Active Directory Lightweight Directory Services could not read the definition of an attribute becausethe system is out of memory.%n%nUser Action%nIncrease physical memory or virtual memory. If this continues to occur, restart the local computer. |
| 0xC000041E | Internal event: An Active Directory Lightweight Directory Services security error occurred while checking access rights.%n%nUser Action%nRestart the directory service. If this error continues to occur, restore this directory service from backup media.%n%nAdditional Data%nError value:%n%1 |
Internal event: An Active Directory Lightweight Directory Services security error occurred while checking access rights.%n%nUser Action%nRestart the directory service. If this error continues to occur, restore this directory service from backup media.%n%nAdditional Data%nError value:%n%1 |
| 0xC0000435 | Internal event: Scheduled periodic replication synchronization was not completed because Active Directory Lightweight Directory Services could not allocate enough memory for this task.%n%nUser Action%nIncrease physical memory or virtual memory. If this continues to occur, restart the local computer and try this task again. |
Internal event: Scheduled periodic replication synchronization was not completed because Active Directory Lightweight Directory Services could not allocate enough memory for this task.%n%nUser Action%nIncrease physical memory or virtual memory. If this continues to occur, restart the local computer and try this task again. |
| 0xC000043C | Internal event: Active Directory Lightweight Directory Services could not update the following object with changes received from the following source directory service. This is because an error occurred during the application of the changes to Active Directory Lightweight Directory Services on the directory service.%n%nObject:%n%1%nObject GUID:%n%2%nSource directory service:%n%3%n%nSynchronization of the directory service with the source directory service is blocked until this update problem is corrected.%n%nThis operation will be tried again at the next scheduled replication.%n%nUser Action%nRestart the local computer if this condition appears to be related to low system resources (for example, low physical or virtual memory).%n%nAdditional Data%nError value:%n%5 %4 |
Internal event: Active Directory Lightweight Directory Services could not update the following object with changes received from the following source directory service. This is because an error occurred during the application of the changes to Active Directory Lightweight Directory Services on the directory service.%n%nObject:%n%1%nObject GUID:%n%2%nSource directory service:%n%3%n%nSynchronization of the directory service with the source directory service is blocked until this update problem is corrected.%n%nThis operation will be tried again at the next scheduled replication.%n%nUser Action%nRestart the local computer if this condition appears to be related to low system resources (for example, low physical or virtual memory).%n%nAdditional Data%nError value:%n%5 %4 |
| 0xC0000442 | Direktereplikering kunne ikke utføres mellom følgende kilde- og måldomenekontrollere fordi en ustøttet områdetransport er konfigurert for følgende Connection-objekt. Connection-objektet som representerer områdereplikering fra kildedomenekontrolleren til måldomenekontrolleren, angir at den skrivbare katalogpartisjonen bør replikeres over områdetransporten.%n%nConnection-objekt:%n%1%nKatalogpartisjon:%n%4%nKildedomenekontroller:%n%2%nMåldomenekontroller:%n%3%nOmrådetransport:%n%5%n%nDomenekontrollere i samme domene, men på forskjellige områder, må bruke IP-transporten til replikering. Bare domenekontrollere på forskjellige domener kan replikere ved hjelp av andre transporter. |
Direct replication could not occur between the following source and destination domain controllers because an unsupported intersite transport is configured for the following Connection object. The Connection object representing intersite replication from the source domain controller to the destination domain controller indicates that the writeable directory partition should be replicated over the intersite transport.%n%nConnection object:%n%1%nDirectory partition:%n%4%nSource domain controller:%n%2%nDestination domain controller:%n%3%nIntersite transport:%n%5%n%nDomain controllers in the same domain, but in different sites are required to use the IP transport for replication. Only domain controllers in different domains can replicate using other transports. |
| 0xC0000452 | Internal event: The Active Directory Lightweight Directory Services replication dispatcher timed out after 30 minutes.%n%nUser Action%nIf this continues to occur, restart the directory service. |
Internal event: The Active Directory Lightweight Directory Services replication dispatcher timed out after 30 minutes.%n%nUser Action%nIf this continues to occur, restart the directory service. |
| 0xC0000453 | Fordelertråden for Active Directory Lightweight Directory Services-replikering kan ikke fortsette.%n%nBrukerhandling%nStart katalogtjenesten på nytt. |
The Active Directory Lightweight Directory Services replication dispatcher thread is unable to continue.%n%nUser Action%nRestart the directory service. |
| 0xC0000458 | Fordelertråden for Active Directory Lightweight Directory Services-replikering ble avsluttet på grunn av en feil. Et forsøk på å starte fordelertråden på nytt vil bli utført i løpet av de neste 35 minuttene av denne hendelsen.%n%nBrukerhandling%nHvis dette problemet vedvarer, starter du katalogtjenesten på nytt.%n%nTilleggsdata%nFeilverdi:%n%1 |
The Active Directory Lightweight Directory Services replication dispatcher thread exited with an error. An attempt to restart the replication dispatcher thread will be tried again within 35 minutes of this event.%n%nUser Action%nIf this event continues to occur, restart the directory service.%n%nAdditional Data%nError value:%n%1 |
| 0xC000045E | Finner ingen kilde for partisjonen %1 på dette området. Konsekvenskontrollen kan ikke opprette tilkoblinger for partisjoner som ikke har en kopi på dette området. Inngående replikering av denne partisjonen kan ikke utføres. Konfigurer en tilkobling for denne partisjonen manuelt. |
No source for partition %1 can be found within this site. The consistency checker cannot create connections for partitions which have no replica within the site. Inbound replication of this partition cannot be performed. Please manually configure a connection for this partition. |
| 0xC0000461 | Formatet for planattributtet for følgende objekt gjenkjennes ikke.%n%nObjekt:%n%1%n%nEn standardplan blir brukt i stedet. Denne hendelsen fortsetter å forekomme til planattributtet for dette objektet har blitt korrigert.%n%nBrukerhandling%nRediger planattributtet. |
The format of the schedule attribute of the following object is unrecognizable.%n%nObject:%n%1%n%nA default schedule will be substituted. This event will continue to occur until the schedule attribute on this object has been corrected.%n%nUser Action%nModify the schedule attribute. |
| 0xC0000465 | Installasjonsveiviseren (Dcpromo) for Active Directory Lightweight Directory Services kan ikke opprette en tilkobling til følgende domenekontroller.%n%nDomenekontroller:%n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The Active Directory Lightweight Directory Services Installation Wizard (Dcpromo) was unable to establish connection with the following domain controller.%n%nDomain controller:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC0000466 | Active Directory Lightweight Directory Services kan ikke opprette en tilkobling til den globale katalogen.%n%nTilleggsdata%nFeilverdi:%n%2 %3%nIntern ID:%n%1%n%nBrukerhandling:%nKontroller at en global katalog er tilgjengelig i skogen, og at den kan nås fra denne domenekontrolleren.Du kan bruke nltest-verktøyet til å analysere problemet. |
Active Directory Lightweight Directory Services was unable to establish a connection with the global catalog.%n%nAdditional Data%nError value:%n%2 %3%nInternal ID:%n%1%n%nUser Action:%nMake sure a global catalog is available in the forest, and is reachable from this domain controller.You may use the nltest utility to diagnose this problem. |
| 0xC0000467 | Det ble registrert en navnekonflikt under replikering av følgende katalogpartisjonsobjekt.%n%nKatalogpartisjonsobjekt:%n%1%nObjekt-GUID:%n%2%n%nDenne hendelsen forekommer vanligvis under replikering med en katalogpartisjon med samme navn, men med en annen objekt-GUID.%n%nBrukerhandling%nSlett det ugyldige katalogpartisjonsobjektet. |
A name conflict was detected while replicating the following directory partition object.%n%nDirectory partition object:%n%1%nObject GUID:%n%2%n%nThis event generally occurs when replicating with a directory partition with the same name, but a different object GUID.%n%nUser Action%nDelete the incorrect directory partition object. |
| 0xC000046A | KCC (Knowledge Consistency Checker) kan ikke fullføre topologien for følgende område.%n%nOmråde:%n%1%n%nEt forsøk på å fullføre topologien for dette området, vil bli forsøkt på nytt ved neste planlagte KCC-intervall (gjeldende standard er 15 minutter).%n%nTilleggsdata%nFeilverdi:%n%2 %4%nIntern ID:%n%3 |
The Knowledge Consistency Checker (KCC) was unable to complete the topology for the following site.%n%nSite:%n%1%n%nAn attempt to complete the topology for this site will be tried again at the next scheduled KCC interval (the current default is 15 minutes).%n%nAdditional Data%nError value:%n%2 %4%nInternal ID:%n%3 |
| 0xC000046B | Det oppstod en feil i KCC (Knowledge Consistency Checker) under tillegg av et Connection-objekt fra følgende kildekatalogtjeneste til følgende målkatalogtjeneste.%n%nKildekatalogtjeneste:%n%1%nMålkatalogtjeneste:%n%2%n%nTilleggsdata%nIntern ID for opprettingspunkt:%n%3 |
The Knowledge Consistency Checker (KCC) encountered an error while adding a Connection object from the following source directory service to the following destination directory service.%n%nSource directory service:%n%1%nDestination directory service:%n%2%n%nAdditional Data%nCreation Point Internal ID:%n%3 |
| 0xC000046F | Søket etter objekter i skjemakatalogpartisjonen mislyktes i løpet av følgende fase.%n%nFase:%n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The search for objects in the schema directory partition failed during the following phase.%n%nPhase:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC0000470 | Active Directory Lightweight Directory Services kan ikke opprette en indeks for følgende attributt.%n%nAttributtidentifikator:%n%1%nAttributtnavn:%n%2%n%nDet gjennomføres en skjemabufferoppdatering fem minutter etter loggingen av denne hendelsen, og det blir gjort et forsøk på å opprette en indeks for attributtet.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
Active Directory Lightweight Directory Services failed to create an index for the following attribute.%n%nAttribute identifier:%n%1%nAttribute name:%n%2%n%nA schema cache update will occur 5 minutes after the logging of this event and will attempt to create an index for the attribute.%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC0000474 | Active Directory Lightweight Directory Services kan ikke tildele følgende mengde minne under bufring av skjemaet.%n%nMinne (byte):%n%1%n%nBrukerhandling%nStart den lokale datamaskinen på nytt. Hvis dette problemet vedvarer, øker du det fysiske eller virtuelle minnet.%n%nTilleggsdata%nIntern ID:%n%2 |
Active Directory Lightweight Directory Services could not allocate the following amount of memory while caching the schema.%n%nMemory (bytes):%n%1%n%nUser Action%nRestart the local computer. If this event continues to occur, increase the physical memory or virtual memory.%n%nAdditional Data%nInternal ID:%n%2 |
| 0xC0000475 | Internal error: The search for objects in the schema directory partition during the following phase did not return the expected number of objects.%nPhase:%n%1%nExpected number of objects:%n%3%nActual objects returned:%n%2 |
Internal error: The search for objects in the schema directory partition during the following phase did not return the expected number of objects.%nPhase:%n%1%nExpected number of objects:%n%3%nActual objects returned:%n%2 |
| 0xC0000476 | Internal event: The auxiliary class identifier for the following schema class is not valid.%n%nAuxiliary class identifier:%n%3%nClass identifier:%n%1%nClass name:%n%2%n%nThe auxiliary class identifier is pointing to a class that does not exist, and the auxiliary class will be ignored. |
Internal event: The auxiliary class identifier for the following schema class is not valid.%n%nAuxiliary class identifier:%n%3%nClass identifier:%n%1%nClass name:%n%2%n%nThe auxiliary class identifier is pointing to a class that does not exist, and the auxiliary class will be ignored. |
| 0xC0000477 | Internal event: The following schema class has a non-auxiliary class incorrectly listed as an auxiliary class.%n%nClass identifier:%n%1%nClass name:%n%2%nNon-auxiliary class identifier:%n%3%nNon-auxiliary class name:%n%4%n%nThe non-auxiliary class will be ignored. |
Internal event: The following schema class has a non-auxiliary class incorrectly listed as an auxiliary class.%n%nClass identifier:%n%1%nClass name:%n%2%nNon-auxiliary class identifier:%n%3%nNon-auxiliary class name:%n%4%n%nThe non-auxiliary class will be ignored. |
| 0xC0000478 | Internal event: The auxiliary schema class identifier %1 (class name %2) derives from structural schema class identifier %3 (class name %4). This error was ignored and the inheritance was processed anyway. |
Internal event: The auxiliary schema class identifier %1 (class name %2) derives from structural schema class identifier %3 (class name %4). This error was ignored and the inheritance was processed anyway. |
| 0xC0000479 | Internal event: The abstract schema class identifier %1 (class name %2) derives from non-abstract schema class identifier %3 (class name %4). This error was ignored and the inheritance was processed anyway. |
Internal event: The abstract schema class identifier %1 (class name %2) derives from non-abstract schema class identifier %3 (class name %4). This error was ignored and the inheritance was processed anyway. |
| 0xC000047E | Forsøket på å opprette en ny databasekolonne for følgende nye attributt mislyktes.%n%nAttributtidentifikator:%n%1%nAttributtnavn:%n%2%n%nAttributtdefinisjonen ble ignorert.%n%nTilleggsdata%nFeilverdi:%n%3 |
The attempt to create a new database column for the following new attribute failed.%n%nAttribute identifier:%n%1%nAttribute name:%n%2%n%nThe attribute definition was ignored.%n%nAdditional Data%nError value:%n%3 |
| 0xC0000486 | Det oppstod en feil i Active Directory Lightweight Directory Services under frigjøring av minne.%n%nBrukerhandling%nStart katalogtjenesten på nytt. |
Active Directory Lightweight Directory Services encountered an error while freeing memory.%n%nUser Action%nRestart the directory service. |
| 0xC0000487 | Et ugyldig tegn ble funnet i følgende posisjon og streng under behandling av en registernøkkel for hendelsesloggoverstyring.%n%nPosisjon:%n%1%nStreng:%n%2%n%nIngen hendelsesloggoverstyringer blir behandlet før registerverdien er korrigert. |
A character that is not valid was found at the following position and string while processing an event log override registry key.%n%nPosition:%n%1%nString:%n%2%n%nNo event logging overrides will be processed until the registry value is corrected. |
| 0xC0000488 | Følgende registerverdi for loggoverstyringer inneholder et antall tegn som er ugyldige.%n%nRegisterverdi:%n%1%n%nIngen hendelsesloggoverstyringer blir behandlet før registerverdien er korrigert. |
The following registry value for logging overrides contains a number of characters that is not valid.%n%nRegistry value:%n%1%n%nNo event logging overrides will be processed until the registry value is corrected. |
| 0xC0000489 | Internal event: Active Directory Lightweight Directory Services could not build the Address Book hierarchy table. The next attempt will occur at the following interval.%n%nInterval (minutes):%n%1%n%nAddress Book searches will be disabled on this domain controller during this interval. |
Internal event: Active Directory Lightweight Directory Services could not build the Address Book hierarchy table. The next attempt will occur at the following interval.%n%nInterval (minutes):%n%1%n%nAddress Book searches will be disabled on this domain controller during this interval. |
| 0xC000048D | Internal error: Active Directory Lightweight Directory Services was unable to allocate a critical new directory server GUID after an install or restore operation. As a result, Active Directory Lightweight Directory Services will not be able to start up in normal mode.%n%nUser Action%nReinstall the Server operating system and either attempt to restore the directory server from backup media again or promote the machine to be a new directory server.%n%nAdditional Data%nError value:%n%1 %2 |
Internal error: Active Directory Lightweight Directory Services was unable to allocate a critical new directory server GUID after an install or restore operation. As a result, Active Directory Lightweight Directory Services will not be able to start up in normal mode.%n%nUser Action%nReinstall the Server operating system and either attempt to restore the directory server from backup media again or promote the machine to be a new directory server.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC0000490 | Internal error: An Active Directory Lightweight Directory Services error has occurred.%n%nAdditional Data%nError value (decimal):%n%1%nError value (hex):%n%2%nInternal ID:%n%3 |
Internal error: An Active Directory Lightweight Directory Services error has occurred.%n%nAdditional Data%nError value (decimal):%n%1%nError value (hex):%n%2%nInternal ID:%n%3 |
| 0xC0000491 | Active Directory Lightweight Directory Services kan ikke tildele den nødvendige mengden minne.%n%nMinne (byte):%n%1%n%nActive Directory Lightweight Directory Services er fortsatt tilgjengelig, men fungerer kanskje ikke optimalt.%n%nBrukerhandling%nStart denne datamaskinen på nytt. Hvis dette problemet vedvarer, øker du det tilgjengelige fysiske eller virtuelle minnet.%n%nTilleggsdata%nIntern ID:%n%2 |
Active Directory Lightweight Directory Services could not allocate the needed amount of memory.%n%nMemory (bytes):%n%1%n%nActive Directory Lightweight Directory Services will continue to operate, but may not function correctly.%n%nUser Action%nRestart this computer. If this condition continues, increase the available physical or virtual memory.%n%nAdditional Data%nInternal ID:%n%2 |
| 0xC0000492 | Internal error: The expression %1 was false at line %2 of file %3. Please contact Microsoft Product Support Services for assistance. |
Internal error: The expression %1 was false at line %2 of file %3. Please contact Microsoft Product Support Services for assistance. |
| 0xC00004AC | Internal error: An error occurred while granting rights to the Domain Administrators group for administering the following Server object.%n%nObject:%n%1%n%nUser Action%nAn enterprise administrator needs to manually grant Full Control rights for this object to the Domain Administrators group. |
Internal error: An error occurred while granting rights to the Domain Administrators group for administering the following Server object.%n%nObject:%n%1%n%nUser Action%nAn enterprise administrator needs to manually grant Full Control rights for this object to the Domain Administrators group. |
| 0xC00004AE | Internal error: Active Directory Lightweight Directory Services failed to restore from backup media.%n%nAdditional Data%nError value:%n%1 (0x%2)%n%3 |
Internal error: Active Directory Lightweight Directory Services failed to restore from backup media.%n%nAdditional Data%nError value:%n%1 (0x%2)%n%3 |
| 0xC00004B5 | Internal error: The security descriptor propagation task found an incorrect or missing object class for the following object.%n%nObject:%n%1%n%nSecurity descriptor propagation will not take place on this object’s child objects.%n%nAdditional Data%nError value:%n%2 %3 |
Internal error: The security descriptor propagation task found an incorrect or missing object class for the following object.%n%nObject:%n%1%n%nSecurity descriptor propagation will not take place on this object’s child objects.%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC00004B7 | Internal event: An internal asynchronous attempt to update the schema cache failed with an error.%n%nActive Directory Lightweight Directory Services will automatically retry the operation after 5 minutes. The following number of retries will be attempted.%n%nRetries:%n%2%nCurrent update attempt:%n%3%n%nAdditional Data%nError value:%n%1 |
Internal event: An internal asynchronous attempt to update the schema cache failed with an error.%n%nActive Directory Lightweight Directory Services will automatically retry the operation after 5 minutes. The following number of retries will be attempted.%n%nRetries:%n%2%nCurrent update attempt:%n%3%n%nAdditional Data%nError value:%n%1 |
| 0xC00004B8 | Et internt asynkront forsøk på å oppdatere skjemabufferen mislyktes på grunn av en feil.%n%nActive Directory Lightweight Directory Services forsøker ikke operasjonen på nytt. Nylige skjemaoppdateringer er kanskje ikke tilgjengelige før denne bufferen har blitt oppdatert.%n%nBrukerhandling%nUtfør en eksplisitt og synkron skjemabufferoppdatering, eller start katalogtjenesten på nytt.%n%nTilleggsdata%nFeilverdi:%n%1 |
An internal asynchronous attempt to update the schema cache failed with an error.%n%nActive Directory Lightweight Directory Services will not retry the operation again. Recent schema updates may not be available until this cache is updated.%n%nUser Action%nPerform an explicit synchronous schema cache update or restart the directory service.%n%nAdditional Data%nError value:%n%1 |
| 0xC00004B9 | Active Directory Lightweight Directory Services kan ikke angi riktige tillatelser for å aktivere sikkerhetskontroll.%n%nDet fører til at alle sikkerhetskontroller mislykkes, og sikkerhetskontroll kan ikke lenger utføres.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services was unable to set appropriate privileges to enable security auditing.%n%nAs a result, all security checks will fail and security auditing will be unavailable.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00004BA | En ny LDAP-tilkobling ble lukket av katalogtjenesten fordi maksimalt antall tilkoblinger ble nådd.%n%nMaksimal tilkoblingsgrense:%n%1%n%nDette problemet blir ikke logget på nytt for følgende intervall.%n%nIntervall (minutter):%n%2%n%nBrukerhandling%nVurder å endre denne grensen ved hjelp av LDAP-spørringspolicyen. |
A new LDAP connection was closed by the directory service because the maximum number of connections has been reached.%n%nMaximum connection limit:%n%1%n%nThis condition will not be logged again for the following interval.%n%nInterval (minutes):%n%2%n%nUser Action%nConsider changing this limit through the LDAP query policy. |
| 0xC00004C6 | Sertifikatet som presenteres av følgende katalogtjeneste for områdereplikering, ble avvist av sertifiseringsinstansen.%n%nKatalogtjeneste:%n%1%nSertifiseringsinstans:%n%2%n%nReplikeringstilgang har blitt avslått til katalogtjenesten som er nevnt ovenfor, og sertifikatet har blitt forkastet.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The certificate presented by the following directory service for intersite replication was rejected by the certification authority.%n%ndirectory service:%n%1%nCertification authority:%n%2%n%nReplication access has been denied to the directory service listed above and the certificate has been discarded.%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC00004C7 | Sertifikatet som presenteres av følgende katalogtjeneste for områdereplikering, ble avvist fordi sertifiseringsinstansen ikke er klarert.%n%nKatalogtjeneste:%n%1%nSertifiseringsinstans:%n%2%n%nReplikeringstilgang har blitt avslått til katalogtjenesten som er nevnt ovenfor, og sertifikatet har blitt forkastet.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The certificate presented by the following directory service for intersite replication was rejected because the certification authority is not trusted.%n%ndirectory service:%n%1%nCertification authority:%n%2%n%nReplication access has been denied to the directory service listed above and the certificate has been discarded.%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC00004CC | Systemovervåking kan ikke åpne ytelsestellere for Active Directory Lightweight Directory Services. Et forsøk på å spørre følgende registernøkkel for ytelsestelleren mislyktes.%n%nRegisternøkkel:%n%3%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
System Monitor was unable to open Active Directory Lightweight Directory Services performance counters. An attempt to query the following performance counter registry key failed.%n%nRegistry key:%n%3%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00004CD | Systemovervåking kan ikke åpne ytelsestellere for Active Directory Lightweight Directory Services. Et forsøk på å åpne et delt minne mislyktes.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
System Monitor was unable to open Active Directory Lightweight Directory Services performance counters. An attempt to open shared memory failed.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00004CE | Systemovervåking kan ikke åpne ytelsestellere for Active Directory Lightweight Directory Services. Et forsøk på å tilordne til et delt minne mislyktes.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
System Monitor was unable to open Active Directory Lightweight Directory Services performance counters. An attempt to map to shared memory failed.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00004CF | Systemovervåking kan ikke åpne ytelsestellere for Active Directory Lightweight Directory Services. Et forsøk på å åpne følgende registernøkkel for ytelsestelleren mislyktes.%n%nRegisternøkkel:%n%3%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
System Monitor was unable to open Active Directory Lightweight Directory Services performance counters. An attempt to open the following performance counter registry key failed.%n%nRegistry key:%n%3%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00004D2 | Internal event: A logon attempt failed because an attempt to lookup Windows account information failed. Error %1. |
Internal event: A logon attempt failed because an attempt to lookup Windows account information failed. Error %1. |
| 0xC00004D3 | Internal event: Can't write offline Address Book to folder. Component %1 returns error %2. |
Internal event: Can't write offline Address Book to folder. Component %1 returns error %2. |
| 0xC00004D4 | Navnet på denne datamaskinen (%1) samsvarer ikke med navnet som er registrert i katalogdatabasen (%2) for Windows Server. Hvis du har gitt nytt navn til denne datamaskinen, må du endre navnet tilbake til %2. Hvis du har gjenopprettet denne databasen fra en sikkerhetskopi, må den gjenopprettes på den samme datamaskinen som ble brukt til sikkerhetskopieringen. |
The name of this computer (%1) does not match the name recorded in the Windows Server directory database (%2). If you have renamed this computer, you must change the name back to %2. If you have restored this database from a backup, it must be restored on the same computer that was used for the backup. |
| 0xC00004D5 | Feilen %1 oppstod under videresending av en operasjon til Security Accounts Manager. |
Error %1 occurred while forwarding an operation to the Security Accounts Manager. |
| 0xC00004D6 | Internal error: Active Directory Lightweight Directory Services was unable to initialize network connections for incoming LDAP requests.%n%nAdditional Data%nError value:%n%2 %3 |
Internal error: Active Directory Lightweight Directory Services was unable to initialize network connections for incoming LDAP requests.%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC00004D9 | OID-området er fullt. Ingen flere attributter eller klasser kan legges til. |
OID Space is Full. No more Attributes or Classes can be added. |
| 0xC00004E8 | Internal error: Active Directory Lightweight Directory Services could not find the directory partition container object.%n%nDirectory partition container:%n%1%n%nUser Action%nRestart the directory service. If this continues to occur, restore from backup media.%n%nAdditional Data%nError value:%n%2 %3 |
Internal error: Active Directory Lightweight Directory Services could not find the directory partition container object.%n%nDirectory partition container:%n%1%n%nUser Action%nRestart the directory service. If this continues to occur, restore from backup media.%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC00004EE | Overføringen av sikkerhetsbeskrivelsen kan ikke behandle en overføringshendelse som starter fra følgende beholder.%n%nBeholder:%n%2%n%nDette fører til at overføringen av sikkerhetsbeskrivelsen utsetter behandlingen i 30 minutter, eller venter til en sikkerhetsbeskrivelse er endret for et objekt.%n%nBrukerhandling%nSjekk sikkerhetsbeskrivelsen for denne beholderen.%n%nTilleggsdata%nFeilverdi:%n%1 %3 |
The security descriptor propagation task could not process a propagation event starting from the following container.%n%nContainer:%n%2%n%nAs a result, the security descriptor propagation task will either suspend processing for thirty minutes or wait until a security descriptor has changed for any object.%n%nUser Action%nCheck the security descriptor on this container.%n%nAdditional Data%nError value:%n%1 %3 |
| 0xC000051D | LDAP-serveren kan ikke starte fordi initialiseringen av Winsock mislyktes. Katalogtjenesten kan ikke svare på LDAP-spørringer i løpet av denne økten.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
The LDAP server could not start because Winsock initialization failed. The directory service will be unable to respond to LDAP queries during this session.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000051F | KCC (Knowledge Consistency Checker) har registrert problemer med følgende katalogpartisjon.%n%nKatalogpartisjon:%n%1%n%nDet er ikke nok informasjon om områdetilkobling for at KCC skal kunne opprette en replikeringstopologi som omfatter hele treet. Eller én eller flere katalogservere med denne katalogpartisjonen kan ikke replikere katalogpartisjonsinformasjonen. Dette skyldes mest sannsynlig utilgjengelige katalogservere.%n%nBrukerhandling%nUtfør én av følgende handlinger:%n- Publiser tilstrekkelig informasjon om områdetilkobling slik at KCC kan definere en metode for at katalogpartisjonen kan nå frem til dette området. Dette er det foretrukkede alternativet.%n- Legg til et Connection-objekt i en katalogtjeneste som inneholder katalogpartisjonen på dette området, fra en katalogtjeneste som inneholder den samme katalogpartisjonen på et annet område.%n%nHvis ingen av disse oppgavene løser dette problemet, kan du se tidligere hendelser som er logget av KCC, som identifiserer utilgjengelige katalogservere. |
The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.%n%nDirectory partition:%n%1%n%nThere is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.%n%nUser Action%nPerform one of the following actions:%n- Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.%n- Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.%n%nIf neither of the tasks correct this condition, see previous events logged by the KCC that identify the inaccessible directory servers. |
| 0xC0000520 | Et kall til Intersite Messaging-tjenesten som angir følgende transport, mislyktes.%n%nTransport:%n%1%n%nDet fører til at KCC (Knowledge Consistency Checker) ikke kan konfigurere en riktig områdereplikeringstopologi.%n%nBrukerhandling%nBekreft at Intersite Messaging-tjenesten kjører.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
A call to the Intersite Messaging service that specifies the following transport failed.%n%nTransport:%n%1%n%nAs a result, the Knowledge Consistency Checker (KCC) cannot configure a correct intersite replication topology.%n%nUser Action%nVerify that the Intersite Messaging service is running.%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC0000523 | Skjemabufferen for Active Directory Lightweight Directory Services kan ikke arve alle attributter for følgende klasse.%n%nKlasse-ID:%n%1%nKlassenavn:%n%2%n%nSkjemabufferen er ufullstendig.%n%nBrukerhandling%nOppdater skjemabufferen. |
Active Directory Lightweight Directory Services schema cache failed to inherit all attributes for the following class.%n%nClass ID:%n%1%nClass name:%n%2%n%nThe schema cache is incomplete.%n%nUser Action%nRefresh the schema cache. |
| 0xC000055D | Intersite Messaging-tjenesten kan ikke motta meldinger for følgende tjeneste via følgende transport. Spørringen etter meldinger mislyktes.%n%nTjeneste:%n%1%nTransport:%n%2%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The Intersite Messaging service could not receive any messages for the following service through the following transport. The query for messages failed.%n%nService:%n%1%nTransport:%n%2%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC000055E | Intersite Messaging-tjenestens forespørsel etter antallet områder som er sammenkoblet via følgende transport, mislyktes.%n%nTransport:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service request for the number of sites interconnected through the following transport failed.%n%nTransport:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC000055F | Intersite Messaging-tjenestens forespørsel etter hvilke domenekontrollere som kan kommunisere til og fra følgende område via følgende transport, mislyktes.%n%nOmråde:%n%1%nTransport:%n%2%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The Intersite Messaging service request for which domain controllers can communicate to and from the following site through the following transport failed.%n%nSite:%n%1%nTransport:%n%2%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC0000560 | Intersite Messaging-tjenestens forespørsel etter planen som følgende områder er koblet til via følgende transport, mislyktes.%n%nOmråde:%n%1%nOmråde:%n%2%nTransport:%n%3%n%nTilleggsdata%nFeilverdi:%n%5 %4 |
The Intersite Messaging service request for the schedule at which the following sites are connected through the following transport failed.%n%nSite:%n%1%nSite:%n%2%nTransport:%n%3%n%nAdditional Data%nError value:%n%5 %4 |
| 0xC0000561 | Initialiseringen av følgende transport mislyktes.%n%nTransport:%n%1%nDLL-fil for transport:%n%2%n%nBrukerhandling%nBekreft at DLL-filen for transporten finnes og har blitt registrert på riktig måte.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The initialization of the following transport failed.%n%nTransport:%n%1%nTransport DLL:%n%2%n%nUser Action%nVerify that the transport DLL is present and has been registered properly.%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC0000562 | Endringer som har blitt gjort i følgende transportobjekt, kan ikke formidles til Active Directory Lightweight Directory Services.%n%nTransport:%n%1%n%nDet fører til at denne transporten ikke kunne oppdateres og har blitt lukket.%n%nBrukerhandling%nStart Intersite Messaging-tjenesten på nytt, eller start den lokale domenekontrolleren på nytt.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
Changes made to the following transport object could not be communicated to Active Directory Lightweight Directory Services.%n%nTransport:%n%1%n%nAs a result, this transport could not be updated and has been closed.%n%nUser Action%nRestart the Intersite Messaging service or restart the local domain controller.%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC0000565 | Planattributtet for følgende områdekoblingsobjekt er ugyldig.%n%nOmrådekoblingsobjekt:%n%1%n%nDet fører til at denne planen ignoreres.%n%nBrukerhandling%nBruk Active Directory Sites and Services til å endre planattributtet. |
The schedule attribute of the following site link object is not valid.%n%nSite link object:%n%1%n%nAs a result, this schedule will be ignored.%n%nUser Action%nUse Active Directory Sites and Services to modify the schedule attribute. |
| 0xC0000566 | Planattributtet for følgende områdekoblingsobjekt er konfigurert på en slik måte at områdene det refererer til, aldri er tilkoblet.%n%nOmrådekoblingsobjekt:%n%1%n%nDet fører til at denne planen ignoreres.%n%nBrukerhandling%nBruk Active Directory Sites and Services til å redigere planattributtet. |
The schedule attribute of the following site link object is configured in a way that the sites it references are never connected.%n%nSite link object:%n%1%n%nAs a result, this schedule will be ignored.%n%nUser Action%nUse Active Directory Sites and Services to modify the schedule attribute. |
| 0xC0000567 | Den lokale domenekontrolleren har ikke et DomainController X.509-sertifikat.%n%nFør dette sertifikatet legges til, mislykkes Active Directory Lightweight Directory Services-replikering mellom den lokale domenekontrolleren og domenekontrollere på alle andre områder.%n%nBrukerhandling%nLegg til dette sertifikatet i den lokale domenekontrolleren. |
The local domain controller has no DomainController X.509 certificate.%n%nUntil this certificate is added, Active Directory Lightweight Directory Services replication between the local domain controller and domain controllers in all other sites will fail.%n%nUser Action%nAdd this certificate to the local domain controller. |
| 0xC000056C | En annen katalogserver har forsøkt å replikere et objekt som ikke finnes i den lokale Active Directory Lightweight Directory Services-databasen, til denne katalogserveren. Objektet er kanskje slettet og datasanering er kanskje allerede utført (utløpstiden/levetiden eller mer har gått siden forrige gang objektet ble slettet) på denne katalogserveren. Attributtsettet som er inkludert i oppdateringsforespørselen, er ikke tilstrekkelig til å opprette objektet. Objektet blir forespurt på nytt med et fullstendig attributtsett, og det blir opprettet på nytt på denne katalogserveren.%nDenne hendelsen logges fordi kildedomenekontrolleren inneholder et etterlatt objekt som ikkefinnes på den lokale domenekontrollerens kopi av Active Directory Lightweight Directory Services-databasen, og den lokale domenekontrolleren har *ikke* følgenderegisternøkkel aktivert for å sikre streng replikeringskonsekvens. Streng replikeringskonsekvenshindrer at etterlatte objekter finnes på en kildedomenekontroller fra ny replikering til en måldomenekontrollersom allerede har behandlet slettingen. Denne registernøkkelen er ikke angitt, og derfor blir ikke objektetreplikert og opprettet på nytt i den lokale Active Directory Lightweight Directory Services-databasen.%n%nDen beste løsningen på dette problemet er å identifisere og fjerne alle etterlatte objekter i konfigurasjonssettet,starte med de skrivbare og skrivebeskyttede partisjonene som inneholder objektet det refereres til i denne hendelsen, ogderetter aktivere følgende registernøkkel for å sikre streng replikeringskonsekvens.%n%n%nKildedomenekontroller (transportspesifikk nettverksadresse):%n%4%nObjekt:%n%1%nObjekt-GUID:%n%2%nKatalogpartisjon:%n%3%nHøyeste nummer for oppdateringssekvens for målegenskap:%n%5%nBrukerhandling:%nBekreft at du vil at dette objektet ikke skal slettes. Du avbryter gjenoppretting av fremtidige identiske objekter ved å opprette følgende registernøkkel.%nRegisternøkkel:%nHKLM\\%7\\%6%nHandlingsplanen for å gjenopprette etter denne feilen, finner du på http://support.microsoft.com/?id=314282.%n%nHvis både kilde- og måldomenekontrollerne er domenekontrollere for Windows Server 2003, installerer du støtteverktøyene som finnes påinstallasjons-CDen. Hvis du vil vise hvilke objekter som ville blitt slettet uten å faktisk utføreslettingen, kjører du kommandoen \"repadmin /removelingeringobjects /ADVISORY_MODE\".Hendelsesloggene i kildedomenekontrolleren nummererer alle etterlatte objekter. Du fjerner etterlatte objekterfra kildedomenekontrolleren ved å kjørekommandoen \"repadmin /removelingeringobjects \".%n%nHvis kilde- eller måldomenekontrolleren er en domenekontroller for Windows 2000 Server, finner du mer informasjon om hvordan dufjerner etterlatte objekter i kildedomenekontrolleren på http://support.microsoft.com/?id=314282, eller fraMicrosofts kundestøttetjeneste.%n%nReplikeringsfeil mellom domenekontrollere som deler en felles partisjon, kan hindre at bruker- og datamaskinkontoer,klareringsforhold, passord for klareringsforholdene, sikkerhetsgrupper,sikkerhetsgruppemedlemskap og andre Active Directory Lightweight Directory Services-konfigurasjonsdata varierer fra domenekontroller til domenekontroller,noe som kan påvirke muligheten til å logge på, søke etter interessante objekter og utføre andre kritiske operasjoner.Disse inkonsekvensene løses først når replikeringsfeil løses. Domenekontrollere som mislykkes på grunn avat den inngående replikeringen slettet objekter i løpet av utløpstiden/levetiden, forblir inkonsekvente tiletterlatte objekter fjernes manuelt av en systemansvarlig fra hver lokale domenekontroller.%n%nEtterlatte objekter kan stoppes ved å sørge for at alle domenekontrollere i skogensom kjører Active Directory Lightweight Directory Services, er tilknyttet ved hjelp av en tilkoblingstopologi som omfatter hele treet, og som utførerinngående replikering før antall dager i utløpstiden er omme. |
Another directory server has attempted to replicate into this directory server an object which is not present in the local Active Directory Lightweight Directory Services database. The object may have been deleted and already garbage collected (a tombstone lifetime or more has passed since the object was deleted) on this directory server. The attribute set included in the update request is not sufficient to create the object. The object will be re-requested with a full attribute set and re-created on this directory server.%nThis event is being logged because the source DC contains a lingering object which does notexist on the local DCs copy of Active Directory Lightweight Directory Services database and the local DC does *not* have the followingregistry key enabled to ensure strict replication consistency. Strict replication consistencyprevents lingering objects residing on a source DC from re-replicating to a destination DCthat has already processed the deletion. Since this registry key is not set, the object willbe re-replicated and recreated in the local Active Directory Lightweight Directory Services database.%n%nThe best solution to this problem is to identify and remove all lingering objects in the configuration set,starting with the writable and read-only partitions containing the object referenced in this event, andthen enable the following registry key to ensure strict replication consistency.%n%n%nSource DC (Transport-specific network address):%n%4%nObject:%n%1%nObject GUID:%n%2%nDirectory partition:%n%3%nDestination highest property USN:%n%5%nUser Action:%nVerify the continued desire for the existence of this object. To discontinue re-creation of future similar objects, the following registry key should be created.%nRegistry Key:%nHKLM\\%7\\%6%nThe action plan to recover from this error can be found at http://support.microsoft.com/?id=314282.%n%nIf both the source and destination DCs are Windows Server 2003 DCs, then install the support tools included on theinstallation CD. To see which objects would be deleted without actually performing thedeletion run \"repadmin /removelingeringobjects /ADVISORY_MODE\".The event logs on the source DC will enumerate all lingering objects. To remove lingering objectsfrom a source domain controller run\"repadmin /removelingeringobjects \".%n%nIf either source or destination DC is a Windows 2000 Server DC, then more information on how toremove lingering objects on the source DC can be found at http://support.microsoft.com/?id=314282 or fromyour Microsoft support personnel.%n%nReplication errors between DCs sharing a common partition can prevent user and computer accounts,trust relationships, their passwords, security groups,security group memberships and other Active Directory Lightweight Directory Services configuration data to vary between DCs,affecting the ability to log on, find objects of interest and perform other critical operations.These inconsistencies are resolved once replication errors are resolved. DCs that fail to inboundreplicate deleted objects within tombstone lifetime number of days will remain inconsistent untillingering objects are manually removed by an administrator from each local DC.%n%nLingering objects may be prevented by ensuring that all domain controllers in the forest arerunning Active Directory Lightweight Directory Services, are connected by a spanning tree connection topology and performinbound replication before Tombstone Live number of days pass. |
| 0xC000056D | Kan ikke senke nivået på SAM (Security Account Manager). |
The security account manager (SAM) could not be demoted. |
| 0xC000056E | En sikkerhetsidentifikator (SID) for det nye lokale kontodomenet kan ikke angis i SAM-databasen (Security Account Manager). |
A security identifier (SID) for the new local account domain could not be set in the security account manager (SAM) database. |
| 0xC000056F | Installasjonsveiviseren (Dcpromo.exe) for Active Directory Lightweight Directory Services kan ikke konfigurere datamaskinkontoen %1 på den eksterne Active Directory Lightweight Directory Services-forekomsten %2.%nBekreft at brukeren som kjører Dcpromo.exe, har brukerrettigheten Enable computer and user accounts to be trusted for delegation i policyen for standard domenekontrollere.%nHvis du vil ha mer informasjon, kan du se løsningsdelen på http://go.microsoft.com/fwlink/?LinkId=178406.%nFeilen var: |
The Active Directory Lightweight Directory Services Installation Wizard (Dcpromo.exe) could not configure the computer account %1 on the remote Active Directory Lightweight Directory Services instance %2.%nVerify that the user running Dcpromo.exe is granted the \"Enable computer and user accounts to be trusted for delegation\" user right in the Default Domain Controllers Policy.%nFor more information, see the resolution section of http://go.microsoft.com/fwlink/?LinkId=178406.%nThe error was: |
| 0xC0000571 | Forsøk på å oppdatere Active Directory Lightweight Directory Services-databasen mislykkes.%n%nActive Directory Lightweight Directory Services kan ikke logge på brukere før dette problemet er løst. Det fører til at tjenesten Net Logon har stoppet midlertidig.%n%nBrukerhandling%nKontroller at du har nok harddiskplass på volumene der Active Directory Lightweight Directory Services-databasen og -loggfilene er lagret.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Attempts to update the Active Directory Lightweight Directory Services database are failing.%n%nActive Directory Lightweight Directory Services will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.%n%nUser Action%nEnsure that adequate hard disk space is available on the volumes where the Active Directory Lightweight Directory Services database and log files reside.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC0000574 | Active Directory Lightweight Directory Services kan ikke overføre driftsovervåkerrollene til en annen Active Directory Lightweight Directory Services-forekomst. Mulige årsaker kan være følgende: Ingen andre AD LDS-forekomster er tilkoblet til å motta en driftsovervåkerrolle, eller AD LDS har registrert at en AD LDS-forekomst ikke lenger finnes. |
Active Directory Lightweight Directory Services was unable to transfer the operations master roles to another Active Directory Lightweight Directory Services instance. Possible causes include: No other AD LDS instance is online to receive an operations master role, or AD LDS has a record of a AD LDS instance that no longer exists. |
| 0xC0000577 | Active Directory Lightweight Directory Services kan ikke flytte standardskjemaet til %1. |
Active Directory Lightweight Directory Services could not move the default schema to %1. |
| 0xC0000578 | Active Directory Lightweight Directory Services kan ikke angi registernøkkelverdien for produkttypen for å senke nivået på denne Active Directory Lightweight Directory Services-forekomsten. |
Active Directory Lightweight Directory Services was unable to set the product type registry key value to demote this Active Directory Lightweight Directory Services instance. |
| 0xC000057B | Kopiering av Active Directory Lightweight Directory Services-databasen mislyktes i løpet av følgende operasjon.%n%nOperasjon:%n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The Active Directory Lightweight Directory Services database dump failed during the following operation.%n%nOperation:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC000057D | Intersite Messaging-tjenesten som bruker SMTP-transporten, kunne ikke lese SMTP-e-postmeldingen som er lagret i følgende fil. Meldingen kunne ikke hentes, deler av meldingen manglet, eller deler av meldingen var ugyldig.%n%nFil:%n%1%nFilmappe:%n%2%nTil-felt:%n%5%nFra-felt:%n%6%nEmne-felt:%n%7%n%nDenne meldingen ignoreres og slettes.%n%nBrukerhandling%nKontroller at feilkonfigurerte programmer ikke sender e-post til feil konto.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The Intersite Messaging service using the SMTP transport failed to read the SMTP mail message stored in the following file. The message could not be obtained, parts of the message were missing, or parts of the message were invalid.%n%nFile:%n%1%nFile folder:%n%2%nMail 'To:' Field:%n%5%nMail 'From:' Field:%n%6%nMail 'Subject:' Field:%n%7%n%nThis message will be ignored and deleted.%n%nUser Action%nCheck for misconfigured applications sending mail to the wrong account.%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC000057F | Intersite Messaging-tjenesten bad om en endringsoperasjon for følgende objekt ved hjelp av LDAP, og operasjonen mislyktes.%n%nObjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The Intersite Messaging service requested a modify operation on the following object using LDAP and the operation failed.%n%nObject:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC0000583 | Active Directory Lightweight Directory Services kan ikke konstruere SPN (Service Principal Name) for gjensidig godkjenning for følgende katalogtjeneste.%n%nKatalogtjeneste:%n%1%n%nKallet ble avslått. Kommunikasjonen med denne katalogtjenesten kan bli påvirket.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
Active Directory Lightweight Directory Services failed to construct a mutual authentication service principal name (SPN) for the following directory service.%n%nDirectory service:%n%1%n%nThe call was denied. Communication with this directory service might be affected.%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC0000586 | Internal event: The infrastructure update task could not add a necessary object.%n%nCode:%n%1%nProblem:%n%4%nData:%n%5%n%nThe task will continue to process phantom objects, but final results will be delayed.%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
Internal event: The infrastructure update task could not add a necessary object.%n%nCode:%n%1%nProblem:%n%4%nData:%n%5%n%nThe task will continue to process phantom objects, but final results will be delayed.%n%nAdditional Data%nError value:%n%2%nInternal ID:%n%3 |
| 0xC0000587 | Internal event: The infrastructure update task could not locate some stale phantom references.%n%nThe task will continue, but final results will be delayed. |
Internal event: The infrastructure update task could not locate some stale phantom references.%n%nThe task will continue, but final results will be delayed. |
| 0xC0000588 | Internal event: The infrastructure update task failed to contact a global catalog while trying to verify the names of some phantom references.%n%nThe task will continue, but final results will be delayed. |
Internal event: The infrastructure update task failed to contact a global catalog while trying to verify the names of some phantom references.%n%nThe task will continue, but final results will be delayed. |
| 0xC0000589 | Internal event: The infrastructure update task failed to find a necessary index.%n%nNo infrastructure updates will complete until the index is found. This operation will be tried again later.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: The infrastructure update task failed to find a necessary index.%n%nNo infrastructure updates will complete until the index is found. This operation will be tried again later.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000058A | Internal event: The infrastructure update task failed to create a necessary index.%n%nNo infrastructure updates will complete until the index is created. This operation will be tried again later.%n%nAdditional Data%nError value:%n%1 %2 |
Internal event: The infrastructure update task failed to create a necessary index.%n%nNo infrastructure updates will complete until the index is created. This operation will be tried again later.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000058B | Den lokale domenekontrolleren er både en global katalog og infrastrukturens driftsovervåker. Disse to rollene er ikke kompatible.%n%nHvis en annen domenekontroller eksisterer i domenet, bør den defineres som infrastrukturens driftsovervåker. Følgende domenekontroller er en god kandidat til denne rollen.%n%nDomenekontroller:%n%1%n%nHvis alle domenekontrollere i dette domenet er globale kataloger, finnes det ingen infrastrukturoppdateringer som skal fullføres, og denne meldingen blir kanskje ignorert. |
The local domain controller is both a global catalog and the infrastructure operations master. These two roles are not compatible.%n%nIf another domain controller exists in the domain, it should be made the infrastructure operations master. The following domain controller is a good candidate for this role.%n%nDomain controller:%n%1%n%nIf all domain controllers in this domain are global catalogs, then there are no infrastructure update tasks to complete, and this message might be ignored. |
| 0xC000058C | Internal event: The local domain controller is unable to process infrastructure updates at the desired rate.%n%nRequired rate (seconds):%n%1%nMaximum rate (seconds):%n%2%nCurrent rate (days):%n%3%n%nUser Action%nMove the infrastructure operations master role to a more powerful computer or adjust the desired rate.%n%nNote: If this domain controller was recently a global catalog, then the infrastructure operations master role should be transferred to a domain controller that has not recently been a global catalog. |
Internal event: The local domain controller is unable to process infrastructure updates at the desired rate.%n%nRequired rate (seconds):%n%1%nMaximum rate (seconds):%n%2%nCurrent rate (days):%n%3%n%nUser Action%nMove the infrastructure operations master role to a more powerful computer or adjust the desired rate.%n%nNote: If this domain controller was recently a global catalog, then the infrastructure operations master role should be transferred to a domain controller that has not recently been a global catalog. |
| 0xC0000593 | Internal event: The cross-domain move of the following object failed at the destination domain.%n%nSource object DN:%n%1%nDestination object DN:%n%2%n%nAdditional Data%nError value:%n%3 %4 |
Internal event: The cross-domain move of the following object failed at the destination domain.%n%nSource object DN:%n%1%nDestination object DN:%n%2%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC0000595 | Følgende objekter representerer kanskje det samme objektet som ble flyttet fra to domenekontrollere i dette domenet til to andre domener.%n%nObjekt (1):%n%1%nObjekt (2):%n%2%n%nObjekt (1) foretrekkes for denne domenekontrolleren.%n%nBrukerhandling%nFjern objektet (2) fra alle andre domener.%n%nGUID for objekt (2):%n%3 |
The following objects might represent the same object that was moved from two domain controllers in this domain to two different domains.%n%nObject (1):%n%1%nObject (2):%n%2%n%nObject (1) is preferred on this domain controller.%n%nUser Action%nRemove object (2) from all other domains.%n%nObject (2) GUID:%n%3 |
| 0xC0000596 | Internal event: The cross-domain move of the following object to a new parent object in the destination domain succeeded.%n%nObject:%n%1%nNew parent object:%n%2 |
Internal event: The cross-domain move of the following object to a new parent object in the destination domain succeeded.%n%nObject:%n%1%nNew parent object:%n%2 |
| 0xC0000597 | Internal event: The cross-domain move of the following object to a new parent object in the destination domain failed.%n%nObject:%n%1%nNew parent object:%n%2%n%nAdditional Data%nError value:%n%3 %4 |
Internal event: The cross-domain move of the following object to a new parent object in the destination domain failed.%n%nObject:%n%1%nNew parent object:%n%2%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC0000598 | Flyttingen av følgende objekt på tvers av domener til et nytt overordnet objekt, var vellykket, men oppryddingen for den lokale domenekontrolleren mislyktes.%n%nObjekt:%n%1%nNytt overordnet objekt:%n%2%n%nBrukerhandling%nSlett objektet manuelt.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
The cross-domain move of the following object to a new parent object succeeded, but cleanup on the local domain controller failed.%n%nObject:%n%1%nNew parent object:%n%2%n%nUser Action%nDelete the object manually.%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC00005A6 | Etter gjenoppretting fra sikkerhetsmediet oppstod det en feil under forsøk på å opprette gjenopprettingsindikatorfilen.%n%nDenne filen må opprettes for at systemet skal kunne kjøres på riktig måte.%n%nBrukerhandling%nForsøk å gjenopprette fra sikkerhetskopieringsmediet på nytt.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
After restoring from backup media, an error occurred when attempting to create the restore marker file.%n%nThis file must be created for your system to run correctly.%n%nUser Action%nAttempt to restore from backup media again.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00005A7 | Etter gjenoppretting fra sikkerhetsmediet oppstod det en feil under forsøk på å slette gjenopprettingsindikatorfilen.%n%nDenne filen må slettes for at systemet skal kunne kjøres på riktig måte.%n%nBrukerhandling%nForsøk å gjenopprette fra sikkerhetskopieringsmediet på nytt.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
After restoring from backup media, an error occurred when attempting to delete the restore marker file.%n%nThis file must be deleted for your system to run correctly.%n%nUser Action%nAttempt to restore from backup media again.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00005A8 | Intersite Messaging-tjenesten som bruker SMTP-transporten, har mottatt en leveringsstatusrapport fra SMTP-tjenesten for en melding den sendte, som angav en leveringsfeil.%n%nTekst i leveringsstatus:%n%2 %3%n%nDette kan være et permanent eller midlertidig problem. Active Directory Lightweight Directory Services forsøker denne operasjonen på nytt senere når en annen replikeringsmelding sendes i henhold til tidsplanen for områdetilkoblingen.%n%nBrukerhandling%n-Hvis SMTP-tjenesten har gitt opp for raskt, justerer du parameterne for nye SMTP-forsøk ved hjelp av SMTP-tjenestebehandling.%n%n-Hvis måldomenekontrolleren er ukjent eller ikke direkte koblet til den lokale domenekontrolleren, må du kanskje konfigurere SMTP til å bruke en gateway til å rute e-post til målsystemet. Dette kan du gjøre ved hjelp av SMTP-tjenestebehandling.%n%n-Hvis DNS-adressen for måldomenekontrolleren ikke kan løses, eller hvis nettverkstilkoblingen ikke kan opprettes, kontakter du nettverksadministratoren.%n%n-Hvis e-postmeldingen er for stor, øker du meldingsstørrelsesgrensen for SMTP-tjenesten, eller deaktiverer begrensningskontrollen.%n%nTilleggsdata%nFeilverdi:%n%1 %4 |
The Intersite Messaging service using the SMTP transport has received a delivery status report from the SMTP service for a message it submitted that indicated delivery failure.%n%nDelivery status text:%n%2 %3%n%nThis may be a permanent or a transient condition. Active Directory Lightweight Directory Services will try this operation again later when it sends another replication message according to the schedule of the intersite connection.%n%nUser Action%n-If the SMTP service has given up too quickly, adjust the SMTP retry parameters using the SMTP service manager.%n%n-If the destination domain controller is unknown or not directly connected to the local domain controller, it may be necessary to configure SMTP to use a gateway to route the mail to the target system. You can do this using the SMTP service manager.%n%n-If the DNS address for the destination domain controller cannot be resolved, or if network connectivity cannot be established, consult your network administrator.%n%n-If the mail message is too large, either increase the message size limit of the SMTP service or disable limit checking.%n%nAdditional Data%nError value:%n%1 %4 |
| 0xC00005AA | Overføringen av sikkerhetsbeskrivelsen kan ikke beregne en ny sikkerhetsbeskrivelse for følgende objekt.%n%nObjekt:%n%1%n%nDenne operasjonen vil bli prøvd på nytt senere.%n%nBrukerhandling%nHvis dette problemet vedvarer, kan du forsøke å vise statusen for dette objektet og manuelt endre sikkerhetsbeskrivelsen.%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
The security descriptor propagation task could not calculate a new security descriptor for the following object.%n%nObject:%n%1%n%nThis operation will be tried again later.%n%nUser Action%nIf this condition continues, attempt to view the status of this object and manually change the security descriptor.%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC00005AC | Under behandling av overføringen av sikkerhetsbeskrivelsen klarte ikke katalogtjenesten å skrive en ny sikkerhetsbeskrivelse for objektet.%nObjekt %1%n%n%nTilleggsdata%nFeilverdi:%n%2 %3 |
While processing security descriptor propagation, the directory service failed to write a new security descriptor for object.%nObject %1%n%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC00005BA | Intersite Messaging-tjenesten som bruker SMTP-transporten, klarte ikke å legge til følgende SMTP-rutingdomene.%n%nSMTP-rutingdomene:%n%1%n%nDette domenet kreves av SMTP for å godta innkommende e-post som bruker dette navnet. Andre replikeringspartnere får en feilmelding når de sender e-post til dette navnet før problemet er løst.%n%nBrukerhandling%nBekreft at SMTP-tjenesten er installert og fungerer riktig. Bekreft også at Active Directory Service Interfaces (ADSI) er installert og fungerer i systemet. Hvis dette problemet vedvarer, kan du forsøke å legge til domenet manuelt ved hjelp av SMTP-tjenestebehandling.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service using the SMTP transport has failed to add the following SMTP routing domain.%n%nSMTP routing domain:%n%1%n%nThis domain is needed by SMTP to accept incoming mail using this name. Other replication partners will receive errors when sending mail to this name until the problem is corrected.%n%nUser Action%nVerify that the SMTP service is installed and functioning correctly. Also, verify that Active Directory Service Interfaces (ADSI) is installed and working on this system. If this event continues to occur, attempt to add the domain manually using SMTP service manager.%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC00005BB | Intersite Messaging-tjenesten som bruker SMTP-transporten, klarte ikke å registrere DLL-filen (Ismsink.dll) for hendelsesmottakeren.%n%nHendelsesmottakeren varsler meldingstjenesten om at en ny e-post er mottatt. Nye e-postmeldinger samles i mappen for sending av e-post til dette problemet er løst.%n%nBrukerhandling%n- Bekreft at DLL-filen (Ismsink.dll) for hendelsesmottakeren finnes og ikke er skadet.%n%n- Registrer DLL-filen for hendelsesmottakeren manuelt ved hjelp av følgende kommandoer:%nregsvr32 /u ismsink.dll%nregsvr32 ismsink.dll%n%nStart Intersite Messaging-tjenesten på nytt.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The Intersite Messaging service using the SMTP transport failed to register the event sink DLL (Ismsink.dll).%n%nThe event sink notifies the messaging service that new mail has arrived. New mail will accumulate in the drop folder until this problem is corrected.%n%nUser Action%n- Verify that the event sink DLL (Ismsink.dll) is present and not corrupted.%n%n- Register the event sink DLL manually using the following commands:%nregsvr32 /u ismsink.dll%nregsvr32 ismsink.dll%n%nRestart the Intersite Messaging service.%n%nAdditional Data%nError value:%n%2 %1 |
| 0xC00005BC | Intersite Messaging-tjenesten som bruker SMTP-transporten, klarte ikke å registrere DLL-filen (Ismsink.dll) for hendelsesmottakeren.%n%nHendelsesmottakeren varsler meldingstjenesten om at en ny e-post er mottatt. Nye e-postmeldinger samles i mappen for sending av e-post til dette problemet er løst.%n%nBrukerhandling%nKontroller at Internet Information Services (IIS) er fullstendig installert. Installasjonen er avhengig av riktig registrering av DLL-filen (Seo.dll) for IIS.%n%nStart Intersite Messaging-tjenesten på nytt.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The Intersite Messaging service using the SMTP transport failed to register the event sink DLL (Ismsink.dll) with SMTP.%n%nThe event sink notifies the messaging service that new mail has arrived. New mail will accumulate in the drop folder until this problem is corrected.%n%nUser Action%nVerify that Internet Information Services (IIS) is fully installed. The installation relies on proper registration of the IIS DLL (Seo.dll).%n%nRestart the Intersite Messaging service.%n%nAdditional Data%nError value:%n%2 %1 |
| 0xC00005BD | Én eller flere klasser fra følgende DLL-fil for COM (Component Object Model) er ikke registrert.%n%nDLL-fil for COM:%n%1%n%nIntersite Messaging-tjenesten som bruker SMTP-transporten, avhenger av denne DLL-filen.%n%nBrukerhandling%nBekreft at denne DLL-filen finnes og er registrert.%n%nRegistrer denne DLL-filen manuelt ved hjelp av følgende kommandoer:%nregsrv32 /u %1%nregsrv32 %1%n%nHvis dette problemet vedvarer, har du kanskje en foreldet versjon av denne DLL-filen. Bekreft versjonen ved hjelp av følgende kommando:%nfilever %windir%\\system32\\%1%n%nStart Intersite Messaging-tjenesten på nytt.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
One or more classes from the following Component Object Model (COM) DLL are not registered.%n%nCOM DLL:%n%1%n%nThe Intersite Messaging service using the SMTP transport depends on this DLL.%n%nUser Action%nVerify that this DLL is present and registered.%n%nRegister this DLL manually using following commands:%nregsrv32 /u %1%nregsrv32 %1%n%nIf this event continues to occur, you might have an obsolete version of this DLL. Verify the version using the following command:%nfilever %windir%\\system32\\%1%n%nRestart the Intersite Messaging service.%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC00005C0 | Følgende verdi er duplisert i SPN-egenskapen for følgende objekt.%n%nVerdi:%n%1%nObjekt:%n%2%n%nVerdien blir ignorert. |
The following value is duplicated in the SPN property on the following object.%n%nValue:%n%1%nObject:%n%2%n%nThe value will be ignored. |
| 0xC00005C7 | Active Directory Lightweight Directory Services kan ikke oppdatere følgende objekt i den lokale Active Directory Lightweight Directory Services-databasen med endringer som ble mottatt fra følgende kildekatalogtjeneste. Active Directory Lightweight Directory Services har ikke tilstrekkelig kapasitet til å ta i bruk alle endringene.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nKildekatalogtjeneste:%n%3%n%nBrukerhandling%nStart denne katalogtjenesten på nytt. Hvis dette ikke løser problemet, øker du størrelsen på lagringskapasiteten. Hvis du fyller objektene med et stort antall verdier, eller størrelsen på verdiene er spesielt stor, reduserer du størrelsen på fremtidige endringer.%n%nTilleggsdata%nFeilverdi:%n%5 %4 |
Active Directory Lightweight Directory Services could not update the following object in the local Active Directory Lightweight Directory Services database with changes received from the following source directory service. Active Directory Lightweight Directory Services does not have enough database version store to apply the changes.%n%nObject:%n%1%nObject GUID:%n%2%nSource directory service:%n%3%n%nUser Action%nRestart this directory service. If this does not solve the problem, increase the size of the database version store. If you are populating the objects with a large number of values, or the size of the values is especially large, decrease the size of future changes.%n%nAdditional Data%nError value:%n%5 %4 |
| 0xC00005C8 | Active Directory Lightweight Directory Services kan ikke oppdatere følgende objekt i den lokale Active Directory Lightweight Directory Services-databasen med endringer som ble mottatt fra følgende kildekatalogtjeneste, fordi diskvolumet som inneholder Active Directory Lightweight Directory Services-databasen, er full.%n%nObject:%n%1%nObjekt-GUID:%n%2%nKildekatalogtjeneste:%n%3%n%nBrukerhandling%nSlett unødvendige filer, eller flytt dem til et annet volum. Hvis volumet er et RAID-sett, kan du kanskje legge til flere harddisker for å øke lagringskapasiteten. Hvis Active Directory Lightweight Directory Services-databasefilene og -loggene er lagret på samme volum, kan du atskille dem for å frigjøre diskplass. |
Active Directory Lightweight Directory Services could not update the following object in the local Active Directory Lightweight Directory Services database with changes received from the following source directory service because the disk volume containing the Active Directory Lightweight Directory Services database is full.%n%nObject:%n%1%nObject GUID:%n%2%nSource directory service:%n%3%n%nUser Action%nDelete unnecessary files or move them to another volume. If the volume is a RAID set, you might be able to add additional hard disks to increase the storage capacity. If the Active Directory Lightweight Directory Services database files and logs are stored in the same volume, you can separate them to create free disk space. |
| 0xC00005C9 | Internal error: The operation on the object failed.%n%nAdditional Data%nError value:%n%2 %1 |
Internal error: The operation on the object failed.%n%nAdditional Data%nError value:%n%2 %1 |
| 0xC00005EF | Internal Error: Active Directory Lightweight Directory Services could not perform an operation because the database has run out of version storage.%n%nAdditional Data%nInternal ID:%n%1 |
Internal Error: Active Directory Lightweight Directory Services could not perform an operation because the database has run out of version storage.%n%nAdditional Data%nInternal ID:%n%1 |
| 0xC00005F2 | Internal event: MAPI address book indices were not created for any language. This might be due to an incorrect value on the following registry key or the appropriate language pack is not installed.%n%nRegistry key:%n\\\\HKLM\\Software\\Microsoft\\NTDS\\Language%n%nNo MAPI address books will be available. |
Internal event: MAPI address book indices were not created for any language. This might be due to an incorrect value on the following registry key or the appropriate language pack is not installed.%n%nRegistry key:%n\\\\HKLM\\Software\\Microsoft\\NTDS\\Language%n%nNo MAPI address books will be available. |
| 0xC00005F3 | Lastingen av skjemabufferen for Active Directory Lightweight Directory Services kan ikke konvertere standard sikkerhetsbeskrivelse for følgende skjemaklasseobjekt.%n%nSikkerhetsbeskrivelse:%n%1%nSkjemaklasseobjekt:%n%2%n%nDet fører til at lastingen av skjemabufferen mislykkes.%n%nBrukerhandling%nBekreft at standard sikkerhetsbeskrivelse for klassen er gyldig. Hvis den er ugyldig, endrer du den til en gyldig verdi.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
The Active Directory Lightweight Directory Services schema cache load could not convert the default security descriptor on the following schema class object.%n%nSecurity descriptor:%n%1%nSchema class object:%n%2%n%nAs a result, the schema cache load will fail.%n%nUser Action%nVerify that the default security descriptor on the class is valid. If it is not valid, change it to a correct value.%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC00005F7 | Intersite Messaging-tjenesten som bruker SMTP-transporten, har fastslått at én eller flere klasser fra CDO-biblioteket (Collaboration Data Object) ikke ble registrert som forventet. Denne feilen kan også forekomme hvis en ny versjon av CDO-biblioteket registreres av en produktinstallasjon mens Intersite Messaging-tjenesten kjører.%n%nDette problemet løser seg selv når biblioteket har blitt registrert på nytt.%n%nBrukerhandling%nBekreft at Cdosys.dll finnes og er registrert ved hjelp av kommandolinjeverktøyet Regsvr32. For systemer som kjører Microsoft Exchange, bekrefter du at Cdoex.dll er registrert.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The Intersite Messaging service using the SMTP transport has determined that one or more classes from the Collaboration Data Object (CDO) library were not registered as expected. This error could also occur if a new version of the CDO library is being registered by a product installation while the Intersite Messaging service is running.%n%nThis condition will correct itself once the library has been registered again.%n%nUser Action%nVerify that the Cdosys.dll is present and registered using the Regsvr32 command-line tool. For systems running Microsoft Exchange, verify that Cdoex.dll is registered.%n%nAdditional Data%nError value:%n%2 %1 |
| 0xC00005F8 | Internal error: The Intersite Messaging service using the SMTP transport has encountered an error originating from the Collaboration Data Object (CDO) library.%n%nAdditional Data%nError value:%n%3 %1%nInternal ID:%n%2 |
Internal error: The Intersite Messaging service using the SMTP transport has encountered an error originating from the Collaboration Data Object (CDO) library.%n%nAdditional Data%nError value:%n%3 %1%nInternal ID:%n%2 |
| 0xC0000600 | Internal event: Active Directory Lightweight Directory Services schema validation failed while performing an LDAP add or modify operation on the following schema object.%n%nSchema object:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
Internal event: Active Directory Lightweight Directory Services schema validation failed while performing an LDAP add or modify operation on the following schema object.%n%nSchema object:%n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC0000601 | Active Directory Lightweight Directory Services kan ikke slette følgende nøkkel fra registret. Denne feilen ble registrert i Active Directory Lightweight Directory Services etter en gjenoppretting.%n%nRegisternøkkel:%nHKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\NTDS\\Parameters\\New database GUID%n%nBrukerhandling%nSlett denne nøkkelen manuelt for å unngå problemer med fremtidige sikkerhetskopierings- eller gjenopprettingsoperasjoner.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services could not delete the following key from the registry. This error was encountered during the Active Directory Lightweight Directory Services recovery process after a restore operation.%n%nRegistry key:%nHKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\NTDS\\Parameters\\New database GUID%n%nUser Action%nDelete this key manually to prevent problems with future backup or restore operations.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000060A | Det ble registrert en konflikt med følgende eksisterende attributt under replikering av følgende skjemaobjekt.%n%nSkjemaobjekt:%n%1%nAttributt:%n%2%n%nDet fører til at inngående replikering fra katalogtjenesten som inneholder konfliktskjemaet, mislykkes for den lokale katalogtjenesten.%n%nBrukerhandling%nHvis attributtdefinisjonen i den lokale databasen er skadet, gjenoppretter du katalogtjenesten fra sikkerhetskopieringsmediet, som ble opprettet før attributtskjemaobjektet ble redigert.%n%nTidspunkt for forrige redigering:%n%4%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
While replicating the following schema object, a conflict was detected with the following existing attribute.%n%nSchema object:%n%1%nAttribute:%n%2%n%nAs a result, inbound replication from the directory service with conflicting schema will fail on the local directory service.%n%nUser Action%nIf the attribute definition in the local database is corrupted, restore the directory service from backup media that was created earlier than the attribute schema object was modified.%n%nTime of last modification:%n%4%n%nAdditional Data%nError value:%n%5 %3 |
| 0xC000060B | Det ble registrert en konflikt med følgende eksisterende skjemaklasse under replikering av følgende skjemaobjekt.%n%nSkjemaobjekt:%n%1%nKlasse:%n%2%n%nDet fører til at inngående replikering fra katalogtjenesten som inneholder konfliktskjemaet, mislykkes for den lokale katalogtjenesten.%n%nBrukerhandling%nHvis klassedefinisjonen i den lokale databasen er skadet, kan du forsøke å gjenopprette katalogtjenesten fra sikkerhetskopieringsmediet, som ble opprettet før klasseskjemaobjektet ble redigert.%n%nTidspunkt for forrige redigering:%n%4%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
While replicating the following schema object, a conflict was detected with the following existing schema class.%n%nSchema object:%n%1%nClass:%n%2%n%nAs a result, inbound replication from the directory service with conflicting schema will fail on the local directory service.%n%nUser Action%nIf the class definition in the local database is corrupted, try restoring the directory service from backup media that was created earlier than the class schema object was modified.%n%nTime of last modification:%n%4%n%nAdditional Data%nError value:%n%5 %3 |
| 0xC000060E | Følgende område har ikke et underordnet objekt for NTDS-områdeinnstillinger.%n%nOmråde:%n%1%n%nBrukerhandling%nOpprett et objekt for NTDS-områdeinnstillinger for dette området. |
The following site has no NTDS Site Settings child object.%n%nSite:%n%1%n%nUser Action%nCreate an NTDS Site Settings object for this site. |
| 0xC000061F | Foretrukkede brohodeservere har blitt valgt til å støtte områdereplikering med følgende område ved hjelp av følgende transport. Ingen av disse foretrukkede brohodeserverne kan imidlertid replikere følgende katalogpartisjon.%n%nOmråde:%n%1%nTransport:%n%2%nKatalogpartisjon:%n%3%n%nBrukerhandling%n%n- Konfigurer en katalogserver som kan støtte replikering av denne katalogpartisjonen som en foretrukket brohodeserver for denne transporten.%n- Bekreft at de tilsvarende Server-objektene har en nettverksadresse for denne transporten. Katalogservere som replikerer ved hjelp av SMTP-transporten, må for eksempel ha et mailAddress-attributt. Dette attributtet konfigureres vanligvis automatisk etter at SMTP-tjenesten har blitt installert.%n%nInntil dette problemet er løst, tolker KCC (Knowledge Consistency Checker) alle katalogservere på dette området som mulige brohodeservere for denne katalogpartisjonen. |
Preferred bridgehead servers have been selected to support intersite replication with the following site using the following transport. However, none of these preferred bridgehead servers can replicate the following directory partition.%n%nSite:%n%1%nTransport:%n%2%nDirectory partition:%n%3%n%nUser Action%n%n- Configure a directory server that can support replication of this directory partition as a preferred bridgehead server for this transport.%n- Verify that the corresponding Server objects have a network address for this transport. For example, directory servers that replicate using the SMTP transport must have a mailAddress attribute. This attribute is normally configured automatically after the SMTP service is installed.%n%nUntil this is rectified, the Knowledge Consistency Checker (KCC) will consider all directory servers in this site as possible bridgehead servers for this directory partition. |
| 0xC0000620 | Ingen av katalogserverne på følgende område som replikerer følgende katalogpartisjon, er konfigurert til å bruke følgende transport, selv om området er konfigurert til å tillate replikering via denne transporten.%n%nOmråde:%n%1%nKatalogpartisjon:%n%3%nTransport:%n%2%n%nBrukerhandling%n%n- Konfigurer området slik at det ikke tillater replikering ved hjelp av denne transporten, ved å redigere de riktige siteLink-objektene.%n- Aktiver én eller flere katalogservere slik at de kan bruke denne transporten. Når det gjelder SMTP-transporten, kreves det at SMTP-tjenesten installeres og at mailAddress-attributtet konfigureres for det tilsvarende Server-objektet. |
None of the directory servers in the following site that replicate the following directory partition are configured to use the following transport, even though the site itself is configured to allow replication over this transport.%n%nSite:%n%1%nDirectory partition:%n%3%nTransport:%n%2%n%nUser Action%n%n- Configure the site to not allow replication using this transport by modifying the appropriate siteLink objects.%n- Enable one or more directory servers to use this transport. For the SMTP transport, this requires installation of the SMTP service and configuration of the mailAddress attribute on the corresponding Server object. |
| 0xC0000628 | Følgende objekt kan ikke arve en SID (security identifier) fra et annet objekt.%n%nObjekt:%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %4%nIntern ID:%n%2 |
The following object could not inherit a security identifier (SID) from another object.%n%nObject:%n%1%n%nAdditional Data%nError value:%n%3 %4%nInternal ID:%n%2 |
| 0xC0000643 | Active Directory Lightweight Directory Services kan ikke opprette en indeks som kreves for optimal bruk.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services failed to create an index necessary for correct operation.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000066A | Et sertifikat som ble sendt til Active Directory Lightweight Directory Services, hevder å være fra en katalogtjeneste med følgende datamaskinkonto. Denne datamaskinen er ikke en katalogserver i henhold til den lokale kopien av katalogpartisjonen for konfigurasjonen. Det fører til at sertifikatet ikke ble godkjent.%n%nObjekt-GUID for datamaskinkonto:%n%1%nServer-objekt (hvis tilgjengelig):%n%2%nNTDS-innstillingsobjekt (hvis tilgjengelig):%n%3%n%nBrukerhandling%nBekreft at katalogpartisjonen for konfigurasjonen i den lokale katalogtjenesten har blitt replikert på riktig måte. |
A certificate presented to Active Directory Lightweight Directory Services claims to be from a directory service with the following computer account. This computer is not a directory server according to the local copy of the configuration directory partition. As a result, the certificate was not authenticated.%n%nComputer account object GUID:%n%1%nServer object (if available):%n%2%nNTDS Settings object (if available):%n%3%n%nUser Action%nVerify that the configuration directory partition on the local directory service has replicated correctly. |
| 0xC000066D | Active Directory Lightweight Directory Services utførte ikke et godkjent eksternt prosedyrekall (RPC) til en annen katalogserver fordi ønsket SPN for målkatalogserveren ikke er registrert for KDC-domenekontrolleren (Key Distribution Center) som løser SPN.%n%nMålkatalogserver:%n%1%nSPN:%n%2%n%nBrukerhandling%nBekreft at navnet på målkatalogserveren og domenet er riktig. Bekreft også at SPN er registrert for KDC-domenekontrolleren. Hvis nivået på målkatalogserveren nylig har blitt hevet, må kontodataene for den lokale katalogserveren replikere til KDC før denne katalogserveren kan godkjennes. |
Active Directory Lightweight Directory Services did not perform an authenticated remote procedure call (RPC) to another directory server because the desired service principal name (SPN) for the destination directory server is not registered on the Key Distribution Center (KDC) domain controller that resolves the SPN.%n%nDestination directory server:%n%1%nSPN:%n%2%n%nUser Action%nVerify that the names of the destination directory server and domain are correct. Also, verify that the SPN is registered on the KDC domain controller. If the destination directory server has been recently promoted, it will be necessary for the local directory server’s account data to replicate to the KDC before this directory server can be authenticated. |
| 0xC0000678 | Active Directory Lightweight Directory Services fant ingen RPC-protokollsekvenser installert på denne datamaskinen.%n%nDet fører til at Active Directory Lightweight Directory Services ikke svarer på noen PRC-forespørsler.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services did not find any RPC protocol sequences installed on this computer.%n%nAs a result, Active Directory Lightweight Directory Services will not respond to any RPC requests.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000067E | Internal event: A MAPI client requested the creation of an Address Book table that was too large to be supported. As a result, the operation was rejected. |
Internal event: A MAPI client requested the creation of an Address Book table that was too large to be supported. As a result, the operation was rejected. |
| 0xC0000680 | Oversettingsoppgaven for Connection-objektet i KCC (Knowledge Consistency Checker) er deaktivert. Denne konfigurasjonen gjelder bare for intern testing.%n%nBrukerhandling%nDu aktiverer oversettingsoppgaven ved å bruke kommandolinjeverktøyet Repadmin og kjøre følgende kommandolinjeoppgave.%n%nrepadmin /options -disable_ntdsconn_xlate |
The Connection object translation task in the Knowledge Consistency Checker (KCC) is disabled. This configuration is for internal testing purposes only.%n%nUser Action%nTo enable the translation task, use the Repadmin command-line tool and run the following command-line task.%n%nrepadmin /options -disable_ntdsconn_xlate |
| 0xC000069E | Active Directory Lightweight Directory Services kan ikke oppdatere følgende objekt med en attributtverdiendring som ble mottatt fra følgende kildekatalogtjeneste. Dette skyldes at det oppstod en feil da endringene skulle implementeres i den lokale Active Directory Lightweight Directory Services-databasen.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nKildekatalogtjeneste:%n%3%nAttributt:%n%5%nAttributtverdi:%n%6%nGUID for attributtverdi:%n%7%nNåværende:%n%8%n%nDenne operasjonen blir ikke prøvd på nytt ved neste planlagte replikering. Synkronisering av den lokale katalogtjenesten med kildekatalogtjenesten er blokkert til problemet med oppdateringen er løst.%n%nTilleggsdata%nFeilverdi:%n%4 |
Active Directory Lightweight Directory Services could not update the following object with an attribute value change received from the following source directory service. This is because an error occurred during the application of the changes to the local Active Directory Lightweight Directory Services database.%n%nObject:%n%1%nObject GUID:%n%2%nSource directory service:%n%3%nAttribute:%n%5%nAttribute value:%n%6%nAttribute value GUID:%n%7%nPresent:%n%8%n%nThis operation will not be tried again at the next scheduled replication. Synchronization of the local directory service with the source directory service is blocked until the update problem is corrected.%n%nAdditional Data%nError value:%n%4 |
| 0xC00006A3 | Denne katalogtjenesten kan ikke hente endringene som ble forespurt for følgende katalogpartisjon. Det fører til at katalogtjenesten ikke kan sende endringsforespørsler til katalogtjenesten på følgende nettverksadresse.%n%nKatalogpartisjon:%n%1%nNettverksadresse:%n%2%nUtvidet forespørselskode:%n%4%n%nTilleggsdata%nFeilverdi:%n%5 %3 |
This directory service failed to retrieve the changes requested for the following directory partition. As a result, it was unable to send change requests to the directory service at the following network address.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nExtended request code:%n%4%n%nAdditional Data%nError value:%n%5 %3 |
| 0xC00006A4 | Den lokale domenekontrolleren kan ikke behandle replikeringsforespørselen fordi følgende områdetransportobjekt mangler.%n%nGUID for områdetransportobjekt:%n%1 |
The local domain controller could not process the replication request because the following intersite transport object is missing.%n%nIntersite transport object GUID:%n%1 |
| 0xC00006A5 | Den lokale domenekontrolleren kan ikke legge til skjemainformasjon i en melding for svar på e-post. Domenekontrolleren på følgende nettverksadresse utførte forespørselen om endringer på følgende katalogpartisjon.%n%nKatalogpartisjon:%n%1%nNettverksadresse:%n%2%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The local domain controller failed to add schema information to a mail reply message. The domain controller at the following network address made the request for changes to the following directory partition.%n%nDirectory partition:%n%1%nNetwork address:%n%2%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC00006B5 | Funksjonsnivået for konfigurasjonssettet er ikke kompatibelt med dette operativsystemet. |
The functional level of the configuration set is incompatible with this operating system. |
| 0xC00006B6 | Funksjonsnivået for konfigurasjonssettet er ikke kompatibelt med funksjonsnivået for den lokale Active Directory Lightweight Directory Services-forekomsten.%n%n funksjonsnivå for konfigurasjonssett:%n%2%nFunksjonsnivå for forekomst av Active Directory Lightweight Directory Services:%n%3%nMinste kompatible funksjonsnivå:%n%4%n%nBrukerhandling%nInstaller riktig operativsystem på denne Active Directory Lightweight Directory Services-forekomsten. |
The functional level of the configuration set is incompatible with the functional level of the local Active Directory Lightweight Directory Services instance.%n%n configuration set functional level:%n%2%n Active Directory Lightweight Directory Services instance functional level:%n%3%nMinimal compatible functional level:%n%4%n%nUser Action%nInstall the correct operating system on this Active Directory Lightweight Directory Services instance. |
| 0xC00006B7 | Active Directory Lightweight Directory Services kan ikke lese NTDS-innstillingsobjektet for den lokale Active Directory Lightweight Directory Services-forekomsten. Det fører til at Active Directory Lightweight Directory Services ikke kan validere funksjonsnivået for Active Directory Lightweight Directory Services-forekomsten.%n%nNTDS-innstillingsobjekt:%n%2%n%nTilleggsdata%nFeilverdi:%n%1 %3 |
Active Directory Lightweight Directory Services could not read the NTDS Settings object for the local Active Directory Lightweight Directory Services instance. As a result, Active Directory Lightweight Directory Services could not validate the functional level of the Active Directory Lightweight Directory Services instance.%n%nNTDS Settings object:%n%2%n%nAdditional Data%nError value:%n%1 %3 |
| 0xC00006B8 | Det gjeldende funksjonsnivået for den lokale Active Directory Lightweight Directory Services-forekomsten, som er angitt av NTDS-innstillingsobjektet, er ikke kompatibelt med operativsystemet fordi funksjonsnivået er satt høyere enn funksjonsnivået som støttes av dette operativsystemet.%n%nFunksjonsnivå basert på NTDS-innstillingsobjekt:%n%1%nFunksjonsnivå som er støttet av operativsystemet:%n%2 |
The current functional level of the local Active Directory Lightweight Directory Services instance as indicated by its NTDS Settings object is incompatible with the operating system because the functional level is set higher than the functional level supported by this operating system.%n%nFunctional level based on NTDS Settings object:%n%1%nFunctional level supported by the operating system:%n%2 |
| 0xC00006B9 | Active Directory Lightweight Directory Services kan ikke oppdatere funksjonsnivået i NTDS-innstillingsobjektet for den lokale Active Directory Lightweight Directory Services-forekomsten.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
Active Directory Lightweight Directory Services could not update the functional level on the NTDS Settings object for the local Active Directory Lightweight Directory Services instance.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC00006BE | Funksjonsnivåene for skogen eller domenet har blitt oppdatert til verdier som ikke er kompatible med funksjonsnivået som støttes av dette operativsystemet.%n%nNytt funksjonsnivå for skog:%n%1%nNytt funksjonsnivå for domene:%n%2%nFunksjonsnivåområde for operativsystem:%n%3 to %4%n%nDet fører til at den lokale domenekontrolleren isoleres fra domenet eller skogen.%n%nBrukerhandling%nInstaller et operativsystem som er kompatibelt med funksjonsnivået for partisjonen og konfigurasjonssettet i den lokale Active Directory Lightweight Directory Services-forekomsten, eller oppdater funksjonsnivået for partisjonen og konfigurasjonssettet slik at det blir kompatibelt med funksjonsnivået som støttes av dette operativsystemet. |
The forest or domain functional levels have been updated to values that are incompatible with the functional level supported by this operating system.%n%nNew forest functional level:%n%1%nNew domain functional level:%n%2%nOperating system functional level range:%n%3 to %4%n%nAs a result, the local domain controller will be isolated from the domain or forest.%n%nUser Action%nInstall an operating system compatible with the functional level of the partition and the configuration set on the local Active Directory Lightweight Directory Services instance or update the functional level of the partition and the configuration set to be compatible with the functional level supported by this operating system. |
| 0xC00006BF | Forsøket på å gjenopprette Active Directory Lightweight Directory Services mislyktes fordi den gjenopprettede kopien av Active Directory Lightweight Directory Services er for gammel.%n%nGjenopprettet Active Directory Lightweight Directory Services-alder (dager):%n%1%nMaksimal gjenopprettingsalder (dager):%n%2 |
The attempt to restore Active Directory Lightweight Directory Services failed because the restored copy of Active Directory Lightweight Directory Services is too old.%n%nRestored Active Directory Lightweight Directory Services age (days):%n%1%nMaximum restored age (days):%n%2 |
| 0xC00006C0 | Kan ikke gjenopprette Active Directory Lightweight Directory Services-filer som kreves for installasjonen. |
Active Directory Lightweight Directory Services files required for installation could not be restored. |
| 0xC00006C1 | Active Directory Lightweight Directory Services kan ikke registrere utløpstid/levetid for konfigurasjonssettet. |
Active Directory Lightweight Directory Services could not detect the tombstone lifetime of the configuration set. |
| 0xC00006E7 | Nivået for denne Active Directory Lightweight Directory Services-forekomsten kan ikke heves på grunn av et mellomrom i NetBIOS-datamaskinnavnet. Gi nytt navn til datamaskinen, og forsøk å heve nivået på nytt. |
This Active Directory Lightweight Directory Services instance cannot be promoted because of a space in the NetBIOS computer name. Rename the computer and restart the promotion. |
| 0xC00006E8 | Følgende områdekoblingsobjekt refererer til et område, men det området ble ikke funnet i KCC-hovedlisten (Knowledge Consistency Checker) over områder.%n%nOmrådekoblingsobjekt:%n%1%nOmråde:%n%2%n%nDette kan påvirke muligheten til å generere områdetopologi. |
The following site link object references a site, but that site was not found in the Knowledge Consistency Checker (KCC) master list of sites.%n%nSite link object:%n%1%nSite:%n%2%n%nThis may affect the ability to generate intersite topology. |
| 0xC00006E9 | Følgende programkatalogpartisjon har ikke et referansedomene for sikkerhetsbeskrivelse.%n%nProgramkatalogpartisjon:%n%1%n%nRotdomenet brukes i stedet.%n%nBrukerhandling%nAngi referansedomenet for sikkerhetsbeskrivelsen for denne programkatalogpartisjonen. |
The following application directory partition has no security descriptor reference domain.%n%nApplication directory partition:%n%1%n%nThe root domain will be used instead.%n%nUser Action%nSet the security descriptor reference domain for this application directory partition. |
| 0xC00006EB | Følgende brohodeobjekt for områdekobling refererer til en områdekobling, men den områdekoblingen ble ikke funnet i KCC-hovedlisten (Knowledge Consistency Checker) over områdekoblinger.%n%nBrohodeobjekt for områdekobling:%n%1%nOmrådekobling:%n%2%n%nDette kan påvirke muligheten til å generere områdetopologi. |
The following site link bridge object references a site link, but that site link was not found in the Knowledge Consistency Checker (KCC) master list of site links.%n%nSite link bridge object:%n%1%nSite link:%n%2%n%nThis may affect the ability to generate intersite topology. |
| 0xC00006ED | Active Directory Lightweight Directory Services kan ikke installeres fra de gjenopprettede filene. Systemoppstartsdisken er kanskje fjernet fra diskettstasjonen. Sett inn en systemoppstartsdisk, og start veiviseren på nytt. |
Active Directory Lightweight Directory Services could not be installed from the restored files. The system startup disk may have been removed from the floppy disk drive. Insert a system startup disk and restart the wizard. |
| 0xC00006EE | Internal event: Active Directory Lightweight Directory Services could not automatically generate a linkID attribute for the following new schema object.%n%nNew schema object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
Internal event: Active Directory Lightweight Directory Services could not automatically generate a linkID attribute for the following new schema object.%n%nNew schema object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC00006FB | Brohodeobjektet %1 for områdekoblingen inneholder færre enn to områdekoblinger.Brohodet for områdekoblingen blir ignorert. |
The site link bridge object %1 contains fewer than two sites links.The site link bridge will be ignored. |
| 0xC00006FC | Fant en kort bane med ikke-kryssende planer under behandling av topologienfor partisjon %1. Banen hadde sitt utspring på området %2, og de ikke-kryssendeplanene ble registrert mellom område %3 og område %4. Denne banen anses somugyldig og blir ignorert. |
When processing the topology for partition %1, a shortest-path with non-intersectingschedules was found. The path originated at site %2 and the non-intersectingschedules were discovered between site %3 and site %4. This path is consideredinvalid and will be ignored. |
| 0xC00006FD | Området %1 inneholder én eller flere katalogservere, men er ikke koblet tilmed områdekoblinger. Dette området kan ikke replikeres med andre områder hvis ikke de andre områdeneer tilkoblet med områdekoblinger. |
The site %1 contains one or more directory servers, but is not connectedby any site links. This site cannot replicate with other sites unless theyare connected by site links. |
| 0xC00006FE | Systemet kan ikke heve nivået på denne serveren til en global katalog %1 ganger.Hvis dette problemet vedvarer, kontakter du Microsoft Product SupportServices for å få hjelp.Feil %2: %3. |
The system failed to promote this server into a Global Catalog %1 times.If this issue persists, please contact Microsoft Product SupportServices for assistance.Error %2: %3. |
| 0xC00006FF | Replikering av programkatalogpartisjonen %1 fra kilden %2 er avbrutt.Replikering krever konsekvent skjema, men det siste forsøket på å synkronisereskjemaet mislyktes. Det er viktig at skjemareplikeringenfungerer som den skal. Se tidligere feil for mer diagnostikk.Hvis dette problemet vedvarer, kontakter du Microsoft Product SupportServices for å få hjelp.Feil %3: %4. |
Replication of application directory partition %1 from source %2 has been aborted.Replication requires consistent schema but last attempt to synchronizethe schema had failed. It is crucial that schema replicationfunctions properly. See previous errors for more diagnostics.If this issue persists, please contact Microsoft Product SupportServices for assistance.Error %3: %4. |
| 0xC0000706 | Forsøket på å hente GUID fra serveren %1 mislyktes. |
The attempt to retrieve the GUID from the server %1 failed. |
| 0xC0000712 | Intersite Messaging-tjenesten kan ikke vente på en melding.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to wait for a message.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC0000713 | Det oppstod en feil i Intersite Messaging-tjenesten underforsøk på å starte tjenestekontrollsenderen.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service encountered an error whileattempting to start the Service Control Dispatcher.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC0000714 | Intersite Messaging-tjenesten kan ikke initialiseres.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to initialize.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC0000715 | Intersite Messaging-tjenesten kan ikke opprette en hendelsefor en ventende post for tjenesten %1 via transporten %2.%nFølgende feilmelding vises:%n%n%3%n%nTilleggsdata%nFeilverdi:%n%4 |
The Intersite Messaging Service failed to create an eventfor a pending entry for service %1 via transport %2.%nThe error message is as follows:%n%n%3%n%nAdditional data%nError value:%n%4 |
| 0xC0000716 | Intersite Messaging-tjenesten registrerte etugyldig transportnavn, %1, for tjenesten %2. Enoperasjon kan ikke fortsette. |
The Inter-Site Messaging Service encountered a malformedtransport distinguished name, %1, for service %2. Anoperation was unable to continue. |
| 0xC0000717 | Intersite Messaging-tjenesten kan ikke tildeleminne fra systemet for transporten %1 og tjenesten %2. |
The Inter-Site Messaging Service was unable to allocatememory from the system for transport %1 and service %2. |
| 0xC0000718 | Intersite Messaging-tjenesten kan ikke starte på grunn avat tjenestkontrollbehandlingen ikke kunne registreres.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to start because ofa failure to register the service control handler.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC0000719 | Intersite Messaging-tjenesten kan ikke startepå grunn av en feil under oppstart av RPC-serveren.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to start because ofa failure to start the RPC server.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC000071A | Intersite Messaging-tjenesten kan ikke starteRPC-serveren på grunn av en feil under konstruksjon av en sikkerhetsbeskrivelse.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to start the RPC serverbecause of a failure to construct a security descriptor.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC000071B | Intersite Messaging-tjenesten kan ikke starteRPC-serveren fordi den ikke kunne initialisere protokollsekvensen.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to start the RPC serverbecause it was unable to initialize the protocol sequence.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC000071C | Intersite Messaging-tjenesten kan ikke starteRPC-serveren fordi den ikke kunne registrere grensesnittet.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to start the RPC serverbecause it was unable to register the interface.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC000071D | Intersite Messaging-tjenesten kan ikke starteRPC-serveren fordi den ikke kunne lytte til eksterne prosedyrekall.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service failed to start the RPC serverbecause it was unable to listen for remote procedure calls.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC000071F | Intersite Messaging-tjenesten bad om å avbryteen LDAP-varslingsmelding. Operasjonen mislyktes.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service requested to abandonan LDAP notification message. The operation was unsuccessful.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC0000720 | Intersite Messaging-tjenesten bad om å utføreen LDAP-bindingsoperasjon. Operasjonen mislyktes.%nFølgende feilmelding vises:%n%n%1%n%nTilleggsdata%nFeilverdi:%n%2 |
The Intersite Messaging Service requested to performan LDAP bind operation. The operation was unsuccessful.%nThe error message is as follows:%n%n%1%n%nAdditional data%nError value:%n%2 |
| 0xC0000721 | Oppgaven som overvåker katalogtjenesten for endringer i Inter-SiteTransport-objektene, ble ikke startet.%nTillegg, slettinger og endringer av Inter-Site Transport-objekterblir ikke gjenspeilet i konfigurasjonen av Inter-Site Messaging-tjenesten. |
The task that monitors the Directory Service for changes in the Inter-SiteTransport objects failed to start.%nAdditions, deletions, and modifications of Inter-Site Transport objectswill not be reflected in the configuration of the Inter-Site Messaging Service. |
| 0xC0000725 | Nivået for Standard Server-produktet kan bare heves til en Active Directory Lightweight Directory Services-forekomstrolle i skoger som har mindre enn %1 eksisterende AD LDS-forekomst. Den valgte skogen har %1 eller flere eksisterende AD LDS-forekomster. |
The Standard Server product can only be promoted to an Active Directory Lightweight Directory Services instance role in forests that have less than %1 existing AD LDS instance. The selected forest has %1 or more existing AD LDS instance. |
| 0xC0000726 | Det oppstod en feil i installasjonsprogrammet under lesing av produkttypen for denneserveren. Installasjonsprogrammet kan ikke fortsette. |
Setup encountered an error when reading the product type of thisServer and cannot continue. |
| 0xC0000727 | Navngivingsovervåkeren har blitt slettet. Innta driftsovervåkerrollen, og prøv installasjonen på nytt. |
The naming master has been deleted. Seize the operation master role and retry the installation. |
| 0xC0000728 | Det administrative navneområdet for SMTP-domenet er ikke tilgjengelig for øyeblikket. E-postbasert replikering kan ikke konfigureres før dette problemet er løst.%n%nDet fører til at områdereplikering som bruker SMTP-transporten mellom den lokale domenekontrolleren og alle domenekontrollere på andre områder, mislykkes.%n%nReplikering ved hjelp av SMTP vil blir forsøkt på nytt senere.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The SMTP domain administrative namespace is not available at this time. Mail-based replication cannot be configured until this condition is corrected.%n%nAs a result, intersite replication using the SMTP transport between the local domain controller and all domain controllers in other sites will fail.%n%nReplication using SMTP will be tried again later.%n%nAdditional Data%nError value:%n%2 %1 |
| 0xC000072A | Intersite Messaging-tjenesten som bruker SMTP-transporten, kan ikke fjerne følgende SMTP-rutingdomene.%n%nSMTP-rutingdomene:%n%1%n%nBrukerhandling%n%n- Bekreft at SMTP-tjenesten er installert og fungerer på riktig måte.%n- Bekreft at Active Directory Lightweight Directory Services Services Interfaces (ADSI) er installert og fungerer på dette systemet.%n%nHvis dette problemet vedvarer, kan du forsøke å fjerne domenet manuelt ved hjelp av SMTP-tjenestebehandling.%n%nTilleggsdata%nFeilverdi:%n%3 %2 |
The Intersite Messaging service using the SMTP transport failed to remove the following SMTP routing domain.%n%nSMTP routing domain:%n%1%n%nUser Action%n%n- Verify that the SMTP service is installed and functioning correctly.%n- Verify that Active Directory Lightweight Directory Services Services Interfaces (ADSI) is installed and working on this system.%n%nIf this event continues to occur, try to remove the domain manually using the SMTP service manager.%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC0000745 | Intersite Messaging-tjenesten kan ikke starte RPC-serveren fordi tjenesten ikke kan registrere godkjenningsinformasjon.%n%nTilleggsdata%nFeilverdi:%n%2 %1 |
The Intersite Messaging service failed to start the RPC server because it was unable to register authentication information.%n%nAdditional Data%nError value:%n%2 %1 |
| 0xC0000747 | Dette er replikeringsstatusen for følgende katalogpartisjon på denne katalogserveren.%n%nKatalogpartisjon:%n%1%n%nDenne katalogserveren har ikke mottatt replikeringsinformasjon fra en rekke katalogservere i det konfigurerte ventetidintervallet.%n%nVentetidintervall (timer): %n%4%nAntall katalogservere på alle områder:%n%2%nAntall katalogservere på dette området:%n%3%n%nVentetidintervallet kan endres ved hjelp av følgende registernøkkel.%n%nRegisternøkkel: %nHKLM\\%5\\Intervall for feil i replikeringsventetid (timer)%n%nDu identifiserer katalogserverne etter navn ved hjelp av verktøyet dcdiag.exe.%nDu kan også bruke støtteverktøyet repadmin.exe til å vise replikeringsventetidene for katalogserverne. Kommandoen er \"repadmin /showvector /latency \". |
This is the replication status for the following directory partition on this directory server.%n%nDirectory partition:%n%1%n%nThis directory server has not received replication information from a number of directory servers within the configured latency interval.%n%nLatency Interval (Hours): %n%4%nNumber of directory servers in all sites:%n%2%nNumber of directory servers in this site:%n%3%n%nThe latency interval can be modified with the following registry key.%n%nRegistry Key: %nHKLM\\%5\\Replicator latency error interval (hours)%n%nTo identify the directory servers by name, use the dcdiag.exe tool.%nYou can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is \"repadmin /showvector /latency \". |
| 0xC0000748 | Dette er replikeringsstatusen for følgende katalogpartisjon på denne katalogserveren.%n%nKatalogpartisjon:%n%1%n%nDenne katalogserveren har ikke nylig mottatt replikeringsinformasjon fra en rekke katalogservere. Antallet katalogservere vises inndelt i følgende intervaller.%n%nMer enn %8 timer:%n%2%nMer enn en uke:%n%3%nMer enn en måned:%n%4%nMer enn to måneder:%n%5%nMer enn utløpstid/levetid:%n%6%nUtløpstid/levetid (dager):%n%7%n%nDet kan oppstå feil på katalogservere som ikke replikerer i tide. De går kanskje glipp av passordendringer, og de kan ikke utføre godkjenninger. En domenekontroller som ikke har replikert i løpet av en utløpstid/levetid, har kanskje gått glipp av slettingen av noen objekter, og kan dermed være automatisk blokkert fra fremtidig replikering til den er avstemmet.%n%nDu identifiserer katalogservere etter navn ved hjelp av verktøyet dcdiag.exe.%nDu kan også bruke støtteverktøyet repadmin.exe til å vise replikeringsventetidene for katalogserverne. Kommandoen er \"repadmin /showvector /latency \". |
This is the replication status for the following directory partition on this directory server.%n%nDirectory partition:%n%1%n%nThis directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals.%n%nMore than %8 hours:%n%2%nMore than a week:%n%3%nMore than one month:%n%4%nMore than two months:%n%5%nMore than a tombstone lifetime:%n%6%nTombstone lifetime (days):%n%7%n%nDirectory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.%n%nTo identify the directory servers by name, use the dcdiag.exe tool.%nYou can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is \"repadmin /showvector /latency \". |
| 0xC000074A | Intersite Messaging-tjenesten mottok informasjon om følgende utvidede feilstreng fra LDAP.%n%nUtvidet feilstreng:%n%1%n%nTilleggsdata%nLDAP-feilverdi:%n%5 %4%nUtvidet WIN32-feilverdi:%n%3 %2 |
The Intersite Messaging service received the following extended error string information from LDAP.%n%nExtended error string:%n%1%n%nAdditional Data%nLDAP error value:%n%5 %4%nWIN32 extended error value:%n%3 %2 |
| 0xC000074F | Replikering av Active Directory Lightweight Directory Services registrerte et manglende overordnet objekt for følgende utgående objekt på denne katalogpartisjonen. Et forsøk på å flytte det frittstående objektet til LostAndFound-beholderen mislyktes.%n%nUtgående objekt:%n%1%nGUID for utgående objekt:%n%2%nKatalogpartisjon:%n%3%n%nDet fører til at objektet ble hoppet over for utgående replikering.%n%nDette problemet oppstår når et overordnet objekt slettes og sendes til datasanering når det fortsatt har aktive underordnede objekter. Det fører til at det frittstående objektet flyttes til LostAndFound-beholderen.%n%nTilleggsdata%nFeilverdi:%n%5 %4 |
Active Directory Lightweight Directory Services replication detected a missing parent object for the following outgoing object in this directory partition. An attempt to move the orphaned object to the LostAndFound container failed.%n%nOutgoing object:%n%1%nOutgoing object GUID:%n%2%nDirectory partition:%n%3%n%nAs a result, the object was skipped for outbound replication.%n%nThis erroneous condition occurs when a parent object is deleted and sent to garbage collection when it still has active child objects. As a result, the orphaned object is moved to the LostAndFound container.%n%nAdditional Data%nError value:%n%5 %4 |
| 0xC0000752 | Active Directory Lightweight Directory Services kan ikke installeres fra gjenopprettede filer fordi veiviseren ikke kan kopiere de gjenopprettede AD LDS-filene fra %1 til %2. |
Active Directory Lightweight Directory Services could not install from restored files because the wizard was unable to copy the restored AD LDS files from %1 to %2. |
| 0xC0000755 | Brukeren har ikke tillatelse til å starte en operasjon for navneendring av domene.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
The user does not have the right to invoke a domain rename operation.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC0000756 | Det oppstod en feil i Active Directory Lightweight Directory Services under utføring av en operasjon for navneendring av domene.%n%nBrukerhandling%nSe loggfilen %windir%\\debug\\scriptlog.log hvis du vil ha mer informasjon. Prøv operasjonen for navneendring av domene på nytt.%n%nTilleggsdata%nFeilverdi: %n%1 %2%nIntern ID: %n%3 |
Active Directory Lightweight Directory Services encountered an error while performing a domain rename operation.%n%nUser Action%nFor more information, see the log file %windir%\\debug\\scriptlog.log. Retry the domain rename operation.%n%nAdditional Data%nError value: %n%1 %2%nInternal ID: %n%3 |
| 0xC0000757 | Det oppstod en feil i Active Directory Lightweight Directory Services under lesing av skriptet for navneendring av domenet.%n%nBrukerhandling%nSe loggfilen %windir%\\debug\\scriptlog.log hvis du vil ha mer informasjon. Prøv operasjonen for navneendring av domene på nytt.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
Active Directory Lightweight Directory Services encountered an error while reading the domain rename script.%n%nUser Action%nFor more information, see the log file %windir%\\debug\\scriptlog.log. Retry the domain rename operation.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC0000758 | Det oppstod en feil i Active Directory Lightweight Directory Services under kjøring av skriptet for navneendring av domene.%n%nBrukerhandling%nSe loggfilen %windir%\\debug\\scriptlog.log hvis du vil ha mer informasjon. Prøv operasjonen for navneendring av domene på nytt.%n%nTilleggsdata%nFeilverdi: %n%1%nIntern ID: %n%2 |
Active Directory Lightweight Directory Services encountered an error while running the domain rename script.%n%nUser Action%nFor more information, see the log file %windir%\\debug\\scriptlog.log. Retry the domain rename operation.%n%nAdditional Data%nError value: %n%1%nInternal ID: %n%2 |
| 0xC0000759 | Det oppstod en feil i Active Directory Lightweight Directory Services under tilordning av følgende nye domenenavn.%n%nNytt domenenavn: %n%1%n%nBrukerhandling%nSe loggfilen %windir%\\debug\\scriptlog.log hvis du vil ha mer informasjon. Prøv operasjonen for navneendring av domene på nytt.%n%nTilleggsdata%nFeilverdi: %n%2 %3 |
Active Directory Lightweight Directory Services encountered an error while assigning the following new domain name.%n%nNew domain name: %n%1%n%nUser Action%nFor more information, see the log file %windir%\\debug\\scriptlog.log. Retry the domain rename operation.%n%nAdditional Data%nError value: %n%2 %3 |
| 0xC000075B | Active Directory Lightweight Directory Services kan ikke avslutte systemet.%n%nActive Directory Lightweight Directory Services fremtvinger en avslutting av systemet.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
Active Directory Lightweight Directory Services failed to shut down the system.%n%nActive Directory Lightweight Directory Services will force a system shutdown.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC0000762 | crossRef-objektet har en referanse til en katalogpartisjon (nCName-attributt) med følgende konfliktnavn. Forsøket på å endre katalogpartisjonsnavnet til et navn som ikke er i konflikt, mislyktes.%n%nCrossRef-objekt: %n%1%nKonfliktnavn: %n%2%nForsøkt partisjonsnavn: %n%3%n%nTilleggsdata%n Feilverdi: %n%5 %4 |
The crossRef object has a reference to a directory partition (nCName attribute) with the following conflicting name. The attempt to change the directory partition name to a name that is not conflicting failed.%n%nCrossRef object: %n%1%nConflicting name: %n%2%nAttempted partition name: %n%3%n%nAdditional Data%n Error value: %n%5 %4 |
| 0xC0000764 | Følgende overordnede objekt var ment å skulle fjernes fysisk fra databasen. Under klargjøringen måtte underordnede objekter for dette overordnede objektet flyttes til LostAndFound-beholderen, men det oppstod en navnekonflikt. Forsøket på å gi nytt navn til det underordnede objektet og flytte det til følgende beholder, mislyktes.%n%nOverordnet objekt: %n%1%nUnderordnet objekt: %n%2%nBeholder: %n%4%nNytt navn på underordnet objekt: %n%3%n%nDet overordnede objektet blir ikke lenger slettet fra databasen.%n%nTilleggsdata%nFeilverdi: %n%5 |
The following parent object was intended to be physically removed from the database. In preparation, child objects for this parent needed to be moved to the LostAndFound container but a name conflict occurred. The attempt to rename the child object and move it to the following container failed.%n%nParent object: %n%1%nChild object: %n%2%nContainer: %n%4%nNew name of child object: %n%3%n%nThe parent object will no longer be deleted from the database.%n%nAdditional Data%nError value: %n%5 |
| 0xC0000765 | Active Directory Lightweight Directory Services kan ikke hente replikeringsepoke fra %1. |
Active Directory Lightweight Directory Services failed to retrieve the replication epoch from %1. |
| 0xC0000766 | Active Directory Lightweight Directory Services kan ikke installeres fra de gjenopprettede databasefilene fordi replikeringsepokene (MsDS-ReplicationEpoch) ikke samsvarer. Replikeringsepoken for den gjenopprettede databasen er %1. Replikeringsepoken for konfigurasjonssettet er %2. Dette skyldes vanligvis at en partisjon får nytt navn etter at det ble utført en sikkerhetskopiering. Utfør en ny sikkerhetskopiering, og forsøk å heve nivået på nytt ved hjelp av samsvarende epoker. |
Active Directory Lightweight Directory Services could not be installed from the restored database files because the replication epochs (MsDS-ReplicationEpoch) do not match. The replication epoch of the restored database is %1. The replication epoch of the configuration set is %2. This is usually caused by renaming a partition after the backup was taken. Perform a new backup and try the promotion again using matching epochs. |
| 0xC000076C | Objektet med GUID-en nedenfor ble duplisert under en flytting på tvers av domener. Objektet finnes lokalt med navnet nedenfor, men fantes tidligere i et annet domene.%n%nObjekt-GUID: %n%1%nGjeldende objektnavn: %n%2%nTidligere objektnavn: %n%3%nEpoke for flytting på tvers av domener: %n%4%n%nObjektduplisering under en flytting på tvers av domener kan forekomme når operasjonen lykkes med å opprette objektet i det nye domenet, men mislykkes med å fjerne det opprinnelige objektet i kildedomenet. I dette tilfellet returnerte flyttingen på tvers av domener feilen \"local cleanup required\". Objektet skulle etter planen fjernes manuelt, men ble ikke fjernet.%n%nBrukerhandling%nSlett en av forekomstene av objektet med GUID-en ovenfor fra ett av domenene. |
The object with the following GUID has been duplicated during a cross domain move. The object exists locally with the following name but previously existed in a different domain.%n%nObject GUID: %n%1%nCurrent object name: %n%2%nFormer object name: %n%3%nCross domain move epoch: %n%4%n%nObject duplication during a cross domain move can occur when the operation succeeds in creating the object in the new domain but fails to remove the original object in the source domain. In this case, the cross domain move returned the error \"local cleanup required.?The object is supposed to be removed manually, but was not.%n%nUser Action%nDelete one of the instances of the object with the above GUID from one of the domains. |
| 0xC0000776 | KCC (Knowledge Consistency Checker) registrerte et inkompatibelt UpToDateness Vector-format.%n%nGjeldende formatversjon: %n%1%nForventet formatversjon: %n2%n%nValgalgoritmen for områdetopologigeneratoren mislykkes. |
The Knowledge Consistency Checker (KCC) detected an incompatible up-to-dateness vector format.%n%nCurrent format version: %n%1%nExpected format version: %n2%n%nThe election algorithm for the intersite topology generator will fail. |
| 0xC0000778 | Forsøket på å initialisere skyggekopitjenesten mislyktes for Active Directory Lightweight Directory Services.%n%nForsøk på å sikkerhetskopiere eller gjenopprette Active Directory Lightweight Directory Services ved hjelp av skyggekopitjenesten vil ikke lykkes før dette problemet er løst.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
The attempt to initialize the shadow copy service failed for Active Directory Lightweight Directory Services.%n%nAttempts to backup or restore Active Directory Lightweight Directory Services using the shadow copy service will not succeed until this is corrected.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC0000779 | Internal error: The Active Directory Lightweight Directory Services backup and restore operation encountered an unexpected error.%n%nBackup or restore will not succeed until this is corrected.%n%nAdditional Data%nError value: %n%3 %1%nInternal ID: %n%2 |
Internal error: The Active Directory Lightweight Directory Services backup and restore operation encountered an unexpected error.%n%nBackup or restore will not succeed until this is corrected.%n%nAdditional Data%nError value: %n%3 %1%nInternal ID: %n%2 |
| 0xC000077A | Skyggekopitjenesten kan ikke brukes til å sikkerhetskopiere Active Directory Lightweight Directory Services i gjenopprettingsmodus for katalogtjenesten.%n%nBrukerhandling%nDu må starte på nytt i normalmodus for å utføre sikkerhetskopieringen. |
The shadow copy service cannot be used to back up Active Directory Lightweight Directory Services in directory services restore mode.%n%nUser Action%nYou must restart in normal mode to perform the backup. |
| 0xC000077B | Skyggekopitjenesten kan ikke gjenopprette Active Directory Lightweight Directory Services fordi Active Directory Lightweight Directory Services kjører.%n%nBrukerhandling%nDu må starte på nytt i gjenopprettingsmodus for katalogtjenesten som Active Directory Lightweight Directory Services ikke kjører i. |
The shadow copy service cannot restore Active Directory Lightweight Directory Services because Active Directory Lightweight Directory Services is running.%n%nUser Action%nYou must restart in directory services restore mode in which Active Directory Lightweight Directory Services does not run. |
| 0xC000077C | Sikkerhetskopieringen av Active Directory Lightweight Directory Services ved hjelp av skyggekopitjenesten mislyktes.%n%nBrukerhandling%nVis hendelsesloggen for de aktuelle hendelsene for å finne årsaken til problemet. |
The shadow copy backup for Active Directory Lightweight Directory Services was unsuccessful.%n%nUser Action%nView the event log for subsequent events to determine the cause of the problem. |
| 0xC000077E | Skyggekopitjenesten kan ikke gjenopprette Active Directory Lightweight Directory Services fordi skyggekopien som ble brukt, er foreldet.%n%nUtløpsdato for skyggekopi: %n%1%n%nBrukerhandling%nVelg en nyere skyggekopi, og kjør gjenopprettingen på nytt. |
The shadow copy service cannot restore Active Directory Lightweight Directory Services because the shadow copy used is too old.%n%nShadow copy expiration date: %n%1%n%nUser Action%nSelect a more recent shadow copy and rerun the restore. |
| 0xC000077F | Gjenoppretting av skyggekopien av Active Directory Lightweight Directory Services mislyktes.%n%nInnholdet i Active Directory Lightweight Directory Services-databasen er uforutsigbart.%n%nBrukerhandling%nVis hendelsesloggen for de aktuelle hendelsene for å finne årsaken til problemet. |
Active Directory Lightweight Directory Services shadow copy restore was unsuccessful.%n%nThe contents of the Active Directory Lightweight Directory Services database are unpredictable.%n%nUser Action%nView the event log for subsequent events to determine the cause of the problem. |
| 0xC000078B | Gjenopprettingen av Active Directory Lightweight Directory Services ved hjelp av skyggekopitjenesten mislyktes i klargjøringsfasen.%n%nTilstanden til databasen på disken er ikke endret. |
The restore of Active Directory Lightweight Directory Services by the shadow copy service failed during the preparatory phase.%n%nThe state of the database on the disk has not been altered. |
| 0xC0000797 | Active Directory Lightweight Directory Services kan ikke fjerne alle de etterlatte objektene på den lokale domenekontrolleren. Noen etterlatte objekter ble imidlertid kanskje slettet på denne domenekontrolleren før denne operasjonen stoppet. Alle objekter fikk eksistensen bekreftet på følgende kildedomenekontroller.%n%nKildedomenekontroller: %n%1%nAntall etterlatte objekter som ble slettet: %n%4%n%nBrukerhandling%nUtfør fjerningen av etterlatte objekter på nytt.%n%nTilleggsdata%nFeilverdi: %n%2 %3 |
Active Directory Lightweight Directory Services was unable to remove all of the lingering objects on the local domain controller. However, some lingering objects might have been deleted on this domain controller before this operation stopped. All objects had their existence verified on the following source domain controller.%n%nSource domain controller: %n%1%nNumber of lingering objects successfully deleted: %n%4%n%nUser Action%nRerun the lingering object removal process.%n%nAdditional Data%nError value: %n%2 %3 |
| 0xC0000798 | Active Directory Lightweight Directory Services kan ikke bekrefte eksistensen av alle etterlatte objekter på den lokale domenekontrolleren i bekreftelsesmodus. Etterlatte objekter som ble funnet før prosessen ble avsluttet, fikk imidlertid eksistensen bekreftet på følgende kildedomenekontroller. Disse objektene har blitt oppført i tidligere hendelsesloggoppføringer.%n%nKildedomenekontroller: %n%1%nAntall etterlatte objekter som ble registrert og bekreftet: %n%4%n%nTilleggsdata%nFeilverdi: %n%2 %3 |
Active Directory Lightweight Directory Services was unable to verify the existence of all lingering objects on the local domain controller in advisory mode. However, lingering objects found prior to the process quitting have had their existence verified on the following source domain controller. These objects have been listed in past event log entries.%n%nSource domain controller: %n%1%nNumber of lingering objects identified and verified: %n%4%n%nAdditional Data%nError value: %n%2 %3 |
| 0xC000079B | Active Directory Lightweight Directory Services kan ikke slette følgende etterlatte objekt på den lokale domenekontrolleren fordi det kanskje har blitt oppdatert eller slettet i løpet av fjerningen av det etterlatte objektet. Objektet ble slettet og datasanert på følgende kildedomenekontroller.%n%nObjekt: %n%1%nObjekt-GUID: %n%2%nKildedomenekontroller: %n%3%n%nBrukerhandling%nUtfør fjerningen av etterlatte objekter på nytt. |
Active Directory Lightweight Directory Services was unable to delete the following lingering object on the local domain controller because it might have been updated or deleted during the lingering object removal process. The object had been deleted and garbage collected on the following source domain controller.%n%nObject: %n%1%nObject GUID: %n%2%nSource domain controller: %n%3%n%nUser action%nRerun the lingering object removal process. |
| 0xC000079C | Active Directory Lightweight Directory Services fant et kritisk systemobjekt på den lokale domenekontrolleren som en kandidat for sletting i løpet av fjerningen av etterlatte objekter. Dette objektet ble slettet og datasanert på følgende kildedomenekontroller.%n%nObjekt: %n%1%nObjekt-GUID: %n%2%nKildedomenekontroller: %n%3%n%nActive Directory Lightweight Directory Services sletter ikke et kritisk systemobjekt selv om slettingen og datasanseringen av objektet ble registrert på kildedomenekontrolleren. |
Active Directory Lightweight Directory Services identified a critical system object on the local domain controller as a candidate for deletion during the lingering object removal process. This object had been deleted and garbage collected on the following source domain controller.%n%nObject: %n%1%nObject GUID: %n%2%nSource domain controller: %n%3%n%nActive Directory Lightweight Directory Services will not delete a critical system object even though its deletion and garbage collection was identified on the source domain controller. |
| 0xC000079D | Active Directory Lightweight Directory Services kan ikke slette følgende etterlatte objekt på den lokale domenekontrolleren. Objektet ble slettet og datasanert på følgende kildedomenekontroller, men slettingen var ikke replikert på den lokale domenekontrolleren.%n%nObjekt: %n%1%nObjekt-GUID: %n%2%nKildedomenekontroller: %n%3%n%nFjerningen av det etterlatte objektet fortsetter, men dette objektet blir ikke slettet fra den lokale domenekontrolleren.%n%nTilleggsdata%nFeilverdi: %n%4 %5 |
Active Directory Lightweight Directory Services was unable to delete the following lingering object on the local domain controller. The object had been deleted and garbage collected on the following source domain controller, but the deletion had not been replicated on the local domain controller.%n%nObject: %n%1%nObject GUID: %n%2%nSource domain controller: %n%3%n%nThe lingering object removal process will continue, but this object will not be deleted from the local domain controller.%n%nAdditional Data%nError value: %n%4 %5 |
| 0xC000079E | Active Directory Lightweight Directory Services kan ikke slette et etterlatt objekt på en lokal domenekontroller. Objektet ble slettet og datasanert på følgende kildedomenekontroller, men slettingen var ikke replikert på den lokale domenekontrolleren.%n%nObjekt-GUID: %n%2%nKildedomenekontroller: %n%3%n%nFjerningen av det etterlatte objektet fortsetter ikke.%n%nTilleggsdata%nFeilverdi: %n%3 %4 |
Active Directory Lightweight Directory Services was unable to delete a lingering object on the local domain controller. The object had been deleted and garbage collected on the following source domain controller, but the deletion had not been replicated on the local domain controller.%n%nObject GUID: %n%2%nSource domain controller: %n%3%n%nThe lingering object removal process will not continue.%n%nAdditional Data%nError value: %n%3 %4 |
| 0xC00007A6 | Det oppstod en replikeringsfeil i Active Directory Lightweight Directory Services fordi et nytt crossRef-objekt ble lagt til i konfigurasjonssettet med samme navn som en lokal katalogpartisjon.%n%nLokal katalogpartisjon: %n%1%n%ncrossRef-objektet kan ikke legges til før den lokale katalogpartisjonen med samme navn er fjernet. Dette forekommer vanligvis når et crossRef-objekt har blitt slettet og gjenopprettet hurtig på navngivingsovervåkeren og endringene har blitt replikert. Feilen oppstår fordi KCC (Knowledge Consistency Checker) ikke har fjernet den lokale katalogpartisjonen. Dette problemet løser seg selv når KCC har fjernet partisjonen, men replikeringen kan bli forsinket.%n%nBrukerhandling%nDu kan løse denne konflikten ved å slette det nylig opprettede crossRef-objektet og opprette det på nytt når den lokale katalogpartisjonen har blitt fjernet fra konfigurasjonssettet. |
Active Directory Lightweight Directory Services encountered a replication error because a new crossRef object was added to the configuration set with the same name as a local directory partition.%n%nLocal directory partition: %n%1%n%nThe crossRef object cannot be added until the conflicting local directory partition is removed. This usually occurs when a crossRef object has been deleted and recreated rapidly on the naming master, and the changes have been replicated. The error occurs because the Knowledge Consistency Checker (KCC) has not yet had a chance to remove the local directory partition. This situation will correct itself when the KCC finishes removing the partition, but replication may be delayed.%n%nUser Action%nYou can rectify this conflict by deleting the newly created crossRef object and creating it again once the local directory partition has been removed from the configuration set. |
| 0xC00007A8 | Internal event: The following directory service received an exception from a remote procedure call (RPC) connection. The operation may have failed.%n%nProcess ID: %n%7%n%nReported error information:%nError value: %n%1 (%2)%ndirectory service: %n%3%n%nExtended error information:%nError value: %n%4 (%5)%ndirectory service: %n%6%n%nAdditional Data%nInternal ID: %n%8 |
Internal event: The following directory service received an exception from a remote procedure call (RPC) connection. The operation may have failed.%n%nProcess ID: %n%7%n%nReported error information:%nError value: %n%1 (%2)%ndirectory service: %n%3%n%nExtended error information:%nError value: %n%4 (%5)%ndirectory service: %n%6%n%nAdditional Data%nInternal ID: %n%8 |
| 0xC00007A9 | Internal event: This log entry is a continuation from the preceding extended error information entry on the following error and directory service.%n%nExtended information:%nError value: %n%1 (%2)%ndirectory service: %n%3%n%nSupplemental information:%nDetection location: %n%4%nGenerating component: %n%5%nTime at directory service: %n%6%n%nAdditional Data%nError value: %n%1 (%2) |
Internal event: This log entry is a continuation from the preceding extended error information entry on the following error and directory service.%n%nExtended information:%nError value: %n%1 (%2)%ndirectory service: %n%3%n%nSupplemental information:%nDetection location: %n%4%nGenerating component: %n%5%nTime at directory service: %n%6%n%nAdditional Data%nError value: %n%1 (%2) |
| 0xC00007AA | Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.%n%ndirectory service: %n%3%n%nAdditional Data%nError value: %n%1 (%2) |
Internal event: The local directory service received an exception from a remote procedure call (RPC) connection. Extended error information is not available.%n%ndirectory service: %n%3%n%nAdditional Data%nError value: %n%1 (%2) |
| 0xC00007AB | Internal event: The following local directory service received an exception from a remote procedure call (RPC) connection. Extensive RPC information was requested. This is intermediate information and might not contain a possible cause.%n%nProcess ID: %n%7%n%nReported error information:%nError value: %n%1 (%2)%ndirectory service: %n%3%n%nExtensive error information:%nError value: %n%4 %5%ndirectory service: %n%6%n%nAdditional Data%nInternal ID: %n%8 |
Internal event: The following local directory service received an exception from a remote procedure call (RPC) connection. Extensive RPC information was requested. This is intermediate information and might not contain a possible cause.%n%nProcess ID: %n%7%n%nReported error information:%nError value: %n%1 (%2)%ndirectory service: %n%3%n%nExtensive error information:%nError value: %n%4 %5%ndirectory service: %n%6%n%nAdditional Data%nInternal ID: %n%8 |
| 0xC00007AC | Den lokale katalogtjenesten har avvist et replikeringsforsøk på følgende katalogpartisjon. Følgende katalogtjeneste bad om å replikere ett eller flere objekter fra en uautorisert katalogpartisjon, men forsøket mislyktes.%n%nKatalogtjeneste: %n%1%nKatalogpartisjon: %n%2%n%nDette kan utgjøre en sikkerhetsrisiko. |
The local directory service has denied a replication attempt on the following directory partition. The following directory service requested to replicate one or more objects from an unauthorized directory partition and the attempt failed.%n%ndirectory service: %n%1%nDirectory partition: %n%2%n%nThis might pose a security risk. |
| 0xC00007B9 | Følgende katalogtjeneste sendte en replikeringsforespørsel for en skrivbar katalogpartisjon som ble avvist av den lokale katalogtjenesten. Den anmodende katalogtjenesten har ikke tilgang til en skrivbar kopi av denne katalogpartisjonen.%n%nAnmodende katalogtjeneste: %n%2%nKatalogpartisjon: %n%1%n%nBrukerhandling%nHvis den anmodende katalogtjenesten må ha en skrivbar kopi av denne partisjonen, bekrefter du at sikkerhetsbeskrivelsen på denne katalogpartisjonen har riktig konfigurasjon for tilgangsrettigheten Replication Get Changes All. Du får kanskje også denne meldingen i løpet av overføringen etter at en underordnet partisjon har blitt fjernet. Denne meldingen forsvinner når kunnskap om fjerningen av den underordnede partisjonen har blitt replikert i hele skogen. |
The following directory service made a replication request for a writable directory partition that has been denied by the local directory service. The requesting directory service does not have access to a writable copy of this directory partition.%n%nRequesting directory service: %n%2%nDirectory partition: %n%1%n%nUser Action%nIf the requesting directory service must have a writable copy of this partition, verify that the security descriptor on this directory partition has the correct configuration for the Replication Get Changes All access right. You may also get this message during the transition period after a child partition has been removed. This message will cease when knowledge of the child partition removal has replicated throughout the forest. |
| 0xC00007BA | IKKE BRUKT |
UNUSED |
| 0xC00007BB | Active Directory Lightweight Directory Services kan ikke opprette standard sikkerhetsbeskrivelse på riktig måte for følgende programkatalogpartisjon.%n%nProgramkatalogpartisjon: %n%3%n%nBrukerhandling%nSe gjennom tilgangskontrollisten (ACL) på den nylig opprettede programkatalogpartisjonen. Kontroller at tilgangsrettigheten Replication Get Changes All er tilordnet til både gruppen Domenekontrollere i organisasjonen og gruppen Skrivebeskyttede domenekontrollere i organisasjonen, og fjern rettigheten fra gruppen Domenekontrollere.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
Active Directory Lightweight Directory Services was unable to correctly create the default security descriptor for the following application directory partition.%n%nApplication directory partition: %n%3%n%nUser Action%nReview the access control list (ACL) on the newly created application directory partition. Ensure the Replication Get Changes All access right is assigned to both the Enterprise Domain Controllers group and the Enterprise Read-only Domain Controllers group, and remove the right from the domain Domain Controllers group.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC00007BD | Active Directory Lightweight Directory Services har ikke tilgang til SIDen (security identifier) som er knyttet til gruppen Domenekontrollere i organisasjonen eller gruppen Skrivebeskyttede domenekontrollere i organisasjonen. |
Active Directory Lightweight Directory Services was unable to access the security identifier (SID) associated with the Enterprise Domain Controllers group or the Enterprise Read-only Domain Controllers group. |
| 0xC00007BE | Active Directory Lightweight Directory Services kan ikke slette tilgangskontrolloppføringen (ACE) for sikkerhetsgruppen Domenekontrollere på den nylig opprettede programkatalogpartisjonen. Denne tilgangskontrolloppføringen gav sikkerhetsgruppen Domenekontrollere rettigheten Replication Get Changes All for følgende nylig opprettede programkatalogpartisjon.%n%nProgramkatalogpartisjon: %n%3%n%nBrukerhandling%nSe gjennom tilgangskontrollisten (ACL) på den nylig opprettede programkatalogpartisjonen. Kontroller at rettigheten Replication Get Changes All er gitt til både gruppen Domenekontrollere i organisasjonen og gruppen Skrivebeskyttede domenekontrollere i organisasjonen, og fjern rettigheten fra gruppen Domenekontrollere.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
Active Directory Lightweight Directory Services was unable to delete the access control entry (ACE) for the domain Domain Controllers security group on the newly created application directory partition. This ACE gave the domain Domain Controllers security group the Replication Get Changes All right for the following newly created application directory partition.%n%nApplication directory partition: %n%3%n%nUser Action%nReview the access control list (ACL) on the newly created application directory partition. Ensure the right Replication Get Changes All is given to both the Enterprise Domain Controllers group and the Enterprise Read-only Domain Controllers group, and remove that right from the domain Domain Controllers group.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC00007BF | Active Directory Lightweight Directory Services kan ikke opprette en tilgangskontrolloppføring (ACE) for gruppen Domenekontrollere i organisasjonen eller gruppen Skrivebeskyttede domenekontrollere i organisasjonen på en nylig opprettet programkatalogpartisjon.%n%nProgramkatalogpartisjon: %n%3%n%nBrukerhandling%nSe gjennom tilgangskontrollisten (ACL) på den nylig opprettede programkatalogpartisjonen. Kontroller at rettigheten Replication Get Changes All er gitt til både gruppen Domenekontrollere i organisasjonen og gruppen Skrivebeskyttede domenekontrollere i organisasjonen, og fjern rettigheten fra gruppen Domenekontrollere. |
Active Directory Lightweight Directory Services failed to create an access control entry (ACE) for the Enterprise Domain Controllers group or the Enterprise Read-only Domain Controllers group on a newly created application directory partition.%n%nApplication directory partition: %n%3%n%nUser Action%nReview the access control list (ACL) on the newly created application directory partition. Ensure the Replication Get Changes All access right is assigned to both the Enterprise Domain Controllers group and the Enterprise Read-only Domain Controllers group, and remove the right from the domain Domain Controllers group. |
| 0xC00007C4 | Replikeringen av Active Directory Lightweight Directory Services fant objekter i følgende partisjonsom har blitt slettet fra Active Directory Lightweight Directory Services-databasen for de lokale domenekontrollerne. Ikkealle direkte eller transitive replikeringspartnere replikerte i slettingen før et gitt antalldager for utløpstid/levetid hadde forløpt. Objekter som har blitt slettet og datasanertfra en Active Directory Lightweight Directory Services-partisjon, men som fortsatt finnes i de skrivbare partisjonene for andre domenekontrollere på sammedomene, eller skrivebeskyttede partisjoner for globale katalogservere på andre domener i skogen, er kjent som\"etterlatte objekter\". %n%n%nKildedomenekontroller: %n%1%nObjekt: %n%2%nObjekt-GUID: %n%3Denne hendelsen logges fordi kildedomenekontrolleren inneholder et etterlatt objekt som ikkeeksisterer i Active Directory Lightweight Directory Services-databasen for de lokale domenekontrollerne. Dette replikeringsforsøket har blitt blokkert.%n%nDen beste løsningen på dette problemet er å identifisere og fjerne alle etterlatte objekter i skogen.%n%n%nBrukerhandling:%n%nFjern etterlatte objekter:%n%nHandlingsplanen for å gjenopprette etter denne feilen, finner du på http://support.microsoft.com/?id=314282.%n%nHvis både kilde- og måldomenekontrollerne er domenekontrollere for Windows Server 2003, installerer du støtteverktøyene som finnes påinstallasjons-CDen. Hvis du vil vise hvilke objekter som ville blitt slettet uten å faktisk utføreslettingen, kjører du kommandoen \"repadmin /removelingeringobjects /ADVISORY_MODE\".Hendelsesloggene i kildedomenekontrolleren nummererer alle etterlatte objekter. Du fjerner etterlatte objekterfra kildedomenekontrolleren ved å kjørekommandoen \"repadmin /removelingeringobjects \".%n%nHvis kilde- eller måldomenekontrolleren er en domenekontroller for Windows 2000 Server, finner du mer informasjon om hvordan dufjerner etterlatte objekter i kildedomenekontrolleren på http://support.microsoft.com/?id=314282, eller fraMicrosofts kundestøttetjeneste.%n%nHvis det kreves at Active Directory Lightweight Directory Services-replikeringen skal fungere umiddelbart uavhengig av kostnad, ogdet det ikke er tid til å fjerne etterlatte objekter, aktiverer du løs replikeringskonsekvens ved å oppheve angivelsen av følgenderegisternøkkel:%n%nRegisternøkkel:%nHKLM\\%5\\%4%n%nReplikeringsfeil mellom domenekontrollere som deler en felles partisjon, kan hindre at bruker- og datamaskinkontoer,klareringsforhold, klareringsforholdenes passord, sikkerhetsgrupper,sikkerhetsgruppemedlemskap og andre Active Directory Lightweight Directory Services-konfigurasjonsdata varierer fra domenekontroller til domenekontroller,noe som kan påvirke muligheten til å logge på, søke etter interessante objekter og utføre andre kritiske operasjoner.Disse inkonsekvensene løses først når replikeringsfeil løses. Domenekontrollere som mislykkes på grunn avat den inngående replikeringen slettet objekter i løpet av utløpstiden/levetiden, forblir inkonsekvente tiletterlatte objekter fjernes manuelt av en systemansvarlig fra hver lokale domenekontroller.%n%nEtterlatte objekter kan stoppes ved å sørge for at alle domenekontrollere i skogensom kjører Active Directory Lightweight Directory Services, er tilknyttet ved hjelp av en tilkoblingstopologi som omfatter hele treet, og som utførerinngående replikering før antall dager i utløpstiden er omme. |
Active Directory Lightweight Directory Services Replication encountered the existence of objects in the following partitionthat have been deleted from the local domain controllers (DCs) Active Directory Lightweight Directory Services database. Notall direct or transitive replication partners replicated in the deletion before the tombstonelifetime number of days passed. Objects that have been deleted and garbagecollected from an Active Directory Lightweight Directory Services partition but still exist in the writable partitions of other DCs in the samedomain, or read-only partitions of global catalog servers in other domains in the forest are known as\"lingering objects\". %n%n%nSource domain controller: %n%1%nObject: %n%2%nObject GUID: %n%3This event is being logged because the source DC contains a lingering object which does notexist on the local DCs Active Directory Lightweight Directory Services database. This replication attempt has been blocked.%n%nThe best solution to this problem is to identify and remove all lingering objects in the forest.%n%n%nUser Action:%n%nRemove Lingering Objects:%n%nThe action plan to recover from this error can be found at http://support.microsoft.com/?id=314282.%n%nIf both the source and destination DCs are Windows Server 2003 DCs, then install the support tools included on theinstallation CD. To see which objects would be deleted without actually performing thedeletion run \"repadmin /removelingeringobjects /ADVISORY_MODE\".The event logs on the source DC will enumerate all lingering objects. To remove lingering objectsfrom a source domain controller run\"repadmin /removelingeringobjects \".%n%nIf either source or destination DC is a Windows 2000 Server DC, then more information on how toremove lingering objects on the source DC can be found at http://support.microsoft.com/?id=314282 or fromyour Microsoft support personnel.%n%nIf you need Active Directory Lightweight Directory Services replication to function immediately at all costs and don't havetime to remove lingering objects, enable loose replication consistency by unsetting the followingregistry key:%n%nRegistry Key:%nHKLM\\%5\\%4%n%nReplication errors between DCs sharing a common partition can prevent user and computer accounts,trust relationships, their passwords, security groups,security group memberships and other Active Directory Lightweight Directory Services configuration data to vary between DCs,affecting the ability to log on, find objects of interest and perform other critical operations.These inconsistencies are resolved once replication errors are resolved. DCs that fail to inboundreplicate deleted objects within tombstone lifetime number of days will remain inconsistent untillingering objects are manually removed by an administrator from each local DC.%n%nLingering objects may be prevented by ensuring that all domain controllers in the forest arerunning Active Directory Lightweight Directory Services, are connected by a spanning tree connection topology and performinbound replication before Tombstone Live number of days pass. |
| 0xC00007C8 | Internal error: Active Directory Lightweight Directory Services was unable to register this domain controller as a global catalog.%n%nThis domain controller will not advertise itself as a global catalog until the error is resolved and the domain controller is restarted.%n%nAdditional Data%nError value: %n%1 %2 |
Internal error: Active Directory Lightweight Directory Services was unable to register this domain controller as a global catalog.%n%nThis domain controller will not advertise itself as a global catalog until the error is resolved and the domain controller is restarted.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC00007CA | Internal event: Active Directory Lightweight Directory Services failed to refresh the Kerberos security tickets.%n%nThis directory service may be unable to gain proper authorization until the Kerberos security tickets automatically refresh.%n%nAdditional Data%nError value: %n%1 %2 |
Internal event: Active Directory Lightweight Directory Services failed to refresh the Kerberos security tickets.%n%nThis directory service may be unable to gain proper authorization until the Kerberos security tickets automatically refresh.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC00007D1 | Standard sikkerhetsinnstillinger for NTFS har ikke blitt tatt i bruk i Active Directory Lightweight Directory Services-mapper.%n%nBrukerhandling%nForsøk å angi standard sikkerhetsinnstillinger på nytt ved hjelp av kommandolinjeverktøyet Ntdsutil.%n%nTilleggsdata%nFeilverdi: %n%1 %2%nIntern ID: %n%3 |
The default NTFS security settings have not been applied to Active Directory Lightweight Directory Services folders.%n%nUser Action%nAttempt to set default security settings again using the Ntdsutil command-line tool.%n%nAdditional Data%nError value: %n%1 %2%nInternal ID: %n%3 |
| 0xC00007D2 | Det har oppstått problemer i Knowledge Consistency Checker (KCC) fordi attributtet i objektet nedenfor ikke hadde nok verdier.%n%nObjekt:%n%1%nAttributtnavn:%n%2%n%n%nEt forsøk på å replikere dette attributtet vil bli utført på nytt ved neste planlagte replikering.%n%nBrukerhandling%nHvis dette forholdet vedvarer, kontrollerer du at replikeringen fungerer som den skal. |
The Knowledge Consistency Checker (KCC) has detected problems because the attribute on the following object did not have enough values.%n%nObject:%n%1%nAttribute name:%n%2%n%n%nAn attempt to replicate this attribute will be tried again at the next scheduled replication.%n%nUser Action%nIf this condition continues, verify that replication is working correctly. |
| 0xC00007D3 | Internal event: During intersite replication, Active Directory Lightweight Directory Services received an update request message for a writeable directory partition from the following domain controller. However, this request cannot be serviced through mail-based replication and the updates will be ignored.%n%nDirectory partition: %n%1%nDomain controller: %n%2 |
Internal event: During intersite replication, Active Directory Lightweight Directory Services received an update request message for a writeable directory partition from the following domain controller. However, this request cannot be serviced through mail-based replication and the updates will be ignored.%n%nDirectory partition: %n%1%nDomain controller: %n%2 |
| 0xC00007D4 | Internal event: During intersite replication, Active Directory Lightweight Directory Services received an update reply message for the following directory partition from the following domain controller. However, the request cannot be serviced through mail-based replication and the updates will be ignored.%n%nDirectory partition:%n%1%nDomain controller:%n%2 |
Internal event: During intersite replication, Active Directory Lightweight Directory Services received an update reply message for the following directory partition from the following domain controller. However, the request cannot be serviced through mail-based replication and the updates will be ignored.%n%nDirectory partition:%n%1%nDomain controller:%n%2 |
| 0xC00007D8 | Internal error: The security descriptor propagation task encountered an error while processing the following object. The propagation of security descriptors may not be possible until the problem is corrected.%n%nObject:%n%4%n%nAdditional Data%nError value:%n%1 %2%nInternal ID:%n%3 |
Internal error: The security descriptor propagation task encountered an error while processing the following object. The propagation of security descriptors may not be possible until the problem is corrected.%n%nObject:%n%4%n%nAdditional Data%nError value:%n%1 %2%nInternal ID:%n%3 |
| 0xC00007DB | subRefs-attributtet for følgende domeneobjekt har en verdi som ikke samsvarer med et gyldig objekt. Dette gjør at Active Directory Lightweight Directory Services ikke fungerer normalt.%n%nDomeneobjekt: %n%1%nVerdi: %n%2%n%nBrukerhandling%nKjør analysealternativet for semantikkdatabasen i verktøyet Dsdbutil for å løse problemet.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
The subRefs attribute on the following domain object has a value that does not correspond to a valid object. This will prevent Active Directory Lightweight Directory Services from functioning normally.%n%nDomain object: %n%1%nValue: %n%2%n%nUser Action%nRun the semantic database analysis option in the Dsdbutil tool to correct the problem.%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC00007E0 | Internal error: Active Directory Lightweight Directory Services was unable to rebuild the following number of indices and has failed.%n%nIndices: %n%1%n%nAdditional Data%nError value:%n%2 %3 |
Internal error: Active Directory Lightweight Directory Services was unable to rebuild the following number of indices and has failed.%n%nIndices: %n%1%n%nAdditional Data%nError value:%n%2 %3 |
| 0xC00007E5 | Active Directory Lightweight Directory Services kan ikke opprette et objekt for en ekstern katalogtjeneste.%n%nKatalogtjeneste (tom = lokal katalogtjeneste): %n%1%nObjekt: %n%2%nObjekt-GUID: %n%3%n%nTilleggsdata%nFeilverdi: %n%4%nUtvidet feilverdi: %n%5 %6%nEkstern intern ID: %n%7%nIntern ID: %n%8 |
Active Directory Lightweight Directory Services was unable to create an object on a remote directory service.%n%ndirectory service (blank = local directory service): %n%1%nObject: %n%2%nObject GUID: %n%3%n%nAdditional Data%nError value: %n%4%nExtended error value: %n%5 %6%nRemote Internal ID: %n%7%nInternal ID: %n%8 |
| 0xC00007E6 | Driftsovervåkerrollene som innehas av denne katalogserveren, kan ikke overføres til følgene eksterne katalogserver.%n%nEkstern katalogserver: %n%1%n%nDette hindrer fjerning av denne katalogserveren.%n%nBrukerhandling%nUndersøk hvorfor den eksterne katalogserveren kanskje ikke kan godta driftsovervåkerrollene, eller overfør alle rollene som innehas av denne katalogserveren, manuelt til den eksterne katalogserveren. Deretter forsøker du å fjerne denne katalogserveren på nytt.%n%nTilleggsdata%nFeilverdi:%n%4 %2%nUtvidet feilverdi:%n%3%nIntern ID:%n%5 |
The operations master roles held by this directory server could not transfer to the following remote directory server.%n%nRemote directory server: %n%1%n%nThis is preventing removal of this directory server.%n%nUser Action%nInvestigate why the remote directory server might be unable to accept the operations master roles, or manually transfer all the roles that are held by this directory server to the remote directory server. Then, try to remove this directory server again.%n%nAdditional Data%nError value:%n%4 %2%nExtended error value:%n%3%nInternal ID:%n%5 |
| 0xC00007E7 | Denne katalogserveren kan ikke replikere endringer til den eksterne katalogserveren nedenfor for den angitte katalogpartisjonen.%n%nEkstern katalogserver:%n%2%nKatalogpartisjon:%n%1%n%nDen lokale domenekontrolleren kan ikke fjerne denne partisjonen.%n%nBrukerhandling%nUndersøk hvorfor replikering mellom disse to domenekontrollerne ikke kan utføres.%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
This directory server was unable to replicate changes to the following remote directory server for the following directory partition.%n%nRemote directory server:%n%2%nDirectory partition:%n%1%n%nThe local domain controller cannot complete removal of this partition.%n%nUser Action%nInvestigate why replication between these two domain controllers cannot be performed.%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC00007E9 | Active Directory Lightweight Directory Services kan ikke hente legitimasjonen for brukeren som ber om denne operasjonen fra sikkerhetsdelsystemet.%n%nMåldomenekontroller: %n%1%n%nDomenekontrolleren kan ikke fullføre den eksterne operasjonen som brukeren ber om.%n%nBrukerhandling%nBekreft at riktig delegeringsnivå for å utføre operasjonen ble forespurt.%n%nTilleggsdata%nFeilverdi: %n%2%nFunksjon: %n%3 |
Active Directory Lightweight Directory Services was unable to get the credentials of the user requesting this operation from the security sub-system.%n%nTarget domain controller: %n%1%n%nThe domain controller will not be able to complete the remote operation requested by the user.%n%nUser Action%nVerify that the appropriate level of delegation to perform the operation was requested.%n%nAdditional Data%nError value: %n%2%nFunction: %n%3 |
| 0xC00007EA | Det ble registrert en midlertidig bufferinkonsekvens i Active Directory Lightweight Directory Services. Programkatalogpartisjonen ble derfor ikke opprettet, og operasjonen mislyktes.%n%nProgramkatalogpartisjon: %n%1%n%nBrukerhandling%nUtfør operasjonen på nytt. |
Active Directory Lightweight Directory Services has encountered a temporary cache inconsistency. Therefore, the application directory partition was not created and the operation failed.%n%nApplication directory partition: %n%1%n%nUser Action%nTry the operation again. |
| 0xC00007EB | Programkatalogpartisjonen kan ikke opprettes fordi brukeren ikke har tilstrekkelige tillatelser til å endre crossRef-objektet.%n%nProgramkatalogpartisjon: %n%1%nCrossRef-objekt: %n%2 |
The application directory partition could not be created because the user does not have sufficient permissions to modify the crossRef object.%n%nApplication directory partition: %n%1%nCrossRef object: %n%2 |
| 0xC00007EC | Det oppstod en feil under endring av crossRef-objektet for å fullføreopprettingen av programkatalogpartisjonen.%n%nProgramkatalogpartisjon:%n%1%nCross-Ref-objekt:%n%2%nFeil%n%3%n%nOperasjonen mislykkes.%n%nBrukerhandling%nForsøk å løse feilen, og utfør operasjonen på nytt.%n%nTilleggsdata%nIntern ID (DSID):%n%4 |
There was an error modifying the cross-ref to complete thecreation of the Application Directory Partition.%n%nApplication Partition Directory:%n%1%nCross-Ref Object:%n%2%nError%n%3%n%nThe operation will be failed.%n%nUser Action%nPlease try to resolve the error condition and retry the operation.%n%nAdditional data%nInternal ID (DSID):%n%4 |
| 0xC00007EF | Finner ikke Configuration-objektet for domeneservertjenesten.Det har kanskje blitt slettet ved en tilfeldighet. ActiveDirectory kan fungere normalt, men dukan ikke angi bestemte tjenesteparametere,for eksempel LDAP-begrensninger, standard spørringspolicyer ogSPN-tilordninger.%n%nConfiguration-objekt for domeneservertjeneste:%n%1%nFeil:%n%2 (%3)%n%nBrukerhandling:%nForsøk å gjenopprette Configuration-objektet for domeneservertjenesten. |
The DS Service Configuration object is not found.It might have been accidentally deleted. The ActiveDirectory will be able to operate normally, but youwill not be able to set certain service parameters,such as LDAP limits, default query policies, andSPN mappings.%n%nDS Service Configuration object:%n%1%nError:%n%2 (%3)%n%nUser Action:%nTry to restore the DS Service Configuration object. |
| 0xC00007F0 | Klargjøring av sikkerhetskopiering av Active Directory Lightweight Directory Services mislyktes. Sikkerhetskopieringen fortsetter ikke.%n |
Active Directory Lightweight Directory Services backup preparation failed. The backup will not continue.%n |
| 0xC00007F1 | Active Directory Lightweight Directory Services kan ikke angi registernøkkelen for replikeringskonsekvens. Kontrollerverdien for følgende registernøkkel.%n%nRegisternøkkel:%nHKeyLocalMachine\\%1\\%2 |
Active Directory Lightweight Directory Services was unable to set the replication consistency registry key. Please check thevalue for the following registry key.%n%nRegistry Key:%nHKeyLocalMachine\\%1\\%2 |
| 0xC00007FA | Det har gått for lang tid siden maskinen replikerte med den navngitte kildemaskinen.Tiden mellom replikeringene med denne kilden har overskredet utløpstiden/levetiden.Replikeringen har blitt stoppet med denne kilden.%n%nÅrsaken til at replikeringen ikke kan fortsette, er at de to domenekontrollerne kanskje inneholder etterlatteobjekter. Objekter som har blitt slettet og datasanertfra en Active Directory Lightweight Directory Services-partisjon, men fortsatt finnes i de skrivbare partisjonene for andre domenekontrollere på sammedomene, eller skrivebeskyttede partisjoner for globale katalogservere på andre domener i skogen, er kjent som\"etterlatte objekter\". Hvis den lokale måldomenekontrolleren replikerte med kildedomenekontrolleren, ville disse potensielleetterlatte objektene blitt opprettet på nytt i den lokale Active Directory Lightweight Directory Services-databasen.%n%nTid siden forrige vellykkede replikering:%n%1%nAktiverings-ID for kildekatalogserver:%n%2%nNavn på kildekatalogserver:%n%3%nUtløpstid/levetid (dager):%n%4%n%nReplikeringsoperasjonen mislyktes.%n%n%nBrukerhandling:%nHandlingsplanen for å gjenopprette etter denne feilen, finner du på http://support.microsoft.com/?id=314282.%n%nHvis både kilde- og måldomenekontrollerne er domenekontrollere for Windows Server 2003, installerer du støtteverktøyene som finnes påinstallasjons-CDen. Hvis du vil vise hvilke objekter som ville blitt slettet uten å faktisk utføreslettingen, kjører du kommandoen \"repadmin /removelingeringobjects /ADVISORY_MODE\".Hendelsesloggene i kildedomenekontrolleren nummererer alle etterlatte objekter. Du fjerner etterlatte objekterfra kildedomenekontrolleren ved å kjørekommandoen \"repadmin /removelingeringobjects \".%n%nHvis kilde- eller måldomenekontrolleren er en domenekontroller for Windows 2000 Server, finner du mer informasjon om hvordan dufjerner etterlatte objekter i kildedomenekontrolleren på http://support.microsoft.com/?id=314282, eller fraMicrosofts kundestøttetjeneste.%n%nHvis det kreves at Active Directory Lightweight Directory Services-replikeringen skal fungere umiddelbart uavhengig av kostnad, ogdet ikke er tid til å fjerne etterlatte objekter, aktiverer du replikering ved å sette følgenderegisternøkkel til en ikke-nullverdi:%n%nRegisternøkkel:%nHKLM\\%6\\%5%n%nReplikeringsfeil mellom domenekontrollere som deler en felles partisjon, kan hindre at bruker- og datamaskinkontoer,klareringsforhold, klareringsforholdenes passord, sikkerhetsgrupper,sikkerhetsgruppemedlemskap og andre Active Directory Lightweight Directory Services-konfigurasjonsdata varierer fra domenekontroller til domenekontroller,noe som kan påvirke muligheten til å logge på, søke etter interessante objekter og utføre andre kritiske operasjoner.Disse inkonsekvensene løses først når replikeringsfeil løses. Domenekontrollere som mislykkes på grunn avat den inngående replikeringen slettet objekter i løpet av utløpstiden/levetiden, forblir inkonsekvente tiletterlatte objekter fjernes manuelt av en systemansvarlig fra hver lokale domenekontroller. I tilleggkan det hende replikering fortsatt blir blokkert etter at denne registernøkkelen er angitt, avhengig av ometterlatte objekter finnes umiddelbart.%n%n%nAlternativ brukerhandling:%n%nSenk nivået, eller installer domenekontrollerne som ble frakoblet, på nytt.%n |
It has been too long since this machine last replicated with the named source machine.The time between replications with this source has exceeded the tombstone lifetime.Replication has been stopped with this source.%n%nThe reason that replication is not allowed to continue is that the two DCs may contain lingeringobjects. Objects that have been deleted and garbagecollected from an Active Directory Lightweight Directory Services partition but still exist in the writable partitions of other DCs in the samedomain, or read-only partitions of global catalog servers in other domains in the forest are known as\"lingering objects\". If the local destination DC was allowed to replicate with the source DC, these potentiallingering object would be recreated in the local Active Directory Lightweight Directory Services database.%n%nTime of last successful replication:%n%1%nInvocation ID of source directory server:%n%2%nName of source directory server:%n%3%nTombstone lifetime (days):%n%4%n%nThe replication operation has failed.%n%n%nUser Action:%nThe action plan to recover from this error can be found at http://support.microsoft.com/?id=314282.%n%nIf both the source and destination DCs are Windows Server 2003 DCs, then install the support tools included on theinstallation CD. To see which objects would be deleted without actually performing thedeletion run \"repadmin /removelingeringobjects /ADVISORY_MODE\".The event logs on the source DC will enumerate all lingering objects. To remove lingering objectsfrom a source domain controller run\"repadmin /removelingeringobjects \".%n%nIf either source or destination DC is a Windows 2000 Server DC, then more information on how toremove lingering objects on the source DC can be found at http://support.microsoft.com/?id=314282 or fromyour Microsoft support personnel.%n%nIf you need Active Directory Lightweight Directory Services replication to function immediately at all costs and don't havetime to remove lingering objects, enable replication by setting the followingregistry key to a non-zero value:%n%nRegistry Key:%nHKLM\\%6\\%5%n%nReplication errors between DCs sharing a common partition can prevent user and computer accounts,trust relationships, their passwords, security groups,security group memberships and other Active Directory Lightweight Directory Services configuration data to vary between DCs,affecting the ability to log on, find objects of interest and perform other critical operations.These inconsistencies are resolved once replication errors are resolved. DCs that fail to inboundreplicate deleted objects within tombstone lifetime number of days will remain inconsistent untillingering objects are manually removed by an administrator from each local DC. Additionally,replication may continue to be blocked after this registry key is set, depending on whetherlingering objects are located immediately.%n%n%nAlternate User Action:%n%nForce demote or reinstall the DC(s) that were disconnected.%n |
| 0xC00007FB | Skriptsignaturen er ugyldig, eller katalogtjenesten kan ikke bekrefte skriptsignaturen.%n%nTilleggsdata:%nFeilverdi:%n%1 %2%n%nBrukerhandling:%nPrøv å laste opp skriptet for domenenavneendringen på nytt ved hjelp av verktøyet rendom. |
Script signature is invalid or the Directory Service could not verify the script signature.%n%nAdditional data:%nError value:%n%1 %2%n%nUser action:%nRetry uploading the domain rename script using rendom tool. |
| 0xC00007FD | Active Directory Lightweight Directory Services kan ikke oppgradere en kritisk indeks som en del av initialiseringen.Kontakt Microsoft Product Support Services for å få hjelp. |
Active Directory Lightweight Directory Services has failed to upgrade a critical index as part of initialization.Please contact Microsoft Product Support Services for assistance. |
| 0xC00007FF | Kan ikke replikere konfigurasjons- og skjemainformasjon. Kontroller nettverks- og servertilgjengeligheten. |
Cannot replicate configuration and schema information. Check network and server availability. |
| 0xC0000800 | Kan ikke ha mer enn ett objekt for klassen msExchConfigurationContainer som et umiddelbart underordnet objekt for Services-beholderen i Configuration NC. |
Cannot have more than one object of class msExchConfigurationContainer as an immediate child of the Services container in the Configuration NC. |
| 0xC0000807 | Databasegjenopprettingen mislyktes.%n%nTilleggsdata%nFeilverdi:%n%1 (0x%2)%n%3 |
The database restore operation failed.%n%nAdditional Data%nError value:%n%1 (0x%2)%n%3 |
| 0xC0000808 | Internal error: Active Directory Lightweight Directory Services failed while preparing to restore from backup media.%n%nAdditional Data%nError value:%n%1 (0x%2)%n%3 |
Internal error: Active Directory Lightweight Directory Services failed while preparing to restore from backup media.%n%nAdditional Data%nError value:%n%1 (0x%2)%n%3 |
| 0xC000080C | Klargjøringen av sikkerhetskopiering av Active Directory Lightweight Directory Services-databasen mislyktes.Brukerhandling:%nUtfør sikkerhetskopieringen på nytt. Hvis dette problemet vedvarer, sjekker du vanlige databaseproblemer, ogderetter utfører du sikkerhetskopieringen på nytt. Sikkerhetskopieringen har blitt avbrutt. Vanlige databaseproblemer inkluderer,men er ikke begrenset til, ugyldige disker, fulle disker og konflikt for eller skade på database.%n%nTilleggsdata:%nFeilverdi: %1 %2Intern ID: %3 |
Active Directory Lightweight Directory Services DB backup preparation failed with:User Action:%nRetry the backup operation. If this problem persists, investigate for common database problems, andthen retry the backup operation. The backup has been cancelled. Common database problems include,but are not limited to failing disks, full disks, database contention, corruption.%n%nAdditional Data:%nError Value: %1 %2Internal ID: %3 |
| 0xC000080E | Internal error: Active Directory Lightweight Directory Services could not boot normally, because the database was in an incorrect state.%n%nUser Action%nRestore Active Directory Lightweight Directory Services from backup.%n%nAdditional Data%nInternal ID (DitState): %1 |
Internal error: Active Directory Lightweight Directory Services could not boot normally, because the database was in an incorrect state.%n%nUser Action%nRestore Active Directory Lightweight Directory Services from backup.%n%nAdditional Data%nInternal ID (DitState): %1 |
| 0xC000080F | Internal error: Active Directory Lightweight Directory Services could not boot normally, because the database is in an incorrect state. This might have been caused by a prior unsuccessful promotion using the ‘Install from media?option in the installation wizard.%n%n%nUser Action%nRemove the directory service and reinstall it. |
Internal error: Active Directory Lightweight Directory Services could not boot normally, because the database is in an incorrect state. This might have been caused by a prior unsuccessful promotion using the ‘Install from media?option in the installation wizard.%n%n%nUser Action%nRemove the directory service and reinstall it. |
| 0xC0000814 | Active Directory Lightweight Directory Services kan ikke oppdatere wellKnownObjects-attributtet for objektet %1. Noen funksjoner for Active Directory Lightweight Directory Services er kanskje ikke tilgjengelige.%n%nTilleggsdata:%nFeilverdi:%n%2 (0x%3)%n%4 |
Active Directory Lightweight Directory Services failed to update the wellKnownObjects attribute on object %1. Some functionalities of Active Directory Lightweight Directory Services may not be available.%n%nAdditional data:%nError value:%n%2 (0x%3)%n%4 |
| 0xC0000815 | Active Directory Lightweight Directory Services registrerte ugyldige antall i kvotesporingstabellen. Kvotehåndhevelsen fungerer kanskje ikke optimalt før kvotesporingstabellen er bygget på nytt.%n%nTilleggsdata:%nNCDNT: %1%nAntall for utløpstid: %2%nTotalt antall: %3 |
Active Directory Lightweight Directory Services detected corrupt counts in the quota-tracking table. Quota enforcement may not behave correctly until the quota-tracking table is rebuilt.%n%nAdditional data:%nNCDNT: %1%nTombstoned count: %2%nTotal count: %3 |
| 0xC0000816 | Active Directory Lightweight Directory Services registrerte et ugyldig forsøk på å senke et slettet objektantall til under null i kvotesporingstabellen. Kvotehåndhevelsen fungerer kanskje ikke optimalt før kvotesporingstabellen er bygget på nytt.%n%nTilleggsdata:%nNCDNT: %1%nUtløpt antall: %2%nTotalt antall: %3%nEier-SID:%4 |
Active Directory Lightweight Directory Services detected an illegal attempt to drop a deleted object count below zero in the quota-tracking table. Quota enforcement may not behave correctly until the quota-tracking table is rebuilt.%n%nAdditional data:%nNCDNT: %1%nTombstoned count: %2%nTotal count: %3%nOwnerSid:%4 |
| 0xC0000817 | Active Directory Lightweight Directory Services registrerte et ugyldig forsøk på å senke et objektantall til under null i kvotesporingstabellen. Kvotehåndhevelsen fungerer kanskje ikke optimalt før kvotesporingstabellen er bygget på nytt.%n%nTilleggsdata:%nNCDNT: %1%nUtløpt antall: %2%nTotalt antall: %3%nEier-SID: %4 |
Active Directory Lightweight Directory Services detected an illegal attempt to drop an object count below zero in the quota-tracking table. Quota enforcement may not behave correctly until the quota-tracking table is rebuilt.%n%nAdditional data:%nNCDNT: %1%nTombstoned count: %2%nTotal count: %3%nOwnerSid: %4 |
| 0xC0000818 | Active Directory Lightweight Directory Services registrerte en manglende post i kvotesporingstabellen. Kvotehåndhevelsen fungerer kanskje ikke optimalt før kvotesporingstabellen er bygget på nytt.%n%nTilleggsdata:%nNCDNT: %1 |
Active Directory Lightweight Directory Services detected a missing record in the quota-tracking table. Quota enforcement may not behave correctly until the quota-tracking table is rebuilt.%n%nAdditional data:%nNCDNT: %1 |
| 0xC0000820 | Intersite Messaging-tjenesten for replikering av domenekontrolleren mottok en SMTP-meldingi leveringsmappen som ikke kunne behandles. Tjenesten kunne ikke slettemeldingen.%n%nIP-adresse for klient: %n%1%nEmne: %n%2%n%nTilleggsdata%nFeilverdi:%n%3 %4 |
The domain controller replication intersite messaging service received an SMTP messagein its drop directory which could not be processed. The service could not deletethe message.%n%nClient IP Address: %n%1%nSubject: %n%2%n%nAdditional Data%nError value:%n%3 %4 |
| 0xC0000821 | Intersite Messaging-tjenesten for replikering av domenekontrolleren mottok en SMTP-meldingi leveringsmappen som ikke kunne behandles. Meldingen var feilaktig adresserteller hadde et format som ikke ble gjenkjent. Det kan også være at Intersite Messaging-tjenesten(ISMSERV) ikke kunne godta meldingen fordi tjenesten ikke kjørte. Meldingenble slettet.%n%nIP-adresse for klient: %n%1%nEmne: %n%2%n%nBrukerhandling%nBekreft at Intersite Messaging-tjenesten (ISMSERV) kjører. Søk etter feilkonfigurerteprogrammer som kanskje sender e-post til domenekontrollerens GUID-baserte e-postadresse.%n%nTilleggsdata%nÅrsaksverdi:%n%3 %4 |
The domain controller replication intersite messaging service received an SMTP messagein its drop directory which could not be processed. The message was addressed incorrectlyor was in a format which it did not recognize. It could also be that the Intersite MessagingService (ISMSERV) was unable to accept the message because it was not running. The messagewas deleted.%n%nClient IP Address: %n%1%nSubject: %n%2%n%nUser Action%nVerify that the Intersite Messaging Service (ISMSERV) is running. Check for misconfiguredapplications that may be sending mail to the domain controller's guid-based mail address.%n%nAdditional Data%nReason value:%n%3 %4 |
| 0xC0000822 | Intersite Messaging-tjenesten kan ikke fjerne følgende melding fra leveringsmappen.%n%nFil:%n%1%nFilmappe:%n%2%nTil-felt:%n%5%nFra-felt:%n%6%nEmne-felt:%n%7%n%nMeldingsbehandling stopper til denne meldingen er fjernet.%n%nBrukerhandling%nSlett meldingen fra leveringsmappen.%n%nTilleggsdata%nFeilverdi:%n%4 %3 |
The Intersite Messaging service failed to remove the following message from the drop directory.%n%nFile:%n%1%nFile folder:%n%2%nMail 'To:' Field:%n%5%nMail 'From:' Field:%n%6%nMail 'Subject:' Field:%n%7%n%nMessage processing will stop until this message is removed.%n%nUser Action%nDelete the message from the drop directory.%n%nAdditional Data%nError value:%n%4 %3 |
| 0xC0000823 | Directory Service Agent har registrert et objekt med en NULL GUID.%n%nTilleggsdata%nObjektnavn:%n%1 |
The Directory Service Agent has detected an object with a NULL GUID.%n%nAdditional Data%nObject name:%n%1 |
| 0xC0000827 | Active Directory Lightweight Directory Services kan ikke løse følgende DNS-vertsnavn forkildedomenekontrolleren til en IP-adresse. Denne feilen hindrer at tillegg,slettinger og endringer i Active Directory Lightweight Directory Services replikerer mellom én ellerflere domenekontrollere i skogen. Sikkerhetsgrupper, gruppepolicy, brukereog datamaskiner og deres passord blir inkonsekvente mellomdomenekontrollere til denne feilen er løst. Dette kan muligens påvirkepåloggingsgodkjenning og tilgang til nettverksressurser.%n%nKildedomenekontroller:%n %1%nUgyldig DNS-vertsnavn:%n %2%n%nObs! Som standard vises bare opptil ti DNS-feil for en tolvtimersperiode,selv om det forekommer mer enn ti feil. Du logger alle feilhendelserved å angi følgende analyseregisterverdi til 1:%n%nRegisterbane:%nHKLM\\%5\\%6%n%nBrukerhandling:%n%n 1) Hvis kildedomenekontrolleren ikke lenger fungerer eller densoperativsystem har blitt installert på nytt med et annet datamaskinnavn eller GUID forNTDSDSA-objektet, fjerner du kildedomenekontrollerens metadata ved hjelp av ntdsutil.exe. Du brukerfremgangsmåten i MSKB-artikkel 216498.%n%n 2) Bekreft at kildedomenekontrolleren kjører Active Directory Lightweight Directory Services oger tilgjengelig på nettverket ved å skrive inn \"net view \\\\\" eller\"ping \".%n%n 3) Bekreft at kildedomenekontrolleren bruker en gyldig DNS-server forDNS-tjenester, og at kildedomenekontrollerens vertspost ogCNAME-post er registrert på riktig måte ved hjelp av DNS Enhanced-versjonenav kommandoen DCDIAG.EXE, som er tilgjengelig på http://www.microsoft.com/dns%n%n dcdiag /test:dns%n%n 4) Bekreft at denne måldomenekontrolleren bruker en gyldigDNS-server for DNS-tjenester ved å kjøre DNS Enhanced-versjonen av kommandoenDCDIAG.EXE på konsollen for måldomenekontrolleren på følgende måte:%n%n dcdiag /test:dns%n%n 5) Se KB 824449 hvis du vil ha ytterligere analyse av DNS-feil:%n http://support.microsoft.com/?kbid=824449%n%nTilleggsdata%nFeilverdi:%n %3 %4%n |
Active Directory Lightweight Directory Services could not resolve the following DNS host name of thesource domain controller to an IP address. This error prevents additions,deletions and changes in Active Directory Lightweight Directory Services from replicating between one ormore domain controllers in the forest. Security groups, group policy, usersand computers and their passwords will be inconsistent between domaincontrollers until this error is resolved, potentially affecting logonauthentication and access to network resources.%n%nSource domain controller:%n %1%nFailing DNS host name:%n %2%n%nNOTE: By default, only up to 10 DNS failures are shown for any given 12 hourperiod, even if more than 10 failures occur. To log all individual failureevents, set the following diagnostics registry value to 1:%n%nRegistry Path:%nHKLM\\%5\\%6%n%nUser Action:%n%n 1) If the source domain controller is no longer functioning or its operatingsystem has been reinstalled with a different computer name or NTDSDSA objectGUID, remove the source domain controller's metadata with ntdsutil.exe, usingthe steps outlined in MSKB article 216498.%n%n 2) Confirm that the source domain controller is running Active Directory Lightweight Directory Services andis accessible on the network by typing \"net view \\\\\" or\"ping \".%n%n 3) Verify that the source domain controller is using a valid DNS server forDNS services, and that the source domain controller's host record and CNAMErecord are correctly registered, using the DNS Enhanced versionof DCDIAG.EXE available on http://www.microsoft.com/dns%n%n dcdiag /test:dns%n%n 4) Verify that this destination domain controller is using a valid DNSserver for DNS services, by running the DNS Enhanced version of DCDIAG.EXEcommand on the console of the destination domain controller, as follows:%n%n dcdiag /test:dns%n%n 5) For further analysis of DNS error failures see KB 824449:%n http://support.microsoft.com/?kbid=824449%n%nAdditional Data%nError value:%n %3 %4%n |
| 0xC000082F | I løpet av en forespørsel om Active Directory Lightweight Directory Services-replikering identifiserte den lokale domenekontrollerenen ekstern domenekontroller som har mottatt replikeringsdata fra den lokale domenekontrolleren ved hjelp av USN-sporingsnumresom allerede er godkjent.%n%nDen eksterne domenekontrolleren mener den har en mer oppdatert Active Directory Lightweight Directory Services-database enn denlokale domenekontrolleren, og derfor bruker ikke den eksterne domenekontrolleren fremtidige endringer i versjonen av Active Directory Lightweight DirectoryServices-databasen eller replikerer endringene til databasens direkte og transitive replikeringspartnere, som stammer fra dennelokale domenekontrolleren.%n%nHvis dette problemet ikke løses umiddelbart, fører det til inkonsekvenser i Active Directory Lightweight Directory Services-databaserfor denne kildedomenekontrolleren og én eller flere direkte og transitive replikeringspartnere. Spesieltkonsekvensen til brukere, datamaskiner og klareringsforhold, deres passord, sikkerhetsgrupper,medlemskap i sikkerhetsgrupper og andre Active Directory Lightweight Directory Services-konfigurasjonsdata kan variere, noe som kan påvirke muligheten til å logge på,søke etter interessante objekter og utføre andre kritiske operasjoner.%n%nDu fastslår om denne feilkonfigurasjonen eksisterer ved å spørre denne hendelses-IDen ved hjelp av http://support.microsoft.com,eller du kan kontakte Microsoft Kundestøtte.%n%nDen mest sannsynlige årsaken til dette problemet er ufullstendig gjenoppretting av Active Directory Lightweight Directory Services på denlokale domenekontrolleren.%n%nBrukerhandlinger:%nHvis dette problemet oppstod på grunn av en ufullstendig eller utilsiktet gjenoppretting, senker du nivået på domenekontrolleren.%n%nEkstern domenekontroller:%n%1%nPartisjon:%n%2%nUSN rapportert av ekstern domenekontroller:%n%3%nUSN rapportert av lokal domenekontroller:%n%4%n |
During an Active Directory Lightweight Directory Services replication request, the local domain controller (DC) identifieda remote DC which has received replication data from the local DC using already-acknowledged USNtracking numbers.%n%nBecause the remote DC believes it is has a more up-to-date Active Directory Lightweight Directory Services database than thelocal DC, the remote DC will not apply future changes to its copy of the Active Directory Lightweight Directory Servicesdatabase or replicate them to its direct and transitive replication partners that originate from thislocal DC.%n%nIf not resolved immediately, this scenario will result in inconsistencies in the Active Directory Lightweight Directory Services databasesof this source DC and one or more direct and transitive replication partners. Specifically theconsistency of users, computers and trust relationships, their passwords, security groups,security group memberships and other Active Directory Lightweight Directory Services configuration data may vary, affecting the ability to log on,find objects of interest and perform other critical operations.%n%nTo determine if this misconfiguration exists, query this event ID using http://support.microsoft.comor contact your Microsoft product support.%n%nThe most probable cause of this situation is the improper restore of Active Directory Lightweight Directory Services on thelocal domain controller.%n%nUser Actions:%nIf this situation occurred because of an improper or unintended restore, forcibly demote the DC.%n%nRemote DC:%n%1%nPartition:%n%2%nUSN reported by Remote DC:%n%3%nUSN reported by Local DC:%n%4%n |
| 0xC0000830 | I løpet av en forespørsel om Active Directory Lightweight Directory Services-replikering identifiserte den lokale domenekontrollerenen ekstern domenekontroller som har mottatt replikeringsdata fra den lokale domenekontrolleren ved hjelp av USN-sporingsnumresom allerede er godkjent.%n%nDen eksterne domenekontrolleren mener den har en mer oppdatert Active Directory Lightweight Directory Services-database enn denlokale domenekontrolleren, og derfor bruker ikke den eksterne domenekontrolleren fremtidige endringer i versjonen av Active Directory Lightweight DirectoryServices-databasen eller replikerer endringene til databasens direkte og transitive replikeringspartnere, som stammer fra dennelokale domenekontrolleren.%n%nHvis dette problemet ikke løses umiddelbart, fører det til inkonsekvenser i Active Directory Lightweight Directory Services-databaserfor denne kildedomenekontrolleren og én eller flere direkte og transitive replikeringspartnere. Spesieltkonsekvensen til brukere, datamaskiner og klareringsforhold, deres passord, sikkerhetsgrupper,medlemskap i sikkerhetsgrupper og andre Active Directory Lightweight Directory Services-konfigurasjonsdata kan variere, noe som kan påvirke muligheten til å logge på,søke etter interessante objekter og utføre andre kritiske operasjoner.%n%nDu fastslår om denne feilkonfigurasjonen eksisterer ved å spørre denne hendelses-IDen ved hjelp av http://support.microsoft.com,eller du kan kontakte Microsoft Kundestøtte.%n%nDen mest sannsynlige årsaken til dette problemet er ufullstendig gjenoppretting av Active Directory Lightweight Directory Services på denlokale domenekontrolleren.%n%nBrukeren har valgt å ignorere dette problemet på eget ansvar.%nBrukerhandlinger:%nHvis dette problemet oppstod på grunn av en ufullstendig eller utilsiktet gjenoppretting, senker du nivået på domenekontrolleren.%n%nEkstern domenekontroller:%n%1%nPartisjon:%n%2%nUSN rapportert av ekstern domenekontroller:%n%3%nUSN rapportert av lokal domenekontroller:%n%4 |
During an Active Directory Lightweight Directory Services replication request, the local domain controller (DC) identifieda remote DC which has received replication data from the local DC using already-acknowledged USNtracking numbers.%n%nBecause the remote DC believes it is has a more up-to-date Active Directory Lightweight Directory Services database than thelocal DC, the remote DC will not apply future changes to its copy of the Active Directory Lightweight Directory Servicesdatabase or replicate them to its direct and transitive replication partners that originate from thislocal DC.%n%nIf not resolved immediately, this scenario will result in inconsistencies in the Active Directory Lightweight Directory Services databasesof this source DC and one or more direct and transitive replication partners. Specifically theconsistency of users, computers and trust relationships, their passwords, security groups,security group memberships and other Active Directory Lightweight Directory Services configuration data may vary, affecting the ability to log on,find objects of interest and perform other critical operations.%n%nTo determine if this misconfiguration exists, query this event ID using http://support.microsoft.comor contact your Microsoft product support.%n%nThe most probable cause of this situation is the improper restore of Active Directory Lightweight Directory Services on thelocal domain controller.%n%nThe user has chosen to ignore this problem at their own peril.%nUser Actions:%nIf this situation occurred because of an improper or unintended restore, forcibly demote the DC.%n%nRemote DC:%n%1%nPartition:%n%2%nUSN reported by Remote DC:%n%3%nUSN reported by Local DC:%n%4 |
| 0xC0000831 | Følgende feil oppstod mens den lokale domenekontrolleren forsøkte ådeaktivere eller aktivere replikering.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
The following error was encountered while the local DC was attempting todisable\\enable replication.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC0000832 | Forsøk på å oppdatere Active Directory Lightweight Directory Services-databasen er vellykket. Hvis ingen andreutestående problemer blokkerer annonsering for denne domenekontrolleren,blir Net Logon-tjenesten startet på nytt.%n |
Attempts to update the Active Directory Lightweight Directory Services database are succeeding. If there areno other outstanding issues blocking advertisement of this domain controller,then the Net Logon service will be restarted.%n |
| 0xC0000834 | Integriteten for Active Directory Lightweight Directory Services-databasen har blitt løst. Hvis ingen andreutestående problemer blokkerer annonsering for denne domenekontrolleren,blir Net Logon-tjenesten startet på nytt.%n |
The integrity of the Active Directory Lightweight Directory Services database has been resolved. If there areno other outstanding issues blocking advertisement of this domain controller,then the Net Logon service will be restarted.%n |
| 0xC0000835 | Integriteten for Active Directory Lightweight Directory Services-databasen er diskutabel.%n%nActive Directory Lightweight Directory Services kan ikke logge på brukere før dette problemet er løst. Det fører til at Net Logon-tjenesten har stoppet midlertidig.%n%nBrukerhandling%nActive Directory Lightweight Directory Services-databasen bør gjenopprettes fra en sikkerhetskopi.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
The integrity of the Active Directory Lightweight Directory Services database is questionable.%n%nActive Directory Lightweight Directory Services will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.%n%nUser Action%nThe Active Directory Lightweight Directory Services database should be restored from backup.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC0000836 | Active Directory Lightweight Directory Services-databasen har blitt reparert etter at det ble registrert en ugyldiggjenopprettingsprosedyre. Hvis ingen andre utestående problemer blokkerer annonsering for denne domenekontrolleren,blir Net Logon-tjenesten startet på nytt.%n |
The Active Directory Lightweight Directory Services database has been repaired after detecting an improper restorationprocedure. If there are no other outstanding issues blocking advertisement of this domain controller,then the Net Logon service will be restarted.%n |
| 0xC0000837 | Active Directory Lightweight Directory Services-databasen har blitt gjenopprettet ved hjelp av en gjenopprettingsprosedyre som ikke støttes.%n%nActive Directory Lightweight Directory Services kan ikke logge på brukere før dette problemet er løst. Det fører til at Net Logon-tjenesten har stoppet midlertidig.%n%nBrukerhandling%nSe tidligere hendelseslogger hvis du vil ha mer informasjon. |
The Active Directory Lightweight Directory Services database has been restored using an unsupported restoration procedure.%n%nActive Directory Lightweight Directory Services will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.%n%nUser Action%nSee previous event logs for details. |
| 0xC0000838 | Forsøket på å annonsere for Active Directory Lightweight Directory Services-forekomsten som skrivbar tilNet Logon-tjenesten mislyktes.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
The attempt to advertise the Active Directory Lightweight Directory Services instance as writable to the Net Logonservice has failed.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC0000839 | Forsøket på å annonsere for Active Directory Lightweight Directory Services-forekomsten som ikke-skrivbar tilNet Logon-tjenesten mislyktes.%n%nTilleggsdata%nFeilverdi:%n%1 %2 |
The attempt to advertise the Active Directory Lightweight Directory Services instance as not writable to the Net Logonservice has failed.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000083A | Det ble gjort et forsøk på å replikere med AD LDS-forekomsten, men ekstern DSA støtter ikke én eller flere valgfrie funksjoner som er aktivert på lokal DSA.%n%nTilleggsdata%nValgfri(e) funksjon(er): %n%1%nKatalogpartisjon: %n%2%nEkstern katalogtjeneste: %n%3%n |
An attempt was made to replicate with the AD LDS instance, but the remote DSA does not support one or more optional features that are enabled on the local DSA.%n%nAdditional Data%nOptional feature(s): %n%1%nDirectory partition: %n%2%nRemote directory service: %n%3%n |
| 0xC000083B | Internal Event: The attempt to prepare the Active Directory Lightweight Directory Services database for a possible future disk restorationhas failed.%n%nAdditional Data%nError value:%n%1 %2 |
Internal Event: The attempt to prepare the Active Directory Lightweight Directory Services database for a possible future disk restorationhas failed.%n%nAdditional Data%nError value:%n%1 %2 |
| 0xC000083C | Denne hendelsen inneholder REPARASJONSPROSEDYRER for 1084-hendelsen som tidligere har blitt logget. Denne meldingen angir et bestemt problem med konsekvensen for Active Directory Lightweight Directory Services-databasen på dette replikeringsmålet. Det oppstod en databasefeil under implementering av replikerte endringer i følgende objekt. Databasen hadde uventet innhold, noe som hindrer endringen i å bli utført.%n%nObjekt:%n%1%nObjekt-GUID:%n%2%nKildedomenekontroller:%n%3%n%nBrukerhandling%n%nSe KB-artikkel 837932 på http://support.microsoft.com/?id=837932. Et delsett av reparasjonsprosedyrene er oppført i denne artikkelen.%n1. Bekreft at tilstrekkelig diskplass er ledig på volumene som er vert for Active Directory Lightweight Directory Services-databasen, og utfør deretter operasjonen på nytt. Bekreft at de fysiske diskene som er vert for NTDS.DIT og loggfiler, ikke er plassert på stasjoner der NTFS-komprimering er aktivert. Kontroller også om det finnes antivirusprogramvare som er knyttet til disse volumene.%n2. Det kan være fordelaktig å bruke overføringen av sikkerhetsbeskrivelsen til å bygge objektbeholderopphavet på nytt i databasen. Dette kan gjøres ved å følge fremgangsmåten i KB-artikkel 251343 på http://support.microsoft.com/?id=251343.%n3. Problemet kan ha sammenheng med objektets overordnede objekt på denne domenekontrolleren. På kildedomenekontrolleren flytter du objektet slik at det får et annet overordnet objekt.%n4. Hvis denne maskinen er en global katalog og feilen forekommer på én av de skrivebeskyttede partisjonene, bør du senke nivået på maskinen som en global katalog ved hjelp av avmerkingsboksen Global katalog i Områder og tjenester. Hvis feilen oppstår i en programpartisjon, kan du hindre at programpartisjonen blir driftet fra denne replikaen. Dette kan du endre ved å bruke kommandoen ntdsutil.exe.%n5. Hent den nyeste versjonen av ntdsutil.exe ved å installere den nyeste oppdateringspakken for operativsystemet. Før du starter på nytt med DSRM (Directory Services Restore Mode), bekrefter du at DSRM-passordet er kjent. Ellers tilbakestiller du det før du starter systemet på nytt.%n6. I DSRM starter du ledeteksten og kjører kommandoen \"ntdsutil files integrity\". Hvis det registreres skader på denne replikaen og det finnes andre replikaer, senker du nivået på kopien og kontrollerer maskinvaren. Hvis det ikke finnes andre replikaer, gjenoppretter du en sikkerhetskopi av systemtilstanden og utfører bekreftelsen på nytt.%n7. Utfør en frakoblet defragmentering ved hjelp av funksjonen \"ntdsutil files compact\".%n8. Funksjonen \"ntdsutil semantic database analysis\" bør også kjøres. Hvis det finnes feil, kan de repareres ved hjelp av funksjonen \"go fixup\". Vær oppmerksom på at denne funksjonen ikke må forveksles med databasevedlikeholdsfunksjonen \"ESE repair\", som ikke bør brukes, fordi den fører til at data i Active Directory Lightweight Directory Services-databaser går tapt.%n%nHvis ingen av disse handlingene var vellykket og du fortsatt opplever replikeringsfeil, bør du senke nivået for denne domenekontrolleren og og heve nivået på nytt.%n%nTilleggsdata%nPrimær feilverdi:%n%5 %4%nSekundær feilverdi:%n%7 %6 |
This event contains REPAIR PROCEDURES for the 1084 event which has previously been logged. This message indicates a specific issue with the consistency of the Active Directory Lightweight Directory Services database on this replication destination. A database error occurred while applying replicated changes to the following object. The database had unexpected contents, preventing the change from being made.%n%nObject:%n%1%nObject GUID:%n%2%nSource domain controller:%n%3%n%nUser Action%n%nPlease consult KB article 837932, http://support.microsoft.com/?id=837932. A subset of its repair procedures are listed here.%n1. Confirm that sufficient free disk space resides on the volumes hosting the Active Directory Lightweight Directory Services database then retry the operation. Confirm that the physical drives hosting the NTDS.DIT and log files do not reside on drives where NTFS compression is enabled. Also check for anti-virus software accessing these volumes.%n2. It may be of benefit to force the Security Descriptor Propagator to rebuild the object container ancestry in the database. This may be done by following the instructions in KB article 251343, http://support.microsoft.com/?id=251343.%n3. The problem may be related to the object's parent on this domain controller. On the source domain controller, move the object to have a different parent.%n4. If this machine is a global catalog and the error occurs in one of the read-only partitions, you should demote the machine as a global catalog using the Global Catalog checkbox in the Sites & Services user interface. If the error is occurring in an application partition, you can stop the application partition from being hosted on this replica. This may be changed using the ntdsutil.exe command.%n5. Obtain the most recent ntdsutil.exe by installing the latest service pack for your operating system. Prior to booting into Directory Services Restore Mode (DSRM), verify that the DSRM password is known. Otherwise reset it prior to restarting the system.%n6. In DSRM, run the NT CMD prompt, run \"ntdsutil files integrity\". If corruption is found and other replicas exist, then demote replica and check your hardware. If no replicas are present, restore a system state backup and repeat this verification.%n7. Perform an offline defragmentation using the \"ntdsutil files compact\" function.%n8. The \"ntdsutil semantic database analysis\" should also be performed. If errors are found, they may be corrected using the \"go fixup\" function. Note that this should not be confused with the database maintenance function called \"ESE repair\", which should not be used, since it causes data loss for Active Directory Lightweight Directory Services Databases.%n%nIf none of these actions succeed and the replication error continues, you should demote this domain controller and promote it again.%n%nAdditional Data%nPrimary Error value:%n%5 %4%nSecondary Error value:%n%7 %6 |
| 0xC0000844 | Nivåhevingen Install-From-Media for en skrivebeskyttet domenekontroller kan ikke starte fordi den angitte databasen ikke er tillatt. Bare databaser fra andre skrivebeskyttede domenekontrollere kan brukes til IFM-nivåheving for en skrivebeskyttet domenekontroller. |
The Install-From-Media promotion of a Read-Only DC cannot start because the specified source database is not allowed. Only databases from other RODCs can be used for IFM promotion of a RODC. |
| 0xC0000845 | Nivåhevingen Install-From-Media for en domenekontroller kan ikke starte fordi den angitte kildedatabasen kommer fra en skrivebeskyttet domenekontroller. Bare databaser fra andre domenekontrollere kan brukes til IFM-nivåheving for en domenekontroller. |
The Install-From-Media promotion of a DC cannot start because the specified source database is from a Read-Only DC. Only databases from other DCs can be used for IFM promotion of a DC. |
| 0xC0000846 | Forsøket på å installere Active Directory Lightweight Directory Services mislyktes. Domenet som ble angitt (%1), var etannet domene enn domenet som sikkerhetskopien ble tatt fra (%2). |
The attempt to Install the Active Directory Lightweight Directory Services failed. The Domain that was specified (%1) wasdifferent than the one the backup was taken from (%2). |
| 0xC000084A | Denne Active Directory Lightweight Directory Services-serveren er konfigurert til å aktivere en funksjon med funksjons-GUIDen %s. Denne funksjonen gjenkjennes ikke og blir ignorert. |
This Active Directory Lightweight Directory Services server is configured to enable a feature with the feature Guid %s. This feature is not recognized, and will be ignored. |
| 0xC000084B | Et forsøk på å senke funksjonsnivået for konfigurasjonssettet til %1 mislyktes fordi den valgfrie funksjonen %2 er aktivert. Funksjonsnivået for konfigurasjonssettet kan ikke senkes til mindre enn %3 hvis den valgfrie funksjonen %2 er aktivert. |
An attempt to lower the configuration set functional level to %1 failed because the %2 optional feature is enabled. The configuration set functional level may not be lowered to less than %3 if the %2 optional feature is enabled. |
| 0xC0000851 | Internal event: The local Active Directory Lightweight Directory Services was failed an attempt to delete the obsolete column %1 with the error %2. |
Internal event: The local Active Directory Lightweight Directory Services was failed an attempt to delete the obsolete column %1 with the error %2. |
| 0xC0000852 | Resirkuleringen av fantomobjektet %1 har blitt opphevet autoritativt. Dette førte til at koblinger fra objekter i den lokale Active Directory Lightweight Directory Services-databasen gikk tapt for det fantomobjektet. Det finnes ingen metode for å identifisere hvilke koblinger som har gått tapt. Dette kan føre til avvik mellom den lokale Active Directory Lightweight Directory Services-databasen og andre replikeringspartnere. |
The phantom object %1 has been authoritatively unrecycled. This resulted in the loss of links from objects in the local Active Directory Lightweight Directory Services database to that phantom. There is no way to identify which links have been lost. This may result in divergence between the local Active Directory Lightweight Directory Services database and other replication partners. |
| 0xC0000853 | Et forsøk på å senke funksjonsnivået for konfigurasjonssettet til %1 mislyktes fordi den valgfrie funksjonen %2 for øyeblikket oppdaterer den interne tilstanden for Active Directory Lightweight Directory Services. Funksjonsnivået FOREST_TERM kan ikke senkes til mindre enn %3 før den valgfrie funksjonen %2 har fullført denne oppgaven.%nDette problemet bør løses av seg selv automatisk. Hvis denne feilen oppstår på nytt, kan det hende du må utføre en manuell handling.%n |
An attempt to lower the configuration set functional level to be %1 failed because the %2 optional feature is currently updating the Active Directory Lightweight Directory Services's internal state. The FOREST_TERM functional level may not be lowered to less than %3 until the %2 optional feature has completed this task.%nThis situation should correct itself automatically. If this error is encountered again, manual intervention may be necessary.%n |
| 0xC0000854 | Ikke brukt |
Unused |
| 0xC000085C | Under behandling av en forespørsel om Active Directory Lightweight Directory Services-replikering forsøkte Active Directory Lightweight Directory Services å endre listen over aktiverte, valgfrie funksjoner for konfigurasjonssettet. Active Directory Lightweight Directory Services aktiverer eller deaktiverer for øyeblikket én eller flere valgfrie funksjoner. Derfor godtas ikke endringer i listen over aktiverte, valgfrie funksjoner for konfigurasjonssettet på dette tidspunktet, og dermed mislykkes replikeringsforespørselen. Active Directory Lightweight Directory Services avbryter denne replikeringsforespørselen midlertidig. Replikeringsforespørselen blir forsøkt på nytt senere.Forespørselsdetaljer:Objekt som blir endret: %1Attributt som blir endret: %2Verdi som blir endret: %3Valgfri funksjon: %4 |
While processing of an Active Directory Lightweight Directory Services replication request, the Active Directory Lightweight Directory Services attempted to modify the list of enabled optional features for the configuration set. The Active Directory Lightweight Directory Services is currently enabling or disabling one or more optional features. Therefore, modifications to the list of enabled optional features for the configuration set are not being accepted at this time, so the replication request failed. The Active Directory Lightweight Directory Services will temporarily discontinue this replication request. The replication request will be attempted again later.Request Details:Object being modified: %1Attribute being modified: %2Value being modified: %3Optional feature: %4 |
| 0xC000085D | Det oppstod en feil under intern behandling av Active Directory Lightweight Directory Services-databasen i forbindelse med oppdatering av Active Directory Lightweight Directory Services' sporing av tilstanden til slettede objekter. Dermed kan ikke denne oppgaven fullføres. Du kan ikke angre sletting av objekter før denne oppgaven er fullført. I tillegg er det ikke sikkert at funksjonen Papirkurv kan aktiveres.%n%nDette problemet kan løses av seg selv automatisk. Hvis denne feilen oppstår på nytt, kan det hende du må utføre en manuell handling.%n%nBrukerhandling%nHvis denne feilen vedvarer, øker du hendelsesloggingen for Datasanering for å få mer informasjon.%n |
Internal processing of the Active Directory Lightweight Directory Services database has encountered an error while updating the Active Directory Lightweight Directory Services's tracking of the state of deleted objects. This error blocks the completion of this task. Until this task completes successfully, objects may not be undeleted. Additionally, the Recycle Bin feature may not be enabled.%n%nThis situation may correct itself automatically. If this error is encountered again, manual intervention may be necessary.%n%nUser Action%nIf this error continues to occur, increase event logging for Garbage Collection for more details.%n |
| 0xC000085E | Intern behandling av Active Directory Lightweight Directory Services-databasen for å oppdatere Active Directory Lightweight Directory Services' sporing av tilstanden til slettede objekter ble ikke fullført fordi det oppstod flere feil. Denne oppgaven må utføres på nytt. Du kan ikke angre sletting av objekter før denne oppgaven er fullført. I tillegg er det ikke sikkert at funksjonen Papirkurv kan aktiveres.%n%nDenne oppgaven planlegges på nytt. Hvis dette problemet vedvarer, kan det hende du må utføre en manuell handling.%n%nBrukerhandling%nHvis denne feilen vedvarer, øker du hendelsesloggingen for Datasanering for å få mer informasjon.%n%n%n Planlegges på nytt om %s sekunder. |
Internal processing of the Active Directory Lightweight Directory Services database to update the Active Directory Lightweight Directory Services's tracking of the state of deleted objects has completed unsuccessfully; errors were encountered. This task must be done again. Until this task completes successfully, objects may not be undeleted. Additionally, the Recycle Bin feature may not be enabled.%n%nThis task is being rescheduled. If this condition persists, manual intervention may be necessary.%n%nUser Action%nIf this error continues to occur, increase event logging for Garbage Collection for more details.%n%n%n Rescheduling in %s seconds. |
| 0xC0000862 | Internal event: The local Active Directory Lightweight Directory Services has detected that a crossRef object exists whose directory partition name reference (ncName attribute) was renamed because it conflicted with a local object. This renamed reference may prevent Active Directory Lightweight Directory Services from functioning normally.%n%nCrossRef object: %n%1%n%nConflicting renamed partion: %n%2%n%nActive Directory Lightweight Directory Services will attempt to automatically correct this conflicting name reference for this domain controller.%n%nUser Action%nCheck if this problem exists in any domain controller running Windows 2008 R2 or prior versions of the operating system. This problem exists if the event [Category:Replication EventId:1969] is logged by the domain controller or if GUIDs are present in the values of ncName attributes in the Configuration container. If this problem is found then you must run Dsdbutil semantic analysis to correct the name reference. |
Internal event: The local Active Directory Lightweight Directory Services has detected that a crossRef object exists whose directory partition name reference (ncName attribute) was renamed because it conflicted with a local object. This renamed reference may prevent Active Directory Lightweight Directory Services from functioning normally.%n%nCrossRef object: %n%1%n%nConflicting renamed partion: %n%2%n%nActive Directory Lightweight Directory Services will attempt to automatically correct this conflicting name reference for this domain controller.%n%nUser Action%nCheck if this problem exists in any domain controller running Windows 2008 R2 or prior versions of the operating system. This problem exists if the event [Category:Replication EventId:1969] is logged by the domain controller or if GUIDs are present in the values of ncName attributes in the Configuration container. If this problem is found then you must run Dsdbutil semantic analysis to correct the name reference. |
| 0xC0000872 | Kloning av virtuell domenekontroller mislyktes.%nKontroller hendelser som er loggført i Systemhendelseslogg og %systemroot%\\debug\\dcpromo.log for mer informasjon om feil som tilsvarer forsøket på kloning av virtuell domenekontroller.%n%nFeilkode: %1 |
Virtual domain controller cloning failed.%nPlease check events logged in System event logs and %systemroot%\\debug\\dcpromo.log for more information on errors that correspond to the virtual domain controller cloning attempt.%n%nError code: %1 |
| 0xC0000874 | Active Directory Lightweight Directory Services kan ikke starte DsRoleSvc-tjenesten for å klone den lokale, virtuelle domenekontrolleren. Se http://go.microsoft.com/fwlink/?LinkId=208030 hvis du vil ha mer informasjon. |
Active Directory Lightweight Directory Services failed to start the DsRoleSvc service to clone the local virtual domain controller. Please see http://go.microsoft.com/fwlink/?LinkId=208030 for more information. |
| 0xC0000875 | Active Directory Lightweight Directory Services kan ikke starte en tråd i løpet av kloningen av den lokale, virtuelle domenekontrolleren. Se http://go.microsoft.com/fwlink/?LinkId=208030 hvis du vil ha mer informasjon.%n%nFeilkode:%n%1%nFeilmelding:%n%2%nNavn på tråd:%n%3 |
Active Directory Lightweight Directory Services failed to start a thread during the cloning of the local virtual domain controller. Please see http://go.microsoft.com/fwlink/?LinkId=208030 for more information.%n%nError code:%n%1%nError message:%n%2%nThread name:%n%3 |
| 0xC0000876 | Active Directory Lightweight Directory Services krever at %2-tjenesten initialiserer omstart til DSRM. Venting på at %2 skal initialisere til en kjørende tilstand mislyktes.%n%nFeilkode:%n%1%n |
Active Directory Lightweight Directory Services needs %2 service to initiate rebooting into DSRM. Waiting for %2 to initialize into a running state failed.%n%nError code:%n%1%n |
| 0xC0000877 | Active Directory Lightweight Directory Services kan ikke initialisere kunnskap om virtuell domenekontroller. Se tidligere oppføringer i hendelsesloggen hvis du vil ha mer informasjon.%n%nTilleggsdata%nFeilkode:%n%1 |
Active Directory Lightweight Directory Services could not initialize virtual domain controller knowledge. See previous event log entry for details.%n%nAdditional Data%nFailure code:%n%1 |
| 0xC000087F | Konfigurasjonsfil for kloning av virtuell domenekontroller finnes på en plattform som ikke støttes. |
Virtual domain controller clone configuration file exists on an unsupported platform. |
| 0xC0000881 | Operasjonen med å gi nytt navn til konfigurasjonsfilen for kloning av virtuell domenekontroller mislyktes.%n%nTilleggsdata%nFilnavn:%n%1%nFeilkode:%n%2 %3 |
Renaming virtual domain controller clone configuration file failed.%n%nAdditional Data%nFile name:%n%1%nFailure code:%n%2 %3 |
| 0xC0000888 | Active Directory Lightweight Directory Services kan ikke opprette en domenekontrollerkonto for den klonede domenekontrolleren.%n%nOpprinnelig navn på domenekontroller:%n%1%nTillatt antall klonede domenekontrollere:%n%2%nGrensen for hvor mange domenekontrollerkontoer som kan genereres ved å klone Active Directory Lightweight Directory Services, ble overskredet. Se http://go.microsoft.com/fwlink/?LinkId=208030 hvis du vil ha mer informasjon. |
Active Directory Lightweight Directory Services failed to create a domain controller account for the cloned DC.%n%nOriginal DC name:%n%1%nAllowed number of cloned DC:%n%2%nThe limit on the number of domain controller accounts that can be generated by cloning Active Directory Lightweight Directory Services was exceeded. Please see http://go.microsoft.com/fwlink/?LinkId=208030 for more information. |
| 0xC000088A | Active Directory Lightweight Directory Services kan ikke stoppe FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen.%n%nTjenestenavn:%n%1%nFeilkode:%n%2%nFeilmelding:%n%3%nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-replikaen. Dette gjøres ved å stoppe FRS- eller DFSR-replikeringstjenesten som brukes til å replikere SYSVOL-mappen og deretter starte den på nytt med de relevante registernøklene og -verdiene for å utløse gjenopprettingen. Active Directory Lightweight Directory Services kan ikke stoppe tjenesten som kjører for øyeblikket og kan ikke fullføre den ikke-autoritative gjenopprettingen. Utfør en ikke-autoritativ gjenoppretting manuelt. Se http://go.microsoft.com/fwlink/?LinkId=208030 for mer informasjon. |
Active Directory Lightweight Directory Services failed to stop the FRS or DFSR service used to replicate the SYSVOL folder.%n%nService name:%n%1%nError code:%n%2%nError message:%n%3%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services must initialize a non-authoritative restore on the local SYSVOL replica. This is done by stopping the FRS or DFSR replication service used to replicate the SYSVOL folder and then starting it with the appropriate registry keys and values to trigger the restore. Active Directory Lightweight Directory Services failed to stop the current running service and cannot complete the non-authoritative restore. Please perform a non-authoritative restore manually. See http://go.microsoft.com/fwlink/?LinkId=208030 for more information. |
| 0xC000088C | Active Directory Lightweight Directory Services kan ikke starte FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen.%n%nTjenestenavn:%n%1%nFeilkode:%n%2%nFeilmelding:%n%3%nActive Directory registrerte at den virtuelle maskinen som er vert for domenekontrolleren, ble tilbakestilt til en tidligere tilstand. Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-kopien. Dette gjøres ved å stoppe FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen, og starte den med en egnet registernøkkel og verdier for å starte gjenopprettingen. Active Directory Lightweight Directory Services kan ikke starte FRS- eller DFSR-tjenesten som brukes til å replikere SYSVOL-mappen, og kan ikke fullføre den ikke-autoritative gjenopprettingen. Utfør en ikke-autoritativ gjenoppretting manuelt og start tjenesten på nytt. Se http://go.microsoft.com/fwlink/?LinkId=208030 hvis du vil ha mer informasjon. |
Active Directory Lightweight Directory Services failed to start the FRS or DFSR service used to replicate the SYSVOL folder.%n%nService name:%n%1%nError code:%n%2%nError message:%n%3%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services needs to initialize a non-authoritative restore on the local SYSVOL replica. This is done by stopping the FRS or DFSR service used to replicate the SYSVOL and starting it with appropriate registry keys and values to trigger the restore. Active Directory Lightweight Directory Services failed to start the FRS or DFSR service used to replicate the SYSVOL folder and cannot complete the non-authoritative restore. Please perform a non-authoritative restore manually and restart the service. See http://go.microsoft.com/fwlink/?LinkId=208030 for more information. |
| 0xC000088E | Active Directory Lightweight Directory Services kan ikke angi følgende registerverdier for å initialisere SYSVOL-replikaen under en ikke-autoritativ gjenoppretting:%n%nRegisternøkkel:%n%1%nRegisterverdi: %n%2%nRegisterverdidata: %n%3%nFeilkode:%n%4%nFeilmelding:%n%5%nActive Directory oppdaget at den virtuelle maskinen som vert for domenekontrollerrollen, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-replikaen.Dette gjøres ved å stoppe FRS- eller DFSR-replikeringstjenesten som brukes til å replikere SYSVOL-mappen og deretter starte den på nytt med de relevante registernøklene og -verdiene for å utløse gjenopprettingen. Active Directory Lightweight Directory Services kan ikke angi registerverdien over, og kan ikke fullføre den ikke-autoritative gjenopprettingen. Utfør en ikke-autoritativ gjenoppretting manuelt. Se http://go.microsoft.com/fwlink/?LinkId=208030 for mer informasjon. |
Active Directory Lightweight Directory Services failed to set the following registry values to initialize the SYSVOL replica during a non-authoritative restore:%n%nRegistry Key:%n%1%nRegistry Value: %n%2%nRegistry Value data: %n%3%nError code:%n%4%nError message:%n%5%nActive Directory detected that the virtual machine that hosts the domain controller role was reverted to a previous state. Active Directory Lightweight Directory Services needs to initialize a non-authoritative restore on the local SYSVOL replica. This is done by stopping the FRS or DFSR service used to replicate the SYSVOL folder and starting it with the appropriate registry keys and values to trigger the restore. Active Directory Lightweight Directory Services failed to set the above registry values and cannot complete the non-authoritative restore. Please perform a non-authoritative restore manually. See http://go.microsoft.com/fwlink/?LinkId=208030 for more information. |
| 0xC0000890 | Active Directory Lightweight Directory Services kan ikke angi følgende registerverdi for å deaktivere DNS-oppdateringer.%n%nRegisternøkkel:%n%1%nRegisterverdi: %n%2%nRegisterverdidata: %n%3%nFeilkode:%n%4%nFeilmelding:%n%5%nI løpet av kloningsprosessen kan det hende den lokale maskinen et kort øyeblikk har hatt samme datamaskinnavn som klonekildemaskinen. DNS A- og AAAA-postregistrering deaktiveres i denne perioden slik at klienter ikke kan sende forespørsler til den lokale maskinen som blir klonet. |
Active Directory Lightweight Directory Services failed to set the following registry value to disable DNS updates.%n%nRegistry Key:%n%1%nRegistry Value: %n%2%nRegistry Value data: %n%3%nError code:%n%4%nError message:%n%5%nDuring the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. |
| 0xC0000892 | Active Directory Lightweight Directory Services kan ikke angi følgende registerverdi for å aktivere DNS-oppdateringer.%n%nRegisternøkkel:%n%1%nRegisterverdi: %n%2%nRegisterverdidata: %n%3%nFeilkode:%n%4%nFeilmelding:%n%5%nI løpet av kloningsprosessen kan det hende den lokale maskinen et kort øyeblikk har hatt samme datamaskinnavn som klonekildemaskinen. DNS A- og AAAA-postregistrering deaktiveres i denne perioden slik at klienter ikke kan sende forespørsler til den lokale maskinen som blir klonet. |
Active Directory Lightweight Directory Services failed to set the following registry value to enable DNS updates.%n%nRegistry Key:%n%1%nRegistry Value: %n%2%nRegistry Value data: %n%3%nError code:%n%4%nError message:%n%5%nDuring the cloning process, the local machine may have the same computer name as the clone source machine for a short time. DNS A and AAAA record registration are disabled during this period so clients cannot send requests to the local machine undergoing cloning. |
| 0xC0000893 | Kan ikke angi DSRM-omstart.%n%nFeilkode:%n%1%nFeilmelding:%n%2%nNår kloning av en virtuell domenekontroller mislykkes eller konfigurasjonsfilen for kloning av virtuelle domenekontrollere vises på en hypervisor som ikke støttes, startes den lokale maskinen på nytt i DSRM for feilsøking. Angivelse av DSRM-oppstart mislyktes. |
Failed to set DSRM boot.%n%nError code:%n%1%nError message:%n%2%nWhen virtual domain controller cloning failed or virtual domain controller clone configuration file appears on a non-supported hypervisor, the local machine will reboot into DSRM for troubleshooting. Setting DSRM boot failed. |
| 0xC0000894 | Kan ikke aktivere avsluttingsrettighet.%n%nFeilkode:%n%1%nFeilmelding:%n%2%nNår kloning av en virtuell domenekontroller mislykkes eller konfigurasjonsfilen for kloning av virtuelle domenekontrollere vises på en hypervisor som ikke støttes, startes den lokale maskinen på nytt i DSRM for feilsøking. Aktivering av avsluttingsrettighet mislyktes. |
Failed to enable shutdown privilege.%n%nError code:%n%1%nError message:%n%2%nWhen virtual domain controller cloning failed or virtual domain controller clone configuration file appears on a non-supported hypervisor, the local machine will reboot into DSRM for troubleshooting. Enabling shutdown privilege failed. |
| 0xC0000895 | Kan ikke initialisere systemavslutting.%n%nFeilkode:%n%1%nError message:%n%2%nNår kloning av en virtuell domenekontroller mislykkes eller konfigurasjonsfilen for kloning av virtuelle domenekontrollere vises på en hypervisor som ikke støttes, startes den lokale maskinen på nytt i DSRM for feilsøking. Initialisering av systemavslutting mislyktes. |
Failed to initiate system shutdown.%n%nError code:%n%1%nError message:%n%2%nWhen virtual domain controller cloning failed or virtual domain controller clone configuration file appears on a non-supported hypervisor, the local machine will reboot into DSRM for troubleshooting. Initiating system shutdown failed. |
| 0xC0000896 | Active Directory Lightweight Directory Services kan ikke opprette eller endre følgende objekt for en klonet domenekontroller.%n%nTilleggsdata:%nObjekt:%n%1%nFeilverdi: %n%2%n%3 |
Active Directory Lightweight Directory Services failed to create or modify the following cloned DC object.%n%nAdditional data:%nObject:%n%1%nError value: %n%2%n%3 |
| 0xC0000897 | Active Directory Lightweight Directory Services kan ikke opprette objektet nedenfor for en klonet domenekontroller fordi objektet allerede finnes.%n%nTilleggsdata:%nKildedomenekontroller:%n%1%nObjekt:%n%2 |
Active Directory Lightweight Directory Services failed to create the following cloned DC object because the object already exists.%n%nAdditional data:%nSource DC:%n%1%nObject:%n%2 |
| 0xC000089A | %nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand. Active Directory Lightweight Directory Services kan ikke replikere for å oppdatere domenekontrolleren. Domenekontrolleren vil bli oppdatert etter neste periodiske replikering.%n%n Feilverdi: %1 |
%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services failed replication to bring the domain controller up-to-date. The domain controller will be updated after next periodic replication.%n%n Error Value: %1 |
| 0xC000089E | Active Directory Lightweight Directory Services kan ikke gjøre gjeldende RID-utvalg ugyldig etter at den virtuelle domenekontrolleren ble gjenopprettet til tidligere tilstand.%n%nYtterligere data:%nFeilkode: %1%nFeilverdi: %2 |
Active Directory Lightweight Directory Services failed to invalidate current RID pool after virtual domain controller was reverted to previous state.%n%nAdditional data:%nError code: %1%nError value: %2 |
| 0xC000089F | Active Directory Lightweight Directory Services kan ikke gjenopprettes etter at den virtuelle domenekontrolleren ble gjenopprettet til tidligere tilstand. En omstart til DSRM ble forespurt. Kontroller tidligere hendelser for mer informasjon. Se http://go.microsoft.com/fwlink/?LinkId=208030 for mer informasjon. |
Active Directory Lightweight Directory Services failed to restore after virtual domain controller was reverted to previous state. A reboot into DSRM was requested. Please check previous events for more information. See http://go.microsoft.com/fwlink/?LinkId=208030 for more information. |
| 0xC00008A1 | Active Directory Lightweight Directory Services kan ikke slette DFSR-databaser.%n%nYtterligere data:%nFeilkode: %1%nFeilverdi: %2%n%nActive Directory oppdaget at den virtuelle maskinen som er vert for domenekontrolleren, ble gjenopprettet til en tidligere tilstand.Active Directory Lightweight Directory Services må initialisere en ikke-autoritativ gjenoppretting på den lokale SYSVOL-replikaen. For DFSR gjøres dette ved å stoppe DFSR-tjenesten, slette DFSR-databaser og starte tjenesten på nytt. Når DFSR startes på nytt, vil databasene gjenoppbygges og den innledende synkroniseringen startes. |
Active Directory Lightweight Directory Services failed to delete DFSR databases.%n%nAdditional data:%nError code: %1%nError value: %2%n%nActive Directory detected that the virtual machine that hosts the domain controller was reverted to a previous state. Active Directory Lightweight Directory Services needs to initialize a non-authoritative restore on the local SYSVOL replica. For DFSR, this is done by stopping the DFSR service, deleting DFSR databases, and re-starting the service. Upon restarting DFSR will rebuild the databases and start the initial sync. |
| 0xC00008A2 | Active Directory Lightweight Directory Services kan ikke opprette objekter for den klonede domenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %6%nNavn på klonedomenekontroller: %1%nForsøksløkke: %2%nUnntaksverdi: %3%nFeilverdi: %4%nDSID: %5 |
Active Directory Lightweight Directory Services failed to create objects for clone domain controller.%n%nAdditional data:%nClone Id: %6%nClone domain controller name: %1%nRetry loop: %2%nException value: %3%nError value: %4%nDSID: %5 |
| 0xC00008AD | Active Directory Lightweight Directory Services kan ikke generere et tilfeldig passord for den klonede domenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nNavn på klonedomenekontroller: %2%nFeil: %3 %4 |
Active Directory Lightweight Directory Services failed to generate a random password for the cloned domain controller.%n%nAdditional data:%nClone Id: %1%nClone domain controller name: %2%nError: %3 %4 |
| 0xC00008AE | Active Directory Lightweight Directory Services kan ikke angi passord for den klonede domenekontrolleren.%n%nTilleggsdata:%nKlone-ID: %1%nNavn på klonedomenekontroller: %2%nFeil: %3 %4 |
Active Directory Lightweight Directory Services failed to set password for the cloned domain controller.%n%nAdditional data:%nClone Id: %1%nClone domain controller name: %2%nError: %3 %4 |
| 0xC00008B0 | Kloning av virtuell domenekontroller mislyktes. Følgende %1 frittstående administrerte tjenestekontoer finnes på den klonede maskinen:%n%2%nAlle frittstående administrerte tjenestekontoer må fjernes for at kloning skal lykkes. Dette kan gjøres ved hjelp av cmdleten Uninstall-ADServiceAccount PowerShell. Grupperte administrerte tjenestekontoer støtter kloning av virtuell domenekontroller. Hvis du vil ha mer informasjon, kan du se http://go.microsoft.com/fwlink/?LinkId=265771 |
Virtual domain controller cloning failed. The following %1 standalone Managed Service Account(s) exist(s) on the cloned machine:%n%2%nFor cloning to succeed, all standalone Managed Service Accounts must be removed. This can be done using the Uninstall-ADServiceAccount PowerShell cmdlet. Group Managed Service Accounts support virtual domain controller cloning. For more information, please see http://go.microsoft.com/fwlink/?LinkId=265771 |
| 0xC00008B2 | Kan ikke fjerne hurtigbufrede hemmeligheter for følgende sikkerhetskontohaver fra lokal domenekontroller:%n%1%nFeil: %2 (%3)Når du har klonet en skrivebeskyttet domenekontroller, må hemmeligheter som tidligere ble hurtigbufret på den skrivebeskyttede domenekontrolleren for klonekilden, fjernes på kloningen. Hvis du ikke gjør dette, økes risikoen for at en angriper kan få tak i denne legitimasjonen fra en stjålet eller skadet kloning. Hvis sikkerhetskontohaveren er en høyt privilegert konto og må beskyttes mot dette, kan du bruke rootDSE-operasjonen rODCPurgeAccount for å fjerne hemmelighetene manuelt på den lokale domenekontrolleren. |
Failed to remove cached secrets of the following security principal from local domain controller:%n%1%nError: %2 (%3)After cloning a read-only domain controller, secrets which were previously cached on the cloning source read-only domain controller need to be removed on the clone. Failed to do this will increase the risk that an attacker can obtain those credentials from stolen or compromised clone. If the security principal is a highly privileged account and should be protected against this, please use rootDSE operation rODCPurgeAccount to manually clear its secrets on local domain controller. |
| 0xC00008B3 | Det oppstod et unntak under forsøk på å fjerne hurtigbufrede hemmeligheter fra lokal domenekontroller.%nTilleggsdata:%nUnntaksverdi: %1%nFeilverdi: %2%nDSID: %3Når du har klonet en skrivebeskyttet domenekontroller, må hemmeligheter som tidligere ble hurtigbufret på den skrivebeskyttede domenekontrolleren for klonekilden, fjernes på kloningen. Hvis du ikke gjør dette, økes risikoen for at en angriper kan få tak i denne legitimasjonen fra en stjålet eller skadet kloning. Hvis sikkerhetskontohaveren er en høyt privilegert konto og må beskyttes mot dette, kan du bruke rootDSE-operasjonen rODCPurgeAccount for å fjerne hemmelighetene manuelt på den lokale domenekontrolleren. |
Exception is raised while trying to remove cached secrets from local domain controller.%nAdditional data:%nException value: %1%nError value: %2%nDSID: %3After cloning a read-only domain controller, secrets which were previously cached on the cloning source read-only domain controller need to be removed on the clone. Failed to do this will increase the risk that an attacker can obtain those credentials from stolen or compromised clone. If any of these security principals is a highly privileged account and should be protected against this, please use rootDSE operation rODCPurgeAccount to manually clear its secrets on local domain controller. |
| 0xC00008B4 | IDen for generering av virtuell maskin i Active Directory-databasen for denne domenekontrolleren er forskjellig fra gjeldende verdi for denne virtuelle maskinen. Det ble imidlertid ikke funnet en konfigurasjonsfil for virtuell domenekontroller (DCCloneConfig.xml), slik at kloning av domenekontroller ikke ble prøvd. Hvis en kloneoperasjon for domenekontroller var tiltenkt, må du sørge for at en DCCloneConfig.xml angis på en av de støttede plasseringene som dokumenteres her: http://go.microsoft.com/fwlink/?LinkId=208030. I tillegg er IP-adressen til denne domenekontrolleren i konflikt med en annen domenekontrollers IP-adresse. Hvis du vil sørge for at det ikke oppstår avbrudd i tjenesten, blir domenekontrolleren konfigurert til å starte opp i DSRM.%nTilleggsdata:%nDen dupliserte IP-adressen: %1 |
The Virtual machine generation ID in the Active Directory database of this domain controller is different from the current value of this virtual machine. However, a virtual domain controller clone configuration file (DCCloneConfig.xml) could not be located so domain controller cloning was not attempted. If a domain controller cloning operation was intended, please ensure that a DCCloneConfig.xml is provided in any one of the supported locations as documented here: http://go.microsoft.com/fwlink/?LinkId=208030. In addition, the IP address of this domain controller conflicts with another domain controller's IP address. To ensure no disruptions in service occur, the domain controller has been configured to boot into DSRM.%nAdditional data:%nThe duplicate IP address: %1 |
| 0xC00008B5 | Det ble oppdaget en feil i databaseisolasjonen som brukes av satsvise LDAP-operasjoner. Flere satsvise LDAP-operasjoner kan føre til uventede eller feile resultater. Start tjenesten på nytt.%n%nTilleggsdata:%nFeilverdi: %1%nDSID: %2 |
An error has been detected in the database isolation used by LDAP batch operations. Further LDAP batch operations may have unexpected or incorrect results. Restart the service.%n%nAdditional data:%nError value: %1%nDSID: %2 |
| 0xC00008B6 | Active Directory Lightweight Directory Services registrerte en ugyldig kolonne for koblingsantall i kvotesporingstabellen. Kvotehåndhevelsen fungerer kanskje ikke optimalt før kvotesporingstabellen er bygget på nytt.%n%nTilleggsdata:%nNCDNT: %1%nKoblingsantall: %2%nTotalt antall: %3%nEier-SID:%4%nstartUSN:%5 |
Active Directory Lightweight Directory Services detected corrupt link count column in the quota-tracking table. Quota enforcement may not behave correctly until the quota-tracking table is rebuilt.%n%nAdditional data:%nNCDNT: %1%nLink count: %2%nTotal count: %3%nOwnerSid:%4%nstartUSN:%5 |
| 0xC0000960 | Et forsøk på å endre et loggsporet attributt mislyktes fordi bruker-IDen som er knyttet til endringen, var null.%nKoblingskilde: %1%nKoblingsmål: %2%nKoblingsattributt: %3%n |
An attempt to modify a history-tracked attribute failed because the User Identifier associated with the modification was zero.%nLink source: %1%nLink target: %2%nLink attribute: %3%n |
| 0xC0000963 | Databasen er merket med en ukjent GUID, noe som stopper initialiseringen:%nGUID: %1 |
The database is tagged with an unrecognized GUID, halting initialization:%nGUID: %1 |
| 0xC0000968 | Active Directory Lightweight Directory Services identifiserte at et attributtobjekt i skjemaet har ukjente systemflagg.%nFlagg: %1%nObjekt: %2 |
Active Directory Lightweight Directory Services identified an attribute object in the schema has unrecognized system flags.%nFlags: %1%nObject: %2 |
| 0xC0000969 | En ukjent valgfri funksjon er aktivert, noe som stopper initialiseringen.%nGUID for valgfri funksjon: %1%nStatus for valgfri funksjon: %2 |
An unrecognized optional feature is enabled, halting initialization.%nOptional feature GUID: %1%nOptional feature status: %2 |
| 0xC00009C7 | Active Directory Lightweight Directory Services kan ikke oppdatere utelukkelsesnøkkelen for sikkerhetskopien i løpet av installasjonen.%nBrukerhandling:%nKontroller at installasjonsprosessen har tilstrekkelige tillatelser til å opprette en verdi forutelukkelsesnøkkelen for sikkerhetskopi.%n%nTilleggsdata:%nNavn på nøkkel:%n%1%nFeilverdi:%n%2 %3 |
Active Directory Lightweight Directory Services was unable to update the backup exclusion key during installation.%nUser Action:%nPlease ensure the installation process has enough permission to create a value underthe backup exclusion key.%n%nAdditional Data:%nKey Name:%n%1%nError Value:%n%2 %3 |
| 0xC00009C9 | Active Directory Lightweight Directory Services kan ikke opprette den påkrevde verdien for VSS-tilgangskontroll.%n%nBrukerhandling:%nDette kan føre til vanskeligheter med å forsøke å registrere grensesnittet for sikkerhetskopien av skyggekopien senere.Hvis dette fører til at sikkerhetskopieringen av skyggekopien ikke starter, må du manuelt registreredenne registernøkkelen. Opprett en DWORD-verdi under registernøkkelen nedenfor medverdinavnet nedenfor og verdien 0x00000001.%n%nTilleggsdata:%nRegisternøkkel:%n%1%n%nNavn på registerverdi:%n%2%n%nFeilverdi:%n%3 %4 |
Active Directory Lightweight Directory Services failed to create the required VSS Access Control value.%n%nUser Action:%nThis may incur difficulties trying to register the shadow copy backup interface later.If this prevents the shadow copy backup service from starting, please manually registerthis registry key. Create a DWORD value, under the registry key below, with the valuename below, and the value of 0x00000001.%n%nAdditional Data:%nRegistry Key:%n%1%n%nRegistry Value Name:%n%2%n%nError Value:%n%3 %4 |
| 0xC00009CB | Forsøket på å initialisere skyggekopitjenesten mislyktes for denne forekomsten avActive Directory Lightweight Directory Services.%n%nBrukerhandling:%nI Windows XP kontrollerer du at denne AD LDS-forekomsten kjører som én avfølgende tillatte tjenestekontoer:%nLokalt system, lokal tjeneste, nettverkstjeneste, administrator eller sikkerhetskopieringsoperatør |
The attempt to initialize the shadow copy service failed for this instance ofActive Directory Lightweight Directory Services.%n%nUser Action:%nOn Windows XP, please ensure that this AD LDS instance is running as one of thefollowing allowed service accounts:%nLocal system, Local service, Network service, Administrator or Backup Operator |
| 0xC00009CC | Forsøket på å initialisere skyggekopitjenesten mislyktes for denne forekomsten avActive Directory Lightweight Directory Services.%n%nBrukerhandling:%nKontroller at nøkkelen for VSS-tilgangskontroll nedenfor har en registerverdi (med samme navn somtjenestekontoen som denne forekomsten av AD LDS kjører på) med verdien 1.%n%nTilleggsdata:%nRegisternøkkel:%n%1 |
The attempt to initialize the shadow copy service failed for this instance ofActive Directory Lightweight Directory Services.%n%nUser Action:%nEnsure that the VSS Access Control key below has a registry value (with the same name as theservice account for which this instance of AD LDS is running) under it with a value of 1.%n%nAdditional Data:%nRegistry Key:%n%1 |
| 0xC00009CE | I løpet av installasjonen mislyktes forsøket på å legge til denne serveren som en replika av følgende programkatalogpartisjon. %n%nProgramkatalogpartisjon: %n%1%nDSA-objekt for serveren: %n%2%nInstallasjonen fortsetter, men denne programkatalogpartisjonen vil ikke finnes i denne forekomsten. %nBrukerhandling: %nHvis du vil definere denne serveren som en replika av denne programkatalogpartisjonen, løser du denne feilen og legger til denne programpartisjonen på nytt etter at installasjonen er fullført.%n%nTilleggsdata:%nFeil:%n%3%nIntern ID:%n%4%n%n |
During installation, the attempt to add this server as a replica of the following application directory partition was not successful. %n%nApplication Directory Partition: %n%1%nDSA object of the server: %n%2%nThe installation process will continue, but this application directory partition will not be present on this instance. %nUser Action: %nIf you would like to make this server a replica of this application directory partition, resolve this error and re-add this application partition after the installation is complete.%n%nAdditional Data:%nError:%n%3%nInternal ID:%n%4%n%n |
| 0xC00009D1 | Forsøk på å angi den ønskede godkjenningsprotokollen for en tilkobling til følgende DSA mislyktes.%nDSA: %n%1%n%nTilleggsdata:%nFeil:%n%3 %2%n |
Attempting to set the desired authentication protocol for a connection to the following DSA failed.%nDSA: %n%1%n%nAdditional Data:%nError:%n%3 %2%n |
| 0xC00009D2 | Denne DSAen kan ikke bindes til følgende domene for å opprette, registrere eller bekrefte hovednavnene for tjenesten som kreves for at gjensidig godkjenning skal lykkes på inngåendetilkoblinger.%n%nDomene:%n%3%n%nTilleggsdata:%nFeilverdi:%n%1 %2 |
This DSA was unable to bind to the following domain in order to create/register/verify the service principal names needed for mutual authentication to succeed on inboundconnections.%n%nDomain:%n%3%n%nAdditional Data:%nError value:%n%1 %2 |
| 0xC00009D3 | Denne DSAen får ikke tilgang til følgende konto for å opprette eller bekrefte hovednavnene for tjenesten som kreves for at gjensidig godkjenning skal lykkes på inngåendetilkoblinger.%n%nKonto:%n%3%n%nTilleggsdata:%nFeilverdi:%n%1 %2 |
This DSA was unable to crack the following account in order to create/verify the service principal names needed for mutual authentication to succeed on inboundconnections.%n%nAccount:%n%3%n%nAdditional Data:%nError value:%n%1 %2 |
| 0xC00009D4 | Denne DSAen kan ikke oppdatere hovednavnene for tjenesten for følgende konto som kreves for at gjensidig godkjenning skal lykkes på inngåendetilkoblinger.%n%nKonto:%n%3%n%nTilleggsdata:%nFeilverdi:%n%1 %2 |
This DSA was unable to update the service principal names for the following account which are needed for mutual authentication to succeed on inboundconnections.%n%nAccount:%n%3%n%nAdditional Data:%nError value:%n%1 %2 |
| 0xC00009D6 | Denne DSAen kan ikke skrive skriptet som er påkrevd for å registrere hovednavnene for tjenesten for følgende konto som kreves for at gjensidig godkjenning skal lykkes på inngåendetilkoblinger.%n%nKonto:%n%3%n%nTilleggsdata:%nFeilverdi:%n%1 %2 |
This DSA was unable to write the script required to register the service principal names for the following account which are needed for mutual authentication to succeed on inboundconnections.%n%nAccount:%n%3%n%nAdditional Data:%nError value:%n%1 %2 |
| 0xC00009D8 | Denne DSAen kan ikke angi hovednavnene for tjenesten som kreves for at gjensidig godkjenning skal lykkes på inngåendetilkoblinger.%n%nTilleggsdata:%nFeilverdi:%n%1 %2 |
This DSA was unable to make the service principal names needed for mutual authentication to succeed on inboundconnections.%n%nAdditional Data:%nError value:%n%1 %2 |
| 0xC00009DA | Denne DSAen kan ikke opprette en skriptfil som kreves for registrering av hovednavn for tjenesten på følgende domene.%n%nDomene:%n%1%nFilnavn:%n%2%n%nTilleggsdata:%nFeilverdi:%n%3 %4 |
This DSA was unable to create a script file needed for service principal name registration in the following domain.%n%nDomain:%n%1%nFile Name:%n%2%n%nAdditional Data:%nError value:%n%3 %4 |
| 0xC00009DB | Hovednavnet for tjenesten (SPN) som denne forekomsten ønsker å registrere, er ikke unikt i virksomheten. Hvisgjensidig godkjenning skal fungere med denne forekomsten, må disse identiske hovednavnene for tjenesten fjernes. Vær oppmerksom på at disse identiskehovednavnene for tjenesten kan registreres i alle klarerte skoger på alle kontoer.%n%nSPN:%n%1%n%nBrukerhandling:%nFinn alle kontoer som har den identiske SPN-strengen for servicePrincipalName-attributtet, og fjern den fra de kontoene.%n |
The service principal name (SPN) that this instance wishes to register is not unique within the enterprise. Inorder for mutual authentication to work with this instance, these duplicate SPNs must be removed. Please note that these duplicateSPNs can be registered in any trusted forest on any account.%n%nSPN:%n%1%n%nUser Action:%nLocate all accounts which have the identical SPN string on the servicePrincipalName attribute and remove it from those accounts.%n |
| 0xC00009DC | Katalogserveren registrerte at databasen har blitt erstattet. Dette er enoperasjon som er utrygg og som ikke støttes.%n%nBrukerhandling:%nIngen. Active Directory Lightweight Directory Services gjenopprettet databasen i denne forekomsten,men dette kan ikke garanteres i alle tilfeller. Det frarådes på detsterkeste å erstatte databasen. Brukeren blir oppfordret på det sterkeste til å bruke sikkerhetskopien oggjenopprette muligheten til å rulle databasen tilbake.%n |
The Directory Server detected that the database has been replaced. This is anunsafe and unsupported operation.%n%nUser Action:%nNone. Active Directory Lightweight Directory Services was able to recover the database in this instance,but this is not guaranteed in all circumstances. Replacing the database isstrongly discouraged. The user is strongly encouraged to use the backup andrestore facility to rollback the database.%n |
| 0xC00009DD | Kan ikke oversette den angitte tjenestekontoen til en sikkerhetsidentifikator. Kjør installasjonen på nytt med enannen tjenestekonto.%n |
We were unable to translate the given service account into a security identifier! Please retry your installation with adifferent service account.%n |
| 0xC00009DE | Denne forekomsten av katalogserveren støtter ikke plassering av datafiler(database- og loggfiler) på flere diskvolumer. Det fører til atkatalogserveren ikke starter.%nBrukerhandling:%nDu starter denne katalogserveren ved å plassere alle datafiler (database- og loggfiler)på samme diskvolum. |
This instance of the directory server does not support placing data files(database and log files) on multiple disk volumes. As a result, the directoryserver will not start.%nUser Action:%nTo start this directory server, place all data files (database and log files)on the same disk volume. |
| 0xC00009DF | Katalogserveren kan ikke oppdatere tjenestekontoen, DNS-navnet og/eller portinformasjonen automatisk.%n%nDenne operasjonen blir forsøkt på nytt med følgende intervall.%n%nIntervall (minutter):%n%1%n%nTilleggsdata%nFeilverdi:%n%3 %4%nIntern ID:%n%2 |
The directory server failed to automatically update service account, dns name and/or port information.%n%nThis operation will be tried again at the following interval.%n%nInterval (minutes):%n%1%n%nAdditional Data%nError value:%n%3 %4%nInternal ID:%n%2 |
| 0xC00009E3 | Katalogserveren kan ikke oppdatere vertsnavnet og/eller portinformasjonen for denne tjenesten på følgende eksterneserver. Denne operasjonen vil bli prøvd på nytt. Andre eventuelle katalogservere i dette konfigurasjonssettet kan ikkereplikere endringer fra denne katalogserveren før denne endringen utføres og replikeres til disse katalogserverne.%n%nTilleggsdata%nMål-DSA-objekt:%n%1%nFeilverdi:%n%2 %3%nIntern ID:%n%4 |
The directory server has failed to update the host name and/or ports information for this service on the following remoteserver. This operation will be retried. Other directory servers in this configuration set (if any) will beunable to replicate changes from this directory server until this change is performed and replicated to them.%n%nAdditional Data%nTarget DSA object:%n%1%nError value:%n%2 %3%nInternal ID:%n%4 |
| 0xC00009E5 | Katalogserveren kan ikke oppdatere vertsnavnet og/eller portinformasjonen for denne tjenesten i den lokale databasen.Denne operasjonen vil bli prøvd på nytt.%n%nTilleggsdata%nFeilverdi:%n%2 %3%nIntern ID:%n%4 |
The directory server has failed to update the host name and/or ports information for this service in the local database.This operation will be retried.%n%nAdditional Data%nError value:%n%2 %3%nInternal ID:%n%4 |
| 0xC00009EB | Konfigurasjonssettet har en ugyldig replikeringsgodkjenningsmodus (msDS-replAuthenticationMode = %1). Replikering med kildeserveren er kanskje ikke mulig.%nJuster replikeringsgodkjenningsmodusen på kildeserveren før du installerer eventuelle kopier. Bruk kommandoen repadmin /replAuthMode. Se Replication and configuration sets i administratorhåndboken for Active Directory Lightweight Directory Services hvis du vil ha mer informasjon om replikeringsgodkjenningsmodus. |
The configuration set has an invalid replication authentication mode (msDS-replAuthenticationMode = %1). Replication with the source server may be impossible.%nPlease adjust the replication authentication mode on the source server before installing any replicas. Use repadmin /replAuthMode command. For more information about replication authentication mode, see \"Replication and configuration sets\" in the Active Directory Lightweight Directory Services Administrator's Guide. |
| 0xC00009EC | Active Directory Lightweight Directory Services kan ikke oppdatere registret.%n%nTilleggsdata%nRegisternøkkel:%n%1%nRegisterverdi:%n%2%nFeilverdi:%n%3 %4 |
Active Directory Lightweight Directory Services was unable to update the registry.%n%nAdditional Data%nRegistry key:%n%1%nRegistry value:%n%2%nError value:%n%3 %4 |
| 0xC00009ED | Finner ikke den tilpassede registreringsbeholderen for ServiceConnectionPoint i Active Directory Lightweight Directory Services.%n%nTilleggsdata%nDN for SCP-beholder:%n%1%nObjekt for konfigurasjon av SCP:%n%2%nFeilverdi:%n%3 %4%n%nBrukerhandling:%nBekreft at msDS-SCPContainer-attributtet som er lagret på msDS-ServiceConnectionPoint, henviser til en eksisterende beholder i Active Directory Lightweight Directory Services,eller fjern verdien for å opprette SCP-objektet på dets standardplassering under datamaskinobjektet. |
The custom ServiceConnectionPoint registration container is not found in Active Directory Lightweight Directory Services.%n%nAdditional Data%nSCP container DN:%n%1%nSCP configuration object:%n%2%nError value:%n%3 %4%n%nUser Action:%nVerify that msDS-SCPContainer attribute stored on the msDS-ServiceConnectionPoint is pointing to an existing container in Active Directory Lightweight Directory Services,or remove the value to create the SCP object in its default location under the computer object. |
| 0xC00009EE | Katalogserveren registrerte at databasen har blitt erstattet. Dette er enoperasjon som er utrygg og som ikke støttes. Tjenesten stopper til problemet erløst.%n%nBrukerhandling:%nGjenopprett den forrige kopien av databasen som var i bruk på denne maskinen.%nBrukeren oppfordres på det sterkeste til å bruke sikkerhetskopien i fremtiden, oggjenopprette muligheten til å rulle databasen tilbake.%n%nDenne feilen kan ignoreres, og databasen kan repareres ved å fjerne følgende registernøkkel.%n%n%nTilleggsdata%nRegisternøkkel:%n%1%nRegisterverdi:%n%2 |
The Directory Server detected that the database has been replaced. This is anunsafe and unsupported operation. The service will stop until the problem iscorrected.%n%nUser Action:%nRestore the previous copy of the database that was in use on this machine.%nIn the future, the user is strongly encouraged to use the backup andrestore facility to rollback the database.%n%nThis error can be suppressed and the database repaired by removing the following registry key.%n%n%nAdditional Data%nRegistry key:%n%1%nRegistry value:%n%2 |
| 0xC00009EF | Active Directory Lightweight Directory Services forsøkte å oppdatere settet med referansedata, men mislyktes. Denne operasjonen vil bli prøvd på nytt.%n%nTilleggsdata%nFeilverdi:%n%1 %2%nIntervall for nytt forsøk (minutter):%n%3%n%nBrukerhandling%nHvis denne operasjonen mislykkes flere ganger, starter du katalogtjenesten på nytt. |
Active Directory Lightweight Directory Services attempted to refresh the set of referral data but failed. The operation will be retried.%n%nAdditional Data%nError value:%n%1 %2%nRetry interval (minutes):%n%3%n%nUser Action%nIf this operation continues to fail, restart the directory service. |
| 0xC00009F0 | Tjenestekontoen for denne forekomsten av Active Directory Lightweight Directory Services kan ikke brukes med det valgte konfigurasjonssettet. Velg en annen tjenestekonto, og prøv deretter på nytt. Se Selecting a service account i Hjelp for Active Directory Lightweight Directory Services hvis du vil ha mer informasjon om AD LDS-tjenestekontoer.%nKontovalidering mislyktes med feilen %1: %2 |
The service account for this instance of Active Directory Lightweight Directory Services cannot be used with the selected configuration set. Select a different service account, and then try again. For more information about AD LDS service accounts, see \"Selecting a service account\" in Active Directory Lightweight Directory Services Help.%nAccount validation failed with error %1: %2 |
| 0xC00009F2 | Konfigurasjonssettet har en ugyldig replikeringsgodkjenningsmodus (msDS-replAuthenticationMode). Konfigurasjonssettet bruker direkte Negotiate-godkjenning, men kildetjenestekontoen er ikke en lokal ikke-systemkonto. Replikering med kildeserveren er ikke mulig.%nJuster replikeringsgodkjenningsmodusen på kildeserveren før du installerer eventuelle kopier. Bruk kommandoen repadmin /replAuthMode. Se Replication and configuration sets i administratorhåndboken for Active Directory Lightweight Directory Services hvis du vil ha mer informasjon om replikeringsgodkjenningsmodus. |
The configuration set has an invalid replication authentication mode (msDS-replAuthenticationMode). It uses negotiate pass-through authentication, but the source service account is not a local non-system account. Replication with the source server will not be possible.%nPlease adjust the replication authentication mode on the source server before installing any replicas. Use repadmin /replAuthMode command. For more information about replication authentication mode, see \"Replication and configuration sets\" in the Active Directory Lightweight Directory Services Administrator's Guide. |
| 0xC00009F3 | Konfigurasjonssettet har en ugyldig replikeringsgodkjenningsmodus (msDS-replAuthenticationMode). Det krever gjensidig Kerberos-godkjenning, men kildeserveren er ikke knyttet til et domene eller bruker en lokal tjenestekonto. Replikering med kildeserveren er ikke mulig.%nJuster replikeringsgodkjenningsmodusen på kildeserveren før du installerer eventuelle kopier. Bruk kommandoen repadmin /replAuthMode. Se Replication and configuration sets i administratorhåndboken for Active Directory Lightweight Directory Services hvis du vil ha mer informasjon om replikeringsgodkjenningsmodus. |
The configuration set has an invalid replication authentication mode (msDS-replAuthenticationMode). It requires Kerberos mutual authentication, but the source server is either not joined to a domain, or is using a local service account. Replication with the source server will not be possible.%nPlease adjust the replication authentication mode on the source server before installing any replicas. Use repadmin /replAuthMode command. For more information about replication authentication mode, see \"Replication and configuration sets\" in the Active Directory Lightweight Directory Services Administrator's Guide. |
| 0xC00009F4 | Konfigurasjonssettet krever gjensidig Kerberos-godkjenning. Den valgte systemtjenestekontoen er ugyldig fordi denne datamaskinen er en domenekontroller. Gjensidig Kerberos-godkjenning er ikke tilgjengelig når forekomsten kjører ved hjelp av denne kontoen. |
The configuration set requires Kerberos mutual authentication. The selected system service account is invalid because this computer is a Domain Controller. Kerberos mutual authentication will be unavailable when the instance runs using this account. |
| 0xC00009F5 | Konfigurasjonssettet krever gjensidig Kerberos-godkjenning. Du kan ikke installere en replika på denne datamaskinen fordi den ikke er knyttet til et domene. |
The configuration set requires Kerberos mutual authentication. You cannot install a replica on this computer because it is not joined to a domain. |
| 0xC00009F6 | Konfigurasjonssettet krever gjensidig Kerberos-godkjenning. Du kan ikke installere en replika i dette konfigurasjonssettet ved hjelp av en lokal konto. Velg en annen konto. |
The configuration set requires Kerberos mutual authentication. You cannot install a replica in this configuration set using a local account. Select a different account. |
| 0xC00009F7 | Den valgte tjenestekontoen kan ikke godkjenne med replikakilden %3:%4 ved hjelp av gjensidig Kerberos-godkjenning. Tjenestekontoen for den nye Active Directory Lightweight Directory Services-replikaen bør være en domenekonto som er klarert av konfigurasjonssettet. Bekreft også at replikakilden har et riktig registrert hovednavn for tjenesten (SPN).%nGodkjenningen mislyktes med feilen %1: %2 |
The selected service account cannot authenticate with the replica source %3:%4 using Kerberos mutual authentication. The service account for the new Active Directory Lightweight Directory Services replica should be a domain account trusted by the configuration set. Also, verify that the replica source has a properly registered service principal name (SPN).%nThe authentication failed with error %1: %2 |
| 0xC00009F8 | Replikakilden %1:%2 krever Kerberos-godkjenning, men har ikke et riktig registrert hovednavn for tjenesten (SPN).%nEn partisjonsadministrator kan registrere hovednavnene for tjenesten for replikakilden ved å kjøre den satsvise filen som finnes i datamappen for replikakilden.%nAlternativt kan du konfigurere Kerberos-godkjenning som valgfri. Endre verdien for attributtet msDS-ReplAuthenticationMode fra ADAM_REPL_AUTHENTICATION_MODE_MUTUAL_AUTH_REQUIRED til ADAM_REPL_AUTHENTICATION_MODE_NEGOTIATE i konfigurasjonspartisjonen for alle forekomster i konfigurasjonssettet. Når msDS-ReplAuthenticationMode er satt til ADAM_REPL_AUTHENTICATION_MODE_NEGOTIATE, kan replikapartnere bruke NTLM til godkjenning hvis Kerberos ikke er tilgjengelig. |
The replica source %1:%2 requires Kerberos authentication but does not have a properly registered service principal name (SPN).%nAn partition administrator can register the SPNs for the replica source by running the batch file that is in the data folder of the replica source.%nAlternatively, you can configure Kerberos authentication as optional; change the value of the attribute msDS-ReplAuthenticationMode from ADAM_REPL_AUTHENTICATION_MODE_MUTUAL_AUTH_REQUIRED to ADAM_REPL_AUTHENTICATION_MODE_NEGOTIATE on the Configuration partition of all instances in the configuration set. When msDS-ReplAuthenticationMode is set to ADAM_REPL_AUTHENTICATION_MODE_NEGOTIATE, replica partners can use NTLM for authentication if Kerberos is not available. |
| 0xC00009F9 | Konfigurasjonssettet bruker direkte Negotiate-godkjenning. Du kan ikke installere en replika i konfigurasjonssettet ved hjelp av en innebygd konto eller domenekonto. Alle forekomster i dette konfigurasjonssettet må bruke lokale kontoer med samme navn og passord. |
The configuration set uses Negotiate pass-through authentication. You cannot install a replica in this configuration set using a built-in or domain account. All instances in this configuration set must use local accounts with the same name and password. |
| 0xC00009FA | Konfigurasjonssettet bruker direkte Negotiate-godkjenning. Det valgte kontonavnet samsvarer ikke med kontonavnet som brukes av kildeserveren. Alle forekomster i dette konfigurasjonssettet må være kontoer med samme navn og passord. |
The configuration set uses Negotiate pass-through authentication. The selected account name does not match the account name used by the source server. All instances in this configuration set must use accounts with the same name and password. |
| 0xC00009FB | Den valgte tjenestekontoen kan ikke godkjenne med replikakilden %3:%4 ved hjelp av Negotiate-godkjenning. Tjenestekontoen er ugyldig eller datamaskinens konfigurasjon støtter ikke NTLM-godkjenning med replikakilden.%nGodkjenningen mislyktes med feilen %1: %2 |
The selected service account cannot authenticate with the replica source %3:%4 using Negotiate authentication. Either the service account is invalid or the computer's configuration does not support NTLM authentication with the replica source.%nThe authentication failed with error %1: %2 |
| 0xC0000A0B | Samler obligatorisk fjerningsinformasjon Active Directory Lightweight Directory Services (%1!S!)...%n |
Collecting required removal information from Active Directory Lightweight Directory Services (%1!S!)...%n |
| 0xC0000A0C | Active Directory Lightweight Directory Services kan ikke startes. Kan ikke samle fjerningsinformasjon. |
Active Directory Lightweight Directory Services could not be started. Removal information could not be collected. |
| 0xC0000A0D | Active Directory Lightweight Directory Services-forekomsten kan ikke replikere endringer som ble gjort i partisjonen %1.%n%nDu unngår at disse endringene går tapt ved å sørge for at minst én Active Directory Lightweight Directory Services-forekomst med denne partisjonen er tilgjengelig, og deretter prøver du på nytt.%n%nHvis du hopper over dette trinnet, går endringer du gjorde på denne partisjonen for denne forekomsten, som ikke ennå har blitt replikert til andre replikaer, tapt.%n |
The Active Directory Lightweight Directory Services instance could not replicate changes made to the partition %1.%n%nTo avoid losing these changes, ensure that at least one Active Directory Lightweight Directory Services instance with this partition is available, and then try again.%n%nIf you skip this step any changes made to this partition on this instance that have not yet replicated to other replicas will be lost.%n |
| 0xC0000A31 | Systemfeil. Det er ikke trygt å fortsette uten å starte maskinen på nytt. |
System error. It is unsafe to continue without rebooting the machine. |
| 0xC0000A32 | Det finnes ingen Active Directory Lightweight Directory Services-forekomst som fungerer i dette konfigurasjonssettet. Forsøket på å finne og koble til en annen Active Directory Lightweight Directory Services-forekomst mislyktes med følgende feil:%nFeil %1!d!%nKontroller at minst én tilgjengelig AD LDS-forekomst eksisterer i konfigurasjonssettet før du fortsetter.%nHvis du hopper over dette trinnet, kan du ikke lagre nylige dataendringer i en annen replika, og metadata blir ikke fjernet fra konfigurasjonssettet. Dette anbefales ikke. |
There is no functioning Active Directory Lightweight Directory Services instance in this configuration set. The attempt to find and connect to another Active Directory Lightweight Directory Services instance failed with the following error:%nError %1!d!%nPlease ensure one available AD LDS instance exists in the configuration set before continuing.%nSkipping this step will prevent saving recent data changes to another replica, and metadata will not be removed from the configuration set. This is not suggested. |
| 0xC0000B12 | Den lokale katalogtjenesten ble bedt om å legge til en skrivbar replika av følgende katalogpartisjon. Den lokale katalogtjenesten er skrivebeskyttet og kan ikke legge til en skrivbar replika av noen partisjon.%n%nKatalogpartisjon:%n%1%nNettverksadresse:%n%2%nAlternativer:%n0x%3 |
The local directory service was prompted to add a writable replica of the following directory partition. The local directory service is read-only and cannot add a writable replica of any partition.%n%nDirectory partition:%n%1%nNetwork address:%n%2%nOptions:%n0x%3 |
| 0xC0000B17 | Internal event: This log entry is a continuation from the preceding extended error information entry.%n%nExtended information:%nExtended Error Parameters: %n%1%nParameter 1: %n%2%nParameter 2: %n%3%nParameter 3: %n%4%nParameter 4: %n%5%nParameter 5: %n%6%nParameter 6: %n%7%nParameter 7: %n%8 |
Internal event: This log entry is a continuation from the preceding extended error information entry.%n%nExtended information:%nExtended Error Parameters: %n%1%nParameter 1: %n%2%nParameter 2: %n%3%nParameter 3: %n%4%nParameter 4: %n%5%nParameter 5: %n%6%nParameter 6: %n%7%nParameter 7: %n%8 |
| 0xC0000B18 | Støtte for sikkerhetskopiering og gjenoppretting av Active Directory Lightweight Directory Services krever at COM+ Event System startes. Sikkerhetskopiering eller gjenoppretting fungerer ikke før dette problemet er løst.%n%nBrukerhandling%nLøs problemet med oppstartsfeil med COM+ Event System-tjenesten. Én mulig årsak kan være at COM+ Event System ikke er konfigurert til å startes automatisk.%n%nTilleggsdata%nFeilverdi: %n%1 %2 |
Active Directory Lightweight Directory Services backup and restore support requires the COM+ Event System to be started. Backup or restore will not succeed until this is corrected.%n%nUser Action%nResolve the issue with COM+ Event System service startup failure. One possible cause is the COM+ Event System is not configured to auto-start.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC0000B1A | Et eksternt prosedyrekall som kjører lokalt, tok for lang tid å fullføre. Klienten har sannsynligvis avbrutt dette kallet.%n%nTilleggsdata%nStarttidspunkt:%n%1%nKall-ID:%n%2%n |
A remote procedure call running locally took too long to complete. The client has likely cancelled this call.%n%nAdditional Data%nStart Time:%n%1%nCall Identifier:%n%2%n |
| 0xC0000B1B | Knowledge Consistency Checker kan ikke finne en replikeringstilkobling for den skrivebeskyttede lokale katalogtjenesten. En replikeringstilkobling med følgende alternativ må eksistere i skogen for at FRS-systemet skal fungere riktig.%n%nTilleggsdata%nAlternativ: %n%1%nBrukerhandling%nGjenopprett den opprinnelige replikeringstilkoblingen for den lokale katalogtjenesteforekomsten på en skrivbar katalogtjenesteforekomst.%n |
The Knowledge Consistency Checker was unable to locate a replication connection for the read-only local directory service. A replication connection with the following option must exist in the forest for correct FRS system behavior.%n%nAdditional Data%nOption: %n%1%nUser Action%nRestore the original replication connection for the local directory service instance on a writable directory service instance.%n |
| 0xC0000B1D | Fant en replikeringstilkobling for den lokale skrivebeskyttede katalogtjenesten i Knowledge Consistency Checker, men kildeserveren svarer ikke eller replikerer ikke. Fant ingen ny passende kildeserver fra de gjeldende replikeringspartnerne. Denne operasjonen vil bli forsøkt på nytt.%n%nTilleggsdata%nTilkobling: %n%1%nKildeserver: %n%2%n |
The Knowledge Consistency Checker located a replication connection for the local read-only directory service, but the source server is not responsive or not replicating. A new suitable source server was not found from the current replication partners. This operation will be retried.%n%nAdditional Data%nConnection: %n%1%nSource Server: %n%2%n |
| 0xC0000B1F | Knowledge Consistency Checker fant en replikeringstilkobling for den lokale skrivebeskyttede katalogtjenesten, og forsøkte å oppdatere den eksternt på følgende katalogtjenesteforekomst. Operasjonen mislyktes. Den vil bli prøvd på nytt.%n%nTilleggsdata%nTilkobling: %n%1%nEkstern katalogtjeneste: %n%2%n%nTilleggsdata%nFeilverdi:%n%3 %4%n |
The Knowledge Consistency Checker located a replication connection for the local read-only directory service and attempted to update it remotely on the following directory service instance. The operation failed. It will be retried.%n%nAdditional Data%nConnection: %n%1%nRemote Directory Service: %n%2%n%nAdditional Data%nError value:%n%3 %4%n |
| 0xC0000B20 | Knowledge Consistency Checker forsøkte å endre følgende objekt i følgende eksterne katalogtjenesteforekomst ved hjelp av LDAP. Operasjonen mislyktes.%n%nTilleggsdata%nObjekt: %n%1%nEkstern katalogtjeneste: %n%2%n%nTilleggsdata%nFeilverdi:%n%3 %4%nLDAP-feilverdi:%n%5 %6%n |
The Knowledge Consistency Checker attempted to ldap-modify the following object on the following remote directory service instance. The operation failed.%n%nAdditional Data%nObject: %n%1%nRemote Directory Service: %n%2%n%nAdditional Data%nError value:%n%3 %4%nLdap Error value:%n%5 %6%n |
| 0xC0000B21 | Knowledge Consistency Checker forsøkte å replikere endringer for følgende enkeltobjekt fra følgende eksterne katalogtjenesteforekomst. Operasjonen mislyktes.%n%nTilleggsdata%nObjekt: %n%1%nEkstern katalogtjeneste: %n%2%n%nTilleggsdata%nFeilverdi:%n%3 %4%n |
The Knowledge Consistency Checker attempted to replicate changes for the following single object from the following remote directory service instance. The operation failed.%n%nAdditional Data%nObject: %n%1%nRemote Directory Service: %n%2%n%nAdditional Data%nError value:%n%3 %4%n |
| 0xC0000B22 | Knowledge Consistency Checker forsøkte å binde til følgende eksterne katalogtjenesteforekomst ved hjelp av LDAP. Operasjonen mislyktes.%n%nTilleggsdata%nEkstern katalogtjeneste: %n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3%nLDAP-feilverdi:%n%4 %5%n |
The Knowledge Consistency Checker attempted to ldap-bind to the following remote directory service instance. The operation failed.%n%nAdditional Data%nRemote Directory Service: %n%1%n%nAdditional Data%nError value:%n%2 %3%nLdap Error value:%n%4 %5%n |
| 0xC0000B23 | Knowledge Consistency Checker forsøkte å oppheve binding til følgende eksterne katalogtjenesteforekomst ved hjelp av LDAP. Operasjonen mislyktes.%n%nTilleggsdata%nEkstern katalogtjeneste: %n%1%n%nTilleggsdata%nFeilverdi:%n%2 %3%nLDAP-feilverdi:%n%4 %5%n |
The Knowledge Consistency Checker attempted to ldap-unbind to the following remote directory service instance. The operation failed.%n%nAdditional Data%nRemote Directory Service: %n%1%n%nAdditional Data%nError value:%n%2 %3%nLdap Error value:%n%4 %5%n |
| 0xC0000B25 | En skrivebeskyttet domenekontroller (RODC) kunne ikke opprette et tilkoblingsobjekt for den skrivebeskyttede domenekontrolleren. |
While promoting a Read-only Domain Controller (RODC), failed to create a connection object for the RODC. |
| 0xC0000B32 | Katalogtjenesten nådde det maksimale antallet overvåkingshendelser som kan bufres i minnet samtidig, under logging av overvåkingshendelser for objektet nedenfor. Operasjonen ble avbrutt fordi denne grensen ble nådd.%n%nMaksimalt antall overvåkingshendelser som kan bufres:%n%1%n%nUnikt navn for objekt:%n%2%n%nDette forekommer vanligvis hvis mange endringer utføres i attributter som krever overvåking. Et eksempel på en slik operasjon kan være sletting av medlemskap for en stor gruppe, der member-attributtet blir overvåket.%n%n%nTilleggsdata fra overvåkingshendelsen%nAttributtnavn eller gammelt unikt navn:%n%3%n%nAttributtverdi eller nytt unikt navn:%n%4%n%n%nBrukerhandling%n(1) Kontroller at det ikke utføres for mange objektopprettinger, endringer, flyttinger, endring av navn eller slettinger.%n(2) Kontroller at ikke for mye overvåking er aktivert. Kontroller for eksempel at det ikke er konfigurert overvåking for flere attributter enn nødvendig.%n(3) Øk om nødvendig størrelsen på overvåkingskøen ved å øke registerparameteren Maximum Audit Queue Size. |
While logging audit events for the following object, the directory service reached the maximum number of audit events that could be cached in memory at any given time. As a result of reaching this limit, the operation was aborted.%n%nMaximum number of audit events that can be cached:%n%1%n%nDistinguished name of object:%n%2%n%nGenerally this occurs if there are a large number of changes being performed on attributes that require auditing. An example of such an operation could be deleting the membership of a large group, where the ‘memberattribute is being audited.%n%n%nAdditional Data From the Audit Event%nAttribute name or old distinguished name:%n%3%n%nAttribute value or new distinguished name:%n%4%n%n%nUser Action%n(1) Check that an excessive number of object creation, modification, move, rename or undelete operations are not being performed.%n(2) Check that an excessive amount of auditing is not enabled. For example, confirm that auditing is not configured for more attributes than is necessary.%n(3) If necessary, increase the size of the audit queue by increasing the 'Maximum Audit Queue Size' registry parameter. |
| 0xC0000B34 | Denne domenekontrolleren ble ikke gjort til driftsovervåker for infrastrukturen i katalogtjenesten.%n%nTilleggsdata:%nFeilverdi:%n%1 %2%n |
The Directory Service failed to make this domain controller the infrastructure operations master.%n%nAdditional data:%nError value:%n%1 %2%n |
| 0xC0000B35 | Nivåhevingen Install-From-Media for en skrivebeskyttet domenekontroller kan ikke starte fordi operativsystemversjonen (%1.%2) for kildedatabasen ikke samsvarer med operativsystemversjonen (%3.%4) for den lokale datamaskinen. |
The Install-From-Media promotion of a DC cannot start because the OS Version (%1.%2) of the source database does not match the OS Version (%3.%4) of the local computer. |
| 0xC0000B38 | Domenekontrolleren forsøker å replikere følgende navngivingskontekst fra følgende skrivebeskyttede domenekontroller.Replikering med kilde som skrivebeskyttet domenekontroller er ikke tillatt.%n%nNavngivingskontekst:%n%1%nServer:%n%2%n |
The domain controller is trying to replicate the following NC from the following read-only domain controller.Replication with source as read-only domain controller is not allowed to proceed.%n%nNaming Context:%n%1%nServer:%n%2%n |
| 0xC0000B39 | Active Directory Lightweight Directory Services kan ikke initialiseres. Oppdatering av standardsikkerhet for følgende objectClass mislyktes.%n%nObjekt: %1 |
Active Directory Lightweight Directory Services could not be initialized. Updating default security for the following objectClass failed.%n%nobject: %1 |
| 0xC0000B3A | Frakoblet AD/DS/LDS-datanettleser.Bruksområde:%1 alternativerAlternativer: -dbpath-filbane (obligatorisk) Filbanen må peke til DIT-filen på lokal server (kan være på et skrivebeskyttet medium (for eksempel et statisk utvalg)). DIT-filen må være i en konsekvent tilstand (ESE-logger må spilles av på nytt). -logpath-bane (valgfritt) Banen bør peke til en skrivbar mappe på den lokale serveren, der ESE-loggfiler blir opprettet. Hvis ingen mappe er angitt, blir temp-mappen brukt. -adlds (valgfritt) Åpne DIT-filen for AD/LDS. -ldapPort-nummer (obligatorisk) LDAP-portverdi. -sslPort-nummer (valgfritt) SSL-portverdi. Standard: LDAP-port+1 -gcPort-nummer (valgfritt) GC-portnummer. Standard: LDAP-port+2 -gcSslPort-nummer (valgfritt) GC SSL-portnummer. Standard: LDAP-port+3 -allowUpgrade (valgfritt) Tillat oppgradering av DIT-filen. Det er nyttig når du skal åpne bakoverkompatible DIT-filer eller statiske utvalg. Må være på et skrivbart medium. -allowNonAdminAccess (valgfritt) Tillat at ikke-administratorer får tilgang til data i katalogen. Hvis ingenting er angitt, har bare domene- og virksomhetsadministratorer fra måldomenet tilgang til dataene. |
AD/DS/LDS offline data browser.Usage:%1 optionsOptions: -dbpath filepath (required) Filepath must point to the DIT file on the local server, which could be on read-only media (such as a snapshot). The DIT must be in a consistent state, that is, the ESE logs must be replayed. -logpath path (optional) The path should point to a writeable folder on the local server, where ESE log files will be created. If not specified, then temp folder will be used. -adlds (optional) open AD/LDS DIT. -ldapPort number (required) LDAP port value. -sslPort number (optional) SSL port value. Default: LDAP port+1 -gcPort number (optional) GC port number. Default: LDAP port+2 -gcSslPort number (optional) GC SSL port number. Default: LDAP port+3 -allowUpgrade (optional) Allow to upgrade the DIT file. This is useful for opening downlevel DITs/snapshots. The file needs to be on writable media. -allowNonAdminAccess (optional) Allow non-administrators to access data in the directory. If not specified, then only Domain Admins and Enterprise Admins from the target domain will be able to access the data. |
| 0xC0000B3B | Internal event: Active Directory Lightweight Directory Services could not automatically generate a mapiID attribute for the following new schema object.%n%nNew schema object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
Internal event: Active Directory Lightweight Directory Services could not automatically generate a mapiID attribute for the following new schema object.%n%nNew schema object:%n%1%n%nAdditional Data%nError value:%n%3 %2 |
| 0xC0000B3C | I løpet av en forespørsel om Active Directory Lightweight Directory Services-replikering registrerte den lokale domenekontrolleren en ugyldig lokalUpToDateness Vector for den angitte partisjonen.%n%nHvis ikke dette problemet løses umiddelbart, fører det til inkonsekvenser i Active Directory Lightweight Directory Services-databasenefor denne domenekontrolleren.%nBrukerhandlinger:%nIverksett senking av nivået for domenekontrolleren.%n%nPartisjon:%n%1%n |
During an Active Directory Lightweight Directory Services replication request, the local domain controller (DC) detected an invalid localup-to-dateness vector for the specified partition.%n%nIf not resolved immediately, this scenario will result in inconsistencies in the Active Directory Lightweight Directory Services databasesof this DC.%nUser Actions:%nForcibly demote the DC.%n%nPartition:%n%1%n |
| 0xC0000B3F | I løpet av en Active Directory Lightweight Directory Services-replikeringssyklus identifiserte den lokale domenekontrollerenen ekstern domenekontroller som har en UpToDateness Vector for den angitte partisjonen som var ugyldig.%n%n%nEkstern domenekontroller:%n%1%nPartisjon:%n%2%n |
During an Active Directory Lightweight Directory Services replication cycle, the local domain controller (DC) identifieda remote DC whose up-to-dateness vector for the specified partition was found to be invalid.%n%n%nRemote DC:%n%1%nPartition:%n%2%n |
| 0xC0000B40 | Active Directory Lightweight Directory Services-databasen har blitt reparert etter at det ble registrert en ugyldig UpToDateness Vector. Hvis det ikke finnes flereutestående problemer som blokkerer annonsering av denne domenekontrolleren,blir Net Logon-tjenesten startet på nytt.%n |
The Active Directory Lightweight Directory Services database has been repaired after detecting an invalid up-to-dateness vector. If there are noother outstanding issues blocking advertisement of this domain controller,then the Net Logon service will be restarted.%n |
| 0xC0000B41 | Active Directory Lightweight Directory Services-databasen har en ugyldig UpToDateness Vector.%n%nActive Directory Lightweight Directory Services kan ikke logge på brukere før dette problemet er løst. Det fører til at Net Logon-tjenesten har stoppet midlertidig.%n%nBrukerhandling%nSe tidligere hendelseslogger hvis du vil ha mer informasjon. |
The Active Directory Lightweight Directory Services database has an invalid up-to-dateness vector.%n%nActive Directory Lightweight Directory Services will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.%n%nUser Action%nSee previous event logs for details. |
| 0xC0000B43 | Følgende katalogtjeneste sendte en replikeringsforespørsel til replikeringsattributter i filtrerte sett, som har blitt avvist av den lokale katalogtjenesten. Den anmodende katalogtjenesten har ikke tilgang til replikeringsattributter i det filtrerte settet.%n%nAnmodende katalogtjeneste: %n%2%nKatalogpartisjon: %n%1%n%nBrukerhandling%nHvis den anmodende katalogtjenesten skal få attributter i en filtrert liste, må du bekrefte at sikkerhetsbeskrivelsen på denne katalogpartisjonen har riktig konfigurasjon for tilgangsrettigheten Replication Get Changes In Filtered Set. Du kan også få denne meldingen når attributtene i filtrerte sett er forskjellige i kilde- og måldomenekontrollerne på grunn av en nylig skjemaendring. Denne meldingen forsvinner når skjemaet er synkronisert mellom mål- og kildedomenekontrollerne. |
The following directory service made a replication request to replicate attributes in filtered set that has been denied by the local directory service. The requesting directory service does not have access to replicate attributes in the filtered set.%n%nRequesting directory service: %n%2%nDirectory partition: %n%1%n%nUser Action%nIf the requesting directory service should get attributes in filtered list, verify that the security descriptor on this directory partition has the correct configuration for the Replication Get Changes In Filtered Set access right. You may also get this message when the attributes in filtered set are different between source and destination DCs because of recent schema change. This message will cease when the schema is in sync between the destination and source DCs. |
| 0xC0000B44 | I løpet av en forespørsel om Active Directory Lightweight Directory Services-replikering identifiserte den lokale domenekontrollerenen uklarert klient som har mottatt replikeringsdata fra den lokale domenekontrolleren ved hjelp av allerede godkjenteUSN-sporingsnumre. Skrivebeskyttede domenekontrollere og DirSync-klienter er eksempler på uklarerte klienter.%n%nKlienten mener den har en mer oppdatert Active Directory Lightweight Directory Services-database enn denlokale domenekontrolleren, og derfor bruker ikke klienten fremtidige endringer i versjonen av Active Directory Lightweight DirectoryServices-databasen, eller replikerer endringene til direkte og transitive replikeringspartnere som stammer fra dennelokale domenekontrolleren.%n%nHvis dette problemet ikke løses umiddelbart, fører det til inkonsekvenser i Active Directory Lightweight Directory Services-databaserfor denne kildedomenekontrolleren og én eller flere direkte og transitive replikeringspartnere. Spesieltkonsekvensen til brukere, datamaskiner og klareringsforhold, deres passord, sikkerhetsgrupper,medlemskap i sikkerhetsgrupper og andre Active Directory Lightweight Directory Services-konfigurasjonsdata kan variere, noe som kan påvirke muligheten til å logge på,søke etter interessante objekter og utføre andre kritiske operasjoner.%n%nDu fastslår om denne feilkonfigurasjonen eksisterer ved å spørre denne hendelses-IDen ved hjelp av http://support.microsoft.com,eller du kan kontakte Microsoft Kundestøtte.%n%nDen mest sannsynlige årsaken til dette problemet er ufullstendig gjenoppretting av Active Directory Lightweight Directory Services på denlokale domenekontrolleren.%n%nBrukerhandlinger:%nHvis dette problemet oppstod på grunn av en ufullstendig eller utilsiktet gjenoppretting, senker du nivået på domenekontrolleren.%n%nUklarert klient:%n%1%nPartisjon:%n%2%nUSN rapportert av en klient som ikke er en domenekontroller:%n%3%nUSN rapportert av lokal domenekontroller:%n%4%n |
During an Active Directory Lightweight Directory Services replication request, the local domain controller (DC) identifiedan untrusted client which has received replication data from the local DC using already-acknowledged USNtracking numbers. Read-only DCs and DirSync clients are examples of untrusted clients.%n%nBecause the client believes it is has a more up-to-date Active Directory Lightweight Directory Services database than thelocal DC, the client will not apply future changes to its copy of the Active Directory Lightweight Directory Servicesdatabase or replicate them to its direct and transitive replication partners that originate from thislocal DC.%n%nIf not resolved immediately, this scenario will result in inconsistencies in the Active Directory Lightweight Directory Services databasesof this source DC and one or more direct and transitive replication partners. Specifically theconsistency of users, computers and trust relationships, their passwords, security groups,security group memberships and other Active Directory Lightweight Directory Services configuration data may vary, affecting the ability to log on,find objects of interest and perform other critical operations.%n%nTo determine if this misconfiguration exists, query this event ID using http://support.microsoft.comor contact your Microsoft product support.%n%nThe most probable cause of this situation is the improper restore of Active Directory Lightweight Directory Services on thelocal domain controller or the remote Read-Only domain controller.%n%nUser Actions:%nIf this situation occurred because of an improper or unintended restore, forcibly demote the affected DC.%n%nUntrusted client:%n%1%nPartition:%n%2%nUSN reported by non-DC client:%n%3%nUSN reported by Local DC:%n%4%n |
| 0xC0000B45 | I løpet av en forespørsel om Active Directory Lightweight Directory Services-replikering identifiserte den lokale domenekontrollerenen uklarert klient som har mottatt replikeringsdata fra den lokale domenekontrolleren ved hjelp av allerede godkjenteUSN-sporingsnumre. Skrivebeskyttede domenekontrollere og DirSync-klienter er eksempler på uklarerte klienter.%n%nKlienten mener den har en mer oppdatert Active Directory Lightweight Directory Services-database enn denlokale domenekontrolleren, og derfor bruker ikke klienten fremtidige endringer i versjonen av Active Directory Lightweight DirectoryServices-databasen, eller replikerer endringene til direkte og transitive replikeringspartnere som stammer fra dennelokale domenekontrolleren.%n%nHvis dette problemet ikke løses umiddelbart, fører det til inkonsekvenser i Active Directory Lightweight Directory Services-databaserfor denne kildedomenekontrolleren og én eller flere direkte og transitive replikeringspartnere. Spesieltkonsekvensen til brukere, datamaskiner og klareringsforhold, deres passord, sikkerhetsgrupper,medlemskap i sikkerhetsgrupper og andre Active Directory Lightweight Directory Services-konfigurasjonsdata kan variere, noe som kan påvirke muligheten til å logge på,søke etter interessante objekter og utføre andre kritiske operasjoner.%n%nDu fastslår om denne feilkonfigurasjonen eksisterer ved å spørre denne hendelses-IDen ved hjelp av http://support.microsoft.com,eller du kan kontakte Microsoft Kundestøtte.%n%nDen mest sannsynlige årsaken til dette problemet er ufullstendig gjenoppretting av Active Directory Lightweight Directory Services på denlokale domenekontrolleren eller den eksterne skrivebeskyttede domenekontrolleren.%n%nBrukeren har valgt å ignorere dette problemet på eget ansvar.%nBrukerhandlinger:%nHvis dette problemet oppstod på grunn av en ufullstendig eller utilsiktet gjenoppretting, senker du nivået på domenekontrolleren.%n%nUklarert klient:%n%1%nPartisjon:%n%2%nUSN rapportert av en klient som ikke er en domenekontroller:%n%3%nUSN rapportert av lokal domenekontroller:%n%4 |
During an Active Directory Lightweight Directory Services replication request, the local domain controller (DC) identifiedan untrusted client which has received replication data from the local DC using already-acknowledged USNtracking numbers. Read-only DCs and DirSync clients are examples of untrusted clients.%n%nBecause the client believes it is has a more up-to-date Active Directory Lightweight Directory Services database than thelocal DC, the client will not apply future changes to its copy of the Active Directory Lightweight Directory Servicesdatabase or replicate them to its direct and transitive replication partners that originate from thislocal DC.%n%nIf not resolved immediately, this scenario will result in inconsistencies in the Active Directory Lightweight Directory Services databasesof this source DC and one or more direct and transitive replication partners. Specifically theconsistency of users, computers and trust relationships, their passwords, security groups,security group memberships and other Active Directory Lightweight Directory Services configuration data may vary, affecting the ability to log on,find objects of interest and perform other critical operations.%n%nTo determine if this misconfiguration exists, query this event ID using http://support.microsoft.comor contact your Microsoft product support.%n%nThe most probable cause of this situation is the improper restore of Active Directory Lightweight Directory Services on thelocal domain controller or the remote Read-Only domain controller.%n%nThe user has chosen to ignore this problem at their own peril.%nUser Actions:%nIf this situation occurred because of an improper or unintended restore, forcibly demote the affected DC.%n%nUntrusted client:%n%1%nPartition:%n%2%nUSN reported by non-DC client:%n%3%nUSN reported by Local DC:%n%4 |
| 0xC0000B4A | Internal event: Active Directory Lightweight Directory Services failed to set a hint in the Kerberos client for a KDC which contains updated account information for the local domain controller.%n%nThis directory service may be unable to gain proper authorization until the Kerberos security tickets are refreshed and an appropriate KDC is contacted.%n%nAdditional Data%nError value: %n%1 %2 |
Internal event: Active Directory Lightweight Directory Services failed to set a hint in the Kerberos client for a KDC which contains updated account information for the local domain controller.%n%nThis directory service may be unable to gain proper authorization until the Kerberos security tickets are refreshed and an appropriate KDC is contacted.%n%nAdditional Data%nError value: %n%1 %2 |
| 0xC0000B4F | En klient sendte en DirSync LDAP-forespørsel for en katalogpartisjon som inkluderte attributter i detfiltrerte settet for skrivebeskyttet domenekontroller. Ingen tilgang på grunn av feilen nedenfor.%n%nKatalogpartisjon: %n%1%nFeilverdi: %n%2 %3%n%nBrukerhandling%nKlienten har kanskje ikke tilgang til disse attributtene. Hvis klienten krever at disse attributtenereturneres, må de få tilordnet kontrolltilgangsrettigheten for replikering av katalogendringer ifiltrert sett på den aktuelle katalogpartisjonen. |
A client made a DirSync LDAP request for a directory partition that included attributes in theRead-Only DC Filtered Set. Access was denied due to the following error.%n%nDirectory partition: %n%1%nError value: %n%2 %3%n%nUser Action%nThe client may not have access to these attributes. If the client requires these attributesto be returned, they should be assigned the control access right \"Replicating Directory Changesin Filtered Set\" on the directory partition in question. |
| 0xC0000B50 | En klient sendte en DirSync LDAP-forespørsel for en katalogpartisjon. Ingen tilgang på grunn av feilen nedenfor.%n%nKatalogpartisjon: %n%1%nFeilverdi: %n%2 %3%n%nBrukerhandling%nKlienten har kanskje ikke tilgang for denne forespørselen. Hvis klienten krever det, måkontrolltilgangsrettigheten for replikering av katalogendringer tilordnes på den aktuelle katalogpartisjonen. |
A client made a DirSync LDAP request for a directory partition. Access was denied due to the following error.%n%nDirectory partition: %n%1%nError value: %n%2 %3%n%nUser Action%nThe client may not have access for this request. If the client requires it, they should beassigned the control access right \"Replicating Directory Changes\" on thedirectory partition in question. |
| 0xC0000B58 | Denne hendelsen dokumenterer ekstra REPARASJONSPROSEDYRER for å løse NTDS KCC-hendelse 1311 på en skrivebeskyttet Active Directory Lightweight Directory Services-forekomst.%n%nLokalt område:%n%1%n%nBrukerhandling:%n%nBrukerhandlingen for å løse NTDS KCC-hendelse 1311 på en skrivebeskyttet Active Directory Lightweight Directory Services-forekomst er identisk med handlingsplanen som ble brukt på en skrivbar (fullstendig) Active Directory Lightweight Directory Services-forekomst med følgende tilleggskrav:%n%n1. Hvis NTDS KCC-hendelse 1789 er logget i nærheten av NTDS KCC-hendelse 1311 og NTDS KCC-hendelse 2904, bruker du det statiske utvalget for Active Directory Sites and Services med fokus på en skrivbar Active Directory Lightweight Directory Services-forekomst til å legge til dette området på en riktig områdekobling, og deretter utfører du trinn 4 og 5.%n%n2. Hendelsen 1311 har mange mulige årsaker. Kjør handlingsplanen i koblingen Event Log Online Help for en tilstøtende 1311-hendelse. Tilleggsinformasjon er kanskje tilgjengelig på http://support.microsoft.com, eller se MSKB-artikkelen på http://support.microsoft.com/default.aspx?scid=kb;NB-NO;307593.%n%n3. Alle korrigeringer som løser 1311-hendelsen, må være utført på en Active Directory Lightweight Directory Services-forekomst som er vert for en skrivbar kopi av Active Directory-partisjonen eller -gruppepolicyen som endres.%n%n4. Hvis den skrivebeskyttede Active Directory Lightweight Directory Services-forekomsten som logger 2904-/1311-hendelsen, ikke har en gyldig repsFrom-kilde for Active Directory Lightweight Directory Services-forekomsten, kjører du følgende kommando, ellers hopper du til trinn 5:%n%n [Obs! Dette trinnet krever legitimasjon for virksomhetsadministrator]%n%n repadmin /add /read-only /selsecrets%n%n5. Start replikering fra den skrivbare Active Directory Lightweight Directory Services-forekomsten som ble oppdatert i forrige trinn, til denne skrivebeskyttede Active Directory Lightweight Directory Services-forekomsten ved hjelp av følgende kommando:%n%n [Obs! Dette trinnet krever legitimasjon for virksomhetsadministrator]%n%n repadmin /replicate %n%n ELLER%n%n Alternativt kan du bruke grensesnittet for Active Directory Sites and Services ved å utføre følgende trinn:%n%n – Klikk området som har denne skrivebeskyttede Active Directory Lightweight Directory Services-forekomsten.%n – Klikk replikeringskonfigurasjonen fra/til den valgte Active Directory Lightweight Directory Services-forekomsten. |
This event documents additional REPAIR PROCEDURES to resolve the NTDS KCC Event 1311 on a read-only Active Directory Lightweight Directory Services instance.%n%nLocal Site:%n%1%n%nUser Action:%n%nThe user action for resolving the NTDS KCC event 1311 on a read-only Active Directory Lightweight Directory Services instance is identical to the action plan used on a writable (full) Active Directory Lightweight Directory Services instance with the following additional requirements:%n%n1. If NTDS KCC event 1789 is logged adjacent to the NTDS KCC 1311 and NTDS KCC 2904 events, use the Active Directory Sites and Services snap-in focused on a writable Active Directory Lightweight Directory Services instance to add this site to an appropriate site-link, then execute steps 4 and 5.%n%n2. The 1311 event has many possible causes. Execute the action plan in the \"Event Log Online Help\" link of an adjacent 1311 event. Additional information may be available on http://support.microsoft.com or referring to MSKB article http://support.microsoft.com/default.aspx?scid=kb;EN-US;307593.%n%n3. All corrective changes that resolve the 1311 event must be made on a Active Directory Lightweight Directory Services instance that hosts a writable copy of the Active Directory partition or group policy being modified.%n%n4. If the read-only Active Directory Lightweight Directory Services instance logging the 2904 / 1311 event does not have a valid \"repsFrom\" source Active Directory Lightweight Directory Services instance, run the following command, otherwise proceed to step 5:%n%n [Note: This step requires enterprise administrator credentials]%n%n repadmin /add /read-only /selsecrets%n%n5. Trigger replication from the writable Active Directory Lightweight Directory Services instance updated in previous steps to this read-only Active Directory Lightweight Directory Services instance using the following command:%n%n [Note: This step requires enterprise administrator credentials]%n%n repadmin /replicate %n%n OR%n%n Alternatively, use the Active Directory Sites and Services UI by performing the following steps:%n%n - Click the site that has this read-only Active Directory Lightweight Directory Services instance.%n - Click replicate configuration from/to the selected Active Directory Lightweight Directory Services instance. |
| 0xC0000B59 | Funksjonsnivået for partisjonen er ikke kompatibelt med dette operativsystemet. |
The functional level of the partition is incompatible with this operating system. |
| 0xC0000B5C | Funksjonsnivået for partisjonen er ikke kompatibelt med funksjonsnivået for den lokale Active Directory Lightweight Directory Services-forekomsten.%n%n funksjonsnivå for partisjon:%n%1%n Funksjonsnivå for forekomst av Active Directory Lightweight Directory Services:%n%2%nMinste kompatible funksjonsnivå:%n%3%n%nBrukerhandling%nInstaller riktig operativsystem på denne Active Directory Lightweight Directory Services-forekomsten. |
The functional level of the partition is incompatible with the functional level of the local Active Directory Lightweight Directory Services instance.%n%n partition functional level:%n%1%n Active Directory Lightweight Directory Services instance functional level:%n%2%nMinimal compatible functional level:%n%3%n%nUser Action%nInstall the correct operating system on this Active Directory Lightweight Directory Services instance. |
| 0xC0000B5F | Partisjonens funksjonsnivåer har blitt oppdatert til verdier som ikke er kompatible med funksjonsnivået som støttes av dette operativsystemet.%n%nFunksjonsnivå for ny partisjon:%n%1%nFunksjonsnivåskala for operativsystem:%n%2 til %3%n%nDet fører til at den lokale Active Directory Lightweight Directory Services-forekomsten isoleres fra partisjonen.%n%nBrukerhandling%nInstaller et operativsystem som er kompatibelt med funksjonsnivået for partisjonen på den lokale Active Directory Lightweight Directory Services-forekomsten, eller oppdater funksjonsnivået for partisjonen slik at det blir kompatibelt med funksjonsnivået som støttes av dette operativsystemet. |
The partition functional levels have been updated to values that are incompatible with the functional level supported by this operating system.%n%nNew partition functional level:%n%1%nOperating system functional level range:%n%2 to %3%n%nAs a result, the local Active Directory Lightweight Directory Services instance will be isolated from the partition.%n%nUser Action%nInstall an operating system compatible with the functional level of the partition on the local Active Directory Lightweight Directory Services instance or update the functional level of the partition to be compatible with the functional level supported by this operating system. |
| 0xC0000B60 | Funksjonsnivåene for konfigurasjonssettet har blitt oppdatert til verdier som ikke er kompatible med funksjonsnivået som støttes av dette operativsystemet.%n%nFunksjonsnivå for nytt konfigurasjonssett:%n%1%nFunksjonsnivåskala for operativsystem:%n%2 til %3%n%nDet fører til at den lokale Active Directory Lightweight Directory Services-forekomsten isoleres fra konfigurasjonssettet.%n%nBrukerhandling%nInstaller et operativsystem som er kompatibelt med funksjonsnivået for konfigurasjonssettet på den lokale Active Directory Lightweight Directory Services-forekomsten, eller oppdater funksjonsnivået for konfigurasjonssettet slik at det blir kompatibelt med funksjonsnivået som støttes av dette operativsystemet. |
The configuration set functional levels have been updated to values that are incompatible with the functional level supported by this operating system.%n%nNew configuration set functional level:%n%1%nOperating system functional level range:%n%2 to %3%n%nAs a result, the local Active Directory Lightweight Directory Services instance will be isolated from the configuration set.%n%nUser Action%nInstall an operating system compatible with the functional level of the configuration set on the local Active Directory Lightweight Directory Services instance or update the functional level of the configuration set to be compatible with the functional level supported by this operating system. |
| 0xC0000B63 | I løpet av en forespørsel om Active Directory Lightweight Directory Services-replikering mottok den lokale skrivebeskyttede domenekontrolleren (RODC) en endring i følgende attributt for følgende objekt. Attributtet for det objektet representerer funksjonsnivået for denne skrivebeskyttede domenekontrolleren. Den mottatte verdien samsvarer ikke med det riktige funksjonsnivået for denne skrivebeskyttede domenekontrolleren. Denne replikerte endringen blir ikke brukt på den lokale skrivebeskyttede domenekontrolleren, og replikering er blokkert til dette problemer er løst.%n%nDette problemet løser seg kanskje automatisk. Hvis denne feilen oppstår på nytt, kan det hende du må utføre en manuell handling.%n%nBrukerhandling%nDu løser dette problemet manuelt ved å angi det riktige funksjonsnivået for denne skrivebeskyttede domenekontrolleren til det angitte attributtet for det angitte objektet på en skrivbar domenekontroller på dette domenet. Funksjonsnivået for den skrivbare domenekontrolleren må være minst Windows Server 2008 R2.%n%n%nAttributtnavn: %n%1%nRiktig funksjonsnivå for denne skrivebeskyttede domenekontrolleren: %n%2%nDomenenavn for objekt: %n%3 |
During an Active Directory Lightweight Directory Services replication request, the local read only domain controller (RODC) received a change to the following attribute of the following object. That attribute on that object represents the functional level of this RODC. The value received does not match the correct functional level of this RODC. This replicated change will not be applied to the local RODC, and replication will be blocked until this has been corrected.%n%nThis situation may correct itself automatically. If this error is encountered again, manual intervention may be necessary.%n%nUser Action%nTo resolve this situation manually, the correct functional level of this RODC should be written to the specified attribute of the specified object on a writable DC in this domain. The functional level of that writable DC must be at least Windows Server 2008 R2.%n%n%nAttribute name: %n%1%nCorrect functional level of this RODC: %n%2%nObject DN: %n%3 |
| 0xC0000B64 | Den lokale skrivebeskyttede domenekontrolleren (RODC) forsøkte å oppdatere funksjonsnivået ved å skrive følgende verdi til følgende attributt for følgende objekt på følgende skrivbare domenekontroller. Dette forsøket mislyktes. Dette forsøket vil bli prøvd på nytt. Denne oppdateringen lykkes bare hvis funksjonsnivået for den skrivbare domenekontrolleren er minst Windows Server 2008 R2. Denne feilen oppstår på nytt til oppdateringsforsøket gjøres i forhold til en slik skrivbar domenekontroller.%nDette problemet løser seg kanskje automatisk. Hvis denne feilen oppstår på nytt, kan det hende du må utføre en manuell handling.%n%nBrukerhandling%nDu løser dette problemet manuelt ved å skrive det riktige funksjonsnivået for denne skrivebeskyttede domenekontrolleren til det angitte attributtet for det angitte objektet på en skrivbar domenekontroller på dette domenet. Funksjonsnivået for den skrivbare domenekontrolleren må være minst Windows Server 2008 R2.%n%n%nAttributtnavn: %n%1%nRiktig funksjonsnivå for denne skrivebeskyttede domenekontrolleren: %n%2%nDomenenavn for objekt: %n%3%nSkrivbart navn på domenekontroller som ble brukt i dette forsøket: %n%4 |
The local read only domain controller (RODC) attempted to update its functional level by writing the following value the following attribute of the following object on the following writable domain controller (DC). This attempt failed. This attempt will be retried. However, this update will only succeed if the functional level of the writable DC is at least Windows Server 2008 R2. This error will re-occur until the update attempt is made against such a writable DC.%nThis situation may correct itself automatically. If this error is encountered again, manual intervention may be necessary.%n%nUser Action%nTo resolve this situation manually, the correct functional level of this RODC should be written to the specified attribute of the specified object on a writable DC in this domain. The functional level of that writable DC must be at least Windows Server 2008 R2.%n%n%nAttribute name: %n%1%nCorrect functional level of this RODC: %n%2%nObject DN: %n%3%nWritable DC name used in this attempt: %n%4 |
| 0xC0000B69 | KCC (Knowledge Consistency Checker) registrerte at følgende objekt har manglende obligatoriske attributter eller attributtverdier.%nObjekt:%n%1%n%nBrukerhandling%nSjekk NTDS-innstillingsobjektet for denne DSAen. |
The Knowledge Consistency Checker (KCC) detected that the following object have missing required attributes or attribute values.%nObject:%n%1%n%nUser Action%nCheck NTDS Settings object for this DSA. |
| 0xC0000B6A | Følgende objekt som hører til den lokale domenekontrolleren, har blitt endret på feil måte på en skrivbar domenekontroller. Endringen blir ikke tatt i bruk i den lokale domenekontrollerdatabasen. Hvis den lokale domenekontrolleren er skrivbar, blir endringen tilbakeført og replikert til andre domenekontrollere. Hvis den lokale domenekontrolleren er skrivebeskyttet (RODC), blir deler av funksjonaliteten påvirket til problemet er løst. Se http://go.microsoft.com/fwlink/?LinkId=185181 hvis du vil ha mer informasjon, inkludert fremgangsmåte for å løse problemet.%nObjekt:%n%1%nAttributt:%n%2 (%3)%n |
The following object belonging to the local domain controller has been modified inappropriately on a writable domain controller. The change will not be applied to the local domain controller database. If the local domain controller is writable the change will be reversed and replicate to other domain controllers. If the local domain controller is read only (RODC) then some functionality will be affected until the problem is corrected. Please see http://go.microsoft.com/fwlink/?LinkId=185181 for more information including steps to correct the problem.%nObject:%n%1%nAttribute:%n%2 (%3)%n |
| 0xC0000B6B | Active Directory Lightweight Directory Services kan ikke analysere transformasjonsreglene som er lagret i domenenavnobjektet med feilen. Se loggfilen hvis du vil ha mer informasjon.%n%nDomenenavn for objekt: %n%1%nFeilstreng: %n%2%nLoggfil: %n%3 |
Active Directory Lightweight Directory Services failed to parse the transformation rules stored in the DN Object with the Error. For detailed error logs, refer to the log file.%n%nObject DN: %n%1%nError String: %n%2%nLog File: %n%3 |
| 0xC0000B6C | Active Directory Lightweight Directory Services kan ikke lese transformasjonsreglene som er lagret i domenenavnobjektet.%n%nDomenenavnobjekt: %n%1%nFeilverdi: %n%2 |
Active Directory Lightweight Directory Services failed to read the transformation rules stored in the DN Object.%n%nDN Object: %n%1%nError Value: %n%2 |
| 0xC0000B6D | Active Directory Lightweight Directory Services kan ikke lese TDO-koblingen. Denne koblingen bør peke til et policyobjekt for kravtransformasjon i lagringsbeholderen.%n%nDomenenavn for kobling: %n%1%nKlarert domeneobjekt: %n%2%nLagringsbeholder: %n%3 |
Active Directory Lightweight Directory Services failed to read the TDO link. This link should point to a Claims Transformation Policy Object stored in Store container.%n%nLink DN: %n%1%nTrusted Domain Object: %n%2%nStore Container: %n%3 |
| 0xC0000B70 | Active Directory Lightweight Directory Services oppdaget én eller flere feil ved behandling av Påstandstyper.Du finner sammendragsinformasjon nedenfor.%n%nBehandlede Påstandstyper: %1%n%nGyldige Påstandstyper: %2%nUgyldige Påstandstyper: %3%n%nUgyldige Påstandstyper som påvirkes av minnetildelingsfeil: %4%n%nObs!%n%n 1) Påstandstyper behandles under oppstart av Active Directory Lightweight Directory Services og under denførste loggføringen etter en endring av Påstandstype.%n%n 2) Som standard vises bare sammendrag for Påstandstypefeil.Hvis du vil ha loggført alle enkeltfeilhendelser, angir du følgende diagnostiske registerverdi til 1:%n%nRegisterbane:%nHKLM\\System\\CurrentControlSet\\Services\\NTDS\\Diagnostics\\26 Claims-Based Access Control%n |
Active Directory Lightweight Directory Services encountered one or more errors while processing Claim Types.Summary information is below.%n%nClaim Types processed: %1%n%nValid Claim Types: %2%nInvalid Claim Types: %3%n%nInvalid Claim Types affected by memory allocation failures: %4%n%nNOTES:%n%n 1) Claim Types are processed during Active Directory Lightweight Directory Services startup and duringthe first log on following any Claim Type changes.%n%n 2) By default, only Claim Type error summaries are shown.To log all individual error events, set the following diagnosticsregistry value to 1:%n%nRegistry path:%nHKLM\\System\\CurrentControlSet\\Services\\NTDS\\Diagnostics\\26 Claims-Based Access Control%n |
| 0xC0000B71 | Følgende Påstandstype er ugyldig. Ett eller flere av de nødvendige attributtene(Aktivert, msDS-ClaimAttributeSource, msDS-ClaimSourceType, msDS-ClaimValueType,navn) inneholder et verdiantall som ikke samsvarer med det forventede antallet én.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. One or more of the required attributes(Enabled, msDS-ClaimAttributeSource, msDS-ClaimSourceType, msDS-ClaimValueType,name) contain a value count which does not match the expected count of one.%n%nObject CN: %n%1%nObject GUID: %n%2 |
| 0xC0000B72 | Følgende Påstandstype er ugyldig. Ett eller flere av de nødvendige attributtene(Aktivert, msDS-ClaimSource, msDS-ClaimSourceType, msDS-ClaimValueType, navn)inneholder et verdiantall som ikke samsvarer med det forventede antallet én.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. One or more of the required attributes(Enabled, msDS-ClaimSource, msDS-ClaimSourceType, msDS-ClaimValueType, name)contain a value count which does not match the expected count of one.%n%nObject CN: %n%1%nObject GUID: %n%2 |
| 0xC0000B73 | Følgende Påstandstype er ugyldig. Det nødvendige attributtet msDS-ClaimTypeAppliesToClassmå inneholde minst én verdi.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The required msDS-ClaimTypeAppliesToClassattribute must contain at least one value.%n%nObject CN: %n%1%nObject GUID: %n%2 |
| 0xC0000B74 | Active Directory Lightweight Directory Services kan ikke behandle følgende Påstandstype. Én eller flere verdier forattributtet msDS-ClaimTypeAppliesToClass kan ikke analyseres.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
Active Directory Lightweight Directory Services failed to process the following Claim Type. One or more values of themsDS-ClaimTypeAppliesToClass attribute could not be parsed.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B75 | Følgende Påstandstype er ugyldig. Den inneholder et msDS-ClaimSourceType-attributt med en verdi som ikke støttes.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. It contains an msDS-ClaimSourceTypeattribute with an unsupported value.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B76 | Følgende Påstandstype er ugyldig. Ett eller flere av de nødvendige attributtene(Aktivert, msDS-ClaimTypeAppliesToClass, msDS-ClaimAttributeSource,msDS-ClaimSourceType, msDS-ClaimValueType, navn) mangler.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. One or more of the required attributes(Enabled, msDS-ClaimTypeAppliesToClass, msDS-ClaimAttributeSource,msDS-ClaimSourceType, msDS-ClaimValueType, name) are missing.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B77 | Følgende Påstandstype er ugyldig. Ett eller flere av de nødvendige attributtene(Aktivert, msDS-ClaimTypeAppliesToClass, msDS-ClaimSource,msDS-ClaimSourceType, msDS-ClaimValueType, navn) mangler.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. One or more of the required attributes(Enabled, msDS-ClaimTypeAppliesToClass, msDS-ClaimSource,msDS-ClaimSourceType, msDS-ClaimValueType, name) are missing.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B78 | Følgende Påstandstype er ugyldig. Attributtet msDS-ClaimSource kan ikkevære angitt hvis attributtet msDS-ClaimSourceType er angitt til verdienAD.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The msDS-ClaimSource attribute mustnot be set if the msDS-ClaimSourceType attribute is set to a valueof AD.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B79 | Følgende Påstandstype er ugyldig. Attributtet msDS-ClaimAttributeSourcekan ikke være angitt hvis attributtet msDS-ClaimSourceTypeer angitt til verdien Sertifikat.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The msDS-ClaimAttributeSourceattribute must not be set if the msDS-ClaimSourceType attributeis set to a value of Certificate.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B7A | Active Directory Lightweight Directory Services oppdaget en ukjent feil ved behandling av følgende Påstandstype.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
Active Directory Lightweight Directory Services encountered an unknown error while processing the following Claim Type.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B7B | Følgende Påstandstype er ugyldig. Attributtet msDS-ClaimAttributeSourcerefererer til et attributt som ikke replikeres.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The msDS-ClaimAttributeSourceattribute refers to an attribute which is not replicated.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B7C | Følgende Påstandstype er ugyldig. Attributtet msDS-ClaimAttributeSourcerefererer til et RODC-filtrert attributt.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The msDS-ClaimAttributeSourceattribute refers to an RODC filtered attribute.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B7D | Følgende Påstandstype er ugyldig. Attributtet msDS-ClaimAttributeSourcerefererer til et blokkert attributt (DBCS-Pwd, Lm-Pwd-History,Nt-Pwd-History, Unicode-Pwd).%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The msDS-ClaimAttributeSourceattribute refers to a blocked attribute (DBCS-Pwd, Lm-Pwd-History,Nt-Pwd-History, Unicode-Pwd).%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B7E | Følgende Påstandstype er ugyldig. Verdien til attributtetmsDS-ClaimValueType er feil.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The value of themsDS-ClaimValueType attribute is incorrect.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B7F | Følgende Påstandstype er ugyldig. Attributtet msDS-ClaimAttributeSourcerefererer til et attributt med en syntaks som ikke støttes.%n%nObjekt-CN: %n%1%nObjekt-GUID: %n%2 |
The following Claim Type is invalid. The msDS-ClaimAttributeSourceattribute refers to an attribute with an unsupported syntax.%n%nObject CN: %n%1%nObjectGUID: %n%2 |
| 0xC0000B85 | Alle kravene for den angitte brukeren ble droppet i Active Directory Lightweight Directory Services på grunn av følgende valideringsfeil.%n%nBruker: %n%1%nFeil:%n%2 |
Active Directory Lightweight Directory Services dropped all the claims of the given user because of the following validation error.%n%nUser: %n%1%nError:%n%2 |
| 0xC0000B86 | De ugyldige kravene nedenfor for brukeren ble droppet i Active Directory Lightweight Directory Services etter transformering av kravene.%n%nBruker: %n%1%nKrav: %n%2%nGå til http://go.microsoft.com/fwlink/?LinkId=285865 for mer hjelp til å feilsøke problemet. |
Active Directory Lightweight Directory Services dropped the following invalid claim[s] of the user after transforming the claims.%n%nUser: %n%1%nClaim[s]: %n%2%nPlease visit http://go.microsoft.com/fwlink/?LinkId=285865 for additional help troubleshooting the issue. |
| 0xC0000B8A | Active Directory Lightweight Directory Services kan ikke slette registernøkkelen %1 rekursivt (DeleteRoot=%2). |
Active Directory Lightweight Directory Services failed to recursively delete the %1 registry key (DeleteRoot=%2). |
| 0xC0000B8B | Active Directory Lightweight Directory Services kan ikke åpne registernøkkelen %1. |
Active Directory Lightweight Directory Services was unable to open the %1 registry key. |
| 0xC0000B8C | Active Directory Lightweight Directory Services kan ikke spørre på registernøkkelen %1. |
Active Directory Lightweight Directory Services was unable to query the %1 registry key. |
| 0xC0000B8D | Active Directory Lightweight Directory Services kan ikke nummerere registernøkkelen %1. |
Active Directory Lightweight Directory Services was unable to enumerate the %1 registry key. |
| 0xC0000B8E | Active Directory Lightweight Directory Services kan ikke slette registernøkkelen %1. |
Active Directory Lightweight Directory Services was unable to delete the %1 registry key. |
| 0xC0000B8F | Internal event: Enabling an optional feature has failed.%n%nOptional feature name:%n%1%nOptional feature guid:%n%2%nScope of optional feature:%n%3%nError value:%n%4%nInternal ID (DSID):%n%5 |
Internal event: Enabling an optional feature has failed.%n%nOptional feature name:%n%1%nOptional feature guid:%n%2%nScope of optional feature:%n%3%nError value:%n%4%nInternal ID (DSID):%n%5 |
| 0xC0000B90 | Internal event: Disabling an optional feature has failed.%n%nOptional feature name:%n%1%nOptional feature guid:%n%2%nScope of optional feature:%n%3%nError value:%n%4%nInternal ID (DSID):%n%5 |
Internal event: Disabling an optional feature has failed.%n%nOptional feature name:%n%1%nOptional feature guid:%n%2%nScope of optional feature:%n%3%nError value:%n%4%nInternal ID (DSID):%n%5 |
| 0xC0000B93 | Opprettet %2 valgfrie systemindekser av %1 nødvendige indekser.%nKan ikke opprette andre nødvendige valgfrie systemindekser.%n%nFeil: %3%nIntern ID (DSID):%4 |
Created %2 optional system indices out of %1 indices required.%nFailed to create other required optional system indices.%n%nError: %3%nInternal ID (DSID):%4 |
| 0xC0000B95 | En LDAP-operasjon overskred de administrativt konfigurerte minnegrensene og ble avvist.%nVurder å forenkle operasjonen eller heve LDAP-minnegrensene ved hjelp av LDAP-policyer.Se http://go.microsoft.com/fwlink/?LinkId=272160 hvis du vil ha mer informasjon om denne policyen. |
An LDAP operation exceeded the administratively configured memory limits and was rejected.%nConsider simplifying the operation or raising the LDAP memory limits using LDAP policies.See http://go.microsoft.com/fwlink/?LinkId=272160 for more details on this policy. |
| 0xC0000B9E | Attributtverdien som er angitt, er ikke unik i skogen eller partisjonen.Attributt: %1%2Winerror: %3%nSe http://go.microsoft.com/fwlink/?LinkID=279782 for mer informasjon om denne policyen. |
The attribute value provided is not unique in the forest or partition.Attribute: %1%2Winerror: %3%nSee http://go.microsoft.com/fwlink/?LinkID=279782 for more details on this policy. |
| 0xC0000BA2 | Standard LDAP QOS-policy er ugyldig og blir ikke tatt i bruk. msDS-LdapQosPolicyMaxCpu kan ikke være null hvis dette er standardpolicyen.Policy-ID for QOS: %1LdapQosPolicyTrigger: %2LdapQosPolicyMaxCpu: %3%n |
The default LDAP QOS policy is invalid and will not be applied. The msDS-LdapQosPolicyMaxCpu must not be zero if this is the default policy.QOS Policy ID: %1LdapQosPolicyTrigger: %2LdapQosPolicyMaxCpu: %3%n |
| 0xC0000BA3 | Oppretting i den sammensatte indeksen mislyktes.Primært attributt: %1IndexName: %2Feil: %3Intern ID (DSID): %4Databasefeil: %5%n |
Creation on the compound index failed.Primary Attribute: %1IndexName: %2Error: %3Internal ID (DSID): %4Database error: %5%n |
| 0xC0000BAE | Forsøket på å opprette en ny kolonne i koblingstabellen for følgende nye attributt mislyktes.%n%nAttributtidentifikator:%n%1%nAttributtnavn:%n%2%nTabelltype:%n%3%n%nAttributtdefinisjonen ble ignorert.%n%nTilleggsdata%nFeilverdi:%n%4 |
The attempt to create a new column in link table for the following new attribute failed.%n%nAttribute identifier:%n%1%nAttribute name:%n%2%nTable type:%n%3%n%nThe attribute definition was ignored.%n%nAdditional Data%nError value:%n%4 |
| 0xC0000BB1 | Oppretting av en dirsync-indeks mislyktes.IndexName: %1Feil: %2Intern ID (DSID): %3Database feil: %4%n |
Creation of a dirsync index failed.IndexName: %1Error: %2Internal ID (DSID): %3Database error: %4%n |
| 0xC0000BB3 | Antall DirSyncSet-attributter overskrider den tillatte grensen%n%nmaks.grense: %n%1%nDette gjør at DirSyncSet-funksjonen ikke fungerer som den skal. Fjern alle DirSyncSet-attributter, start på nytt og tilbakestille dem med DirSyncSet-funksjonen aktivert. |
The number of DirSyncSet attributes exceeds the maxinum limit%n%nmaxinum limit: %n%1%nThe DirSyncSet feature would not work properly. Please clear all the DirSyncSet attributes, reboot and reset them with DirSyncSet feature enabled. |
| 0xC0000BB5 | Det har oppstått en navngivningskontekst med en ugyldig referanse. %n%nunikt navn for navngivningskontekst:%1%nintern kode for navngivningskontekst:%2%n%nDette problemet kan føre til enkelte feil under opplisting av sikkerhetskontohavere i denne navngivningskonteksten. |
A naming context with an invalid Naming Context Handle has been detected. %n%nnaming context distinguished name:%1%nnaming context internal tag:%2%n%nThis condition may cause some failures enumerating security principals in this naming context. |
| 0xC0002710 | Databaseoperasjonen var vellykket. |
The database operation was successful. |
| 0xC0002711 | Databaseoperasjonen var mislykket. |
The database operation failed. |
| 0xC0002712 | Databaseoperasjonen kunne ikke plasseres i objektet som kreves for å starte søkeoperasjonen. |
The database operation failed to position on the object needed to restart the search operation. |
| 0xC0002713 | Databaseoperasjonen fant ikke en annen kandidat for søkeoperasjonen. |
The database operation failed to find another candidate for the search operation. |
| 0xC0002714 | Databaseoperasjonen mislyktes fordi resultatene ikke kunne sorteres. |
The database operation failed because the results could not be sorted. |
| 0xC0002715 | Databaseoperasjonen ble avsluttet fordi tidsgrensen er nådd. |
The database operation terminated because the time limit has been reached. |
| 0xC0002716 | Databaseoperasjonen mislyktes fordi attributtet ikke har noen verdier. |
The database operation failed because the attribute has no values. |
| 0xC0002717 | Databaseoperasjonen mislyktes fordi bufferen er for liten. |
The database operation failed because the buffer is too small. |
| 0xC0002719 | Verdien som er returnert av denne databaseoperasjonen, er avkortet. |
The value returned by this database operation has been truncated. |
| 0xC000271A | Databaseoperasjonen mislyktes fordi attributtet allerede finnes. |
The database operation failed because the attribute already exists. |
| 0xC000271B | Databaseoperasjonen mislyktes fordi attributtet ikke finnes. |
The database operation failed because the attribute does not exist. |
| 0xC000271C | Databaseoperasjonen mislyktes fordi verdien allerede finnes. |
The database operation failed because the value already exists. |
| 0xC000271D | Databaseoperasjonen mislyktes fordi syntakskonverteringen ikke kunne utføres. |
The database operation failed because the syntax conversion could not be performed. |
| 0xC000271E | Databaseoperasjonen er ikke tillatt i attributter for tilbakekobling. |
The database operation is not allowed on back link attributes. |
| 0xC000271F | Databaseoperasjonen mislyktes fordi verdien ikke finnes. |
The database operation failed because the value does not exist. |
| 0xC0002720 | Databaseoperasjonen mislyktes fordi det ikke er flere overføringer igjen for utføring. |
The database operation failed because there are no more propagations left to be performed. |
| 0xC0002722 | Databaseoperasjonen mislyktes fordi slettetiden ikke ble funnet. |
The database operation failed because the deletion time could not be found. |
| 0xC0002723 | Databaseoperasjonen kan ikke fastsette det unike navnet som er knyttet til en post. |
The database operation failed to determine the distinguished name associated with a record. |
| 0xC0002724 | Databaseoperasjonen fant ikke flere slettede poster. |
The database operation failed to find any more deleted records. |
| 0xC0002725 | Databaseoperasjonen kan ikke opprette en sorteringstabell. |
The database operation failed to create a sort table. |
| 0xC0002726 | Filteret for denne databaseoperasjonen kan ikke optimaliseres. |
The filter for this database operation cannot be optimized. |
| 0xC0002727 | Databaseoperasjonen fant ikke indeksen. |
The database operation failed to find the index. |
| 0xC0002729 | Databaseoperasjonen overskred det maksimale antallet oppføringer som kan sorteres. |
The database operation exceeded the maximum number of entries that can be sorted. |
| 0xC000272B | Databaseoperasjonen kan ikke utføres på attributter med denne syntaksen. |
The database operation cannot be performed on attributes with this syntax. |
| 0xC000272D | Databasemarkøren er ikke plassert i riktig verdi. |
The database cursor is not positioned on the correct value. |
| 0xC000272E | Databaseoperasjonen kan bare utføres på koblede attributter. |
The database operation can be performed only on linked attributes. |
| 0xC000272F | Databaseoperasjonen mislyktes med et uventet unntak. |
The database operation failed with an unexpected exception. |
| 0xC0002730 | Databaseoperasjonen mislyktes fordi Active Directory Lightweight Directory Services-forekomsten avsluttes. |
The database operation failed because the Active Directory Lightweight Directory Services instance is shutting down. |
| 0xC0002731 | Databaseoperasjonen mislyktes på grunn av en skrivekonflikt. |
The database operation failed because of a write conflict. |
| 0xC0002732 | Operasjonen for virtuell listevisning for databasen mislyktes. |
The database virtual list view operation failed. |
| 0xC0002733 | Posten databaseoperasjonen fant, er ikke et objekt. |
The record encountered by this database operation is not an object. |
| 0xC0002734 | Databaseoperasjonen mislyktes fordi det allerede finnes en post med denne nøkkelen. |
The database operation failed because a record with this key already exists. |
| 0xC0002735 | Databaseoperasjonen mislyktes fordi databasemarkøren ikke er plassert i en post. |
The database operation failed because the database cursor is not positioned on a record. |
| 0xC0002736 | Databaseoperasjonen mislyktes fordi posten ikke ble funnet. |
The database operation failed because the record could not be found. |