ERROR CODES: 2011

SBL-EAI-50187: The file '%1' does not exist.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50187: The file reference '%1' does not exist.
ScopeThis document is informational and intended for any user.
SBL-EAI-50187: The file reference '%1' does not exist.ExplanationThe specified file cannot be found on the file system.
Corrective ActionCheck whether the specified file exists and whether the user temporary directory is defined and accessible.

Applies to: Siebel System Software - Version: 8.0 [20405] and later [Release: V8 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405] FRA Pub Sect
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-3474521161.
***Checked for relevance on 22-NOV-2010***
SymptomsHave a Siebel Web Service that has a file (buffer) as an input parameter.
Push a file bigger thant 10 Kilobyte and get the following error :
Erreur lors du traitement de l'argument http://www.siebel.com/xml/RBQ%20Form%20Instance%20Attachment:ListOfRBQFormInstanceNumerisation de l'opï¿½ration IncrireDocument(SBL-EAI-04316)

in english
SBL-EAI-50187 The file 'D:\sba80\siebsrvr\temp\1-IG49_0.tmp'does not exist.
CauseWS-Security is used to pass security credentials in the SOAP header. When a SOAP / inline XML message reaches Siebel the SOAP header is parsed and temporary attachment files are created.

After the authenticate event the EAI OM runs the ReLogin event to disconnect the anon user and connect the SOAP header user. During this event the EAI OM deletes the temporary files.

When the XML Converter is invoked to convert the XML message and attachment temp file into property set the message error SBL-EAI-50187 is experienced, crashing the EAI OM component.

The Change Request# 10531649 was created to address this issue on future releases.
Solution

Since customer was not allowed to pass security credentials in the URL it was suggested to use the Session Management instead of WS-Security.

Reference Bookshelf 8.0 > Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > About Siebel Authentication and Session Management SOAP Headers

This issue has been fixed in 8.0.0.6 Fix Pack and 8.1.1.1 Fix Pack
ReferencesNOTE:745864.1 - EAI File Streaming is NOT supported before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack

SBL-EAI-50177: Error getting the size of file reference file '%1'

SBL-EAI-50176: Error writing to file reference file '%1'

Applies to: Siebel CRM - Version: 8.0 [20405] to 8.1.1 [21112] - Release: V8 to V8
Information in this document applies to any platform.
***Checked for relevance on 23-NOV-2010***
SymptomsThe "Error writing to file reference 'C:\sba80\siebsrvr\temp\1-18RZ0U_0.tmp' (SBL-EAI-50176)" error reported by the "IntObjHierToXMLDo" method of the "EAI XML Converter", broke the integration process, worked well before.
Cause
The "temp" folder's file system on the affected Siebel Server was likely lack of free space.

Since Siebel CRM Release 8.0, the internal memory management mechanism has been significantly improved for optimized RAM usage. The EAI XML Converter BS and other EAI business services which are manipulating with property set hierarchies and XML Documents are using now the "temp" sub-folder of the Siebel Product installation root to store temporary XML file references if the parsed or produced document size exceeds the 50Kb size. So the big XML documents can be efficiently passed between an XML Converter and an EAI Transport without its intermediate loading it into memory buffer.

Normally, all temporary files are automatically removed once the BS is unregistered (unloaded) or Siebel Session is completed . However some orphan files could remain there in case of unexpected Siebel CRM Application crash and termination.
Solution
Monitor the space usage in the "temp" folder of each Siebel Server installation
and periodically clean-up .tmp files from the "temp" sub-folder when the accordant Siebel Server is shutdown.

Product Enhancement Request CR # BUG 10566911 "Enable parameterization of XML file reference creation" has been logged to address the need in parametrisation of the XML file referencing feature (e.g. either increase the XML document file size threshold or turn it off or change the path to the temporary folder). This will be reviewed and evaluated for a possible implementation in future releases.
ReferencesBUG:10566911 - ENABLE PARAMETERIZATION OF XML FILE REFERENCE CREATION.
NOTE:745864.1 - EAI File Streaming is NOT supported before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack

