Hi,

We have an issue when trying to add vCenter Server to new ASR Vmware to Azure deployment. We receive an "Internal Error - code 499. More details:

• Process Server has network connection to vCenter an it has vSphere CLI 5.5 (build 1384587) installed
• The account which is used to log into vCenter has full administrative efforts. In vCenter logs we can see that user session is initiated but nothing happens and after a couple of minutes the session disappears.
• vCenter version is 5.5 (build 1378901)

See screenshot below. Please help with any suggestions to resolve the issue

Thanks

Bartek Sollich

Hi,

Does the Vcenter name contain non-ASCII characters? Because of this ,the discovery is failing.

Thanks

Shashank

Hi,

No, only numbers and letters.

Thanks

Bartek

Hi, We are having the same error... 

VMware CLI 5.5

no non-ASCII chars in name

Any ideas on solution? Any ideas on logs to look at?

Johan Persson

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 33 minutes ago

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 38 minutes ago

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:39 AM

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:39 AM

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:39 AM

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:39 AM

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:39 AM

This issue is because of non-English/special characters exist on vCenter infrastructure.  please add individual ESX hosts for discovery and protect the VM's as a work around.

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Wednesday, July 15, 2015 6:39 AM

Hi All, is the above work around working or are you still facing issues?

Kindly also upgrade to the latest GA release so that you get improved features.

Thank you,

Ruturaj