Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Token renewal and auto upgrade issue and remediation for non US region customers for Horizon Cloud Connector (78184)

Last Updated: 3/19/2020Categories: TroubleshootingTotal Views: 3648Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When refreshing token or during auto-upgrade for non US region customers for Horizon Cloud Connector, you see these symptoms:

Refresh token renewal fails.

Auto upgrade fails.

In the viewproxyadapter.log file, you see entries similar to:

Errors: Failed to get API access token: 401 – Unauthorized

Purpose

This article provides mitigation on token renewal related issues after on-boarding Horizon Cloud Connector for customers in Non US region.

Cause

This issue occurs  due to an existing issue with Horizon Cloud Connector 1.5 and below.

In case of token renewal failure for 1.5 version, onboarding UI will show error under health section due to connector-client session failure after 6 days. In this case, license push fails and Horizon Enterprise server license eventually expire.

In such a case, a reconfigure is required.

Resolution

This issue is resolved in VMware Horizon Cloud Connector 1.6, available at VMware Downloads.

Workaround

To work around this issue, restart the Horizon Cloud Connector virtual appliance between 24-48 hours of onboarding. However, VMware highly recommends to upgrade to Horizon Cloud Connector 1.6.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vSphere コンソールからの vRealize Operations Manager ノードへのアクセス (78377)

KB
•
VPP アカウントの場所への移行のベスト プラクティス (2960233)

KB
•
「AMQP ブローカ接続のテスト：失敗 - ACCESS_REFUSED - 認証メカニズム PLAIN を使用したログインが拒否されました。詳細については、ブローカのログ ファイルを参照してください。(Test AMQP Broker Connection: Failed - ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.)」 (76149)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon Connector

Related Versions:

VMware Horizon Connector 1.x

Take Our Survey

Support Assistant