Applies to: Siebel CRM - Version: 8.1.1 SIA [21111] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsDuring 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 file

ObjMgrLog 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'.

CauseIn 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.
SolutionThe 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, as discussed in :-

The "Error writing to file reference '...\siebsrvr\....tmp (SBL-EAI-50176)'" is raised from "IntObjHierToXMLDoc" method of the "EAI XML Converter" BS when producing large XML document (Doc ID 824888.1)

3. Check that no other processes (e.g. anti-virus software) are trying to access the files being written to by Siebel.

ReferencesNOTE:824888.1 - The "Error writing to file reference '...\siebsrvr\....tmp (SBL-EAI-50176)'" is raised from "IntObjHierToXMLDoc" method of the "EAI XML Converter" BS when producing large XML document

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50176: Error writing to file reference '%1'.
ScopeThis document is informational and intended for any user.
SBL-EAI-50176: Error writing to file reference '%1'.ExplanationUnable to write to temporary file.
Corrective ActionCheck whether the specified file exists and is writable.

Applies to: Siebel CRM - Version: 8.0.0.2 [20412] to 8.0.0.5 [20420] - Release: V8 to V8
Information in this document applies to any platform.
***Checked for relevance on 22-NOV-2010***
DescriptionEAI File Streaming is NOT supported on Siebel before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack
There are known issues in using the new "EAI File Streaming" that causes failure in specific cases.

One example is BUG :12-1LTG2F6 described in "Problem with file attachment size with EAI object manager (Doc ID 496506.1)"
Please do not use it prior to 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack
Likelihood of OccurrenceMay happen if "LargeFileChunkingEnabled" is explicitly set to TRUE in the [Application] section of eapps.cfg and a large dataset is returned from an inbound web service call.
Possible SymptomsEAIFileAttachments EAIFileAttachmentDebug 5 00000af848f814f2:0 2008-10-18 11:35:28 Getting file reference manager Session Global by key 'FileReferenceManager'
EAIFileAttachments EAIFileAttachmentDetail 4 00000af848f814f2:0 2008-10-18 11:35:28 New large file reference is created - '/sbsiebcrmtest/siebsrvr/temp/1-DN5R_0.tmp'
EAIFileAttachments EAIFileAttachmentDebug 5 00000af848f814f2:0 2008-10-18 11:35:28 New large file reference is registered - '/sbsiebcrmtest/siebsrvr/temp/1-DN5R_0.tmp'
ObjMgrLog Error 1 00000af848f814f2:0 2008-10-18 11:35:28 (filerefutil.cpp (249)) SBL-GEN-10103: Error opening specified file
ObjMgrLog Error 1 00000af848f814f2:0 2008-10-18 11:35:28 (filerefutil.cpp (249)) SBL-EAI-50176: Error writing to file reference
and
Erreur lors du traitement de l'argument http://www.siebel.com/xml/RBQ%20Form%20Instance%20Attachment:ListOfRBQFormInstanceNumerisation de l'opï¿½ration IncrireDocument(SBL-EAI-04316)

SBL-EAI-50187 The file 'D:\sba80\siebsrvr\temp\1-IG49_0.tmp'does not exist
Workaround or Resolution
Please ensure "LargeFileChunkingEnabled" is explicitly set to FALSE in the [Application] section of eapps.cfg. and restart the web server.

Or please apply 8.0.0.6 Fix Pack or higher or 8.1.1.1 Fix Pack or higher.

Related

Products

Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM

Keywords

WEB SERVICES; INBOUND; SERVICES

Errors

SBL-EAI-50176; SBL-EAI-04316; SBL-EAI-50187; SBL-GEN-10103; ERROR 1

SBL-EAI-50175: Error reading from file reference file '%1'

SBL-EAI-50174: Error deleting file reference file '%1'

SBL-EAI-50173: Error creating file reference file '%1'

SBL-EAI-50172: The Workflow Process '%1' is either not active or its status is not "Completed" and cannot be exposed as a Web Service.

SBL-EAI-50171: The Business Service '%1' is not active. Please activate it first.

SBL-EAI-50170: The Business Service %s does not contain any method that can be exposed.

