I found the following posting that describes the exact error although there
was no answer. It just started working for him. Evidently SP4 is not the
culprit as his problem was back in February '03. See below!
_______________________________________________________________
I can't explain it.
I came in this morning and decided to try the Migration Wizard again. You
know, just to get my bearings straight, so to speak. The fool thing decided
to work! Now the first time this morning, it got past the point where I got
the "endpoint mapper" error before, but the actual migration process stopped
prematurely because (according to the log file) a previous relationship
existed between the servers other than <Domain>\Administrator.
I don't know how that could be, but I restarted the Target server just to be
sure. Re-ran the ADMT User Migration Wizard, and it worked with nary a
complaint!
I'm not knocking the results, mind you, but it always leaves me wanting when
I can't explain away a problem like this.
Thanks again for the assist, Caleb.
Mike Finn
=================================
"Calebb [MS]" <(E-Mail Removed)> wrote in message
news:OxyOmfF2CHA.1628@TK2MSFTNGP10...
> An extra config check is run when sidHistory is migrated, it looks like
this
> is failing. By not migrating sidHistory you skip the config check.
>
> You could try the migration from the command line in case it is just a
> problem in the wizard, but I doubt it.
> admt user /sd:<src> /td:<trg> /mss:yes /to:users /testmigration:yes
> /n:<userName>
>
> also you can try sidhist.vbs from the win2000 reskit to try just a
> sidHistory migration. It will call the same underlying api that admt does
> to migrate the sidHistory, so I would expect the same result, but it would
> confirm if it is an ADMT problem or a problem that the underlying api is
> encountering.
>
> thanks
>
> --
>
> Caleb Baker
> Microsoft
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> ____________________________
> "Michael Finn" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> > It's Microsoft NT4 Server w/ SP6a: Windows NT ver. 4.00.1381
> > Same server also has Exchange Server 5.5 running on it. (Exchange 2000
> > migration is pending domain migration.)
> >
> > <scratching_head>
> > As additional info, if I do *not* select the "Migrate SID History"
> checkbox
> > in ADMT, I don't get the endpoints error message. (Found this out using
> the
> > "test" option -- haven't tried the actual migration until I get a
> successful
> > test!)
> > </scratching_head>
> >
> >
> > "Calebb [MS]" <(E-Mail Removed)> wrote in message
> > news:e9Gb1qE2CHA.2076@TK2MSFTNGP10...
> > > HI,
> > > I've been trying to reproduce this failure, but no luck. What SP are
> you
> > > running on your NT4 PDC?
> > >
> > > --
> > >
> > > Caleb Baker
> > > Microsoft
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > >
> > > ____________________________
> > > "Michael Finn" <(E-Mail Removed)> wrote in message
> > > news:uk45O5C2CHA.2912@TK2MSFTNGP10...
> > > > Good thoughts... I checked RPC services on both servers (Started)
and
> > > Event
> > > > Log has no RCP messages. I earlier had got a message that the NT4
PDC
> > had
> > > > not been rebooted after changing the reg. key, so I rebooted it (and
> > > checked
> > > > RPC, etc). That's when the endpoints error message popped up.
> > > >
> > > > The Password Export Server installation got to the "Welcome to
> Password
> > > > Migration DLL Wizard" screen, and I hit Next.
> > > > After a moment or two, msiexec.exe triggered Dr. Watson "An
> application
> > > > error has occurred".
> > > > "Installation ended prematurely because of an error."
> > > > The DRWTSN32.LOG file shows nothing.
> > > >
> > > > I made sure the MSI / Windows Installer is up to date (even used the
> > > > Instmsiw.exe in the PwdMig directory). If it matters, I'm using the
> > ADMT
> > > > installer on TechNet Windows .NET Standard Server RC1 CD dated Sept.
> > 2002.
> > > > I tried starting from pwdmig.exe; I tried starting from
pwdmig.msi --
> > same
> > > > failure results. In the interest of time, I decided the ~100 users
> > could
> > > > reset their own passwords and tried to move on, but then the
endpoints
> > > > error... :-/
> > > >
> > > > Other ideas?
> > > >
> > > > "Calebb [MS]" <(E-Mail Removed)> wrote:
> > > > > Hi Michael,
> > > > >
> > > > > The error you are seeing is usually generated if a client attempts
> to
> > > > > connect to a RPC server that hasn't started. I'd recommend
checking
> > the
> > > > > state of the rpc service on your source pdc (also check the
eventlog
> > for
> > > > any
> > > > > rpc errors). It is also possible the nt4 pdc was not rebooted
after
> > > > making
> > > > > the tcpipClientSupport registry change.
> > > > > Also I'm curious, what was the failure you got when you tried to
> > install
> > > > the
> > > > > password export server?
> > > > >
> > > > > --
> > > > >
> > > > > Caleb Baker
> > > > > Microsoft
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > >
> > > > >
> > > > > ____________________________
> > > > > "Michael Finn" <(E-Mail Removed)> wrote in message
> > > > > news:#JP#0m51CHA.1632@TK2MSFTNGP12...
> > > > > > So, I'm trying to migrate user accounts from an NT4 domain to a
> new,
> > > > > native
> > > > > > W2K AD native domain on a separate server (There were issues
with
> > > > > upgrading
> > > > > > in place). I've gone through all the Q article and MS Help file
> > > > > > specifications to set up the Active Directory Migration Tool
> > transfer
> > > > > > (domain trusts, Domain Admin rights, registry keys, etc.).
> > > > > > First, the Password Export Server install failed on the NT4
> server.
> > > No
> > > > > > problem, I'll just have the users change passwords after
> migration.
> > > > > >
> > > > > > Now, I'm logged on to the W2K server as
<newDomain>\Administrator.
> > > When
> > > > I
> > > > > > use the User Account Migration Wizard, and choose to Migrate
user
> > SIDs
> > > > to
> > > > > > target domain, the next screen asks for userid/password/domain
> info
> > > for
> > > > a
> > > > > > source domain account with administrative rights. I've tried
both
> > the
> > > > > > <newDomain>\Administrator and <sourceDomain>\Administrator
> > > credentials,
> > > > > and
> > > > > > both ways I get the following error: "There are no more
endpoints
> > > > > available
> > > > > > from the endpoint mapper. (Error code=6d9)" and it refuses to
go
> > on.
> > > > > > Without those SIDs, this process is kinda pointless.
> > > > > >
> > > > > > Please tell me someone out there has an idea how to get past
this?
> > > > > >
> > > > > > Sincerely,
> > > > > > Michael Finn
> > > > > > MinerCorp.com Administrator
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
__________________________________________________________________
"Fred Yarbrough" <(E-Mail Removed)> wrote in message
news:ux1B4%(E-Mail Removed)...
> We are having a problem with using the ADMT 2.0 utility and migrating user
> accounts with the SID attached. The ADMT wizard steps us through
selecting
> the options and then simply hangs upon submitting the screen when you must
> enter the account information for the source domain username, password,
and
> domain. This has worked perfectly in the past and we are using the
correct
> usernames and passwords. They are the same with only the domain names
being
> different. All other aspects work fine, just this SID history part hangs
up
> the ADMT. I am not seeing any errors or log file entries. We are running
> the ADMT 2.0 utility on one of our Native AD domain DC's and the actual
> account exists on our Windows NT 4.0 SP6a domain. If I run the User
> Migration wizard without selecting the Migrate user SID option, it works
> just fine.
>
> Any Ideas?
>
>
> Thanks,
> Fred
>
>
>
Similar Threads
