I am restoring my current Small Business Server 2000 to a test system so I
can test a migraton to SBS 2003. The restore worked fantastic except for one
small problem. I can't log into the domain from workstations, or create
objects in Active Directory. I receive the error when I try to create an
object in Active Directory.

Active Directory
Windows cannot create the object because:
The Directory Service was unable to allocate a relative identifier.

I have also listed the Event Log errors I am getting.

I am receiving SAM 16650 errors in my System Event Log as follows:
Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 16650
Date: 11/02/2004
Time: 8:01:57 AM
User: N/A
Computer: THOMAS
Description:
The account-identifier allocator failed to initialize properly.
The record data contains the NT error code that caused the failure.
Windows 2000 will retry the initialization until it succeeds; until that
time,
account creation will be denied on this Domain Controller. Please look for
other SAM event logs that may indicate the exact reason for the failure.

I am also receiveing NETLOGON error 5723 when I try to log into a connected
workstation as follows.:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5723
Date: 11/02/2004
Time: 7:56:22 AM
User: N/A
Computer: THOMAS
Description:
The session setup from the computer NE008 failed because there is no trust
account in the security database for this computer. The name of the account
referenced in the security database is NE008$.

I have checked the fsmo roles and they are all set to Thomas (listed below),
which is the restored server. I am not sure what to do and have found
limited information. I did have a backup domain controller in the live
system that is not in the test system and wonder if that mught be where the
problem lies.

tdsutil: roles
fsmo maintenance: Connections
server connections: Connect to server Thomas
Binding to Thomas ...
Connected to Thomas using credentials of locally logged on user
server connections: Quit
fsmo maintenance: select Operation Target
select operation target: List roles for connected server
Server "Thomas" knows about 5 roles
Schema - CN=NTDS
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
ration,DC=NE
Domain - CN=NTDS
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
ration,DC=NE
PDC - CN=NTDS
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
ration,DC=NE
RID - CN=NTDS
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
ration,DC=NE
Infrastructure - CN=NTDS
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
ration,DC=NE
select operation target: Quit
fsmo maintenance: Quit
ntdsutil: Quit
Disconnecting from Thomas ...

Any help would be greatly appreciated.

See your other post in microsoft.public.windows.server.active_directory

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

"Amanda" skrev i meddelandet
news:uvF$oYL8DHA.2736@TK2MSFTNGP10.phx.gbl...
> I am restoring my current Small Business Server 2000 to a test system so I
> can test a migraton to SBS 2003. The restore worked fantastic except for
one
> small problem. I can't log into the domain from workstations, or create
> objects in Active Directory. I receive the error when I try to create an
> object in Active Directory.
>
> Active Directory
> Windows cannot create the object because:
> The Directory Service was unable to allocate a relative identifier.
>
> I have also listed the Event Log errors I am getting.
>
> I am receiving SAM 16650 errors in my System Event Log as follows:
> Event Type: Error
> Event Source: SAM
> Event Category: None
> Event ID: 16650
> Date: 11/02/2004
> Time: 8:01:57 AM
> User: N/A
> Computer: THOMAS
> Description:
> The account-identifier allocator failed to initialize properly.
> The record data contains the NT error code that caused the failure.
> Windows 2000 will retry the initialization until it succeeds; until that
> time,
> account creation will be denied on this Domain Controller. Please look
for
> other SAM event logs that may indicate the exact reason for the failure.
>
> I am also receiveing NETLOGON error 5723 when I try to log into a
connected
> workstation as follows.:
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5723
> Date: 11/02/2004
> Time: 7:56:22 AM
> User: N/A
> Computer: THOMAS
> Description:
> The session setup from the computer NE008 failed because there is no trust
> account in the security database for this computer. The name of the
account
> referenced in the security database is NE008$.
>
> I have checked the fsmo roles and they are all set to Thomas (listed
below),
> which is the restored server. I am not sure what to do and have found
> limited information. I did have a backup domain controller in the live
> system that is not in the test system and wonder if that mught be where
the
> problem lies.
>
> tdsutil: roles
> fsmo maintenance: Connections
> server connections: Connect to server Thomas
> Binding to Thomas ...
> Connected to Thomas using credentials of locally logged on user
> server connections: Quit
> fsmo maintenance: select Operation Target
> select operation target: List roles for connected server
> Server "Thomas" knows about 5 roles
> Schema - CN=NTDS
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> ration,DC=NE
> Domain - CN=NTDS
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> ration,DC=NE
> PDC - CN=NTDS
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> ration,DC=NE
> RID - CN=NTDS
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> ration,DC=NE
> Infrastructure - CN=NTDS
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> ration,DC=NE
> select operation target: Quit
> fsmo maintenance: Quit
> ntdsutil: Quit
> Disconnecting from Thomas ...
>
> Any help would be greatly appreciated.
>
>
>

