Search This Blog

SBL-OMS-00107: Object manager error: (%1)

Applies to:

Siebel System Software - Version: 7.8.2 [19213] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Object Manager - OMS
Version:Siebel 7.8

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-OMS-00107: Object manager error: (%1)

Scope

This document is informational and intended for any user.

SBL-OMS-00107: Object manager error: (%1)

Explanation

This error message in itself is not indicative of a specific behavior. The additional error message that accompanies this error is more specific to the issue. Use the additional error message for troubleshooting purposes. To obtain more detailed information in the log file from the Siebel Object Manager component, refer to Doc ID 477897.1. NOTE: The following bookshelf version is also applicable to the version listed in the header of this error message documentation. Also review the Siebel Bookshelf > System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging > Common Event Types for Application Object Manager Diagnostics.

Corrective Action

It is not feasible to list all the Corrective Actions to resolve this error because the solution will vary with each specific situation. After enabling the event logging for the particular server component, you should review the appropriate log file for additional information. Then take appropriate action depending on the cause of the error. After the behavior has been corrected, do not forget to reset the event logging levels back to the default value of 1 for the server component to reduce the amount of information generated in the log files.



Applies to:

Siebel System Software - Version: 7.8.2 [19213] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Object Manager - OMS
Version:Siebel 7.8

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-OMS-00107: Object manager error: (%1)

Scope

This document is informational and intended for any user.

SBL-OMS-00107: Object manager error: (%1)

Explanation

This error message in itself is not indicative of a specific behavior. The additional error message that accompanies this error is more specific to the issue. Use the additional error message for troubleshooting purposes. To obtain more detailed information in the log file from the Siebel Object Manager component, refer to Doc ID 477897.1. NOTE: The following bookshelf version is also applicable to the version listed in the header of this error message documentation. Also review the Siebel Bookshelf > System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging > Common Event Types for Application Object Manager Diagnostics.

Corrective Action

It is not feasible to list all the Corrective Actions to resolve this error because the solution will vary with each specific situation. After enabling the event logging for the particular server component, you should review the appropriate log file for additional information. Then take appropriate action depending on the cause of the error. After the behavior has been corrected, do not forget to reset the event logging levels back to the default value of 1 for the server component to reduce the amount of information generated in the log files.




Applies to:

Siebel CRM - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 19-Mar-2012***

Symptoms

After setting advanced parameter 'OM - Preload SRF Data' with value 'TRUE' for any Receiver component in Siebel (such as MQReceiver or JMSReceiver), component fails during initialization with error messages below found in log file:


(objdef.cpp (3854)) SBL-DAT-00477: The object definition manager has already been initialized.

( (0) err=2818155 sys=7668189) SBL-OMS-00107: Object manager error: ([0] The object definition manager has already been initialized.(SBL-DAT-00477) (0x7501dd))

(ccfom.cpp (560) err=2818149 sys=0) SBL-OMS-00101: Error 7668189 loading product configuration information

GenericLog GenericError 1 000000074c9a1df8:0 2010-09-22 19:10:40 (eaircvr.cpp (372) err=2818149 sys=0) SBL-OMS-00101: Error 7668189 loading product configuration information

GenericLog GenericError 1 000000074c9a1df8:0 2010-09-22 19:10:40 (smishell.cpp (335) err=2818149 sys=0) SBL-OMS-00101: Error 7668189 loading product configuration information


Cause

This is a known and expected behavior whenever a single-threaded Object Manager process, as receiver components (MQReceiver, JMSReceiver) tries to perform some of the initialization more than once. It would happen at process startup and at login time.

In the case of such components, the Repository Load process is handled by the same parameter set at Enterprise Level.

So, whenever the same value is used for this parameter at both, Enterprise and Component level, this error occurs.

It is suggested not to set this parameter 'OM - Preload SRF Data' for single-threaded Object Manager processes.

Solution


Parameter 'OM - Preload SRF Data' exists both at enteprise and component levels.
If set only at enterprise level, the component inherits the setting.
The solution here is to set the parameter to TRUE at enterprise and FALSE at component level.


After setting the parameter 'OM - Preload SRF Data' with value 'FALSE' (same parameter is 'TRUE' at Enterprise level), the issue is not longer observed and the component starts as expected.

Information related can be found in Bookshelf > Transports and Interfaces > About EAI Transport Methods.





Applies to:

Siebel Loyalty Engine - Version 8.1.1.1 SIA [21211] to 8.1.1.7 SIA [21238] [Release V8]
Information in this document applies to any platform.

Symptoms

Customer had started the Loyalty Batch and Interactive Engines.

These exited immediately without processing any records

Errors seen were:

GenericLog GenericError 1 0001623d4fa90098:0 2012-05-08 15:27:29 ( (0) err=2818155 sys=7667927) SBL-OMS-00107: Object manager error: ([0] This operation is not allowed when there are no records displayed.
and
GenericLog GenericError 1 0001623d4fa90098:0 2012-05-08 15:27:29 (bsvcmgr.cpp (946) err=2818251 sys=0) SBL-OMS-00203: Error 7667927 invoking method "BusSvcMgrInit" for Business Service "LOY Processing Engine"


Cause

When the LoyEngineBatch component is started, in the main thread of the component, you will see the requests to create the tasks according to the value of “LOY - Engine Number of Tasks” parameter.
For example, when LOYEngineNumberOfTasks = 2, for each process, you will see 3 requests to start new tasks on LoyEngineBatch component. This is an extract from the main thread log file:

"SrmRouting SrmRoutingSubevent 4 0 2009-08-13 20:25:55 SNDREQ
IDS : FLAGS [7] : REQID [] : SRBSESSID [73ca9ab01acsiebsrvr1] : SRMCONNID [8]
SRC : SRC_ID [0-1] : SRC_KEY []
DEST : ROUTE_ID [LoyEngineBatch] : ROUTE_KEY [siebsrvr1:1] : ROUTE_SRVR [siebsrvr1] : LANG_CODE [ENU] : CODE_PAGE [1200]

However in the customers log files the route id and server information was missing.

DEST : ROUTE_ID [] : ROUTE_KEY [] : ROUTE_SRVR [] : LANG_CODE [ENU] : CODE_PAGE [1200]

This is the same for the SRBroker information:

Standard:
IDS : FLAGS [7] : REQID [] : SRBSESSID [73ca9ab01acsiebsrvr1] : SRMCONNID [8]
SRC : SRC_ID [0-1] : SRC_KEY []


Customers logs show:

SrmRouting SrmRoutingSubevent 4 000000074fa90036:0 2012-05-08 15:26:03 SNDREQ
  IDS : FLAGS [11] : REQID [] : SRBSESSID [] : SRMCONNID [1]
  SRC : SRC_ID [cache] : SRC_KEY [CTEvent]
  DEST : ROUTE_ID [] : ROUTE_KEY [] : ROUTE_SRVR [] : LANG_CODE [ENU] : CODE_PAGE [1200]



Solution

The customer added the server keys to the environment via Loyalty Program Administration > Server Key map.

Once these mappings were added, the batch engine started successfully and processed transactions.

References

NOTE:874062.1 - How is the LoyEngineBatch Automatically Starting the Desired Number of Tasks?
NOTE:1458439.1 - Siebel Loyalty Engine Crash - error SBL-OMS-00107: This operation is not allowed when there are no records displayed and SBL-OMS-00203: Error 7667927 invoking method "BusSvcMgrInit" for Business Service "LOY Processing Engine"




Applies to:

Siebel Universal Customer Master - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms


SIEBEL VERSION:
---------------
UCM via Siebel 8.1.1.1 with ACR437 implemented into the repository

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

When customer runs the "UCM Daily Publish" workflow, it is getting this error:


"( (0) err=2818155 sys=7667856) SBL-OMS-00107: Object manager error: ([2] Could not find 'Integration Object' named 'Contact'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
GenericLog GenericError 1 000006584df200a8:0 2011-06-12 09:46:22 ( (0) err=2818155 sys=8454659) SBL-OMS-00107: Object manager error: ([1] Contact is not a registered object type with UCM Publish Subscribe service(SBL-IAI-00515) (0x810203))
GenericLog GenericError 1 000006584df200a8:0 2011-06-12 09:46:22 ( (0) err=2818155 sys=6750370) SBL-OMS-00107: Object manager error: ([0] Error invoking service 'UCM Publish/Subscribe Service', method 'PublishMethod' at step 'UCM Daily Publish'.(SBL-BPR-00162) (0x6700a2))
GenericLog GenericError 1 000006584df200a8:0 2011-06-12 09:46:22".


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

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

1. Install and setup UCM via Siebel 8.1.1.1 with ACR437 implemented into the repository
2. Run a task using Workflow Process Manager component for the workflow process "UCM Daily Publish"

The error will occur during the task execution.

BEHAVIOR PATTERN:
-------------------------------
The behavior occurs consistently when running this workflow process.

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that the workflow should complete without error and publish the data out to subscribing system.

WHAT IS NOT WORKING/ACTUAL RESULTS:
-------------------------------------
The actual result is that the workflow task fails with error.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
------------------------------
Due to the error message, no messages are published out to subscribing systems.

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


"( (0) err=2818155 sys=7667856) SBL-OMS-00107: Object manager error: ([2] Could not find 'Integration Object' named 'Contact'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
GenericLog GenericError 1 000006584df200a8:0 2011-06-12 09:46:22 ( (0) err=2818155 sys=8454659) SBL-OMS-00107: Object manager error: ([1] Contact is not a registered object type with UCM Publish Subscribe service(SBL-IAI-00515) (0x810203))
GenericLog GenericError 1 000006584df200a8:0 2011-06-12 09:46:22 ( (0) err=2818155 sys=6750370) SBL-OMS-00107: Object manager error: ([0] Error invoking service 'UCM Publish/Subscribe Service', method 'PublishMethod' at step 'UCM Daily Publish'.(SBL-BPR-00162) (0x6700a2))
GenericLog GenericError 1 000006584df200a8:0 2011-06-12 09:46:22".

Cause


The cause of the error was due to providing the wrong value for the "UCM Batch Publish Subscribe" server job 'UCM Batch Object Type' parameter. Instead of providing the value as 'Contact' for the object type defined in the publish/subscribe view, the correct value should be 'CIFContact' for the IO name.


Once the value of "CIFContact" was provided for the 'UCM Batch Object Type' parameter, the error no longer occurred.

Solution


Instead of providing the value as 'Contact' for the object type defined in the publish/subscribe view, the correct value should be 'CIFContact' for the IO name.

Support has tested using CIFContact and once the IO name was provided for the 'UCM Batch Object Type' parameter, the error no longer occurred, the publishing functionality was performed as we can see the Business Service 'SyncPersonUCMJMSProducerService' method 'SyncPerson' was invoked in the log file.

Please try using parameter 'UCM Batch Object Type' = 'CIFContact' (no quotes)

---------------------------------------

I checked the Siebel UCM Guide to see if this is documented or not, found 3 places that reference this component and parameter:

1. Siebel Master Data Applications Reference for Industry Applications > Configuring Siebel Master Data Applications > Configuring Siebel Master Data Application Features > Configuring UCM Server Components for Data Management and Survivorship > To configure UCM Server Components for Data Management and Survivorship :- this table has a list of parameters for the component, one of them includes:

Parameter: UCM Batch Object Type
Default Value: Contact

2. Siebel Master Data Applications Reference for Industry Applications > Administering Siebel Master Data Applications > About System Publish and Subscribe Modes > Batch Mode:

[Last Update - SDQ] = the business component field name of the integration component field name specified by the SearchFieldName user property configured in the UCMBatchObjectType integration object. By default, the IO CIFContact has the IC property SearchFieldName = Last Update, which maps to the BC Contact's field Last Update - SDQ component field value [Last Update - SDQ]

3. Siebel Master Data Applications Reference for Industry Applications > Administering Siebel Master Data Applications > Running Data Management in Batch Mode > 6 In the Job Parameters list, add the following parameters for the component job:

Parameter Name: UCM Batch Object Type
Value: Select Contact or Account

None of the above mention that it is actually that IO name (CIFContact for contact and CIFAccount for account) that should be used instead of the "object type" name defined in the pubsub view.

Point #2 makes a reference to the IO CIFContact having an IC property that is used to search for the data to publish, but this is not clear. It seems to imply that CIFContact IO is used internally by EAI Siebel Adapter to search for the data, but it doesn't specifically instruct users that it is the IO name that should be used as opposed to the object type name/value provided in the pubsub view.

I have logged a documentation bug to clarify/indicate that 'UCM Batch Object Type' uses IO name and not the object type name in the pubsub view:

Bug 12684248 - UCM GUIDE HAS WRONG DOCUMENTATION FOR THE 'UCM BATCH OBJECT TYPE' PARAMETER VALUE

References

BUG:12684248 - UCM GUIDE HAS WRONG DOCUMENTATION FOR THE 'UCM BATCH OBJECT TYPE' PARAMETER VALU
NOTE:941755.1 - Where to find the Siebel CRM documentation





Applies to:

Siebel System Software - Version: 7.7.2 [18325] to 8.0.0.5 [20420] - Release: V7 to V8
All Platforms
This document was previously published as Siebel SR 38-1715068851.

Symptoms

We have configured password hashing as described in the Siebel Security Guide's section "Security Adapter Authentication: Configuring Password Hashing."  After restarting the server and gateway, we were able to successfully login using a dedicated client with the clear-text password.  However we are not able to connect using the web client and the following components were not running but had passed one or more of the errors listed below:

PDbXtract/DbXtract
SSEObjMgr_enu
WfProcBatchMgr
WfProcMgr
WfRecvMgr

SBL-DAT-00446, SBL-DCK-00164, SBL-GEN-04031, SBL-OMS-00102, SBL-OMS-00107, SBL-SEC-10018, SBL-SEC-10007, SBL-SVR-00040

Solution

Customer was implementing Password Hashing, and after changing parameter DSHashUserPwd in Server Data Source named subsystem to “TRUE” and restarting the Siebel environment, the following components did not start:

PDbXtract/DbXtract
SSEObjMgr_enu
WfProcBatchMgr
WfProcMgr
WfRecvMgr

WfRecvMgr, WfProcMgr, and WfProcBatchMgr had the following error messages:


SBL-SEC-10007: The password you have entered is not correct. Please enter your password again. (0x5a94))
SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)