SBL-EAI-50169: No method was selected to get exposed. Please selecte the methods to be exposed.

SBL-EAI-50168: The following selected methods either have arguemnt(s) of unsupported type hierarchy without an Integration Object specified or do not have any argument at all.

SBL-EAI-50167: The selected Workflow Process contains process properties of hierarchy type without Integration Object name specified. This is not supported in Siebel Inbound Web Service.

SBL-EAI-50166: The web service URL is not valid. Please replace and with the appropriate values.

SBL-EAI-50165: The operation name '%1' is not unique. Please enter a new one or use the one generated for you.

SBL-EAI-50164: Please enter a operation name for the web service.

SBL-EAI-50163: Please enter a valid path for the wsdl file.

SBL-EAI-50162: WSDL cannot be generated for web service '%1'. The Workflow Process '%1' may not be activated and caused the WSDL generation to fail.

SBL-EAI-50161: The Business Service or Workflow Process '%1' has already been deployed as a web service of namespace '%2'.

SBL-EAI-50160: Cannot find integration component field definition (Integration Component '%1', Integration Object '%2') corresponding to the property '%3' (Property Set Type '%4')

SBL-EAI-50157: Error converting property set hierarchy to integration object hierarchy. Cannot find integration component definition correspoding to property set with type '%1'

SBL-EAI-50156: Cannot find definition for integration component field '%1' in Integration Component '%2' (Integration Object '%3')

SBL-EAI-50152: Cannot have more than one active Id specified on Integration Object Instance, current active Id is '%1'

SBL-EAI-50145: No record retrieved corresponding to the business component '%1' and Id '%2'

SBL-EAI-50143: During Business Component Query, error returned '%1'

SBL-EAI-50134: Integration object instance '%1' did not have a valid root component.

SBL-EAI-50120: Please examine the server log file '%1'.

SBL-EAI-50129: Could not create state, No Active ID was found on the leaf level in Integration Object Instance '%1'

SBL-EAI-50128: No rows retrieved corresponding to the business component '%1' and Id '%2'

SBL-EAI-50127: No rows retrieved corresponding to the business component '%1'

SBL-EAI-50126: Multiple matches found for record using search specification '%2' in the business component '%3'.

Related

SBL-EAI-50125: Could not create state, No Active ID was specified in Integration Component '%1'

SBL-EAI-50124: Could not obtain Business Object; No external name set on Integration Object

SBL-EAI-50123: The integration object '%1' is inactive. Please activate it first.

SBL-EAI-50122: Required data is missing in the integration object '%1' definition: the '%2' for integration component '%3' has to be set.

SBL-EAI-50121: The %1 is missing in the input parameters for method %2.

SBL-EAI-50119: Integration Object '%1' contains an Integration Component with invalid XML tags.

SBL-EAI-50118: Integration Component '%1' in Integration Object '%2' contains Integration Fields with invalid XML tags.

SBL-EAI-50117: The XML tag '%1' for Integration Object '%2' contains invalid character.

SBL-EAI-50116: The XML tag '%1' for Integration Component Field '%2' contains invalid character.

SBL-EAI-50115: The XML tag '%1' for Integration Component %2 contains invalid character '%3'.

Related

Products

Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software

SBL-EAI-50114: Ingegration Components have to form a tree. The following components form a loop: %1. %1.

SBL-EAI-50113: Ingegration Components have to form a tree. There should be only one root component. Instead the following components do not have a Parent Component: %1.

SBL-EAI-50112: Required data is missing in the integration object '%1' definition: '%2' has to be set.

SBL-EAI-50111: An invalid EAI Message was received. Please check your configuration

SBL-EAI-50110: The input parameter %1 is missing or invalid for the Integration Ojbect Definition Wizard Service.

SBL-EAI-50109: The Project %1, which the Integration Object belongs to is not locked.

SBL-EAI-13011: Field '%1' in the integration component '%2' contains value '%3', which is longer than allowed length of %4 characters.

Applies to: Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Life Sci
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP 9000 Series HP-UX