I have done that and had the restored server come up as the Role Owner for
all roles. I have also ran:

Netdom Query /d:NE FSMO and had all roles come up as Thomas (recovered
server)
ntdsutil fsmo maintenance - listed below comes up with the right DC
Dcdiag also passes with all roles for Thomas.

I am at a loss.

"Chriss3" wrote in message
news:#zYQqiL8DHA.2524@TK2MSFTNGP11.phx.gbl...
> See your other post in microsoft.public.windows.server.active_directory
>
> --
> Regards,
>
> Christoffer Andersson
> No email replies please - reply in the newsgroup
> If the information was help full, you can let me know at:
> http://www.itsystem.se/employers.asp?ID=1
>
> "Amanda" skrev i meddelandet
> news:uvF$oYL8DHA.2736@TK2MSFTNGP10.phx.gbl...
> > I am restoring my current Small Business Server 2000 to a test system so
I
> > can test a migraton to SBS 2003. The restore worked fantastic except for
> one
> > small problem. I can't log into the domain from workstations, or create
> > objects in Active Directory. I receive the error when I try to create an
> > object in Active Directory.
> >
> > Active Directory
> > Windows cannot create the object because:
> > The Directory Service was unable to allocate a relative identifier.
> >
> > I have also listed the Event Log errors I am getting.
> >
> > I am receiving SAM 16650 errors in my System Event Log as follows:
> > Event Type: Error
> > Event Source: SAM
> > Event Category: None
> > Event ID: 16650
> > Date: 11/02/2004
> > Time: 8:01:57 AM
> > User: N/A
> > Computer: THOMAS
> > Description:
> > The account-identifier allocator failed to initialize properly.
> > The record data contains the NT error code that caused the failure.
> > Windows 2000 will retry the initialization until it succeeds; until that
> > time,
> > account creation will be denied on this Domain Controller. Please look
> for
> > other SAM event logs that may indicate the exact reason for the failure.
> >
> > I am also receiveing NETLOGON error 5723 when I try to log into a
> connected
> > workstation as follows.:
> > Event Type: Error
> > Event Source: NETLOGON
> > Event Category: None
> > Event ID: 5723
> > Date: 11/02/2004
> > Time: 7:56:22 AM
> > User: N/A
> > Computer: THOMAS
> > Description:
> > The session setup from the computer NE008 failed because there is no
trust
> > account in the security database for this computer. The name of the
> account
> > referenced in the security database is NE008$.
> >
> > I have checked the fsmo roles and they are all set to Thomas (listed
> below),
> > which is the restored server. I am not sure what to do and have found
> > limited information. I did have a backup domain controller in the live
> > system that is not in the test system and wonder if that mught be where
> the
> > problem lies.
> >
> > tdsutil: roles
> > fsmo maintenance: Connections
> > server connections: Connect to server Thomas
> > Binding to Thomas ...
> > Connected to Thomas using credentials of locally logged on user
> > server connections: Quit
> > fsmo maintenance: select Operation Target
> > select operation target: List roles for connected server
> > Server "Thomas" knows about 5 roles
> > Schema - CN=NTDS
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > ration,DC=NE
> > Domain - CN=NTDS
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > ration,DC=NE
> > PDC - CN=NTDS
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > ration,DC=NE
> > RID - CN=NTDS
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > ration,DC=NE
> > Infrastructure - CN=NTDS
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > ration,DC=NE
> > select operation target: Quit
> > fsmo maintenance: Quit
> > ntdsutil: Quit
> > Disconnecting from Thomas ...
> >
> > Any help would be greatly appreciated.
> >
> >
> >
>
>

