| Siebel SQLs/Error Messages > Siebel Error: SBL-EAI-50176, SBL-GEN-10107,SBL-GEN-10109,SBL-GEN-10203
SBL-GEN-10001 Siebel internal error (OSA layer)SBL-GEN-10001 Siebel internal error (OSA layer)
SBL-GEN-10051 Error adding environment variable
SBL-GEN-10052 Error reading environment variable
SBL-GEN-10101 Error creating specified file
SBL-GEN-10102 Error deleting specified file
SBL-GEN-10103 Error opening specified file
SBL-EAI-50176 Error When Writing Large XML Files (Doc ID 1130826.1)
APPLIES TO:
Siebel CRM - Version 8.1.1 [21112] and laterInformation in this document applies to any platform.
SYMPTOMS
During processing for some interfaces, XML is written to a file in a network folder, for further processing by the middleware. The 'EAI XML Write to File' Business Service is used to write the file to the intended network location.
When processing some large files (e.g. 1 MB), it was observed that Siebel would write to a temporary location. And when this occurred, a failure was reported :-
ObjMgrBusServiceLog Error 1 000002ef4be2083c:0 2010-05-06 01:53:54 (eaixmlprtsvc.cpp (234)) SBL-EAI-04266: 'EAI XML Write to File' service with method 'WriteXMLHier' failed while generating XML to be written to file '\\10.10.10.10\SiebFS\CreditCard\FileWJ05.000006.xml'.
New large file reference is created - 'D:\sba811\siebsrvr\temp\1-6TU2_0.tmp'.
EAIFileAttachments EAIFileAttachmentDebug 5 000030134bde1fbc:0 2010-05-04 04:36:40 New large file reference is registered - 'D:\sba811\siebsrvr\temp\1-6TU2_0.tmp'.ObjMgrLog Error 1 000030134bde1fbc:0 2010-05-04 04:36:40 (filerefutil.cpp (272)) SBL-GEN-10103: Error opening specified fileObjMgrLog Error 1 000030134bde1fbc:0 2010-05-04 04:36:40 (filerefutil.cpp (272)) SBL-EAI-50176: Error writing to file reference 'D:\sba811\siebsrvr\temp\1-6TU2_0.tmp '.
CAUSE
In this case, it was determined that the error arose because the middleware application was picking up the file before Siebel had completed writing the file.
SOLUTION
The middleware process picking up the file was delayed, to allow Siebel to complete it's operation.
Other points to check :-
1. Ensure the \temp directory being written to is accessible from the operating system user running the Siebel Server service.
2. Ensure there is sufficient space
3. Check that no other processes (e.g. anti-virus software) are trying to access the files being written to by Siebel.
Error While Activating Workflow Process (Doc ID 2066042.1)
APPLIES TO:
Siebel CRM - Version 8.1.1.11.11 [IP2013] and laterInformation in this document applies to any platform.SYMPTOMSOn : 8.1.1.11.11 [IP2013] version, Siebel Workflow
We recently upgraded from 8.1.1.10 to 8.1.1.11
We are getting the errors SBL-GEN-10103, SBL-EAI-04112 while activating workflow process, the activation fails.
This is occurring for all workflow processes regardless of size, vanilla or custom.
I have confirmed the following.
1. siebsrvr\TEMP is not full and has a lot of space.2. The Directory path for the file system is accessible to user running the Siebel service.3. Siebel is installed on windows server. Workflow activation is working on other environments. I compared the temp folder. For both working and non working environments, the temp folder is empty.
File system seems to be working fine in general. We are able to attach files and open attachments.
ERROR
ObjMgrLog Error 1 000000b055ba1e04:0 2015-07-30 13:43:12 (xmlcnv.cpp (1729)) SBL-GEN-10103: Error opening specified fileObjMgrBusServiceLog Error 1 000000b055ba1e04:0 2015-07-30 13:43:12 (eaixmlcnvsv.cpp (203)) SBL-EAI-04112: The XML hierarchy cannot be converted to an XML document.
CAUSE
Siebel File System problem, using relative path instead of absolute path.
While trying to import a .xml file by placing the xml file in the D:\siebdev\siebsrvr\TEMP, and since I was importing the xml into Siebel Server from another system with SADMIN credentials I entered the path as application server network name\d$\siebdev\siebsrvr\TEMP in the pop up window, this resulted in a different error:
[1]Error writing XML to file '\sea\temp\LOV.xml'.(SBL-EAI-04262)[2]Unable to open file 'sea\temp\LOV.xml'(SBL-EAI-04224)
SOLUTION
It is identified to be the same issue as the following Doc:
Getting Error SBL-EAI-04224 While Dumping XML To A Shared Path in Windows (Doc ID 1900066.1)
For more information on absolute path and relative path, please refer to the following Doc:
Siebel File System Master Note (Doc ID 1459875.1)
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)
APPLIES TO:
Siebel CRM - Version 8.1.1.10 [23021] and laterInformation in this document applies to any platform.
SYMPTOMS
PRODUCT VERSIONS:------------------------------SIEBEL VERSION: Siebel 8.1.1.14 PatchSet 9
DATABASE VERSION: Oracle 11.2.0.1SIEBEL 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 fileObjMgrLog Error 1 00005905560510d4:0 2015-10-07 09:58:41 (xmlcnv.cpp (1973)) SBL-GEN-10103: Error opening specified fileObjMgrBusServiceLog 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 dda77e0ObjMgrBusServiceLog 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
The cause of the issue was due to incorrect value provided for the component parameter "XMLP Temp File Path" on the Public Sector OM component used for the Siebel Web Client which were used for activating the workflow process. For the public sector OM, there was the "XML Temp File Path" parameter that was not set correctly when compared to other working environments onsite:
XML Temp File Path : /temp/
The environment where the workflow activation failed had this parameter set to the path /temp/ , while in the environment where the activation works properly had this parameter set to same path value as the File System Parameter "/data/tres/siebfs"
SOLUTION
Customer has since fixed the issue by doing the following:
1. Update the Public Sector OM component on the problematic Siebel environment by setting the "XML Temp File Path" parameter to the same value as the File System Parameter value/path of: /data/tres/siebfs
2. Restarted the Siebel server services
3. Tested the workflow activation with the Siebel Public Sector OM web client and confirm that the workflow activation no longer generates the error message
SBL-GEN-10104 Error closing specified fileSBL-GEN-10105 Error seeking within specified fileSBL-GEN-10106 Error reading from specified fileSBL-GEN-10107 Error writing to specified file.
Campaign Load of Segment Tree Fails with Errors SBL-BPR-00162 and SBL-GEN-10107 (Doc ID 947084.1)
APPLIES TO:
Siebel Marketing - Version 8.0 [20405] to 8.1 SIA [21039] [Release V8]Information in this document applies to any platform.***Checked for relevance on 10-Jul-2014***
SYMPTOMS
The Campaign Load of a Segment Tree is failing with the error:
Error/Warning : Error invoking service 'Mktg Data Load Service', method 'PrepareCache' at step 'Prepare Cahce'.(SBL-BPR-00162)--Error writing to specified file.(SBL-GEN-10107)
CAUSE
The cause of the problem was determined to be the fact that there are 44 GB of temp files in the siebsrvr/temp directory. These tmp files have this format:
1-1VZ1Q_0.tmp
Thousands of them are generated when a campaign load of a segment is executed and the contents of these temp files are the SOAP response from the GetJobInfo outbound web service calls that are made from the CRM to the OBI PS server. At this moment it appears that if the response from the OBI Presentation Server (OBIPS) is larger than a certain threshold (not yet determined) the response is written as a tmp file. This does not occur for smaller requests, such as the loading of one segment. It only seems to happen for larger requests like the loading of a segment tree which might produce a SOAP response of ~ 50 - 100 KB. These temp files are not being deleted.
Oracle Customer Support was able to reproduce the problem of SOAP response tmp files being created in the siebsrvr/temp directory when loading a large segment tree which contained many nodes to be cached.
As the polling frequency of a marketing job is very high by default (can be several hundred calls a minute), if there are temp files being written for every getJobInfo soap request for a large long-running segment, then the siebsrvr/temp directory could fill up and cause this problem.
SOLUTION
The solution to this problem was to clear out the old temp files in the siebsrvr/temp directory and to make sure that they are not created in the future, it is advisable to set the following parameter in the InstanceConfig.xml file on the BI Presentation server so that GetJobInfo SOAP responses are not too large as to trigger the creation of the temp files in the first place:
1. Stop the OBI Presentation Server service2. Open the InstanceConfig.xml configuration file on the OBI Presentation Server (normally located in OracleBIData\web\config directory)3. Add the following XML tags to within the ServerInstance tag:
<MarketingJobsLogDetailLevel>0</MarketingJobsLogDetailLevel>4. Restart the OBI Presentation Server service
Once this was done, the campaign load of a segment tree was executed successfully without the leftover tmp files in the siebsrvr/temp directory.
Note: There were reported cases where setting the MarketingJobsLogDetailLevel parameter to 0 wasn't enough to solve the issue.
In some cases it was found that .tmp files were still being created to hold the temporary data. ( in case of large segments with many nodes).
In this case, it is suggested to have physical temporary (OBI Temp) tables created to temporarily hold this data:
1) Make sure "IN_SUPPORTED" is turned on in DB features in RPD for the database in the DBFeatures tab.
2) In the "General" tab of the DB definition, make sure that "Persist Conn Pool" is not empty. It should point to one of the connection pools.
Set "Allow Populate Queries by default" to true and make sure the user defined for the connection pool has create table privileges on the DB.
SBL-GEN-10108 Error flushing buffers for specified file
SBL-GEN-10109 Error loading specified DLL or shared object library
Siebel Remote 8.x : Database Extract (DbXtract) tasks end with errors SBL-DCK-52067 and SBL-GEN-10109 (Doc ID 1136114.1)
APPLIES TO:
Siebel Remote - Version 8.0 SIA [20405] to 15.0 [IP2015] [Release V8 to V15]Information in this document applies to any platform.Concurrency review 22-JUN-2015
SYMPTOMS
Database Extract (DbXtract) task is failing for a Mobile user. In detailed execution logs could be found lines like:
GenericLog GenericError 1 00000008488574ee:0 2008-07-22 15:35:45 (utlmisc.cpp (1647) err=10109 sys=0) SBL-GEN-10109: Error loading specified DLL or shared object library
GenericLog GenericError 1 00000008488574ee:0 2008-07-22 15:35:45 An error occurred loading encryption subsystem. Please check for more detailed errors from encryption subsystem in this log file
GenericLog GenericError 1 00000008488574ee:0 2008-07-22 15:35:45 (utlmisc.cpp (2180) err=1166179 sys=0) SBL-DCK-52067: An error occurred loading encryption subsystem. Please check for more detailed errors from encryption subsystem in this log file
GenericLog GenericError 1 00000008488574ee:0 2008-07-22 15:35:45 ProcessRow - failed
In some cases, for Unix OS servers it was noticed that DbXtract task could also crash (generating core dumps) -enterprise log would report:
SBL-SRB-00061: Process DbXtract on Siebel Server [ServerName] terminated.
CAUSE
DbXtract may fail when extracting some tables with encrpyted columns that contain migrated data encrypted using some previous versions algorithms or keys (i.e. following an Upgrade from 7.x to 8.x version).
SOLUTION
As workarounds following steps should be tried:
1) starting DbXtract task from srvrmgr instead of Siebel GUI.
2) If this may still fail, ensure adding for task execution parameter DataFileType=DAT instead of default BCP value (BCP would extract data to some text file format). For instance - replacing [UserName] with Mobile client name to be extracted (last 2 parameters would ensure Local DBF would not be encrypted or have its password stored in encrypted form, suitable for Developer users case):
srvrmgr> start task for comp DbXtract with Client=[UserName], DataFileType=DAT, EncryptLocalDbPwd=FALSE, EncryptLocalDbMethod=NONE
3) If using DAT format would still not help extraction shoud be attempted using Parallel Database Extract component (PdbXtract) instead of DbXtract.
That is normally meant to be used for Regional Nodes' databases extraction, but it should work for normal remote users as well. Please review the details about PDbXtract and its parameters in Siebel Bookshelf (v8.1): Remote and Replication Manager Administration Guide - Implementing Replication Manager > Extracting the Regional Database > "Parameters That You Can Specify When Extracting a Regional Database".
srvrmgr> start task for comp PDbXtract with Client=[UserName], DataFileType=DAT, EncryptLocalDbPwd=FALSE, EncryptLocalDbMethod=NONE, InitMethod="Sql Anywhere"
If data stored in encrypted columns was migrated from a previous Siebel version environment by upgrade - these details should be checked and followed - Siebel Bookshelf (v8.1): Security Guide > Communications and Data Encryption > About Data Encryption:* Encrypted Database Columns* Upgrade Issues for Data Encryption* Upgrading Encrypted Data to a Higher Encryption Level sections.
Database Extract Fails After Upgrade with Error Message SBL-DCK-52067 (Doc ID 1635162.1)
APPLIES TO:
Siebel Remote - Version 8.1 [21039] and laterSiebel CRM - Version 8.1 [21039] and laterInformation in this document applies to any platform.**** Checked for relevance on 01-May-2016 *****
SYMPTOMS
On : 8.1.1.11 SIA [23030] version, Remote / Replication / Anywhere
When attempting to Extract the db for remote clients, the following errors occur.
ERROR
----------------------
SBL-SMI-00077: Component error, see the trace file for more information
SBL-GEN-10109: Error loading specified DLL or shared object library
An error occurred loading encryption subsystem. Please check for more detailed errors from encryption subsystem in this log file
SBL-DCK-52067: An error occurred loading encryption subsystem. Please check for more detailed errors from encryption subsystem in this log file
STEPS
-----------------------
The issue can be reproduced at will with the following steps:1. (Oracle Solution Support Engineering) create some encrypted columns on Siebel base tables2. Upgrade from 8.1.1.9 to 8.1.1.11 for instance3. Run GenNewDB4. Run Database Extract (DbXtract)
BUSINESS IMPACT
-----------------------
The issue has the following business impact:Due to this issue, Development team can not work.
CHANGES
Upgraded Siebel application from 8.1.1.9 to 8.1.1.11 version.
CAUSE
Further investigation revealed that keyfile.bin which is use for Data Encryption was outdated.
Keyfile.bin on the server was dated all the way back in 2002. THis keyfile.bin is a important file in Siebel and could be used for authentication and data encryption.After some Fix Pack or Quick Fix installations this keyfile.bin may be updated.If Siebel Strong Encryption Pack (SSEP) was used at any stage then also keyfile.bin gets updated.
SOLUTION
After following up below action plan issue was resolved and DbXtract started to work with out issues:
1. If a backup of keyfile.bin exists from before the upgrade process, the size and time stamp should be compared to the one after the upgrade.2. Rename the existing keyfile.bin3. Restore the keyfile.bin from backup4. If there is no backup available of this keyfile.bin file, but there is another environment with the same encryption setup, one may try to copy the keyfile.bin from that environment.
If using data encryption, it is always advisable before upgrading or installing patches to keep a backup of the keyfile.bin file.
SBL-GEN-10110 Error unloading specified DLL or shared object library
SBL-GEN-10111 Error getting address of specified entry point within DLL or shared object library
SBL-GEN-10112 Internal: DLL or shared object library has not been loaded
SBL-GEN-10113 Internal: DLL or shared object library has already been loaded
SBL-GEN-10114 File is not open yet
SBL-GEN-10115 Error getting file lengthSBL-GEN-10116 Error acquiring file lock
SBL-GEN-10117 Error setting file size
SBL-GEN-10118 File already existsSBL-GEN-10201 Error creating O/S mutex
SBL-GEN-10202 Could not obtain O/S mutex because it is currently being held
SBL-GEN-10203 Error attempting to obtain O/S mutex
Communications Server recovery (Doc ID 491752.1)
APPLIES TO:
Product Release: V7 (Enterprise)Version: 7.5.3.2 [16168] NLD Engy/OilDatabase: Oracle 9.2.0.2Application Server OS: HP-UX 11iDatabase Server OS: HP-UX 11i
SYMPTOMS
SBL-GEN-10203, SBL-OSD-00219A crash in the CTI driver (see SR #38-1333516351) has twice resulted in a crash of the CommSessionManager component. The root cause of this is being addressed separately by the CTI vendor (Aspect) under the other SR. This SR is specifically to minimise the overall service outage resulting from such a crash.When the crash has previously occurred it has affected all Siebel users, and taken around one hour each time before full service is restored, involving manual restarts of Siebel Servers and components. A description of each scenario together with some of the relevant log files is included in the attached report.It's understood that such a crash will always result in a loss of the CTI toolbar until users logout and login again. This is acceptable. However it's hoped the administrator intervention to recycle Siebel Servers & Components together with the associated time taken should not be needed.Note: The system is not currently down. Siebel CTI functionality has been disabled across all call centres pending resolution of this issue and of SR #38-1333516351
SOLUTION
Message 1For the benefit of others,
The customer was integrating Siebel version 7.5.3.2 with Aspect CTI middleware.They had experienced a communication session manager crash, the root cause of this was being addressed separately by the CTI vendor (Aspect).Their object managers were on HP-UX and their CTI components were enabled on an application server on a windows 2000 server.When the crash occurred on the Communication Session Manager component on the windows server, the customer also experienced a crash on the SRBroker on the HP_UX server once CTI server was restarted.The SRBroker log files contained errors like the following:SBL-GEN-10203: Error attempting to obtain O/S mutexSBL-OSD-00219: Internal: pthread_mutex_lock failed with errorThe customer was able to replicate this behavior in their test environment.
This was not reproducible on a replicate test environment setup internally using the standard .srf.On further investigation it was found that the customer did not have their CTI configuration pointing to the request server on the windows server.
Continued in next activity........Message 2Continued from previous activity...................
Firstly to give you an understanding of what my environment setup was like.1. One application server on a HPUX server with the eCommunications object manager enabled for testing on Siebel version 7.5.3.6 SIA.Gateway: eghtshp1:2331, EnterpriseServer: E753SIAORA, Siebel Server: s753siaora2. One application server on Windows 2000 server with the CTI communication components enabled on Siebel version 7.5.3.6 SIA.This application server is connecting to the same gateway: eghtshp1:2331, EnterpriseServer: E753SIAORA and Siebel Server is: SIA753NUONAs part of the setup from the CTI side, it was necessary to specify the following CTI configuration parameters at the Communications administration > All configurations > Parameters view.GatewayAddress = "eghtshp1:2331"EnterpriseServer = "E753SIAORA"RequestServer = "SIA753NUON"CommSessionMgr = "CommSessionMgr"
These parameters are defined based on the following definitions:GatewayAddress. Specify the Siebel Gateway. For example, specify a value like "gateway-host" for this parameter.EnterpriseServer. Specify the Siebel Enterprise Server. For example, specify a value like "siebel" for this parameter.RequestServer. Specify the Siebel Server. For example, specify a value like "server-host" for this parameter.
Continued in next activity...........Message 3Continued from previous activity............
CommSessionMgr. Specify the Communications Session Manager. For example, specify a value like "CommSessionMgr" for this parameter.If an agent logs in using a configuration containing these parameters, the agent will be connected to the component identified by these values.
Details of these parameters can be found in Siebel Bookshelf version 7.5.3 > Siebel Communications Server Administration Guide > Administering Siebel Communications Server > Administering Communications Session ManagerFor further information please refer also to Performance Tuning Guide > Tuning Siebel Communications Server for Performance > Topology Considerations for Session CommunicationsIn this guide explains the considerations to take into account when running CommSessionMgr on dedicated servers.In particular take into account the following statement:“If your AOM components (Call Center Object Manager) run on machines using a different platform, then you set several parameters in the communications configuration, including CommSessionMgr and RequestServer, in order to designate the machine where CommSessionMgr is running. All communications session requests from an AOM supporting users for this communications configuration will be routed to the CommSessionMgr component on the dedicated machine.”
Continued in next activity........................Message 4Continued from previous activity.......................
In the customers case none of the above parameters had been set at the CTI configuration parameters level. Once they adjusted these parameters appropriately they no longer saw the SRBroker component fall over on the HP-UX application server.
| 
