Platforms affected: Windows Server 2008 R2, Server 2008, Server 2003 R2, Server 2003, Server 2000 (both 32-bit and 64-bit installs are affected). History: The history of this error, which has mostly gone unsolved, dates back to Windows 2000. I realize this is probably too late for you, but I had this problem, and was able to solve it.Ī complete solution to the RRAS won’t start with 8007042a or event ID 7024, aka the “routing remote access unable to load Iprtrmgr.dll” problem.
DimUnloadRouterManagers: fAllRouterManagersStoppedĪll the above solutions didn't work for us.the Routing and Remote access service still doesn't start. RTRMGR is unloaded from DIM ServiceMain: Error 31 occured while loading router managers. In the router.log (c:\windows\tracing\ we find:Įrror 31 occured during the router manager C initialization. Renamed the ias.xlm and dynary.xml in c:\windows\system32\iasĬopied the file iprtmgr.dll from another SBS 2008 computer. Opened Device Manager (Start - Run - devmgmt.msc) and select "View" menu and choose "Show Hidden Devices".ģ. Expand Network Adapters and look for any non-existing network adapters.Ĥ. Uninstall all the phantom adaptors except RAS Async adapter, WAN Miniport adapters, Microsoft ISATAP Adapter and Microsoft Virtual Machine Bus Removed phantom adapters (there were none) by using the following tip:ġ Run the command "set devmgr_show_nonpresent_devices=1"toĢ. Removing the registry ( HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess \RouterManagers\Ipv6 ) Removing the Role Routing and Remote access and reinstalling it. We got the error message "Unable to load c:\Windows\System32\iprtrmgr.dll" and event 2010 ( The Routing and Remote Access service terminated with service-specific error 31 (0x1F) ).Īfter going through internet we found differtent solutions which sadly didn't work after we removed Eset NOD32 all things started to look ok again except the Routing and Remote
After the corrupt patch a lot of problems started with the LAN interface. It all started with a corrupt patch from Eset NOD32 which was installed on our server.
Okay we have some serious problem here with starting the Routing and Remote acces service on