Hi Amanda! Sorry I'm also lost here. Is there any thing in the event log you
can find related to this, Post Warnings and Errors in the Directory Service
Log

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

"Amanda" skrev i meddelandet
news:ub6xSAM8DHA.1816@TK2MSFTNGP12.phx.gbl...
> I have done that and had the restored server come up as the Role Owner for
> all roles. I have also ran:
>
> Netdom Query /d:NE FSMO and had all roles come up as Thomas (recovered
> server)
> ntdsutil fsmo maintenance - listed below comes up with the right DC
> Dcdiag also passes with all roles for Thomas.
>
> I am at a loss.
>
> "Chriss3" wrote in message
> news:#zYQqiL8DHA.2524@TK2MSFTNGP11.phx.gbl...
> > See your other post in microsoft.public.windows.server.active_directory
> >
> > --
> > Regards,
> >
> > Christoffer Andersson
> > No email replies please - reply in the newsgroup
> > If the information was help full, you can let me know at:
> > http://www.itsystem.se/employers.asp?ID=1
> >
> > "Amanda" skrev i meddelandet
> > news:uvF$oYL8DHA.2736@TK2MSFTNGP10.phx.gbl...
> > > I am restoring my current Small Business Server 2000 to a test system
so
> I
> > > can test a migraton to SBS 2003. The restore worked fantastic except
for
> > one
> > > small problem. I can't log into the domain from workstations, or
create
> > > objects in Active Directory. I receive the error when I try to create
an
> > > object in Active Directory.
> > >
> > > Active Directory
> > > Windows cannot create the object because:
> > > The Directory Service was unable to allocate a relative identifier.
> > >
> > > I have also listed the Event Log errors I am getting.
> > >
> > > I am receiving SAM 16650 errors in my System Event Log as follows:
> > > Event Type: Error
> > > Event Source: SAM
> > > Event Category: None
> > > Event ID: 16650
> > > Date: 11/02/2004
> > > Time: 8:01:57 AM
> > > User: N/A
> > > Computer: THOMAS
> > > Description:
> > > The account-identifier allocator failed to initialize properly.
> > > The record data contains the NT error code that caused the failure.
> > > Windows 2000 will retry the initialization until it succeeds; until
that
> > > time,
> > > account creation will be denied on this Domain Controller. Please
look
> > for
> > > other SAM event logs that may indicate the exact reason for the
failure.
> > >
> > > I am also receiveing NETLOGON error 5723 when I try to log into a
> > connected
> > > workstation as follows.:
> > > Event Type: Error
> > > Event Source: NETLOGON
> > > Event Category: None
> > > Event ID: 5723
> > > Date: 11/02/2004
> > > Time: 7:56:22 AM
> > > User: N/A
> > > Computer: THOMAS
> > > Description:
> > > The session setup from the computer NE008 failed because there is no
> trust
> > > account in the security database for this computer. The name of the
> > account
> > > referenced in the security database is NE008$.
> > >
> > > I have checked the fsmo roles and they are all set to Thomas (listed
> > below),
> > > which is the restored server. I am not sure what to do and have found
> > > limited information. I did have a backup domain controller in the live
> > > system that is not in the test system and wonder if that mught be
where
> > the
> > > problem lies.
> > >
> > > tdsutil: roles
> > > fsmo maintenance: Connections
> > > server connections: Connect to server Thomas
> > > Binding to Thomas ...
> > > Connected to Thomas using credentials of locally logged on user
> > > server connections: Quit
> > > fsmo maintenance: select Operation Target
> > > select operation target: List roles for connected server
> > > Server "Thomas" knows about 5 roles
> > > Schema - CN=NTDS
> > >
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > > ration,DC=NE
> > > Domain - CN=NTDS
> > >
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > > ration,DC=NE
> > > PDC - CN=NTDS
> > >
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > > ration,DC=NE
> > > RID - CN=NTDS
> > >
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > > ration,DC=NE
> > > Infrastructure - CN=NTDS
> > >
> >
>
Settings,CN=THOMAS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu
> > > ration,DC=NE
> > > select operation target: Quit
> > > fsmo maintenance: Quit
> > > ntdsutil: Quit
> > > Disconnecting from Thomas ...
> > >
> > > Any help would be greatly appreciated.
> > >
> > >
> > >
> >
> >
>
>