This document was previously published as Siebel SR 38-1568626871.
SymptomsSBL-EAI-13011
When I create a Deployment Project of type "AssignGroup" I can export the Assignment Rules out of Siebel in a Deployment Session. However, when I attempt to reimport the rules using a Vanilla SRF, I get an error stating that the Party name exceeds 30 characters for one of the position candidates.

Error Message:
We detected an Error which may have occurred for one or more of the following reasons:
Field 'Party Name' in the integration component 'Assignment Group Position' contains value 'Salesrep1 - Hospital - AssgnMgr Test', which is longer than allowed length of 30 characters.(SBL-EAI-13011)

I've updated both the "UDA Assignment Rule Groups" and "UDA Assignment Rules" integration objects --> Assignment Group Position --> Party Name field's External Length property from "30" to "150". Note that the column it maps to is also 150 length, S_PARTY.NAME. After recompiling I was able to import the assignment rules as expected.

At your earliest convenience please confirm:
1) Was the "External Length" property set to "30" for any particular reason?
2) Is the workaround supported by Siebel?
3) Can I expect this repository change to be in a future Siebel release?

Thank you
SolutionMessage 1For the benefit of other readers:
Customer is using Application Deployment Manager (ADM) to import AssignGroup data using Deploy from file option and getting error
â€œField 'Party Name' in the integration component 'Assignment Group Position' contains value 'Salesrep1 - Hospital - AssgnMgr Test', which is longer than allowed length of 30 characters.(SBL-EAI-13011)â€

Resolution
Customer updated both the "UDA Assignment Rule Groups" and "UDA Assignment Rules" Integration Objects --> Assignment Group Position --> Party Name field's External Length property from "30" to "150". Note that the column it maps to is also 150 length, S_PARTY.NAME.
After doing the above changes and recompiling the changes the problem was resolved.
Similar problem was also found on Integration Object - UDA Assignment Rules and UDA Assignment Rule Groups
for Integration Components (IC) Assignment Group Organization for both the IO's. It is suggested to change the length from 30 to 150 for Party Name field for both the Integration Components.
A Change Request # 12-Q3KZZH was logged to address this Product Defect.

Thank you,

Siebel Technical Support
Keywords: ADM, ADM and AssignGroup, Application Deployment Manager, ADM and Assignment

Applies to: Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-1547599769.
SymptomsSBL-EAI-13011, SBL-EAI-04397
Hi,

The ADM tool was working well for migrating Views and Responsibilities untill we applied Siebel 7.7.2 patch. Here we are observing that View names with less than 50 characters have no issues but more than 50 characters are throwing out the attached error. Have included the XML files and screen shots of the error messages.

Thanks.
SolutionMessage 1For the benefit of other users, ADM uses vanilla "UDA View Access" Integration Object to deploy views. In 7.7.1 if you create a new view named "Siebel Account Invoice Adjustment Request Items View (eService)" in Tools, by using "Copy Record" on vanilla view named "Account Invoice Adjustment Request Items View (eService)". This view name is 62 characters (with spaces); you are able to deploy it successfully. After applying 7.7.2 patch, you are unable to deploy it.

In customerâ€™s case, they got 2 different errors:

1. Single file import:

No use key can be used for the Integration Component instance 'Feature Access'.(SBL-EAI-04397)

2. Multiple files import through workflow process, a different error:

Field '<?>' in the integration component '<?>' contains value '<?>', which is longer than allowed length of '<?>' characters.(SBL-EAI-13011)

The problem is identified to be as follows:
=====
The problem is with the external length of the Name field of "Feature Access" Integration component. Should be set to column length of 75 instead of BC Text Length of 50.
=====

The Change Request CR# 10482048 has been logged to address this issue, and it has been fixed in Siebel 7.8.

...continued in next activity...
Message 2The workaround is the following:

In Siebel Tools:
1. Lock the project "EMT Objects".
2. Navigate to Integration Object > choose "UDA View Access" > Integration Component > choose "Feature Access" > Integration Component Field > choose "Name" field. Change "External Length" property from 50 to 75.
3. Recompile client srf, and copy the recompiled srf to Siebel Server side.

And after that, the import works fine on 7.7.2 for the view with name = 62 characters. This should be the only change required.

