Import DHCP leases fails.


hello,

i'm trying migrate dhcp 2008 r2 new server 2012 dhcp server.

i'm following steps in following teamdhcp article.

http://blogs.technet.com/b/teamdhcp/archive/2012/09/11/migrating-existing-dhcp-server-deployment-to-windows-server-2012-dhcp-failover.aspx

the problem i'm having import of existing leases.

once config , leases exported current server, i'm running running following command import server config, , 1 of scopes initially:

import-dhcpserver –computername <new dhcp server> -leases –file c:\dhcp\export\dhcpexp.xml -backuppath c:\dhcp\backup\ -verbose -scopeid 10.3.37.0

the command imports data successfully, including reservations, not import active leases.

the following error returned upon attempting import each active lease.

import-dhcpserver : failed add ip address lease 10.3.37.x on server <servername>. : the

remote procedure call failed. (1726)

at line:1 char:1
+ import-dhcpserver -computername <servername> -leases -fil ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + categoryinfo          : notspecified: (10.3.37.11:root/microsoft/...cpserverv4lease) [import-dhcpserver], cimexc
   eption
    + fullyqualifiederrorid : win32 1726,import-dhcpserver
import-dhcpserver : failed add ip address lease 10.3.37.12 on server <servername> :
there no more endpoints available endpoint mapper. (1753)

the error occurs when new dhcp authorised or unauthorised, bindings enabled or disabled.

i've left server authorised , ensured dhcp server object has replicated throughout forest, , present in adsiedit, , tried scope import again. same error.

can assist please?

regards

matt


matt

hi,

specific root causes 1753 error include:

  1. the server app never started (i.e. step #1 in "more information" diagram located above never attempted).
  2. the server app started there failure during initialization prevented registering rpc endpoint mapper (i.e. step #1 in "more information" diagram above attempted failed).
  3. the server app started subsequently died. (i.e. step #1 in "more information" diagram above completed successfully, undone later because server died).
  4. the server app manually unregistered endpoints (similar 3 intentional. not included completeness.)
  5. the rpc client (destination dc) contacted different rpc server intended 1 due name ip mapping error in dns, wins or host/lmhosts file.

for more information , resolutions please refer to:

http://technet.microsoft.com/en-us/library/replication-error-1753-there-are-no-more-endpoints-available-from-the-endpoint-mapper(v=ws.10).aspx

hope helps



Windows Server  >  Windows Server 2012 General



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group