The XML hierarchy cannot be converted to an XML document (SBL-EAI-04112) When Activating Siebel Workflow Process Via Web Client (Doc ID 2069133.1)

Last updated on MAY 01, 2023

Applies to:

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: Siebel 8.1.1.14 PatchSet 9
DATABASE VERSION: Oracle 11.2.0.1
SIEBEL APP O/S: Oracle Solaris on SPARC (64-bit)

ISSUE STATEMENT:
----------------------------

Customer is using Siebel Client application to activate workflow processes through the Sitemap > Administration - Business Process screen > Active Workflow Process List View. Most of the workflow processes being activated this way activates successfully. However, some of the workflow processes cannot be activated using this approach and generates an error instead.

ERROR MESSAGE:
--------------------------
The error message that occurs with this issue is:

ObjMgrLog Error 1 00005905560510d4:0 2015-10-07 09:58:41 (filerefmgr.cpp (234)) SBL-GEN-10103: Error opening specified file
ObjMgrLog Error 1 00005905560510d4:0 2015-10-07 09:58:41 (xmlcnv.cpp (1973)) SBL-GEN-10103: Error opening specified file
ObjMgrBusServiceLog InvokeMethod 4 00005905560510d4:0 2015-10-07 09:58:41 Business Service 'XML Hierarchy Converter' invoke method 'HierToDoc' Execute Time: 0.032 seconds.
ObjMgrBusServiceLog InvokeMethod 4 00005905560510d4:0 2015-10-07 09:58:41 End: Business Service 'XML Hierarchy Converter' invoke method: 'HierToDoc' at dda77e0
ObjMgrBusServiceLog Error 1 00005905560510d4:0 2015-10-07 09:58:41 (eaixmlcnvsv.cpp (203)) SBL-EAI-04112: The XML hierarchy cannot be converted to an XML document.

WHERE IT HAPPENED:
-------------------------------
The issue happens in customer's Production Test environment.

STEPS TO REPRODUCE:
---------------------------------
The behaviour occurs as follows:

1. Launch the Siebel Client application.

2. Navigate to the Sitemap > Administration - Business Process screen > Active Workflow Process List View.

3. Select a workflow process in the top applet and click the {Activate} button.

4. Most of the workflow processes being activated this way activates successfully. However, some of the workflow processes cannot be activated using this approach and generates an error instead.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
------------------------------
Due to error message, customer is not able to activate some of the workflow processes and thus not able to use those workflow processes in the environment.

Cause

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