Enterprise Manager For Siebel: Siebel Servers And Siebel Server Components Status DOWN After Discovery: Failed To Connect Server Hostname: Handshake Failed (Doc ID 2901491.1)

Last updated on OCTOBER 13, 2022

Applies to:

Enterprise Manager for Siebel - Version 13.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

When using Enterprise Manager for Siebel - Siebel Servers and Siebel Server Components status are DOWN after Discovery.

The following error can be found in the gcagent_sdk_trc file.

gcagent_sdk.trc file
-----------------------------------------------------------------------------------------------------------------------------
Failed to connect server hostname: Handshake failed
at oracle.sysman.siebel.management.serveraccess.SrvrMgrInvoker.validateSession(SrvrMgrInvoker.java:1327)
at oracle.sysman.siebel.management.serveraccess.SrvrMgrInvoker.startSession(SrvrMgrInvoker.java:1059)
at oracle.sysman.siebel.management.serveraccess.SrvrMgrInvoker.runCmd(SrvrMgrInvoker.java:659)
at oracle.sysman.siebel.management.serveraccess.SrvrMgrInvoker.run(SrvrMgrInvoker.java:561)
at oracle.sysman.siebel.management.serveraccess.Admin.listServersPtrn(Admin.java:171)
at oracle.sysman.siebel.management.serveraccess.Admin.listServers(Admin.java:160)
at oracle.sysman.siebel.management.serveraccess.ServerAdmin.listServers(ServerAdmin.java:39)
at oracle.sysman.siebel.management.serveraccess.objinterfaces.SiebelServer.refreshAttributes(SiebelServer.java:284)
at oracle.sysman.siebel.management.serveraccess.objinterfaces.SiebelServer.isAvailable(SiebelServer.java:210)
at oracle.sysman.siebel.management.emagent.EMAgent.getSiebelServer(EMAgent.java:206)
at oracle.sysman.siebel.management.emagent.EMAgent.getSiebelServer(EMAgent.java:260)
at oracle.sysman.siebel.management.emagent.EMServerAgent.isCompGroupAvailable(EMServerAgent.java:623)
at sun.reflect.GeneratedMethodAccessor1058.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at oracle.sysman.siebel.management.emagent.SiebelCacheableJavaFetchlet.getMetric(SiebelCacheableJavaFetchlet.java:213)
at oracle.sysman.gcagent.target.interaction.execution.FetchletFactory.getMetric(FetchletFactory.java:466)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.executeQueryDescriptor(ExecuteTask.java:1332)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.runTask(ExecuteTask.java:3226)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.call(ExecuteTask.java:4577)
at oracle.sysman.gcagent.metadata.impl.collection.MetricColl$1.call(MetricColl.java:585)
at oracle.sysman.gcagent.metadata.impl.collection.MetricColl$1.call(MetricColl.java:545)
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.accountedCall(TaskFutureImpl.java:600)
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.call(TaskFutureImpl.java:644)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at oracle.sysman.gcagent.task.TaskFutureImpl.run1(TaskFutureImpl.java:373)
at oracle.sysman.gcagent.task.TaskFutureImpl.run(TaskFutureImpl.java:330)
at oracle.sysman.gcagent.task.CompositeTask.runSubtask(CompositeTask.java:70)
at oracle.sysman.gcagent.task.CompositeTask.run(CompositeTask.java:77)
at oracle.sysman.gcagent.metadata.impl.collection.CollectionItem$CollectionItemTask.run(CollectionItem.java:2668)
at oracle.sysman.gcagent.task.AbstractTemplateTask.call(AbstractTemplateTask.java:271)
at oracle.sysman.gcagent.task.AbstractTemplateTask.call(AbstractTemplateTask.java:56)
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler$ReschedulingHelper$ReschedulingTask.call(DispatchingTaskScheduler.java:639)
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler$ReschedulingHelper$ReschedulingTask.call(DispatchingTaskScheduler.java:580)
at oracle.sysman.gcagent.task.executor.DiagWrappedTask.call(DiagWrappedTask.java:60)
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.accountedCall(TaskFutureImpl.java:600)
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.call(TaskFutureImpl.java:644)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at oracle.sysman.gcagent.task.TaskFutureImpl.run1(TaskFutureImpl.java:373)
at oracle.sysman.gcagent.task.TaskFutureImpl.run(TaskFutureImpl.java:330)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at oracle.sysman.gcagent.task.executor.TrackThreadFactory$1.run(TrackThreadFactory.java:54)
at oracle.sysman.gcagent.util.system.GCAThread$RunnableWrapper.run(GCAThread.java:198)
at java.lang.Thread.run(Thread.java:748)

STEPS
----------------------------------------------
1. Install Siebel Enterprise.
2. Install Enterprise Manager for Siebel.
3. Start the Siebel Enterprise.
4. Start the Enterprise Manager for Siebel Agent.
5. Start the Enterprise Manager Pre Discovery Process.
6. Start the Enterprise Manager Discovery Process.
7. Observe the Enterprise Manager is reporting the Siebel Server and Siebel Server Components as DOWN

Changes

Installed Siebel Enterprise and Enterprise Manager for Siebel.

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Enterprise Manager For Siebel: Siebel Servers And Siebel Server Components Status DOWN After Discovery: Failed To Connect Server Hostname: Handshake Failed (Doc ID 2901491.1)

Applies to:

Symptoms

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!