Another property for this Integration Component Field is "Length"; it can be left as 50. We don't need to change "Text Length" property on Name field of "Feature Access" Business Component either.

keyword search: SBL-EAI-13011

Applies to: Siebel eConfigurator - Version: 7.8.2.4 [19224] - Release: V7

Information in this document applies to any platform.
GoalWhen entering more than 100 characters in a product attribute within the configurator the following error occurs:
Error:"Error invoking service "ISS Copy Service", method "StoreEAI" at step "Save Instance". (SBL-BPR-00162)
Field "Value" in the integration component "XA" contains value "Long Value.....", which is longer than allowed length of 00 characters. (SBL-EAI-13011)"
How to define a Product Attribute to store more than 100 characters?
SolutionFor the benefit of other readers,

Please note, 250 is the default size of the column definition in the database. Theoretically you can increase this definition as well as the definition of the according business components and integration objects. However, this may have adverse impact to your application. Therefore, in order to have more than 250 characters I strongly recommend to consult with Expert Services in order to find the best solution for your business needs.

Currently it is possible to increase the attribute text length up to 250 characters. For a detailed description how to achieve this, please refer to the following posting:
HOW TO: How can the size and the amount of text that can be entered into an attribute edit box within an eConfigurator selection page be adjusted? (Doc ID 477258.1)

The same change has to be done in the "XA" integration component of "7.7 Quote Integration Object" integration object.

recompile .srf

NOTE, similarly you may need to adjust some other Integration Objects as well in order to allow more characters per attribute for Orders and Assets.

Thank you,
Oracle Product Support
References

BUG:10547901 - PROVIDE COMMENT FIELD WITH 2000 CHARS LENGTH PER PRODUCT THAT IS EDITABLE IN CONFIGURATOR
NOTE:477258.1 - How can the size and the amount of text that can be entered into an attribute edit box within an eConfigurator selection page be adjusted?

Applies to: Siebel CRM - Version: 7.5.3 SIA [16157] to 8.1 [21039] - Release: V7 to V8
Information in this document applies to any platform.
SymptomsWhen importing WSDL in Siebel Tools, the following error was generated:
Field 'Comments' in the integration component 'Repository Integration Component' contains value '(long line of comments)', which is longer than allowed length of 255 characters.(SBL-EAI-13011)
CauseThe Documentation data in a WSDL file or included XSD files is exceeding the Comments field in the Siebel Database Column which is limited by 255 chars.
SolutionIn order to avoid this error the Documentation data from WSDL or XSD must be reduced or eliminated.
This way Siebel will be able to import the WSDL without problems.

Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-3365807821.
SymptomsI am seeing following error in log file while synching appointment from Siebel to Outlook.

1. ObjMgrLog Error 1 0 2007-06-01 06:55:42 (eaiobjinst.cpp (1732)) SBL-EAI-13011: Field 'Description' in the integration component 'Action' contains value 'Discus the plan of SSSE Component installation, ESM Tool Install and other related software on Track 2 ', which is longer than allowed length
of 100 characters.

From Bookshelf I expected PIMSI to truncate the data to enable it to sync.
SolutionMessage 1For the benefit of other readers:-

The customer was seeing the following error whiel syncing appointments:

ObjMgrLog Error 1 0 2007-06-01 06:55:42 (eaiobjinst.cpp (1732)) SBL-EAI-13011: Field 'Description' in the integration component 'Action' contains value 'Discus the plan of SSSE Component installation, ESM Tool Install and other related software on Track 2 ', which is longer than allowed length
of 100 characters.

It was determined that in Administration â€“ PIM Server Integration> Siebel Domains, for the Siebel Calendar domain, the field Description had a length of 150. Once this was changed to 100 and the server restarted, SSSE truncated the description to 100 characters and EAI did not fail.

On the Action business component the description field has a length of 100, although the underlying database field has a length of 150. When the sync fields button is used the length was set to 150. This caused SSSE to present description with up to 150 characters, which fails the BC limit of 100. Changing the domain field length causes SSSE to truncate the description to a maximum of 100 characters which meets the BC limit.

