Avoiding Error 10048/port conflicts on protected Exchange RRS feed

  • Question

  • This weekend (the first weekend with DPM 2010 protecting our Exch. 2007 environment) we had several smaller issues. One of them (solved an hour ago) showed up as an "agent unreachable" on our DPM and on the Exchange-server, the dpmra-agent failed to initialize due to a 10048.

    googling around, we found that the probable cause was that another process has allocated the agents ports; 5718-5719. We ran netstat but found no sockets being bind to these ports.

    But we tried stopping the Assistant Service anyway and once stopped, DPMRA went up fine again and synchronization started.

    So first question; Is there only TCP/UDP sockets that can conflict between system components and dpm agent, or are there more since we found no ports with netstat?

    second; What can we do to prevent this again? I know we can change the ports being used by the agent, but if it WAS ports conflicting, what would that solve since the Exchange Assistant service is using dynamic ports, and nothing would stop it from binding to the new ports we set for the dpm agent?


    Sunday, April 8, 2012 10:13 AM


All replies