locked
SDN v2 error (50125) Network service threw an unhandled exception Network Controller element RRS feed

  • Question

  • We have installed SDNv2 onto a redundant VMM platform and everything seems to of gone perfectly well. We can create virtual networks and connect to the internet from them with routing or Natting. VPN works, so far so good. However if we try and snapshot, migrate, refresh or try any other action with a virtual machine attached to one of these networks it fails with the above error.

    Any ideas?

    Monday, January 15, 2018 8:46 AM

Answers

  • Hello,

    We have solved the issue yes. It is related to a bug in VMM. When a virtual machine is refreshed the checkpoint was being addressed towards the network controller (that doesn't know anything about check pointing since it is a storage component) this resulted in the unhandled exception error.

    Microsoft do have an unsupported hotfix for this issue. We have tested it and it works. They have said that the hotfix will be released as supported as part of the next update rollup in April 2018. I would just wait for that otherwise you will be installing and uninstalling hotfixes and have to deal with MS support to get the hotfix which took us weeks.

    • Marked as answer by BlakeThompson Monday, March 26, 2018 8:16 AM
    Monday, March 26, 2018 8:16 AM

All replies

  • Hello,

    The following article introduces the detailed troubleshooting tools and methods. 

    You can refer to it.

    Bye the way, if you disconnect the VM, can you perform the actions(Take Checkpoint, migrate and refresh) to the VM successfully?

    https://docs.microsoft.com/en-us/windows-server/networking/sdn/troubleshoot/troubleshoot-windows-server-software-defined-networking-stack

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 16, 2018 9:56 AM
  • Hello,

    did you managed to solve the problem?

    I also have the same issue in 2 different environments (at my lab and at customer's site). The checkpoint is actually being created, but with disconnected NIC, you can see it in scvmm console/vm/manage checkpoints.

    If VMNIC is disconnected, the checkpoint creation succeeds.

    The problem persists in vmm2016 UR3 and UR4, seems to be Network Controller issue?

    Best regards,

    Leon.

    Thursday, March 22, 2018 4:09 PM
  • Hello,

    Just opened premier case.

    This is known problem.

    Will be fixed next Update Rollup.

    Sunday, March 25, 2018 12:22 PM
  • Hello,

    We have solved the issue yes. It is related to a bug in VMM. When a virtual machine is refreshed the checkpoint was being addressed towards the network controller (that doesn't know anything about check pointing since it is a storage component) this resulted in the unhandled exception error.

    Microsoft do have an unsupported hotfix for this issue. We have tested it and it works. They have said that the hotfix will be released as supported as part of the next update rollup in April 2018. I would just wait for that otherwise you will be installing and uninstalling hotfixes and have to deal with MS support to get the hotfix which took us weeks.

    • Marked as answer by BlakeThompson Monday, March 26, 2018 8:16 AM
    Monday, March 26, 2018 8:16 AM