6 Replies Latest reply on Dec 28, 2019 10:42 AM by StEdmunds

    Horizon View 6.0.1 - ADAM data error

    Lalegre Enthusiast

      Hello guys i am having this problem in my production environment.

       

      I cannot create or edit any desktop pool. When i try to perform this operations the message "ADAM data error" is displayed. Searching more this is what appears in the logs:

       

      ADAM Error code: 2 103 com.vmware.vdi.admin.ui.DesktopBean.saveDesktop(SourceFile:2396)

      com.vmware.vdi.adamwrapper.exceptions.ADAMServerException: [LDAP: error code 16 - 00000057: LdapErr: DSID-0C090B3D, comment: Error in attribute conversion operation, data 0, v1db1

       

      I did these workarounds:

      • Restart vCenter Server and View Connection Servers.
      • Force replication between ADAM databases and the replication is okay.
      • Verify with vdmadmin the LDAP collisions, nothing appeared.
      • Check the integrity of the ADAM database and all the attributes are there.
      • Check connection with View Composer and vCenter and it is okay.

       

      Also this problem appeared when i upgrade from Horizon View 5.2 to Horizon view 6.0.1

       

      Any help would be graceful.

       

      Thanks you in advance!

        • 1. Re: Horizon View 6.0.1 - ADAM data error
          StEdmunds Novice

          Hi, I know this was a while ago but do you remember what you did to fix this issue.  We are having a very similar issue.


          Many thanks

           

           

          Stuart

          • 2. Re: Horizon View 6.0.1 - ADAM data error
            Amin Masoudifard Expert

            VMware View 6 is a very old version product. It's strongly recommended to upgrade it to at least any version of Horizon View 7.x.

            Probably your problem will be solved

            Please mark my comment as the Correct Answer if this solution resolved your problem
            • 3. Re: Horizon View 6.0.1 - ADAM data error
              StEdmunds Novice

              Hi,

               

              Our problem has occurred while upgrading from 7.4 to 7.10 (although we get the same error upgrading to either 7.6 and 7.9).

               

              We have, at the request of VMWare support, rolled back to our 7.4 snapshots, removed all but 1 connection server and repeated the upgrade and run the vdmadmin -schemacollisions -resolve command which did find issues and successfully resolved them.  We are still receiving the ADAM data error message though when we try to modify an existing pool.

               

              The logs show the following:

               

              2019-12-20T09:43:02.651Z DEBUG (1290-17E8) <ajp-nio-8009-exec-3> [AdamEntityManager] Replace ADAM object attributes failed:  com.vmware.vdi.logger.Logger.debug(Logger.java:44)

              javax.naming.directory.NoSuchAttributeException: [LDAP: error code 16 - 00000057: LdapErr: DSID-0C090D50, comment: Error in attribute conversion operation, data 0, v2580

              2019-12-20T09:43:02.652Z DEBUG (1290-17E8) <ajp-nio-8009-exec-3> [FlexFaultHandler] ADAM data error com.vmware.vdi.logger.Logger.debug(Logger.java:44)

              com.vmware.vdi.adamwrapper.exceptions.ADAMServerException: [LDAP: error code 16 - 00000057: LdapErr: DSID-0C090D50, comment: Error in attribute conversion operation, data 0, v2580

              2019-12-20T09:43:02.652Z ERROR (1290-17E8) <ajp-nio-8009-exec-3> [FlexFaultHandler] ADAM data error

              2019-12-20T09:43:02.654Z DEBUG (1290-17E8) <ajp-nio-8009-exec-3> [ViewFlexFactory] ADAM data error com.vmware.vdi.logger.Logger.debug(Logger.java:44)

              com.vmware.vdi.admin.ui.common.FlexRemoteException: ADAM data error

              at com.vmware.vdi.admin.ui.common.FlexFaultHandler.a(SourceFile:326)

              at com.vmware.vdi.admin.ui.common.FlexFaultHandler.handleADAMError(SourceFile:116)

              at com.vmware.vdi.admin.ui.DesktopBeanFlexAdapter.saveAutoPool(SourceFile:4072)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:498)

              at com.vmware.vdi.admin.ui.common.ViewFlexFactory$ViewProxy.invoke(SourceFile:113)

              at com.sun.proxy.$Proxy279.saveAutoPool(Unknown Source)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:498)

              at flex.messaging.services.remoting.adapters.JavaAdapter.invoke(JavaAdapter.java:386)

              at flex.messaging.services.RemotingService.serviceMessage(RemotingService.java:180)

              at flex.messaging.MessageBroker.routeMessageToService(MessageBroker.java:1472)

              at flex.messaging.endpoints.AbstractEndpoint.serviceMessage(AbstractEndpoint.java:1046)

              at flex.messaging.endpoints.amf.MessageBrokerFilter.invoke(MessageBrokerFilter.java:101)

              at flex.messaging.endpoints.amf.LegacyFilter.invoke(LegacyFilter.java:154)

              at flex.messaging.endpoints.amf.SessionFilter.invoke(SessionFilter.java:42)

              at flex.messaging.endpoints.amf.BatchProcessFilter.invoke(BatchProcessFilter.java:63)

              at flex.messaging.endpoints.amf.SerializationFilter.invoke(SerializationFilter.java:190)

              at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.java:328)

              at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java:373)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

              at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:728)

              at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:470)

              at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:395)

              at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:316)

              at com.vmware.vdi.admin.ui.servlet.AMFProxyServlet.a(SourceFile:90)

              at com.vmware.vdi.admin.ui.servlet.AMFProxyServlet.doPost(SourceFile:57)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

              at org.apache.catalina.filters.FailedRequestFilter.doFilter(FailedRequestFilter.java:96)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

              at com.vmware.vdi.support.ViewAdminFilter.doFilter(SourceFile:103)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

              at com.vmware.vdi.admin.be.filters.CertificateAuthFilter.doFilter(SourceFile:140)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

              at com.vmware.vdi.admin.be.filters.DisableUrlSessionFilter.doFilter(SourceFile:80)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

              at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)

              at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)

              at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:528)

              at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)

              at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)

              at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)

              at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:476)

              at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)

              at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:810)

              at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)

              at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

              at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

              at java.lang.Thread.run(Thread.java:748)

              Caused by: com.vmware.vdi.adamwrapper.exceptions.ADAMServerException: [LDAP: error code 16 - 00000057: LdapErr: DSID-0C090D50, comment: Error in attribute conversion operation, data 0, v2580

              2019-12-20T09:43:02.654Z DEBUG (1290-17E8) <ajp-nio-8009-exec-3> [ViewFlexFactory] com.vmware.vdi.admin.ui.DesktopBeanFlexAdapter.saveAutoPool 1711 ms

              2019-12-20T09:43:02.660Z DEBUG (12E8-1424) <AJP-95> [SimpleAJPService] (ajp:admin:Request103) Response 200 OK

              2019-12-20T09:43:04.036Z DEBUG (1290-07B4) <DesktopControlSessions> [DesktopTracker] start session reader broadcast

              2019-12-20T09:43:12.188Z DEBUG (1290-16D8) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createTag(): Tag: {CMS-SMSS:1}

              2019-12-20T09:43:12.188Z DEBUG (1290-16D8) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: CMS#1

              2019-12-20T09:43:12.188Z DEBUG (1290-16D8) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=exist, ok=0, msecs=0

              2019-12-20T09:43:12.188Z DEBUG (1290-16D8) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: SHARED##CMS#1

              2019-12-20T09:43:12.188Z DEBUG (1290-16D8) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=exist, ok=1, msecs=0

              2019-12-20T09:43:12.188Z DEBUG (1290-16D8) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: SHARED##CMS#1

              2019-12-20T09:43:12.204Z DEBUG (1290-16D8) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=decipherWithDerivedKey, ok=1, msecs=16

              2019-12-20T09:43:12.204Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [ServiceConnection25] Connecting instance Publish VC Cert Task Instance at URL https://horizonvcenter:443/sdk

              2019-12-20T09:43:12.220Z DEBUG (1290-0F34) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createTag(): Tag: {CMS-SMSS:1}

              2019-12-20T09:43:12.220Z DEBUG (1290-0F34) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: CMS#1

              2019-12-20T09:43:12.220Z DEBUG (1290-0F34) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=exist, ok=0, msecs=0

              2019-12-20T09:43:12.220Z DEBUG (1290-0F34) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: SHARED##CMS#1

              2019-12-20T09:43:12.220Z DEBUG (1290-0F34) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=exist, ok=1, msecs=0

              2019-12-20T09:43:12.220Z DEBUG (1290-0F34) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: SHARED##CMS#1

              2019-12-20T09:43:12.236Z DEBUG (1290-0F34) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=decipherWithDerivedKey, ok=1, msecs=16

              2019-12-20T09:43:12.236Z DEBUG (1290-0B2C) <VCHealthUpdate> [ServiceConnection25] Connecting instance VCHealth Test instance at URL https://horizonvcenter:443/sdk

              2019-12-20T09:43:14.074Z DEBUG (1290-07B4) <DesktopControlSessions> [SDMessageManager] finished waiting, was waiting for 10000ms

              2019-12-20T09:43:14.130Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [CertMatchingTrustManager] Created new CertMatchingTrustManager com.vmware.vdi.ssl.CertMatchingTrustManager@5541e900 with ThumbprintManager com.vmware.vdi.desktopcontroller.LdapThumbprintManager@60f98b02

              2019-12-20T09:43:14.130Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [HardenedSSLSocketFactory] Creating new HardenedSSLSocketFactory, caller=com.vmware.vdi.vcsupport25.ServiceConnection25.a

              2019-12-20T09:43:14.130Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [HardenedSSLSocketFactory] SSL provider: SunJSSE version 1.8

              2019-12-20T09:43:14.130Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [HardenedSSLSocketFactory] SSL protocol: TLSv1.2

              2019-12-20T09:43:14.130Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [HardenedSSLSocketFactory] SSL secure protocols (3): [TLSv1.2, TLSv1.1, TLSv1]

              2019-12-20T09:43:14.130Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [HardenedSSLSocketFactory] SSL cipher suites (7): [TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA]

              2019-12-20T09:43:14.136Z DEBUG (1290-0238) <MessageFrameWorkDispatch> [MessageFrameWork] ValidateCertificateChain ok=1, msecs=0

              2019-12-20T09:43:14.136Z DEBUG (1290-0238) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=validateCertificateChain, ok=1, msecs=0

              2019-12-20T09:43:14.137Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [CertMatchingTrustManager] invalid certificate (as expected) for horizonvcenter:443 InvalidCertificateException[reasons:nameMismatch;notTrusted;cantCheckRevoked; subject:'C=US, CN=HorizonVCenter.network.sec' message:'ValidateCertificateChain Result: FAIL, EndEntityReasons: nameMismatch, cantCheckRevoked, ChainReasons: partialChain']

              2019-12-20T09:43:14.157Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [ServiceConnection25] Connected instance Publish VC Cert Task Instance at URL https://horizonvcenter:443/sdk

              2019-12-20T09:43:14.157Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [ServiceConnection25] Fetched reference objects for instance Publish VC Cert Task Instance at URL https://horizonvcenter:443/sdk in 1 seconds. CBRC supported by VC: true

              2019-12-20T09:43:14.157Z DEBUG (1290-130C) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createTag(): Tag: {CMS-SMSS:1}

              2019-12-20T09:43:14.157Z DEBUG (1290-130C) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: CMS#1

              2019-12-20T09:43:14.157Z DEBUG (1290-130C) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=exist, ok=0, msecs=0

              2019-12-20T09:43:14.157Z DEBUG (1290-130C) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: SHARED##CMS#1

              2019-12-20T09:43:14.157Z DEBUG (1290-130C) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=exist, ok=1, msecs=0

              2019-12-20T09:43:14.157Z DEBUG (1290-130C) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Key::createKeyspec(): Keyspec: SHARED##CMS#1

              2019-12-20T09:43:14.163Z DEBUG (1290-0B2C) <VCHealthUpdate> [CertMatchingTrustManager] Created new CertMatchingTrustManager com.vmware.vdi.ssl.CertMatchingTrustManager@799cf6dc with ThumbprintManager com.vmware.vdi.desktopcontroller.LdapThumbprintManager@60f98b02

              2019-12-20T09:43:14.163Z DEBUG (1290-0B2C) <VCHealthUpdate> [HardenedSSLSocketFactory] Creating new HardenedSSLSocketFactory, caller=com.vmware.vdi.vcsupport25.ServiceConnection25.a

              2019-12-20T09:43:14.164Z DEBUG (1290-0B2C) <VCHealthUpdate> [HardenedSSLSocketFactory] SSL provider: SunJSSE version 1.8

              2019-12-20T09:43:14.164Z DEBUG (1290-0B2C) <VCHealthUpdate> [HardenedSSLSocketFactory] SSL protocol: TLSv1.2

              2019-12-20T09:43:14.164Z DEBUG (1290-0B2C) <VCHealthUpdate> [HardenedSSLSocketFactory] SSL secure protocols (3): [TLSv1.2, TLSv1.1, TLSv1]

              2019-12-20T09:43:14.164Z DEBUG (1290-0B2C) <VCHealthUpdate> [HardenedSSLSocketFactory] SSL cipher suites (7): [TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA]

              2019-12-20T09:43:14.165Z DEBUG (1290-130C) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=decipherWithDerivedKey, ok=1, msecs=16

              2019-12-20T09:43:14.170Z DEBUG (1290-112C) <MessageFrameWorkDispatch> [MessageFrameWork] ValidateCertificateChain ok=1, msecs=0

              2019-12-20T09:43:14.170Z DEBUG (1290-112C) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=validateCertificateChain, ok=1, msecs=0

              2019-12-20T09:43:14.170Z DEBUG (1290-0B2C) <VCHealthUpdate> [CertMatchingTrustManager] invalid certificate (as expected) for horizonvcenter:443 InvalidCertificateException[reasons:nameMismatch;notTrusted;cantCheckRevoked; subject:'C=US, CN=HorizonVCenter.network.sec' message:'ValidateCertificateChain Result: FAIL, EndEntityReasons: nameMismatch, cantCheckRevoked, ChainReasons: partialChain']

              2019-12-20T09:43:14.185Z DEBUG (1290-0B2C) <VCHealthUpdate> [ServiceConnection25] Connected instance VCHealth Test instance at URL https://horizonvcenter:443/sdk

              2019-12-20T09:43:14.185Z DEBUG (1290-0B2C) <VCHealthUpdate> [ServiceConnection25] Fetched reference objects for instance VCHealth Test instance at URL https://horizonvcenter:443/sdk in 1 seconds. CBRC supported by VC: true

              2019-12-20T09:43:14.185Z DEBUG (1290-0B2C) <VCHealthUpdate> [ServiceConnection25] Logging in instance VCHealth Test instance at URL https://horizonvcenter:443/sdk

              2019-12-20T09:43:14.197Z DEBUG (1290-1348) <MessageFrameWorkDispatch> [MessageFrameWork] ValidateCertificateChain ok=1, msecs=0

              2019-12-20T09:43:14.197Z DEBUG (1290-1348) <MessageFrameWorkDispatch> [MessageFrameWork] KeyVault service got operation=validateCertificateChain, ok=1, msecs=0

              2019-12-20T09:43:14.197Z DEBUG (1290-0CF8) <Publish VC Cert Task-1576774268166> [CertMatchingTrustManager] invalid certificate (as expected) for horizonvcenter:18443 InvalidCertificateException[reasons:nameMismatch;notTrusted; subject:'CN=HorizonVCenter.network.sec' message:'ValidateCertificateChain Result: FAIL, EndEntityReasons: nameMismatch, ChainReasons: invalid']

              2019-12-20T09:43:14.319Z DEBUG (1290-0B2C) <VCHealthUpdate> [ServiceConnection25] Logged into instance VCHealth Test instance at URL https://horizonvcenter:443/sdk

              2019-12-20T09:43:14.319Z DEBUG (1290-0B2C) <VCHealthUpdate> [VCHealth] The VC with URL=https://horizonvcenter:443/sdk has reported a status of STATUS_UP, description=Connected

              2019-12-20T09:43:14.324Z DEBUG (1290-0B2C) <VCHealthUpdate> [TrackerObject] Sync complete: VcHealth:HORIZCONINT|cb429a7e-e0eb-4216-a8e7-144059531e13 to version: 964

              2019-12-20T09:43:14.324Z DEBUG (1290-0B2C) <VCHealthUpdate> [TrackerManager] Sending message: (TrackerMessage SYNC {}: {nn=HorizConint, u=[{"type":"SET","item":{"name":"ATTR_VC_STATUS","type":"STRING","stringValue":"STATUS_UP"}},{"type":"SET","item":{"name":"ATTR_VC_STATUS_DESCRIPTION","type":...

              2019-12-20T09:43:15.490Z DEBUG (1290-0AD8) <CBHealthUpdate> [CBHealth] IPsec status IPSEC_OK for HORIZSECINT

              2019-12-20T09:43:15.490Z DEBUG (1290-0AD8) <CBHealthUpdate> [AdminUtils] Fetching aggregated session information

              2019-12-20T09:43:15.490Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] attempting to get JMSCluster instance

              2019-12-20T09:43:15.490Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] got JMSCluster, routers: [[ name=router1, username=broker/horizconint, password=null, siteName=null, swiftMQHost = localhost, swiftMQPort = 4002, swiftMQSocketFactory = com.vmware.vdi.servercommon.messagesecurity.swiftmq.BrokerSSLSocketFactory, swiftMQKeepAlive = 60000, usingJNDINames = true ]]

              2019-12-20T09:43:15.491Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] connection established to routerId: router1

              2019-12-20T09:43:15.493Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] ready to publish on topic: topic/IceTunnelTopic

              2019-12-20T09:43:15.494Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] temporary topic created and subscribed to: tmp$8684-1576774170306@HORIZCONINT

              2019-12-20T09:43:15.496Z DEBUG (12E8-0864) <MsgWorker#9> [bp] Item on queue "Inbound JMS Worker" for 373 us, queue length = 0, available workers = 9 of 10

              2019-12-20T09:43:15.497Z DEBUG (12E8-0864) <MsgWorker#9> [t] RequestCurrentSessions: serverType = null, server = null, localHostname = HORIZCONINT, requestedCapID = NONE

              2019-12-20T09:43:15.498Z DEBUG (12E8-0ECC) <Outbound JMS Responder Thread> [bp] Item on queue "Outbound JMS Responder" for 1 ms, queue length = 0, available workers = 0 of 1

              2019-12-20T09:43:15.498Z DEBUG (12E8-0ECC) <Outbound JMS Responder Thread> [o] Sending JMS message: CurrentSessions

              2019-12-20T09:43:15.499Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] 6 sessions added for server: HorizConint

              2019-12-20T09:43:15.501Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] 0 sessions added for server: HORIZCONINT

              2019-12-20T09:43:15.501Z DEBUG (1290-0AD8) <CBHealthUpdate> [CurrentSessions] 6 sessions added for server: HORIZSECINT

              2019-12-20T09:43:15.501Z DEBUG (12E8-0ECC) <Outbound JMS Responder Thread> [o] Sent ObjectMessage in 3 ms

               

              Has anyone else had this issue?

              • 4. Re: Horizon View 6.0.1 - ADAM data error
                Amin Masoudifard Expert

                Do you have access to the LDAP data (open in with ADSIEDIT in windows, I mentioned how to do it here)

                Find the related desktop pool object and check can you modify its attributes, which one that you need (take a snapshot before that).

                Please mark my comment as the Correct Answer if this solution resolved your problem
                • 5. Re: Horizon View 6.0.1 - ADAM data error
                  StEdmunds Novice

                  Hi.  Yes we do.  I have taken a look at one of the pools and can edit the settings.  I have updated the powerpolicy on a pool from alwayson to poweroff and when I go back into view administrator the change is reflected.  The desktops of the pool also shutdown so the command is getting to composer and vcenter okay.  I then tried using view administrator to power the pool back on and I still get the ADAM error.

                   

                  It's really annoying that the log doesn't tell us more so we know what to look at to fix the issue.  I am awaiting a call back from VMWare support.

                   

                  Many thanks

                   

                  Stuart

                  • 6. Re: Horizon View 6.0.1 - ADAM data error
                    StEdmunds Novice

                    Okay so this has now been resolved and I wanted to post our solution in case anyone else has this issue.  Our LDAP schema had some issues.

                     

                    Best to disable the composer service while you do this.

                     

                    The following will force the updated schema.

                     

                    1. Shutdown the Connection Server and take a snapshot of it for rollback purposes.
                    2.    Uninstall and remove the paired Security Server.
                    3.    Take an LDAP backup. (https://docs.vmware.com/en/VMware-Horizon-7/7.10/horizon-administration/GUID-6EDC7F4C-5FD0-411F-9823-9405DD31C852.html)
                    4.    Fully uninstall the Connection Server software and LDAP instance.
                    5.    After rebooting the server, reinstall the Connection Server software. This creates a brand new ADAM DB (LDAP).
                    6.    Confirm the newly clean CS is up and admin page accessible, then stop the CS service.
                    7.    Decrypt and import the LDAP backup taken in step 3. (https://docs.vmware.com/en/VMware-Horizon-7/7.10/horizon-administration/GUID-EFA249B5-1D21-4B8C-BF6A-8CE2A15916C0.html)
                    8.    Uninstall just the Connection Server software (leaving the LDAP instance this time).
                    9.    Install the Connection Server choosing to utilize the existing LDAP instance when prompted.
                    10.    Reinstall the Security Server.