Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Unable to recompose or unknown provisioning error thrown in Horizon 7.5 and above versions (56978)

Last Updated: 3/31/2023Categories: TroubleshootingTotal Views: 5762Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

When using the Horizon 7.5 or above versions with vCenter Server 6.5, the VCCache initialization fails to complete with vCenter Server.

In the Horizon View Admin Dashboard, ESXi hosts and Datastores are missing under vSphere Component. Only vCenter Server gets listed.

You see stack trace similar to:

2018-07-11T15:03:18.712+02:00 DEBUG (0D84-1970) <VCC-d2d712e2-057f-4251-89ad-305ce0b2402b-1531313834768> [VcCache] Exception from connectAndWait() com.vmware.vdi.logger.Logger.debug(Logger.java:44)
java.lang.NullPointerException
at com.vmware.vdi.vcsupport25.VmException25.getMethodFault(SourceFile:230)
at com.vmware.vdi.vcsupport25.ServiceConnection25.a(SourceFile:1219)
at com.vmware.vdi.vcsupport25.ServiceConnection25.waitForUpdatesCancelable(SourceFile:1101)
at com.vmware.vdi.vccache.VcCache.f(SourceFile:786)
at com.vmware.vdi.vccache.VcCache.run(SourceFile:294)
at com.vmware.vdi.vccache.VcCacheInitializer.run(SourceFile:77)
at com.vmware.vdi.vccache.VcCacheFederatedTask.run(SourceFile:192)
at com.vmware.vdi.common.taskmanager.ExecutorImmediate$a.run(SourceFile:55)
2018-07-11T15:03:18.712+02:00 DEBUG (0D84-1970) <VCC-d2d712e2-057f-4251-89ad-305ce0b2402b-1531313834768> [VcCache] Sleeping for 5 seconds before reconnecting

In the Connection Server logs, you see these exceptions:

javax.xml.ws.soap.SOAPFaultException: Unmarshalling Error: Maximum Element Depth limit (100) Exceeded
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:161)
at com.sun.proxy.$Proxy158.retrieveProperties(Unknown Source)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.retrieveProperties(VcSubsystem25.java:3602)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.access$000(VcSubsystem25.java:156)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25$27.invoke(VcSubsystem25.java:3145)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25$27.invoke(VcSubsystem25.java:3142)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25$VcExceptionHandler.invoke(VcSubsystem25.java:3274)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.callVcMethod(VcSubsystem25.java:1917)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.initializeCache(VcSubsystem25.java:3142)
at com.vmware.daas.cloneprep.cache.CacheManager.populateTempStores(CacheManager.java:768)
at com.vmware.daas.cloneprep.cache.CacheManager.populateCache(CacheManager.java:632)
at com.vmware.daas.cloneprep.cache.CacheManager.<init>(CacheManager.java:284)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystem25.<init>(VcSubsystem25.java:277)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystemFactory.getVcSubsystemNoLock(VcSubsystemFactory.java:302)
at com.vmware.daas.cloneprep.vcsubsystem.VcSubsystemFactory.getVcSubsystem(VcSubsystemFactory.java:192)
at com.vmware.daas.cloneprep.service.ClonePrepServiceImpl.initialize(ClonePrepServiceImpl.java:123)
at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.e(SourceFile:6583)
at com.vmware.vdi.desktopcontroller.VirtualCenterDriver.run(SourceFile:7055)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.stream.XMLStreamException: Maximum Element Depth limit (100) Exceeded]
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handleStreamException(UnmarshallerImpl.java:470)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:402)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:379)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.doUnmarshal(JAXBEncoderDecoder.java:857)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.access$100(JAXBEncoderDecoder.java:102)
at org.apache.cxf.jaxb.JAXBEncoderDecoder$2.run(JAXBEncoderDecoder.java:896)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:894)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:714)
at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:179)
at org.apache.cxf.wsdl.interceptors.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:109)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:835)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1684)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1560)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1361)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:658)
at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:535)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:444)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:345)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:298)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
... 18 more
Caused by: javax.xml.stream.XMLStreamException: Maximum Element Depth limit (100) Exceeded
at com.ctc.wstx.sr.InputElementStack.push(InputElementStack.java:329)
at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2951)
at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2839)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1073)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:181)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:400)
... 42 more

2018-07-11T14:59:00.095+02:00 WARN (0D84-197C) <VirtualCenterDriver-d2d712e2-057f-4251-89ad-305ce0b2402b> [VcUtil] Unknown type of SOAPFaultException.Unmarshalling Error: Maximum Element Depth limit (100) Exceeded Will retry.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

Apache CXF Webservice data parser has a limitation of 100 as MaxElementDepth. When a response from vCenter Server exceeds this range, the data is dropped at the parser level causing exceptions thrown at UI layer.
Note: This limitation is for security purpose. For more information, see http://cxf.apache.org/docs/security.html.

Resolution

To resolve this issue, add the JvmOptions parameter in Tomcat Service of each CS and restart the 'VMware Horizon View Connection Server' service:

Go to the following registry path:

HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wsnm\tomcatService\Params

Add this parameter to the JvmOptions.

-Dorg.apache.cxf.stax.maxElementDepth=500

Note: Ensure to add a space before -D if you have added at the end of line. No space to be added at the end if it is last parameter in JVmOptions.

If the issue persists, increase the value to 1000 or 2000.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
升级 vCenter Server Appliance 6.7 时：“添加用户失败：cm to group: cis”、“PAM：身份验证令牌不再有效” (55863)

KB
•
vCenter Server のアップグレード後に VCDB が過剰に大きくなる (2058670)

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

KB
•
升级后无法启动 Web Client 服务 (2150318)

KB
•
vSAN Health Service - 群集 - vSAN 扩展配置同步 (57202)

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

Related Versions:

VMware Horizon 7.x

VMware Horizon 7 version 7.7.x

VMware Horizon 7 version 7.6.x

VMware Horizon 7 version 7.5.x

VMware Horizon 7

Take Our Survey

Support Assistant