Summary
Error
When using two default CM integration points in Integration Studio.
- Configuration Manager KPI Adapter
- Configuration Manager Policy Adapter
when trying Test Connection option from Integration Studio for both points, getting this error message:
com.hp.ucmdb.discovery.probe.request.ProbeSideProc
to Integration{Configuration Manager KPI Adapter, CMKpiAdapter, null}]
Integration[Configuration
Manager KPI Adapter]: Unable to connect to the Configuration Manager server. The current user does
not have authorization to access to the Configuration Manager server.
--- Start of probe-side exception
---
com.hp.ucmdb.dataAccess.exceptions.AdapterAccessCo
connect to Integration{Configuration Manager KPI Adapter, CMKpiAdapter,
null}]
Integration[Configuration Manager KPI Adapter]: Unable to connect to the Configuration
Manager server. The current user does not have authorization to access to the Configuration
Manager server.
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConver
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConver
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConver
at
com.hp.ucmdb.discovery.probe.processor.FederationN
at
com.hp.ucmdb.discovery.probe.processor.FederationN
at
com.hp.ucmdb.discovery.probe.agents.probemgr.adhoc
at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskd
at sun.reflect.GeneratedMethodAccessor65.invoke(Unkno
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
at java.lang.reflect.Method.invoke(Method.java:497)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java
at sun.reflect.GeneratedMethodAccessor12.invoke(Unkno
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
at java.lang.reflect.Method.invoke(Method.java:497)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInt
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanS
at javax.management.StandardMBean.invoke(StandardMBea
at
com.sun.jmx.interceptor.DefaultMBeanServerIntercep
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxM
at
javax.management.MBeanServerInvocationHandler.invo
at
org.springframework.jmx.access.MBeanClientIntercep
at
org.springframework.jmx.access.MBeanClientIntercep
at
org.springframework.aop.framework.ReflectiveMethod
at org.springframework.aop.framework.JdkDynamicAopPro
at com.sun.proxy.$Proxy48.dispatchTask(Unknown Source)
at
com.hp.ucmdb.discovery.probe.agents.probegw.manage
at org.eclipse.jetty.util.thread.QueuedThreadPool.run
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.r
at java.lang.Thread.run(Thread.java:745)
--- End of probe-side exception ---
UCMDB and CM versions are 10.22 CUP2 with CP19.
IP's and User credentials were created during CM installation process. the user credentials can be used to log in in CM.
Cause
There are three possiblities which might cause this issue:
1. The UCMDB is configured with multi tenant (MT)
When UCMDB is MT and CM is installed the user created on CM install is not created corectly as it does not set up the asigned tenant. To solve this issue please check the cm integration user and for that user set up tenant owner and tenant uses (The recommandation is to run CM reconfiguration and so CM restart as the new user settings needs to be reflected in CM as well)
2.The user set up in the integration is LDAP user
You may try to test with out of the box sysadmin user (set it in the integration point configuration).
3.There is also the pasword policy functionality. When CM is installed it will require user with an password that is according to the policy (contains upper and lower and number and special char) but this would reflect in errors in the _installation\logs.