Quantcast
Viewing all articles
Browse latest Browse all 8539

Having trouble getting rid of an RPC error

I've got an SBS 2003 server that I'm trying to make redundant and shift to a new Server 2012 box with Outlook 2013. To do this, I've got a temporary SBS 2011 box that I'm using to facilitate the migration. Here's the problem:

Upon running the migration preparation tool on the 2003 box, I get a few errors, namely that the "log on as a batch job" assignment is wrong, and that some FSMO roles are missing.

  • Trying to correct the first error brings up a "The remote call procedure failed and did not run."
  • Trying to correct the second error by using (ntdsutil > roles > connect > connect to server SERVER) throws up the error "DSBindW error (0x6bf): The remote procedure call failed and did not execute."
  • Running a portqry on port 135 from another machine tells me that port 135 is LISTENING but not responding.
  • Running repadmin /bind shows everything as "yes". (should I be using different parameters?)
  • Running dcdiag tells me: "Directory binding error 1727: The remote procedure call failed and did not execute".

Can anyone please point me in the direction I should be looking to resolve this? Otherwise, is there another way of migrating the server that doesn't involve RPC? If anyone wants, I can post more detailed logs and outputs.


Viewing all articles
Browse latest Browse all 8539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>