- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
New deployment for me with ver. 4.1, and I too receive the same error. No idea how to resolve it yet, and no articles could be found referring to this message. I am working with support for deploying NSX for us, so hopefully they can find a solution. Not exactly a reassuring start to our NSX experience.