none
the directory service has exhausted the pool of relative identifiers RRS feed

  • Domanda

  • Buonasera,

    in azienda ho un Windows Server 2008r2 che funge da server di dominio e DNS e un Windows Server 2003r2 che funge principalmente da File server.

    Ultimamente riscontro il seguente problema

    quando cerco di creare un nuovo utente in Windows Server 2003 mi spunta il seguente messaggio di errore: "the directory service has exhausted the pool of relative identifiers" e inoltre l'accesso alle risorse di rete condivise risulta quasi impossibile perchè bloccato.

    Potete aiutarmi?
    Grazie

    mercoledì 12 luglio 2017 18:02

Risposte

Tutte le risposte

  • Ciao, scusa ma se hai una AD perchè crei degli utenti locali sul 2003? non capisco. gli utenti li creerai sul 2008 da utenti e computers di AD no? non devi mica farli locali!

    ciao!

    A.

    mercoledì 12 luglio 2017 19:57
    Moderatore
  • Da quello che capisco sono entrambi domain controller o sbaglio?

    Leggendo un po' di doc Per questo problema si presenta con qualche vecchio DC rimosso non corretamente

    https://community.spiceworks.com/topic/359076-the-directory-service-has-exhausted-the-pool-of-relative-identifiers

    C'è qualcosa che non va nella tua active directory, riporta gli errori che trovi nell'event viewer


    Gastone Canali >http://www.armadillo.it


    Se alcuni post rispondono al tuo quesito(non necessariamente i miei), ricorda di contrassegnarli come risposta e non dimenticare di contrassegnare anche i post utili. GRAZIE! Ricorda di dare un occhio ai link Click Here andHere

    giovedì 13 luglio 2017 00:43
    Moderatore
  • Mi sono espresso male.

    Il WinServer 2008 e il WinServer2003 hanno ad separati, sono scollegati fra loro.

    Sul 2003 le utenze le creo da AD utenti e computers. Adesso però non posso perchè ho esaurito il pool.

    Praticamente il rid master non riesce ad allocare il pool a se stesso

    se eseguo dcdiag /v /test:ridmanager ottengo

    Domain Controller Diagnosis

    Performing initial setup:
       * Verifying that the local machine autodialer, is a DC.
       * Connecting to directory service on server autodialer.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 1 of them.
       Done gathering initial info.

    Doing initial required tests

       Testing server: Default-First-Site-Name\AUTODIALER
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... AUTODIALER passed test Connectivity

    Doing primary tests

       Testing server: Default-First-Site-Name\AUTODIALER
          Test omitted by user request: Replications
          Test omitted by user request: Topology
          Test omitted by user request: CutoffServers
          Test omitted by user request: NCSecDesc
          Test omitted by user request: NetLogons
          Test omitted by user request: Advertising
          Test omitted by user request: KnowsOfRoleHolders
          Starting test: RidManager
             * Available RID Pool for the Domain is 2664 to 1073741823
             * autodialer.verbalcc.local is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 1664 to 2163
             * rIDPreviousAllocationPool is 1664 to 2163
             * rIDNextRID: 2163
             * Warning :Next rid pool not allocated
             * Warning :There is less than 0% available RIDs in the current pool
             ......................... AUTODIALER passed test RidManager
          Test omitted by user request: MachineAccount
          Test omitted by user request: Services
          Test omitted by user request: OutboundSecureChannels
          Test omitted by user request: ObjectsReplicated
          Test omitted by user request: frssysvol
          Test omitted by user request: frsevent
          Test omitted by user request: kccevent
          Test omitted by user request: systemlog
          Test omitted by user request: VerifyReplicas
          Test omitted by user request: VerifyReferences
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: CheckSecurityError

       Running partition tests on : ForestDnsZones
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom

       Running partition tests on : DomainDnsZones
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom

       Running partition tests on : Schema
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom

       Running partition tests on : Configuration
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom

       Running partition tests on : verbalcc
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom

       Running enterprise tests on : verbalcc.local
          Test omitted by user request: Intersite
          Test omitted by user request: FsmoCheck
          Test omitted by user request: DNS
          Test omitted by user request: DNS

    venerdì 14 luglio 2017 13:46
  • vedi qui:

    hi I solve this problem raising the rid pooll, editig the ridManager$ object with LDP.exe !
    More details at this link:

    http://blogs.dirteam.com/blogs/jorge...12/09/255.aspx

    ref: https://www.petri.com/forums/forum/server-operating-systems/windows-server-2000-2003-2003-r2/10880-rid-pool


    Edoardo Benussi
    Microsoft MVP - Cloud and Datacenter Management
    edo[at]mvps[dot]org

    martedì 18 luglio 2017 16:02
    Moderatore