SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Applies to:

Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI


Version:Siebel 8.1


Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Scope

This document is informational and intended for any user.

SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Explanation

Each integration component should have only valid children components, consistent with the integration object definition. There was a component type found that is not expected to be a child of another component.

Corrective Action

Check whether the data contains valid integration component structure


















Applies to:

Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI


Version:Siebel 8.1


Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Scope

This document is informational and intended for any user.

SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Explanation

Each integration component should have only valid children components, consistent with the integration object definition. There was a component type found that is not expected to be a child of another component.

Corrective Action

Check whether the data contains valid integration component structure


















Applies to:

Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI


Version:Siebel 8.1


Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Scope

This document is informational and intended for any user.

SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Explanation

Each integration component should have only valid children components, consistent with the integration object definition. There was a component type found that is not expected to be a child of another component.

Corrective Action

Check whether the data contains valid integration component structure


















Applies to:

Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI


Version:Siebel 8.1


Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Scope

This document is informational and intended for any user.

SBL-EAI-04008: Integration component type '%1' is not a valid child type for component type '%2'

Explanation

Each integration component should have only valid children components, consistent with the integration object definition. There was a component type found that is not expected to be a child of another component.

Corrective Action

Check whether the data contains valid integration component structure


תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

Access control with EAI Siebel Adapter

User properties in siebel are as thrilling as gadgets in bond movie. Yes, we can define visibility view modes at integration object level. "ViewMode" user property defined at IC level does the magic. This user property can take different values, as defined by LOV type " REPOSITORY_BC_VIEWMODE_TYPE" . However,as i keep saying the beauty of siebel is the flexibility it provides. One can even use "ViewMode" input argument in the Query/Query Page methods of " EAI Siebel Adapter " business service. However this argument is not exposed in the tools but one can use it. We can see presence of this argument in Query method of another business service " XMLP Siebel Adapter ", which is used in the BIP reporting. This BS can also be used to extract the siebel message. Happy Crunching!!
המשך לקרוא

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
המשך לקרוא

SBL-SVC-00281

Applies to: Siebel CRM - Version 8.0.0.5 [20420] - DO NOT USE and later Information in this document applies to any platform. ***Checked for relevance on 24-OCT-2012*** Symptoms Siebel 8.0.0.5 is trying to access the keydbmgr prior to upgrading to the Siebel Strong Encryption Pack. The utility appears to do its initial load properly, but after they press the "c" button to continue they get an error about not being able to decrypt the password. Inspection of the keydbmgr.log shows the following two errors: Decrypt failed with 10879085. Error during encryption or decryption operation by the RC2 Encryptor. (keymanager.cpp (268)) SBL-SVC-00281: Internal: error occurred during password decryption. Desired behavior is that the keydbmgr would present the password prompt and then allow access to the utility menu. Cause Mismatch between keyfile.bin file in the environment (which is standard vanilla) and the S_APP_VER.ENCRYPT_PWD_FL_KEY which should be NULL in this case but has a val...
המשך לקרוא