SBL-SVR-00040: Internal: Informational, encrypted parameter. (0x5a8f))

SBL-OMS-00107: Object manager error: ([2] SBL-SVR-00040: Internal: Informational, encrypted parameter. (0x5a8f))
SBL-OMS-00107: Object manager error: ([1] SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)
ORA-01017: invalid username/password; logon denied

SBL-OMS-00107: Object manager error: ([0] SBL-SEC-10007: The password you have entered is not correct. Please enter your password again. (0x5a94))
SBL-OMS-00102: Error 23188 logging in to the application

SSEObjMgr had the following error messages:

SBL-DAT-00446: You have entered an invalid set of logon parameters. Please type in your logon parameters again.
SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)
ORA-01017: invalid username/password; logon denied


The above errors were resolved by setting the Password parameter for each component to the unhashed password for the SADMIN user and restarting the environment.  Further information is available in the Siebel Bookshelf > Security Guide > Security Adapter Authentication > Configuring Password Hashing.


Components PDbXtract (during server startup) and DbXtract (at component task start) had the following error message:

SBL-GEN-04031: Internal: Error occurred during base64 decoding.

Error message SBL-GEN-04031 in PDbXtract and DbXtract log files occur because the password length is greater than 21 characters. If SADMIN password has more than 21 characters, PDbXtract and DbXtract components will fail with the error message.

The SADMIN password was hashed using the RSA SHA-1 encryption algorithm. When using SADMIN as password in test environment, the hashed password contained 28 characters.  Since "SADMIN" is a fairly simple and short password, we would expect that most good passwords would result in RSA SHA-1 values that are too long. 
Change Request 12-SQ798U has been opened to address this Product Defect.

