Siebel Could Not Open Connection To Siebel Gateway Server (null) Is Unavailable On Workmon Component Log
(Doc ID 2594531.1)
Last updated on MAY 12, 2020
Applies to:Siebel CRM - Version 188.8.131.526  and later
Information in this document applies to any platform.
On : 184.108.40.2066  version, Siebel Workflow
The custom Workmon process in all Siebel Server where the component is enabled sporadically show the following error in the log files:
The error does not stop the WorkMon process to process the requests most of the time. This is also affects Jobs for WfProcBatchMgr component sporadically in which case the Job need to be resubmit manually to recover.
The errors started on 09/03 when new Siebel Servers were added on the Siebel Enterprise. 10 new Siebel Servers were added to the Siebel Enterprise BUT were not used yet and would be user in the future for new projects.
On 09/09 after all 10 Siebel Server were added the whole Siebel Enterprise were restarted to see if the problem goes away, but it persisted.
The error show up with the new Siebel Servers up up or down, currently they are keeping the new Siebel Servers down.
After rollback the siebns.dat to prior to the 10 new Siebel Server the issue persisted too.
The Siebel Gateway is running on a Microsoft Cluster environment on an Active/Passive mode, change the active/passive machine also did not helped to avoid the problem.
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