We could not reproduce the issue, but we saw where the exception was generated, so we handled the exception in the plugin code and so it should fix this problem. We will release the update/fix in the next UCCNC development release which will be out soon.