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

Cloud Pod Architecture fails to initialize after a failed upgrade (76048)

Last Updated: 7/13/2022Categories: TroubleshootingTotal Views: 4505Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Upgrading the Horizon Pods in a Cloud Pod Architecture (CPA) fails.

CPA will not initialize after reverting to the pre-upgrade version.

The Cloud Pod page doesn't display the Join/Initialize options.

In the debug log, you see entries similar to:

2019-09-19T01:36:21.684-04:00 ERROR (0F6C-22DC)  [LdapUtil] (SESSION:5834_***_9863) Unable to read Global LDAP
2019-09-19T01:36:21.685-04:00 DEBUG (0F6C-22DC)  [LdapUtil] (SESSION:5834_***_9863) Unable to read Global LDAP:  com.vmware.vdi.logger.Logger.debug(Logger.java:44)
javax.naming.CommunicationException: 127.0.0.1:22389 [Root exception is java.net.ConnectException: Connection refused: connect]
at com.sun.jndi.ldap.Connection.(Connection.java:216)

Cause

This issue occurs due to the global Adam instances being removed during the upgrade. The replica servers show the status as Disabled (Unreachable Server).

Resolution

To resolve this issue the local ADAM database needs to manually be reset to default settings.

Connect to the View ADAM database. For more information, see Connecting to the View ADAM Database.

Edit the following properties for each Adam instance.

Navigate to Properties > LMV > Server Name

Search for:

pae-LinkedModeEnabledPercent: 100 and change the value to 0.

pae-LinkedModeLastError: LMV_OP_UNREACHABLE_SERVER and change the value to LMV_OP_OK.

pae-LinkedModeEnabled: 1 and change the value to 0.

Close the View ADAM Database. Reattempt the operation.

For further troubleshooting, see Recovery scenarios for Horizon 7 environment (70906)

Note:
In some rare instances, you may be unable to clear this error state.  In which case, you will need to identify which pod is experiencing an issue and remove it from the CPA federation.  You can do this by accessing the Horizon Console administrative page from each pod and observing where the issue is seen.

To remove a Pod from CPA, first RDP into a Connection Server in the pod you wish to remove and use a command prompt to run the command

lmvutil --unjoin

Full command example:

lmvutil --authAs MyAdminAcct --authDomain MyDomain --authPassword "*" --unjoin

Second, RDP into a Connection Server in a different pod and use a command prompt to run the command

lmvutil --ejectPod --pod OtherPodName

Full command example:

lmvutil --authAs MyAdminAcct --authDomain MyDomain --authPassword "*" --ejectPod --pod USEast

After taking these steps, confirm in the Horizon Console page of a remaining pod that the issue is cleared, then re-join the Pod which you removed back into the CPA and re-add the pools to the Global Entitlements.

For further details, see Administering Cloud Pod Architecture with lmvutil

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server, ESXi et/ou NSX sont déconnectés après une mise à niveau de Cloud Director 10.1, 10.3 ou 10.4 (78885)

KB
•
升级到 VCD 10.1 后，vCenter Server 和/或 NSX 断开连接 (78885)

KB
•
1709 以降の Windows 10 仮想デスクトップで AllowDirectRDP グループ ポリシー設定が機能しない (76593)

KB
•
vRealize Automation 8.0.1 的累积更新 (76805)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon View

VMware Horizon

Related Versions:

Take Our Survey

Support Assistant