The workaround is to change the Hashing algorithm to use Siebel Hash instead of RSA SHA-1. Siebel Hash will encrypt passwords with a length smaller than RSA SHA-1 algorithm.  Please refer to the Security Guide for more information about how to change encryption algorithm.





Applies to:

Siebel CRM - Version: 8.1.1.2 and later   [Release: V8 and later ]
Information in this document applies to any platform.

Goal


Batch components are in unavailable status, eg:

Workflow Process Manager
ObjMgrLicense Error 1 00020da44c742d77:0 2010-08-24 16:58:22 (dmlicmgr.cpp (380)) SBL-DAT-00124: Unable to load licensed options configuration.

Please contact your systems administrator.
GenericLog GenericError 1 00020da44c742d77:0 2010-08-24 16:58:22 Object manager error: ([0] Unable to load licensed options configuration.

Please contact your systems administrator.(SBL-DAT-00124) (0x75007c))
GenericLog GenericError 1 00020da44c742d77:0 2010-08-24 16:58:22 ( (0) err=2818155 sys=7667836) SBL-OMS-00107: Object manager error: ([0] Unable to load licensed options configuration.


Solution


The cause is related to access privilege to these 2 files:
/siebel/siebsrvr/lib/options.bin
/siebel/siebsrvr/lib/sia_options.bin

Granting full read, write, execute (rwx) these 2 files to siebel owner and restarting the siebel server helps resolve the issue:
/siebel/siebsrvr/lib/options.bin
/siebel/siebsrvr/lib/sia_options.bin

keywords: options.bin, sia_options.bin, SBL-OMS-00107, SBL-DAT-00124





Applies to:

Siebel Loyalty Engine - Version: 7.7.2.4 SIA [18365] to 7.7.2.9 [18382] - Release: V7 to V7
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.4 [18365] FRA Travel
Database: Oracle 9.2.0.6
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2

This document was previously published as Siebel SR 38-2959756969.

Symptoms

SBL-DBC-00104, SBL-BPR-00162 The Loyalty Batch Engine tasks fail when the queue is empty i.e. there are no transactions to process.

ObjMgrBusServiceLog    InvokeMethod    4    0    2006-03-14 17:15:28    Business Service 'Workflow Process Manager' invoke method 'RunProcess' Execute Time: 4241.648 seconds.
ObjMgrBusServiceLog    InvokeMethod    4    0    2006-03-14 17:15:28    End: Business Service 'Workflow Process Manager' invoke method: 'RunProcess' at 37507ae8
GenericLog    GenericError    1    0    2006-03-14 17:15:28    Erreur resignalisée depuis le gestionnaire d'objets: ([0] Erreur lors de la récupération de l'enregistrement suivant depuis la base de données.(SBL-DBC-00104) (0x5614))
GenericLog    GenericError    1    0    2006-03-14 17:15:28    Erreur resignalisée depuis le gestionnaire d'objets: ([1] Erreur de mise en œuvre du service 'LOY Processing Engine', méthode 'ProcessBatch' à l"étape 'Invoke LPE in Batch Mode'.(SBL-BPR-00162) (0x80d8))
GenericLog    GenericError    1    0    2006-03-14 17:15:28    ( (0) err=4300107 sys=32984) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([1] Erreur de mise en œuvre du service 'LOY Processing Engine', méthode 'ProcessBatch' à l"étape 'Invoke LPE in Batch Mode'.(SBL-BPR-00162) (0x80d8))
GenericLog    GenericError    1    0    2006-03-14 17:15:28    ( (0) err=4300107 sys=22036) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([0] Erreur lors de la récupération de l'enregistrement suivant depuis la base de données.(SBL-DBC-00104) (0x5614))
GenericLog    GenericError    1    0    2006-03-14 17:15:28    (bsvcmgr.cpp (1339) err=4300203 sys=0) SBL-OMS-00203: Erreur 22036 d'appel de la méthode "RunProcess" pour le service commercial "Workflow Process Manager"
GenericLog    GenericError    1    0    2006-03-14 17:15:28    (bsvcmgr.cpp (1207) err=4300203 sys=0) SBL-OMS-00203: Erreur 22036 d'appel de la méthode "RunProcess" pour le service commercial "Workflow Process Manager"
The Loyalty Batch Engine tasks were failing once there was no data in the queue to be processed i.e. no transactions in queued status. If the tasks were restarted when data available to process, the tasks would process the data and then fail once the queue was empty again.

Cause

The batch engine was recorded against the realtime engine key in the List of Values.

Solution

It was determined that the problem was because the Loyalty LOV were incorrectly setup. The LOY_ENGINE_COMPONENT_KEYED type is used to record the batch engine components, and the LOY_ENGINE_COMPONENT_UNKEYED is used to record the realtime engine components. For example, in a standard install you should have two records:

Type / Value
LOY_ENGINE_COMPONENT_KEYED / LoyEngineBatch
LOY_ENGINE_COMPONENT_UNKEYED / LoyEngineRealtime

The batch engine was recorded against the realtime engine key. Once this was corrected the issue was resolved.











Applies to:

Siebel Server Sync - Microsoft Exchange Server - Version: 7.8.2.1 SIA [19216] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.1 [19216] Fin Svcs
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: IBM AIX 5L 5.2

This document was previously published as Siebel SR 38-3132687043.

Symptoms

SSSE does not sync users with email address containing apostrophe.
This is the error we found from the PIMSIEng log:

ObjMgrQueryLog    Warning    2    0    2006-08-25 03:37:13    (query.cpp (2417)) SBL-DAT-00501: Invalid search specification '[PIM User Identifier]='XX.O'YYY@zzz.com' AND [PIM Server Type]='Exchange 2000''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

PIMSIEngSvc    PIMSICompFatal    0    0    2006-08-25 03:37:13    (engmgrsvc.cpp (1375)) EngMgrService: Unable to dispatch extract request message to extract engine. (err: 0x569D).


ObjMgrBusServiceLog    Error    1    0    2006-08-25 03:37:13    (service.cpp (666)) SBL-DAT-00501: Invalid search specification '<?>'.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

GenericLog    GenericError    1    0    2006-08-25 03:37:13    Object manager error: ([0] Invalid search specification '<?>'.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501) (0x569d))

GenericLog    GenericError    1    0    2006-08-25 03:37:13    ( (0) err=4300107 sys=22173) SBL-OMS-00107: Object manager error: ([0] Invalid search specification '<?>'.

Cause

Customer reported that, SSSE does not sync users with email address containing apostrophe.

Comments: Siebel was able to reproduce the behavior internally. Particularly, the sync USERS whose email id contains apostrophe sign (for example “ssse'user04@siebel.com”) fails to synchronize.

Further, the following error message was noticed as well in the PIMSI Engine logs:-

ObjMgrQueryLog Warning 2 0 2006-08-31 17:55:20 (query.cpp (2409)) SBL-DAT-00501: Invalid search specification '[PIM User Identifier]='ssse'user04@siebel.com' AND [PIM Server Type]='Exchange 2000''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

Solution

Please note that currently there is no possible workaround for this reported issue. The only recommendation from Siebel is to not allow the apostrophe sign for the SSSE users email id.

Further, the following change request has been submitted for this issue.

Change Request: "CR # BUG 10512076  - SSSE fails to sync users with email addresses containing apostrophe sign."

References

BUG:10512076 - SSSE FAILS TO SYNC USERS WITH EMAIL ADDRESSES CONTAINING APOSTROPHE SIGN.



Applies to:

Siebel Server Sync - Microsoft Exchange Server - Version: 7.8.2.1 SIA [19216] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.1 [19216] Fin Svcs
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: IBM AIX 5L 5.2

This document was previously published as Siebel SR 38-3132687043.

Symptoms

SSSE does not sync users with email address containing apostrophe.
This is the error we found from the PIMSIEng log:

ObjMgrQueryLog    Warning    2    0    2006-08-25 03:37:13    (query.cpp (2417)) SBL-DAT-00501: Invalid search specification '[PIM User Identifier]='XX.O'YYY@zzz.com' AND [PIM Server Type]='Exchange 2000''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

PIMSIEngSvc    PIMSICompFatal    0    0    2006-08-25 03:37:13    (engmgrsvc.cpp (1375)) EngMgrService: Unable to dispatch extract request message to extract engine. (err: 0x569D).


ObjMgrBusServiceLog    Error    1    0    2006-08-25 03:37:13    (service.cpp (666)) SBL-DAT-00501: Invalid search specification '<?>'.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

GenericLog    GenericError    1    0    2006-08-25 03:37:13    Object manager error: ([0] Invalid search specification '<?>'.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501) (0x569d))

GenericLog    GenericError    1    0    2006-08-25 03:37:13    ( (0) err=4300107 sys=22173) SBL-OMS-00107: Object manager error: ([0] Invalid search specification '<?>'.

Cause

Customer reported that, SSSE does not sync users with email address containing apostrophe.

Comments: Siebel was able to reproduce the behavior internally. Particularly, the sync USERS whose email id contains apostrophe sign (for example “ssse'user04@siebel.com”) fails to synchronize.

Further, the following error message was noticed as well in the PIMSI Engine logs:-

ObjMgrQueryLog Warning 2 0 2006-08-31 17:55:20 (query.cpp (2409)) SBL-DAT-00501: Invalid search specification '[PIM User Identifier]='ssse'user04@siebel.com' AND [PIM Server Type]='Exchange 2000''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.

Solution

Please note that currently there is no possible workaround for this reported issue. The only recommendation from Siebel is to not allow the apostrophe sign for the SSSE users email id.

Further, the following change request has been submitted for this issue.

Change Request: "CR # BUG 10512076  - SSSE fails to sync users with email addresses containing apostrophe sign."

References

BUG:10512076 - SSSE FAILS TO SYNC USERS WITH EMAIL ADDRESSES CONTAINING APOSTROPHE SIGN.



Applies to:

Siebel Call Center - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms


When creating and generating a forecast on the server (instead of the client itself) the forecast remains with status "Pending".  This issue is only reproducible when generating forecast with a manager position which is not associated with SADMIN user.


Reproducible steps:

   1. Login with SADMIN user and create three employees and three positions:
  
  MANAGER
  EMPLOYEE1
  EMPLOYEE2
  
  2. Navigate to Admnistration Group -> Position and set MANAGER position as
  parent position of EMPLOYEE1 and EMPLOYEE2
  
  3. Navigate to Admninistration data -> Periods and create some periods of
  type Month
  
  4. Navigate to Revenues and create some revenues for the three employees
  with revenue date falling into the periods of time created in step 3
  
  
  5. Navigate to Administration Forecast screen and create a forecast serie as
  follow:
  
  Detail Depth: Summary Only
  
  Visibility: My revenues
  
  Interval Period Type: Month
  
  Summary Period Type: Month
  
  
  6. Select Forecast Series Dates and add the periods created in step 3
  
  7. Select Forecast Series Participants and add the MANGER position in the
  list.
  
  8. Navigate to Admnistration Application -> System preferences
  
  Set "Forecast: Use Server Task" preference to TRUE and logout.
  
  9. Enable the forecast manager component.
  
 10. Login as MANAGER employee, navigate to Forecast screen, and create a new
  forecats record.
  
  11.If it is not automatically selected, select the forecast serie created
  in step 1-7
  
  12. Select a period for the forecast record and Save the record.
  
  The forecast will be submitted to server, but it will remain in Pending
  status.
  The log shows errors:
  
SBL-DAT-00179: Invalid login position id '<?>'.
SBL-OMS-00107: Object manager error: ([0] Invalid login position id '<?>'.(SBL-DAT-00179)  SBL-OMS-00203: Error 7667891 invoking method "ForecastGenerate" for Business Service "Forecast 2000 Internal Service"

Cause


Behavior represents a product defect.


Solution

Bug: 12355431 was logged to address this defect.

References

BUG:12355431 - MANAGER FORECAST REMAIN IN PENDING STATUS ON SERVER
NOTE:476897.1 - Siebel Forecasting Forecast Service Manager Server Component




Applies to:

Siebel Reports - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

When running reports from a Object Manager using a language other than the base language in the enterprise there may be errors reported when running Siebel BI Publisher reports.

Once the report request has been submitted a generic error will appear in a dialog as follows (in the language native to the requesting Object Manager):
Erreur <?> d'appel de la m�thode "<?>" pour le Business Service "<?>" (SBL-OMS-00203)

Cause

This behavior can occur in environments in which language specific PDQs have been implemented following the instructions provided in 'Document 477073.1Can You Have Different PDQs for Each Language in a Multilingual Environment?'.

The behavior occurs because the XMLPReportServer runs the report request in it's originally installed language (i.e. the language set against the XMLPReportServer component and therefore the base language), rather than the language of the requesting Object Manager and that which is included in the report request.

As the initially reported error is generic in nature this error is suspected then a review of the XMLPReportServer logs with increased logging in place will show evidence of the following additional errors :

GenericLog GenericError 1 000000044c180f68:0 2010-06-16 09:41:27 Object manager error: ([0] An error setting the named query has occurred.
Please execute another query or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00312) (0x750138))
GenericLog GenericError 1 000000044c180f68:0 2010-06-16 09:41:27 ( (0) err=2818155 sys=7668024) SBL-OMS-00107: Object manager error: ([0] An error setting the named query has occurred.
Please execute another query or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00312) (0x750138))
GenericLog GenericError 1 000000044c180f68:0 2010-06-16 09:41:27 (bsvcmgr.cpp (1384) err=2818251 sys=0) SBL-OMS-00203: Error 7668024 invoking method "GenerateReport" for Business Service "XMLP Driver Service"

in addition the named query error will also appear just below a query which is being run against the S_APP_QUERY table in some circumstances as follows :

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27 SELECT statement with ID: 130B3770
SELECT
T1.CONFLICT_ID,
CONVERT (VARCHAR (10),T1.LAST_UPD, 101) + ' ' + CONVERT (VARCHAR (10),T1.LAST_UPD, 8),
CONVERT (VARCHAR (10),T1.CREATED, 101) + ' ' + CONVERT (VARCHAR (10),T1.CREATED, 8),
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.CACHE_RSLT_FLG,
T1.DESC_TEXT,
CONVERT(NVARCHAR(2000),SUBSTRING(T1.QUERY_STRING, 1, 4000)),
T1.OWNER_ID,
CAST(? AS VARCHAR(128))
FROM
dbo.S_APP_QUERY T1
WHERE
((T1.OWNER_ID = ? OR T1.PRIV_FLG = N'N') AND
(T1.LANG_ID = ?)) AND
(T1.NAME = ? AND T1.DESC_TEXT = ?)
ORDER BY
T1.NAME, T1.DESC_TEXT

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27 Bind variable 1: XMLPReportServer,ssia81,22020098,SADMIN,000000044c180f68:0,Account,Query List,

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27 Bind variable 2: 0-1

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27 Bind variable 3: ENU

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27 Bind variable 4: Account

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27 Bind variable 5: FRA All Account

ObjMgrSqlLog Debug 5 000000044c180f68:0 2010-06-16 09:41:27 User search spec: ='Account'
AND ='FRA All Account'

ObjMgrSqlLog Debug 5 000000044c180f68:0 2010-06-16 09:41:27 Named search [VisibilitySearch]: [Owner Id] = '0-1' OR [Private] = 'N'

ObjMgrSqlLog Debug 5 000000044c180f68:0 2010-06-16 09:41:27 Named search [System Search]: [Lang Id]=Language()

ObjMgrSqlLog Debug 5 000000044c180f68:0 2010-06-16 09:41:27 User sort spec: Business Object, Description

ObjMgrSqlLog Debug 5 000000044c180f68:0 2010-06-16 09:41:27 System sort spec:

ObjMgrSqlLog Debug 5 000000044c180f68:0 2010-06-16 09:41:27 sscfom +0x5736f = CSSQueryList::SqlExecute() +0x10f
sscfom +0x35fb6 = CSSBusComp::Execute() +0x7e6
sscfom +0x571e0 = CSSQueryList::PositionOnQuerySpec() +0x150
sscfom +0x5973c = CSSQueryList::GetQuerySpec() +0x3c
sscfom +0x53343 = CSSBusObj::SetNamedQuery() +0x83
SSCAEISA +0x7d63 = CSSEAIDateTimeCnvUtil::~CSSEAIDateTimeCnvUtil() +0x5413
SSCAEISA +0x1cfe1 = CSSEAIDateTimeCnvUtil::~CSSEAIDateTimeCnvUtil() +0x1a691
SSCAEISA +0x1e815 = CSSEAISiebelAdapterService::DoInvokeMethod() +0x575
sscfom +0x1880a = CSSService::InvokeMethod() +0x1ba
SSCAXMLPSV +0x18d28 = CSSXMLPDataSvc::IntObjToDoc() +0x688
SSCAXMLPSV +0x19d9c = CSSXMLPDataSvc::GetDataAsBinary() +0x18c
SSCAXMLPSV +0x1a165 = CSSXMLPDataSvc::DoInvokeMethod() +0x95
sscfom +0x1880a = CSSService::InvokeMethod() +0x1ba
SSCAXMLPSV +0x4267 = CSSXMLPDriverSvc::ProcessRequest() +0x2d7
SSCAXMLPSV +0x3450 = CSSXMLPDriverSvc::DoInvokeMethod() +0x280
sscfom +0x1880a = CSSService::InvokeMethod() +0x1ba
sssabsvm +0x2a92 = LessComparison::operator()() +0x13f2
sssabsvm +0x422e = CreateSmiMThreadObj() +0xaae
siebmtshmw +0x1a2d9 = GetSmiTaskAPI() +0x1059
siebmtshmw +0x1a973 = GetSmiTaskAPI() +0x16f3
siebmtshmw +0x1b444 = GetSmiTaskAPI() +0x21c4
siebmtshmw +0x1c4f4 = GetSmiTaskAPI() +0x3274
siebmtshmw +0x1c881 = GetSmiTaskAPI() +0x3601
siebmtshmw +0x15e65 = SmiBeginTrace() +0x3155
siebmtshmw +0x1741f = GetSmiWorkQObj() +0x148f
siebmtshmw +0xc7c7 = SmiCleanupDetTask() +0x3bd7
sslcosd +0x2132 = OSDThreadPrivIsInit() +0x1d2
sslcosd +0x21bc = OSDThreadPrivIsInit() +0x25c
MSVCR71 +0x9565 = endthreadex() +0xa0
kernel32 +0x2482f = GetModuleHandleA() +0xdf


ObjMgrSqlCursorLog Prepare 5 000000044c180f68:0 2010-06-16 09:41:27 Begin: PrepareStmt for Sql Cursor at 130b3770

ObjMgrSqlCursorLog Prepare 5 000000044c180f68:0 2010-06-16 09:41:27 End: PrepareStatement for Sql Cursor at 130b3770

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27
***** SQL Statement Prepare Time for SQL Cursor with ID 130B3770: 0.004 seconds *****


ObjMgrSqlLog SqlTag 2 000000044c180f68:0 2010-06-16 09:41:27 Begin: Execute SqlObj 'Query List' at 130b2d88 with SqlTag=XMLPReportServer,ssia81,22020098,SADMIN,000000044c180f68:0,Account,Query List,

ObjMgrSqlCursorLog Execute 5 000000044c180f68:0 2010-06-16 09:41:27 Begin: ExecuteStmt for Sql Cursor at 130b3770

ObjMgrSqlCursorLog Execute 5 000000044c180f68:0 2010-06-16 09:41:27 End: ExecuteStmt for Sql Cursor at 130b3770

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27
***** SQL Statement Execute Time for SQL Cursor with ID 130B3770: 0.037 seconds *****


ObjMgrSqlLog SqlTag 2 000000044c180f68:0 2010-06-16 09:41:27 End: Execute SqlObj with SqlTag

ObjMgrSqlObjLog Execute 4 000000044c180f68:0 2010-06-16 09:41:27 End: execute SqlObject at 130b2d88

ObjMgrSqlCursorLog Fetch 5 000000044c180f68:0 2010-06-16 09:41:27 Begin: Fetch for Sql Cursor at 130b3770

ObjMgrSqlCursorLog Close 5 000000044c180f68:0 2010-06-16 09:41:27 Begin: Close Sql Cursor at 130b3770

ObjMgrSqlCursorLog Trace 5 000000044c180f68:0 2010-06-16 09:41:27 SQL Cursor with ID 130B3770 Buscomp: Query List, Forward Only: 0, Fetch Rows: 0, Fetch All Time: 0.000 seconds.

ObjMgrSqlCursorLog Close 5 000000044c180f68:0 2010-06-16 09:41:27 End: Close Sql Cursor at 130b3770

ObjMgrSqlCursorLog Fetch 5 000000044c180f68:0 2010-06-16 09:41:27 End: Fetch for Sql Cursor 130b3770

ObjMgrSqlLog Detail 4 000000044c180f68:0 2010-06-16 09:41:27
***** SQL Statement Initial Fetch Time for SQL Cursor with ID 130B3770: 0.002 seconds *****


ObjMgrMiscLog Error 1 000000044c180f68:0 2010-06-16 09:41:27 (busobj.cpp (2874)) SBL-DAT-00312: An error setting the named query has occurred.

Please execute another query or ask your systems administrator to check your application configuration if the problem persists.

EAISiebAdptPerf EAISiebAdptPerfStat 3 000000044c180f68:0 2010-06-16 09:41:27 QueryPage|0|3734


EAISiebAdpt EAISiebAdptErr 1 000000044c180f68:0 2010-06-16 09:41:27 [0] An error setting the named query has occurred.

Please execute another query or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00312) (0x750138)

EAISiebAdpt EAISiebAdptTrcDebug 5 000000044c180f68:0 2010-06-16 09:41:27 Finished execution of QueryPage method

Note that although the request was from an FRA Object Manager and using a language specific FRA PDQ (FRA All Accounts) the Bind Variable 3: shows 'ENU' as the language being searched for the query name.

Solution

A Change Request #10595312 "XMLPReportServer is unable to find language-specific PDQs" has been raised for this behavior and will be reviewed, analyzed, and prioritized for possible inclusion in a future release of the application.





Applies to:

Siebel Workflow - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms


====Issue Clarification====

On : 8.1.1.1 SIA [21211] version, Siebel Workflow

Workflow Process Manager is failing in SIT Environment while the same is running fine in Development Environment.

the following error occurs.

ERROR
-----------------------
Object manager error: ([0] Could not find 'Business Object' named 'Investor Account'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
SBL-OMS-00107: Object manager error: ([0] Could not find 'Business Object' named 'Investor Account'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
SBL-OMS-00203: Error 7667856 invoking method "RunProcess" for Business Service "Workflow Process Manager"
SBL-OMS-00203: Error 7667856 invoking method "RunProcess" for Business Service "Workflow Process Manager"
SBL-OMS-00203: Error 7667856 invoking method "RunProcess" for Business Service "Workflow Process Manager"

Cause

The problem is observed to happen only when running on the wfprocmgr component but not on object manager. Further to the siebns.dat file as follows, the component are running accessing different srf file :

[/enterprises/Siebel/component groups/eAutomotive/components/edealerObjMgr_enu/parameters/CFGRepositoryFile]
Persistence=full
Type=string
Value="siebel_sia.srf"
Length=28
:
[/enterprises/Siebel/component groups/Workflow/components/WfProcMgr/parameters/CFGRepositoryFile]
Persistence=full
Type=string
Value="siebel.srf"
Length=20

This suggests that 'Investor Account' does not exist in the siebel.srf file that is accessed by the wfprocmgr component.

Solution

Customer resolved the problem after compiling the object on the siebel.srf that is assessed by the wfprocmgr component.




Applies to:

Siebel CRM - Version: 7.7.2.1 SIA [18353] - Release: V7

Information in this document applies to any platform.

Symptoms


Fresh installed Siebel server on windows machine for document server. It does not connect.
The following error appears in the doc server component and Server table cleanup:

GenericLog GenericError 1 0 2009-05-18 10:46:51 ( (0) err=4300107 sys=23183) SBL-OMS-00107: Error del administrador de objetos: ([1] SBL-SEC-10018: Se ha producido un error de base de datos Oracle.

Continúe o solicite al administrador del sistema que verifique la configuración de la aplicación si el problema continúa.(SBL-DBC-00107)
ORA-00604: error occurred at recursive SQL level 1
ORA-00026: missing or invalid session ID
ORA-06512: at line 40

Cause


There was some incorrect setting for Database connectivity

Solution


The following was done to resolve it:

1) in the tnsnames.ora , we removed the extension .VESPUCIOSUR.CL changing from CRM2.VESPUCIOSUR.CL to CRM2.

2) we changed the same for the odbc in windows machine, leaving only CRM2

3) in the Enterprise Profile , changed the DSConnectString from SIEBELDB to CRM2
SIEBELDB is the Oracle instance name and this parameter should point to the alias from the tnsnames.ora

4) there was an entry on the tnsnames.ora with the same name as the ODBC. We removed this entry since it is unecessary and it can affect the correct operation of the application

After that , Siebel server came up fine. 




Applies to:

Siebel Communications, Media and Energy CRM - Version: 8.0.0.2 [20412] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

During List Import process the following errors arise:

"Object manager error: ([0] You cannot currently update this record. Please check the No Update properties on the Applet, Business Component, and Link.(SBL-DAT-00284)"

"SBL-OMS-00107: Object manager error: ([0] You cannot currently update this record. Please check the No Update properties on the Applet, Business Component, and Link.(SBL-DAT-00284)"

The issue has been observed in 8.0.0.2 SIA [20412] environment.

The specific of the environment is that the there Siebel Administrator is not SADMIN but different user.

The following user properties have been set for "List Mgmt Lists" Business Component:
1) "SLM Disable Update/Delete Check" = TRUE
2) "SLM Admin Login" = the name of Siebel Administrator user.

Cause

The behavior was caused by wrong class of the "List Mgmt Lists" BC.

"List Mgmt Lists" BC has been compared with the standard "List Mgmt Lists" BC.

In standard Vertical environment (SIA), "List Mgmt Lists" BC has the class: CSSBCFINSListMgmtList.
The BC in environment facing the SBL-DAT-00284 error message has the class: CSSBCListMgmtList.
Kindly note that CSSBCListMgmtList is the standard class for "List Mgmt Lists" BC in Horizontal implementation.

Solution

Changing the class of the "List Mgmt Lists" BC to CSSBCFINSListMgmtList resolved the behavior and list import process completed successfully.

Thank you,









 

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)