Registering the NSX manager to ePO fails with Username/Password Error

[Former Member]

ePO 5.10
MOVE Agentless AV 4.8
NSX 6.4.3

This is the second NSX manager we are adding to the ePO. I have added it to the cloud registration and it populates vms just fine. The NSX that is installed has already deployed its GI's. However when i go to the Move AV Deployment > Agentless > NSX Manager > "edit" and attempt to enter the proper credentials (that are tested and working) it responds with a failed to authinticate message.

Any guidance on what might be causing this issue would be appreciated.

[akatt]

We can extrapolate some more information on the failure, by reviewing ePO's orion.log.  Reproduce the failure (to update the log), and then go to:

C:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\Logs

We should be able to see a failure message pertaining to the account/registration.  Often, we need to enable debug logging for the Orion.log, to get more valuable information for the failure.  This can be achieved by following the below KB:

https://kc.mcafee.com/corporate/index?page=content&id=KB52369

Was my reply helpful?

If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?

[Former Member]

Ok, I went thru and enabled debug logs for orion and replicated the error. the log noted that the credentials are incorrect. however I have already verified that the exact credintials im inputting are the ones that work with NSX thru the NSX login panel.

util.SvaDeploymentUtil - API call generic status check: false

register.SVARegMgrImpl - Fetching Service manager for NSX server: Server Address- ["xxx.xxx.xxx.xxx"] failed

util.ErrorParrseUtil - Credentials are incorrect

action.MoveCommonConfigNSXManagerAction - Error occurred while validating with nsx server with Error code: 502
com.mcafee.dccommon.deployment.nsx.exeception.RestApiFailException: Fetching service() manager failed

[Former Member · Accepted solution]

I figured out the issue. the password was 17 characters and it only accepts 16 characters. one that was changed it accepted it no problem.