Re: Name reference invalid
- From: Peter Lillington <NospamTemp014@xxxxxxxxxxxxx>
- Date: Thu, 11 Sep 2008 17:31:01 -0700
Answers to your questions inline below:
Thanks,
Peter
PS As an update - It appears the only accounts affected were those I
targeted with AD Modify .NET (v2), bulk changing the description field to
read (say) "newtext %'description'" - so for example changing a description
of "oldtext" to read "newtext oldtext". Other accounts without a preexisting
description were modified with AD Modify and do not exhibit this behaviour.
In another word, bizarre!
"Ace Fekay [MVP Direcrtory Services]" wrote:
In news:04A3D398-F766-4C3D-ADB0-1070A221AD9D@xxxxxxxxxxxxx,
Peter Lillington <NospamTemp014@xxxxxxxxxxxxx> requesting assistance, typed
the following:
I have a problem in copying (cloning) a user in ADUC - when doing so
I get an error message 'Windows cannot create the object because the
name reference is invalid.' Creating a new user is fine, cloning
from that new user, also fine.
The error messages started to occur after we moved the users to
another OU and used AD Modify to bulk change the description field.
I'm having no luck tracing the message other than the error is
errer_dc_name_reference_invalid. This leads to questions such as what
reference, and why is it invalid? Google is not much help.
Any advice appreciated.
I am assume you have one domain in this forest with two DCs.
One forest, one domain, approximately 15 DCs. Windows 2000 (unfortunately)
Native mode.
I assume the following you posted: "errer_dc_name_reference_invalid," you
actually mean "error_dc_name_reference_invalid" or was it something else?
As you say, that was meant to be error.
Did it provide the DC name in that error string? This error kind of hints at
AD problems may exist, especially if it's happening on one DC and not the
other. Many things can contribute to this such as DNS misconfig, multiple
NICs on a DC, single label name, a GC that is not reachable, and numerous
other things. To better assist, we'll need additional information to help.
No specific DC was mentioned.
To better assist, can you post responses for the following questions,
please?
1. Are there any errors in either DC's event logs? Please post any and all
errors from any of the logs (EventID# and Source Name).
Only event errors are related to some sites that are transitorily out of
communication, KCC 1566 and 1311.
2. What operating system version and service pack level are your DCs?
W2K SP4
3. What are the Forest and Domain Functional Levels set to?
Native
4. Is Exchange installed?
No
5. Were there any recent problems prior to adding the new DC?
No new DCs (see comments above), no problems that would be relevant to this
issue.
6. Which DCs hold each Role? Please specify which DC holds the PDC Emulator,
Infrastructure Master, Domain Name Master, Schema Master and RID Master.
Two hub DCs sharing the roles, forest roles on one DC, domain roles on the
other
7. Are both DCs GCs? (note, a GC is not a role, but rather an AD service)
The DC holding the IM role is not a GC as per best practice.
8. Please also post an unedited ipconfig /all from both DCs. This will help
us understand your AD infrastructure configuration (no matter how small or
large) and will help coorelate any possible misconfiguration that may
contribute to this error.
As a consultant working for another company, I would need to verify that
this info is releasable. However, this appears to be an internal AD problem,
network connectivity is not an issue (bar the transitiory issue mentioned
earlier).
.
Thank you,
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
Infinite Diversities in Infinite Combinations
- Follow-Ups:
- Re: Name reference invalid
- From: Ace Fekay [MVP Direcrtory Services]
- Re: Name reference invalid
- References:
- Name reference invalid
- From: Peter Lillington
- Re: Name reference invalid
- From: Ace Fekay [MVP Direcrtory Services]
- Name reference invalid
- Prev by Date: Re: FQDN cannot be managed because it is not running Windows NT
- Next by Date: Re: Windows restore
- Previous by thread: Re: Name reference invalid
- Next by thread: Re: Name reference invalid
- Index(es):
Relevant Pages
|
Loading