• State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 27 subscribers
  • Views 6819 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Anyone else having connectivity issues with the latest Windows 10 build?

rbrown
over 8 years ago

 I'm getting a RPC service is down error only on machines with the latest build (14393).  I was using v6.0.2, upgraded to 6.1 and still no joy.

  • 0 over 8 years ago
    Hi rbrown:
    There is not enough data in your post to attempt even an educated guess. Were you able to protect the Windows 10 agents? If it is the case, are they protected with the RR agent software or agentlessly? When does the RPC error show up? Are the Win 10 agents showing offline, are they showing on line and the error pops up when attempting to take a snaphot? Is the metadata collection successful? Is the data transfer starting and failing after some data goes through or the RPC failure kills the job right away (and the list of questions may go on and on).
    I would check the WMI state (and restart it) as there are many connectivity/metadata collection errors are caused by WMI issues. However since the issue you experience shows up only on the latest Win 10 built there may be some Windows related bug/feature causing the issue as well.
    Please post a better description of the issue or open a case with our support team.
    • 0 over 8 years ago
      I was able to protect the clients with installed agents before the upgrade to the latest W10Pro build. The RPC error shows up attempting to connect to the agent and doesn't collect the metadata, so the backup never takes place. I removed a machine from protection and attempted to reconnect and get the same error. The agents were showing offline with 6.0.2 but are showing online with 6.1. I've taken steps to restart services (WMI and others) and it doesn't help. I did open a support request.
      • +1 over 8 years ago

        Hi rbrown:
        Thank you for your reply. It sheds some light on the issue. If you have a Win 10 machine that you can play with (and the time to do it) I would suggest to downgrade the agent to 5.4.3.106 and see if it works. I just heard from a colleague that it worked for his customer after some volumes were not seen anymore after an agent upgrade. It may be a far fetched connection but, if you can, it may be worth a try wile the Support Engineer is looking to asses the issues you have on a more in depth basis.
        The agent can be downloaded from here

        Prior to removing the 6.1 agent it makes sense to export HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Agent\AgentId

        and import it after the downgrade to keep the same agent ID.

        Please let us know if it works for you if you try this work around.

        • 0 over 8 years ago
          Thank you. I will give it a try and follow up later.
          • 0 over 8 years ago
            Using the old agent seems to have worked. Thank you for the workaround!