Forum Discussion

ges87's avatar
ges87
Level 5
8 years ago

incorrect password EC8F1B8E EC8F17B7 EC8F03ED E7D10041 EBAb03F1

When trying to run automated backup jobs, multiple clients are reporing this error. When this happens, usually the clients goes on reporting the same error at every attempt. Result: multiple clients ...
2013 R2
Windows Server 2012 R2
  • ges87's avatar
    ges87
    8 years ago

    I solved the problem by uninstalling from all affected server SSR2013R2, the agent, cleaning up any remaining file, registry key, removing all policies related to those server and the relative backup destinations, and then reinstalling everything. In test VM that had this problem, I instead just tried to upgrade SSR to V16 and that also solved the problem, without any need to reinstall or delete anything.

    So it seems that it's exactly the upgrade of the agent that causes the problem...

criley's avatar
criley
Moderator
8 years ago

ges87

This sounds very similar to an issue that has already been reported to us. Did this problem start following an upgrade of the Management Solution?

  • ges87's avatar
    ges87
    Level 5
    8 years ago

    more or less yes, little after upgrading to 2016. Clients still 2013R2

    • criley's avatar
      criley
      Moderator
      8 years ago

      ges87

      OK, the solution/workaround involved is not simple at all. We'll also need to review client-side logs to confirm it's the same issue.

      Can you open a support case please? (provide case number here)

      • ges87's avatar
        ges87
        Level 5
        8 years ago

        I solved the problem by uninstalling from all affected server SSR2013R2, the agent, cleaning up any remaining file, registry key, removing all policies related to those server and the relative backup destinations, and then reinstalling everything. In test VM that had this problem, I instead just tried to upgrade SSR to V16 and that also solved the problem, without any need to reinstall or delete anything.

        So it seems that it's exactly the upgrade of the agent that causes the problem...