Siebel Technical Support

Applies to: Siebel CRM - Version: 8.0.0.3 SIA [20416] - Release: V8

Information in this document applies to any platform.
Goal
When customer was trying to import a state model XML file into their application they were getting the following error message:

"Field 'Node Name' in the integration component 'Position' contains value 'SH CS,FeedbackMgmtFeedbackMgmt,Fulfillment&Selfcare Executive()', which is longer than allowed length of 50 characters.(SBL-EAI-13011)"

After investigation, they found that Siebel is updating â€˜Node Nameâ€™ Filed of Position BC, which is a calculated field and is the concatenation of â€˜Nameâ€™ and â€˜Full Nameâ€™ with the â€˜Text Lengthâ€™ property is 50.

â€˜Nameâ€™ filed contains Position Name and this filed also has the â€˜Text Lengthâ€™ property set to 50.

Some of the positions used by the customer are of 49 and 50 Character length. When â€˜Nameâ€™ and â€˜Full Nameâ€™ are concatenated, text length of â€˜Node Nameâ€™ goes beyond 50 and the import is getting failed.

So, they would like to know the following:

1. Can the â€˜Text Lengthâ€™ property of â€˜Node Nameâ€™ filed be increased to 100 as they have a text length constraint on â€˜Nameâ€™ Field.

2. Can the â€˜Text Lengthâ€™ property can be left blank for 'Node Name' as it is a calculated field?
SolutionDuring research found a Change Request related to this issue in both 7.8 and 8.0 as follows:

"12-RHY205 - Deploy session file for State Model causes an error when importing it."

As per this CR, the workaround to resolve this issue is, increase "Length" and "External Length" of the field "Node Name" in the integration component "Position".

This resolved the customer's problem.

Additionally, you may have to change the length in related integration objects.

TOOLS Changes for Quotes:
Integration Object: "SIS OM Quote"
Integration Component: "XA" (External Name Context=MACD Quote Item XA)
Component Field: "Value"
set Length=250
set External Length=250

Component Field: "Previous Value"
set Length=250
set External Length=250

SBL-EAI-13006: Invalid operator: %1

Applies to: Siebel Web UI Dynamic Developer Kit - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ]
Information in this document applies to any platform.
***Checked for relevance on 15-OCT-2010***
Symptoms

Using the Siebel Web UI DDK when a query using NOT LIKE is executed, the following error is received

Invalid operator: (SBL-EAI-13006)
CauseThis issue has been caused by unsupported feature. EAI UI Data Adapter Business Service Methods / QueryPage Method does not support " NOT LIKE " operator.

When NOT LIKE operator is used the following error message is experienced.

Invalid operator: NOT LIKE 'TEST'(SBL-EAI-13006)
As described in Siebel Bookshelf EAI UI Data Adapter Business Service /Query Page method only supports the following operators.
Bookshelf Section > Integration Platform Technologies: Siebel Enterprise Application Integration > EAI UI Data Adapter Business Service > EAI UI Data Adapter Business Service Methods >QueryPage Method describes the supported operators that can be used in the seach Specification.

Search Specification:

Operators: = | ~= | < | <= | > | >= | <> | LIKE | ~LIKE
SolutionTo implement the proposed solution, the following steps needs to be done:

1. In Siebel Client for the correspondent Business Object create a new PDQ that uses NOT LIKE operation.

2. The Web service client should pass the following element instead of the operator NOT LIKE.
<NamedSearchSpec>PDQName</NamedSearchSpec>
PDQName = Name of the PDQ create in Siebel client.

The enhancement request CR#10565567 (Cannot use NOT LIKE operator in the searchspec field of UI Data Web service causes error) was created in order to address this requirement in future Siebel releases.
Best regards,
Oracle | Siebel Technical Support

SBL-EAI-12002: Attempting to set %1 as the root component for the integration object (%2), but it already has a root component set (%3).

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM Keywords
WEB SERVICES; INBOUND; SERVICES
Errors
SBL-EAI-50176; SBL-EAI-04316; SBL-EAI-50187; SBL-GEN-10103; ERROR 1

Search This Blog