tag:blogger.com,1999:blog-51768279304005497272024-03-15T18:10:22.712-07:00SIEBEL ERROR CODES<br> <br>
<p>This site has been specifically designed to troubleshoot all Siebel related issues. When any exception or error occurs in Siebel, the cause is given by a specific error code. Whenever we face an issue, we try to Google or search for a resolution mostly from Oracle Support, IT Toolbox, Siebel Unleashed etc. I have tried to search for all the solutions for a particular error code in all the mentioned sites and put all the solutions in this site.</p>Unknownnoreply@blogger.comBlogger880125tag:blogger.com,1999:blog-5176827930400549727.post-49307202594318278762015-07-28T17:10:00.002-07:002016-02-15T14:01:02.029-08:00SBL-UIF-00401: View: %1 does not contain applet: %2.<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 8.0.0.2 [20412] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Checked for Relevance on 05-Aug-2013</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="GOAL"></a>GOAL</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In log files generated by their customized Siebel application the customer noticed multiple errors like the following:<br />- - -<br />SBL-UIF-00401: View: xxx does not contain applet: yyy.<br />- - -</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
They determined that these errors are generated while accessing a view with several dynamic applet toggles. They found then the following information in the Bookshelf version 8.0:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Configuring Siebel Business Applications > Configuring Screens and Views >About Applet Toggles<br />- - -<br /><br /># You cannot configure more than one applet toggle in a view.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
CAUTION: Only one static applet toggle is supported in each view. If you create more than one applet toggle in a particular view, unpredictable behavior might occur. Instead, you can use detail views with the Parent Category property set to Detail Category to access multiple views. For more information, see About Screen Views.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
# You cannot use a static and a dynamic applet toggle in the same applet.<br />...<br />- - -</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
They were unclear if the sentence "You cannot configure more than one applet toggle in a view" applies to both dynamic and static applet toggles or to static applet toggles only. They wanted to know if their configuration was supported or not.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The error:<br />- - -<br />SBL-UIF-00401: View: xxx does not contain applet: yyy.<br />- - -</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
appears also in log files generated by standard Siebel application if you access a view containing an applet that has dynamic applet toggles and a toggle is triggered. An example is the standard view 'Account Detail View' (labeled "More Info") in screen "Accounts Screen". This view contains the applet 'Account Profile Applet' that has several applet toggles.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This error is benign and can be ignored therefore.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Note also that the sentence:<br />- - -<br /># You cannot configure more than one applet toggle in a view.<br />- - -</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
apples to static applet toggle only.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
It is indeed supported to have multiple dynamic applet toggles in a single view and it is also supported to have one static applet toggle and multiple dynamic applet toggles.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=789807.1&id=10562399" target="_blank">BUG 10562399</a> has been logged asking to clarify this matter in the Bookshelf. UPDATE: This information has now been added in the Bookshelf version 8.0 and 8.1.<br /><br />On the other hand it is important to be aware of potential performance impact of using applet toggles, particularly dynamic toggles. This matter is discussed in the Bookshelf:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Performance Tuning Guide<br />Tuning Customer Configurations for Performance<br />Best Practices for User Interface Objects Layer<br />Maintaining Performance When Using Applet Toggles</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.7.2.5 [18368] and later<br />z*OBSOLETE: Microsoft Windows Server 2003<br />Database: Microsoft SQL Server 2000 SP4<br />Application Server OS: Microsoft Windows 2003 Server SP1<br />Database Server OS: Microsoft Windows 2003 Server SP1<br /><br />This document was previously published as Siebel SR 38-3053292323.<br />”Checked for Relevance on 29-01-2013”<br />**Checked for Relevance on 04-07-2014**<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="GOAL"></a>GOAL</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Is there a way to remove SBL-UIF-00401: View: XYZ does not contain applet: .(dot) from OM log file.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://www.blogger.com/null" name="aref_section21"></a></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
OM Log error " SBL-UIF-00401 " can be ignored and that is the only work around at this stage.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.8.2.3 [19221] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When attempting to navigate to the "All Agreements" and "All Agreements Across Org" views the displayed data is not being filtered with correct visibility settings and the following error occurs in the log file.<br /><br />ERROR<br />-----------------------<br />SBL-UIF-00401: View: Agreement List View does not contain applet: Agreement List Applet No Parent.<br /><br />The issue can be reproduced by navigating to either the "All Agreements" and "All Agreements Across Org" view in the customer application.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The unexpected behavior was due to misconfiguration of the Visibility Applet property for the views Agreement List View and All Agreements across Organizations. The views objects were incorrectly configured to reference a Visibility Applet called "Agreement List Applet No Parent". No such applet was configured to appear on these views.<br /><br />This resulted in the errors:<br /><br />SBL-UIF-00401: View: Agreement List View does not contain applet: Agreement List Applet No Parent.<br />SBL-UIF-00401: View: All Agreements across Organizations does not contain applet: Agreement List Applet No Parent.<br /><br />Due to the errors, the correct SQL query was not executed to populate the view with data relating to the correct visibility for the views.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The view objects were incorrectly configured to reference a Visibility Applet called "Agreement List Applet No Parent". It was advised to review the configuration of the view objects and ensure the Visibility Applet property was correctly set.<br /><br />It was suggested that the appropriate value should have been "Agreement List Applet No Parent - Read Only" as this was the only list applet appearing on the views.<br /><br />After reconfiguring the view objects to have the correct value for the Visibility Applet is was confirmed that correct visibility was being applied in all the views and expected agreement records were now visible to the user.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.8.2 [19213] and later<br />Information in this document applies to any platform.<br />*** Checked for relevance on 07-NOV-2011 ***<br />Error Message Area:UI Framework - UIF<br />Version:Siebel 7.8<br />""CHECKED FOR RELEVANCE ON 13-JUN-2013""<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00401: View: %1 does not contain applet: %2.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>DETAILS</h2>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1"></a>Explanation</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1. Either the applet is not set as a View Web Template Item or is not set as an Applet Toggle in the repository.<br /><br />2. If you are using eMail Response and the Spell Check feature is enabled you will encounter this error if you have made modifications to the name of the Comm Outbound Item Form Applet as this applet is used by Spell Check.</div>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2"></a>Corrective Action</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://www.blogger.com/null" name="aref_section31"></a><a href="https://www.blogger.com/null" name="aref_section32"></a></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1. Set the applet as a View Web Template Item or an Applet Toggle in the repository.<br /><br />NOTE: The following bookshelf reference is also applicable to the version listed in the header of this error message documentation.<br /><br />For more information on View Web Template Items, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > View Web Template Item.<br /><br />For more information on Applet Toggles, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > Applet Toggle.<br /><br />2. You should not modify the name of this applet if you want to enable Spell Check in the eMail Response views as the name of the applet is hard coded in the Spell Check functionality<br /><br />Change Request 12-MAEFZJ has been logged to address this documentation enhancement request.<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.5.3 [16157] and later<br />Information in this document applies to any platform.<br />Error Message Area:UI Framework - UIF<br />Version:Siebel 7.5.3<br />""CHECKED FOR RELEVANCE ON 28-MAR-2013""<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00401: View: %1 does not contain applet: %2.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>DETAILS</h2>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1"></a>Explanation</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1. Either the applet is not set as a View Web Template Item or is not set as an Applet Toggle in the repository.<br /><br />2. If you are using eMail Response and the Spell Check feature is enabled you will encounter this error if you have made modifications to the name of the Comm Outbound Item Form Applet as this applet is used by Spell Check.</div>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2"></a>Corrective Action</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://www.blogger.com/null" name="aref_section31"></a><a href="https://www.blogger.com/null" name="aref_section32"></a></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1. Set the applet as a View Web Template Item or an Applet Toggle in the repository.<br /><br />NOTE: The following bookshelf reference is also applicable to the version listed in the header of this error message documentation.<br /><br />For more information on View Web Template Items, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > View Web Template Item.<br /><br />For more information on Applet Toggles, refer to Siebel Bookshelf version 7.8 > Object Types Reference > Siebel Object Types > Applet Toggle.<br /><br />2. You should not modify the name of this applet if you want to enable Spell Check in the eMail Response views as the name of the applet is hard coded in the Spell Check functionality<br /><br />Change Request Bug Id 0477343 has been logged to address this documentation enhancement request.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-12045540429064349242015-07-28T16:59:00.000-07:002016-02-15T14:01:01.999-08:00SBL-UIF-00359<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Marketing - Version 8.1.1.6 SIA [21233] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.1.1.6 SIA [21233] version, Siebel Marketing<br /><br />When attempting to save list record, inconsistent error message shows up.<br />the following error occurs.<br /><br />ERROR<br />-----------------------<br />When saving using on the List Form :<br />"'List Name' is a required field. Please enter a value for the field.(SBL-DAT-00498)"<br /><br />When saving on the Form applet :<br />"Please use the file selection menu to select a file.(SBL-UIF-00359).<br /><br />STEPS<br />-----------------------<br />The issue can be replicated if you follow the steps below:<br />1. Go to Site Map > List Management > Lists.<br />2. Click New on the list applet.<br />3. Save the record without populating any field. Error message displayed is "'List Name' is a required field. Please enter a value for the field.(SBL-DAT-00498)"<br />4. Click OK to close the error message. Do not undo the record.<br />5. Go to the bottom applet (form applet) and save again the record without populating any field. Error message displayed is "Please use the file selection menu to select a file.(SBL-UIF-00359).<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This behavior has been reproduced internally and Bug has been raised to address this.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
See Bug:14333724 - INCONSISTENT ERROR MESSAGES DISPLAYED WHEN SAVING RECORD IN LIST MGMT</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version: 8.x - Release: V8<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Customer has upgraded from 7.0 to 8.0. In Siebel 8.0, while trying to attach files, if the user types in the File Name, instead of selecting the file from “Add Attachments” dialog box, the following error message is displayed:<br /><br />“Siebel Error Message SBL-DBC-00111: An error has occurred writing to a record. Please continue or ask your systems administrator to check your application configuration if the problem persists.”<span class="kmfixedwidthfont" style="font-family: 'Courier New', Courier, monospace;"></span><br /><br />Whereas in Siebel 7.0, if the same action is done, the following error message is displayed:<br /><br />“Siebel Error Message SBL-UIF-00359: Please use the file selection menu to select a file.”<span class="kmfixedwidthfont" style="font-family: 'Courier New', Courier, monospace;"></span><span class="kmfixedwidthfont" style="font-family: 'Courier New', Courier, monospace;"></span></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The reported behavior by the customer seems to be a new product defect in Siebel 8.0. The same behavior was reproducible Standard 8.0. with the following steps:<br /><br />1. In "Service Request Attachment List Applet", creat a new record from Applet Menu.<br /><br />2. Type in some characters for the "Attachment Name" column and try to save it.<br /><br />3. It will the same error (SBL-DBC-00111) that the customer has mentioned.<br /><br />Then, on testing in Standard 7.8, following the same steps as above, got a different error message like below, which is much more readable format for end-users:<br /><br />"Siebel Error Message SBL-UIF-00359: Please use the file selection menu to select a file."<br /><br />Hence the behavior reported by the customer should be a product defect in 8.0.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />A new bug #- 12-1PG85NN has been logged to address this behavior. Please note that bugs will be considered and prioritized only for future releases.<br /><br />As a workaround, you may consider writing a script in PreWriteRecord of the Attachment BC to generate an error message as required. For example:</div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
<code class="km" style="font-family: 'Courier New', Courier, monospace; font-size: 10.5299997329712px; white-space: pre-wrap; word-wrap: break-word;">
function BusComp_PreWriteRecord () <br />{ <br />if (this.GetFieldValue("ActivityFileDeferFlg")== "") <br />{ <br />TheApplication().RaiseErrorText("Please use the file selection menu to select a file."); <br />return (CancelOperation) <br />} <br />return (ContinueOperation); <br />} </code></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Product Release: V7 (Enterprise)<br />Version: 7.7.2.6 [18372]<br />Database: Oracle 9.0.1.0<br />Application Server OS: Sun Solaris 8<br />Database Server OS: Sun Solaris 8<br /><br />This document was previously published as Siebel SR 38-3276810871.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
We are getting an error "Please use the file selection menu to select a file. (SBL-UIF-00359)" when saving a New List in List Mgmt. The error only occurs when the user tries to save from the form applet; the list applet does not receive the error. We have experimented with the Form applet class and the behavior is only on the CSSSWEFrameFileFINSListMgmt and CSSSWEFrameFileListMgmt classes. We also see in Siebel Support numerous change request in other modules for various releases with a similar issue. Do these change request extend to List Mgmt?</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1">Message 1</a></h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
For the benefit of other users:<br /><br />The reproted behavior was reproduced inhouse by following the below mentioned steps:<br /><br />1. On the FINS List Mgmt Lists Entry Applet make a “Region” field displayed required in the List Mgmt Lists BC.<br />2. Compile List Mgmt Lists BC<br />3. Navigate to the My List Mgmt Lists View in List Mgmt.<br />4. Select NEW Button or CTL+N<br />5. From the lower form applet (FINS List Mgmt Lists Entry Applet) select SAVE RECORD (CTL+S)<br /><br />You will get the incorrect error message SBL-UIF-00359. If you select CTL+S from the LIST APPLET ABOVE (List Mgmt Lists List Applet) you will get the correct message "'Region is a required Field... (SBL-DAT-00498)"<br /><br />To address this issue I have logged CR “12-1IAUGW9 - FINS List Mgmt Lists Entry Applet applet displaying incorrect error message” and associated to this service request.<br /><br />As a workaround, now to overcome the issue, you may follow any of the below mentioned option:<br /><br />1. If your business permits, disable the Menu Item – Save in the “FINS List Mgmt Lists Entry Applet”<br />2. You can have your own custom Alert message in Browser Script tp display "required" error message.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Product Release: V7 (Enterprise)<br />Version: 7.7.2 [18325] Fin Svcs<br />Database: Oracle 9.2.0.4<br />Application Server OS: Microsoft Windows 2000 Server SP 4<br />Database Server OS: Microsoft Windows 2000 Server SP 4<br /><br />This document was previously published as Siebel SR 38-1850892562.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
SBL-UIF-00359, SBL-DAT-00498</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
We have an issue with creating "New URL" on Attachment Applets when there are required fields. If I add a "New URL" and then try to step off the record, without the required field being populated, I get the following error message:<br /><br />"Please use the file selection menu to select a file.(SBL-UIF-00359)"<br /><br />This is incorrect behaviour, as I would expect the required field message to be shown.<br />Also, this does not occur when using 'New File' function which produces a correct message.<br /><br />Please advise. </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1">Message 1</a></h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
For the benefit of other readers:<br /><br />The behavior described by the customer is reproducible using a standard Siebel environment version 7.7.2 SIA and the sample database. The steps are the following:<br /><br />Using Tools:<br />----<br />- In 'Account Attachment' BC set the 'Required' property of field 'Comment' to TRUE.<br /><br />Using Siebel application:<br />----<br />1. In Siebel application go to Accounts > Attachments<br />2. Create a new record using the "New URL" button and save it:<br />> You will get this error that is not appropriate:<br />----<br />Please use the file selection menu to select a file.(SBL-UIF-00359)<br />----<br /><br />3. Click the "New URL" button again or the "Query" button:<br />> The correct message will be displayed:<br />----<br />Comment is a required field. Please enter a value for the field.(SBL-DAT-00498)<br />----<br /><br />The behavior is as expected when the "New File" button is used.<br /><br />This behavior is not specific to 'Account Attachment' BC. It is for example also reproducible with 'Contact Attachment' BC. Note that it is the same in version 7.7 SEA.<br /><br />Change Request 12-VSCWP4 has been logged to address this product defect.<br /><br />'Account Attachment' BC is based on specialized class CSSBCFile and 'Account Attachment Applet' is based on specialized class CSSFrameListFile. The behavior observed cannot be changed via standard configuration or scripting.<br /><br />[...]</div>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2">Message 2</a></h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
[...]<br /><br />Note that a similar issue related to BC 'Action Attachment' in version 7.5 is discussed in posting 38-896713951. Change Request 12-F2PSUK has previously been logged to address this issue that has been fixed in Siebel application version 7.7.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Error Message Area:UI Framework - UIF<br />Version:Siebel 7.8</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00359: Please use the file selection menu to select a file.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>SBL-UIF-00359: PLEASE USE THE FILE SELECTION MENU TO SELECT A FILE.</h2>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1">Explanation</a></h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When doing a file upload, either the user has not selected a file to upload, or tries to upload an empty file.</div>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2">Corrective Action</a></h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Please inform the user that he needs to select a non-empty file in order to successfully upload the file.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-41650855187026289542015-07-28T16:49:00.002-07:002016-02-15T14:01:02.016-08:00SBL-UIF-00348: Method %1 is not allowed here.<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 7.8.2 [19213] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">*** Checked for relevance on 30-OCT-2011 ***</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Error Message Area:UI Framework - UIF</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Version:Siebel 7.8</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00348: Method %1 is not allowed here.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>DETAILS</h2>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
Explanation</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The Method cannot be invoked. The reason depends on the circumstances. For instance, the applet may be configured as not editable, but the EditRecord method is being invoked. Under the standard configuration, if a method cannot be invoked, the button on the web page would have been either grayed out or hidden. Most likely, the method is invoked by customized code.</div>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
Corrective Action</h3>
<a href="https://www.blogger.com/null" name="aref_section31" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;"></a><a href="https://www.blogger.com/null" name="aref_section32" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;"></a><br />
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
If the method is invoked by customized code, please check the return value of CanInvokeMethod call before invoking the method. If this is not the case, please contact Siebel Technical Support and provide details about the steps used to cause the error especially with regard to navigation in the User Interface, and include relevant details about customizations made in the environment.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.8.2.6 [19230] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="GOAL"></a>GOAL</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The requirement is to deactivate sort column functionality in some list applets due to the huge amounts of data which affects performance. To do so, the following script has been used:<br /></div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
function WebApplet_PreCanInvokeMethod (MethodName, &CanInvoke)<br />{<br /> if (MethodName=="SortAscending" || MethodName=="SortDescending")<br /> {<br /> CanInvoke = "FALSE";<br /> return (CancelOperation);<br /> }<br /> else<br /> return (ContinueOperation);<br />}</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /><br /><br />This eScript works fine, but the system displays a general Siebel error message ("Methode SortAscending hier nicht zul䳳ig. (SBL-UIF-00348)") (translated to "Method SortAscending is not allowed here. (SBL-UIF-00348)"). How can a customized message text be used in place of this error?<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>FIX</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
It is not possible to replace the "Methode SortAscending hier nicht zul䳳ig. (SBL-UIF-00348)" system message with a customized message. However, to prevent such an error from showing, rather than placing the script in "WebApplet_PreCanInvokeMethod" event to disable the ability to sort, "WebApplet_PreInvokeMethod" event can be used to cancel the sorting. For example:<br /></div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
function WebApplet_PreInvokeMethod (MethodName)<br />{<br /> if (MethodName=="SortAscending" || MethodName=="SortDescending")<br /> {<br /> TheApplication().RaiseErrorText("Sorting is not allowed here"); //Add this, if needed<br /> return (CancelOperation);<br /> }<br /> else<br /> return (ContinueOperation);<br />}</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /><br /><br />If needed, you could add in your custom error message here by using "RaiseErrorText" method.<br /><br />In addition, disabling column sorting for the whole application is not available. Bug 10564912 <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=814613.1&id=12-1STC0Q5">CR 12-1STC0Q5</a> has been logged to request for this feature.<br /><br />Disabling column sorting can only be performed as follows:<br />(1) On a specific applet by using script.<br />(2) On a specific column/field by using "DisableSort" user property. This property can be used in list column user property or business component field user property. A value of "TRUE" or "FALSE" will determine if the sorting can be performed. For details on this property, please refer to Siebel Developer's Reference > User Properties.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.1.1.3[21219] and later<br />Information in this document applies to any platform.<br />Checked for Relevance on 04-05-2013</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.1.1.3[21219] version, Siebel VB / eScript / COM<br /><br />In Prospects>Opportunities, When New Button is clicked then It navigates to Opportunity>My Opportunity – Individual Access, creating a new record and the cursor points to the child applet.<br /><br />ERROR<br />-----------------------<br />"Method NewRecord is not allowed here.(SBL-UIF-00348)"<br /><br /><br />STEPS<br />-----------------------<br />The issue can be reproduced at will with the following steps in custom Srf:<br />1. Navigate to Prospects Screen >> Opportunities<br />2. In My Opportunity – Individual Access >> Click "New" button<br />3. It navigates to Opportunity>My Opportunity – Individual Access view> then it displays the error :SBL-UIF-00348<br /><br />BUSINESS IMPACT<br />-----------------------<br />Due to this issue, users cannot create new Prospects record.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Improper usage of script is causing the issue. The following line was failing when there were no records in the current BusComp context:<br /><br />var sStatus = this.BusComp().GetFieldValue("BNYM Final Status");<br /><br /><br />From the script, FieldValue from the current record is being fetched. Since there are no records to be displayed for New Position, this part of script is failing which is causing the all the methods to be disable.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />1.<br />Change the script as follows:<br />var sStatus;<br />var count = this.BusComp().CountRecords();<br />if(count != 0)<br />{<br />sStatus = this.BusComp().GetFieldValue("BNYM Final Status");<br />//then paste all your code for if MethodName here<br />} /<br /><br />2. Remove the Applet_PreInvoke method script</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
3.Compile and Test</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.8.2.5 SIA [19227] and later<br />Information in this document applies to any platform.<br />”Checked for Relevance on 24-Jan-2014”<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span face="Times New Roman" style="font-family: 'Times New Roman';">After returning to an MVG applet after attempting to delete multiple records customer we are experiencing error "Method DeleteRecord is not allowed here (SBL-UIF-00348)" and buttons which were previously enabled are being disabled.</span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span lang="EN-US" style="font-family: 'Times New Roman'; font-size: 12pt;"><span lang="EN-US" style="font-family: Arial; font-size: 11pt;"><span size="3" style="font-size: small;"></span></span></span></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CHANGE"></a>CHANGES</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In order to allow multi-row selection in MVG applet customer has set the HTML Multi-Row Select property = TRUE.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Customer was getting error (SBL-UIF-00348) because Siebel application does not have the ability to delete multiselected rows in a list applet.<br /><br />The following Enhancement Request has been logged and they are still target to future version.<br /><br /><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=564420.1&id=10455778" target="_blank">Bug 10455778</a>: Delete is disabled after multi select...<br /><br />Actually the “Delete” button should be disabled when multiple rows are selected, however in Standard Interactivity Mode the applet is not refreshed when you select the rows by checking the rows and due to that it is not disabled in the UI.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
However if you perform the multi-select and then highlight a different row the applet is refreshed and button is disabled correctly.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
It was also verified that the same behavior also happens with List applets.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 10539898 DELETE BUTTON IS NOT DISABLED IN SI WHEN MULTISEL has been logged to address the issue where “DELETE” button appears enabled when selecting multiple records in standard interactivity mode.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Currently no workaround has been found to refresh the applet when selecting multiple rows in standard interactivity mode.</div>
</div>
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-5176827930400549727.post-90826379427511798042015-07-28T16:47:00.002-07:002016-02-15T14:01:02.064-08:00SBL-UIF-00340<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel CRM - Version 8.1.1.10 [23021] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In Siebel Open UI, when attempting to drill-down an attachment search result, the below error message is displayed:<br /><br /><strong>Error</strong></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<img alt="Search Attachment Result" border="0" hspace="0" src="https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1602346.1&attachid=1602346.1:3&clickstream=yes" style="max-width: 100%;" title="Search Attachment Result" vspace="0" /> </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
We detected an Error which may have occurred for one or more of the following reasons:<br />Invalid parameter: '1-2B09' passed to SWE.(SBL-UIF-00340)<br /><br /><img alt="Error" border="0" hspace="0" src="https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1602346.1&attachid=1602346.1:1&clickstream=yes" style="max-width: 100%;" title="Error" vspace="0" /><br /><br /><strong><br />Steps To Reproduce</strong><br />The issue can be reproduced at will with the following steps:<br />1. Configure Siebel Search: Siebel and Oracle Secure Enterprise Search (OSES or SES) have been integrated.<br />2. Open the Search center.<br />3. Select a search attachment category, e.g.: 'SR Attachment'.<br />4. Enter a keyword.<br />5. Execute the search operation.<br />6. Click 'Show All' button.<br />7. Drill-down a search result.<br />8. The below message is displayed:<br /> invalid parameter: '1-2B09' passed to SWE.(SBL-UIF-00340)<br /><br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This behavior occurs with search results that have child records. The behavior does not occur due to user specific privileges; it occurs due to differences in the responsibilities of Client and Server part in 'High Interactivity' (HI) and 'Open UI' (OUI) clients.<br /><br />When results are searched for any Search Categories, Siebel gets all intended results from SES in the form of URL for each results.<br />In the URL, the ROWID will be of parent record(i.e. if there is no child record present) or corresponding Child record.<br /><br />The differences in the responsibilities of Client and Server part in HI and OUI clients are as follows:<br /><br /><span style="text-decoration: underline;"><strong>HI</strong></span><br />The View mode is selected to VIEWALL while querying the records from the related buscomp of the search category.<br />In customized rendered, the same URL is used to create a hyper link of the search result, which will be encoded/decoded and later converted to Name-Value pair.<br />Later, a view method is used to create the view and show the page.<br />It successfully drills-down all search result records, be it Parent or Child.<br /><br /><span style="text-decoration: underline;"><strong>OUI</strong></span><br />If the record returned is having a child record, the RowID is replaced by the Parent RowID. And the control is getting returned from Server to Client to display the Search Results in UI.<br />For drill-down on any search results, the view method invoked is different; no Name-Value pair is used.<br /><br />As per information found while investigating <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1602346.1&id=16287768" target="_blank">Bug 16287768</a> - OUI Search: Indexing And Drilldown Of SR Attachment For FTP/HTTP Should Work, the way to build the view and show the page is OUI is different from HI.<br />In OUI there's a limitation related to parent-child pair records.<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The fix of Bug 16287768 has been implemented in 8.1.1.11 fix pack.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Also one of the below 2 changes should be implemented.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<strong>CHANGE 1</strong>1. Navigate to Administration - Search > Search Index Settings > select the attachment search category (e.g.: 'SR Attachment') > click 'Delete Index' button.<br />2. Open the field-mappings file.<br />3. Modify the attachment BC by setting the parent and fkey-field to blank in BC's header. For example:<br /><br />From</div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
<BusComp name="Service Request Attachment" ui-name= "SR Attachments" on-name=""<br />url="http://myweb.com/callcenter_enu/start.swe?SWECmd=GotoView&SWEView=#VIEWNAME#&SWERF=1&SWEHo=myweb&SWEBU=1&SWEApplet0=#APPLETNAME#&SWERowId0=#ROWID#&sblindexcategory=#SBLINDEXCATEGORY#"<strong>parent="Service Request" fkey-field="Activity Id"</strong>></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
To</div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
<BusComp name="Service Request Attachment" ui-name= "SR Attachments" on-name=""<br />url="http://myweb.com/callcenter_enu/start.swe?SWECmd=GotoView&SWEView=#VIEWNAME#&SWERF=1&SWEHo=myweb&SWEBU=1&SWEApplet0=#APPLETNAME#&SWERowId0=#ROWID#&sblindexcategory=#SBLINDEXCATEGORY#"<strong>parent="" fkey-field=""</strong>></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />3. Restart the Siebel Server for changes to take effect.<br /><br />4. Index again the attachment search category.<br /><br />5. Any drill-down on an attachment search result in either HI or OpenUI should be successful.<strong> </strong></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<strong>Or</strong></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<strong>CHANGE 2</strong><br />1. For Destination/Target view, change the visibility to ALL.<br />For example: for 'SR Attachment' with 'Service Request detail view w/attachments' as Destination/Target view.<br /> a. Open Siebel Tools and navigate to View<br /> b. Select 'Service Request detail view w/attachments' view<br /> c. Change the below view’s column values as mentioned:<br /> Visibility Applet : Service Request Detail Applet<br /> Visibility Applet Type : All<br /> d. Compile the changes.<br /> e. Deploy the new SRF.<br /><br />2. When drilling down on SR attachment records, it behaves as per the expected behavior. If the above mentioned tools changes are done, then the Siebel user can view all the SR attachment records. The same applies for tree drilldown views.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.1.1.11 SIA [23030] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.1.1.11 SIA [23030] version, Configuration - General<br /><br />In Open UI, when drilling into a record in the find results from find objectst, the following error occurs.<br /><br />ERROR<br />-----------------------<br />Invalid Parameter: '<FIELD>' passed to SWE.(SBL-UIF-00340).<br /><br /><br />STEPS<br />-----------------------<br />The issue can be reproduced at will with the following steps:<br />1. Select a customized find object.<br />2. Search for a record.<br />3. Click on "Find" button.<br />4. On the returned results, drill into the record.<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The mentioned behavior has been reported in Bug 18221843 : ERROR SBL-UIF-00340 ON CUSTOMIZED SEARCH ITEM IS GIVING ERROR IN OPENUI.<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The error is no longer seen in patchset 9. As such, please download "8.1.1.11 SIA [23030] patchset 9". The patch number is 19079078.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.11 SIA [23030] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.1.1.11 SIA [23030] version, Configuration - General<br /><br />Find Fails With SBL-UIF-00340 Error While Drilling Down An Find Result<br /><br />ERROR<br />-----------------------<br />We detected an Error which may have occurred for one or more of the following reasons:<br />Invalid parameter: '1-2B09' passed to SWE.(SBL-UIF-00340)<br /><br /><br />STEPS<br />-----------------------<br />The issue can be reproduced at will with the following steps:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span id="form1:panelPage1">1. Create a new Find object with Applet as "Order Entry - Line Item List Applet (Sales)", Drilldown View as "Order Entry - Line Items XA View (Sales)" and Preview as "Order Entry - Line Item List Applet (Sales)"<br />2. For this Find object, add the Find fields as follows:<br /> i. Field: Order Number<br />Display In Results: True<br />Display In Entry: True<br />Drilldown Business Component: Order Entry - Orders<br />Drilldown Destination Field: Id<br />Drilldown Source Id: Order Header Id<br />Drilldown View: Order Entry - Line Items XA View (Sales)<br /><br /> ii: Field: Service Id<br />Display In Results: True<br />Display In Entry: True<br />Drilldown Business Component: Order Entry - Orders<br />Drilldown Destination Field: Id<br />Drilldown Source Id: Order Header Id<br />Drilldown View: Order Entry - Line Items XA View (Sales)<br /><br />3. Add this Find object in Application --> Application Find object "Siebel Power Communications"</span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
After that<br />1. Login to Application<br />2. Click on Search.<br />3. Select Order Line Items in the search.<br />4. Provide any Service Id and click on search button.<br />5. All the relevant records will be available.<br />6. Drilldown on any Service Id field.<br />7. As soon as we drilldown on the Service Id, we get the error.<br /><br />BUSINESS IMPACT<br />-----------------------<br />The issue has the following business impact:<br />Due to this issue, users cannot access Find Results<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This is a known issue.<br /><br /><br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 18226723 - NAVIGATION ON CUSTOMIZED SEARCH ITEM IS GIVING ERROR IN OPENUI, was logged.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Keyword: <span id="form1:panelPage1">binaculor search</span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span><br /></span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span><br /></span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span><br /></span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span><br /></span></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.11 SIA [23030] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
STEPS<br />-----------------------<br />The issue can be reproduced at will with the following steps:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />1. Login into the OpenUI Application<br />2. Make sure you have records with rowid's with "+" sign for example '1+QMD+ABCN'<br />3. Open Search Center (binoculars).<br />3. Under Find category select account and execute a find operation.<br />4. Find results are displayed.<br />5. Drill-down on Find result which has rowid with "+" sign.<br />6. The drill-down fails with below message: Invalid parameter: 'x xxx xxxxx' passed to SWE.(SBL-UIF-00340)<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Product issue so following bug is opened for 8.1.1.11</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span id="mainframespan"><strong>Bug 17958953 - ERROR DRILLING INTO FIND RESULT WHERE ROWID OF THE RECORD CONTAINS '+' (PLUS)</strong></span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Issue is resolved</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
in 8.1.1.11 apply PATCHSET4</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-68545523304462416042015-07-28T16:33:00.003-07:002016-02-15T14:01:02.036-08:00SBL-UIF-00335: BACK or REFRESH <div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel CRM - Version 8.0.0.4 SIA [20417] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.0.0.4 SIA [20417] version, Client Functionality<br /><br />SBL-UIF-00335 on dedicated client<br /><br />During debugging, the customer killed one of the session, from then on, every time they use dedicated client the web browser would show below. error message<br /><br />'Encountered an error.<br />We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.(SBL-UIF-00335)'<br /><br />They cleaned the cache/history and restart the pc and tried to clear the log but the issue was not resolved.<br /><br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The cause of the issue was resolved by the customer , they found from reviewing of their Templates that some were missing and after replaceing the missing templates the issue was resolved.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
No further details as to which templates were missing so you should confirm that all are present .</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Replace missing Templates</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Healthcare Service - Version 8.0.0.6 [20423] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
It was reported that when the default homepage view for the application is not part of the user's responsibilities, that a white page and SBL-UIF-00335 error is shown. In this case, the application did not load, and a white page was shown instead.<br /><br />This is illustrated below:<br /><br /><img src="https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1314641.1&attachid=1314641.1:00335&clickstream=yes" style="max-width: 100%;" /><br /><br />The text of this error is listed below:<br /></div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
Encountered an error.<br />We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.(SBL-UIF-00335)</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /><strong>EXPECTED RESULT:</strong><br />The expected behavior in this scenario is that instead of a white page and the SBL-UIF-00335 error, the application should load properly and a SBL-DAT-00329 error should be shown. When the user does not have access to the default starting view of the application, the user should be able to continue to use the application and access the other views which they have been granted access by responsibilities.<br /><br />The expected error message is shown below:<br /><br /><img src="https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1314641.1&attachid=1314641.1:00329&clickstream=yes" style="max-width: 100%;" /><br /><br />(Note that in this example, the test user has access to only one view in the Contact screen.)<br /><br />The text of the expected error for this situation is listed below:<br /></div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
We detected an Error which may have occurred for one of the following reasons:<br />The responsibility of user '<user id>' does not allow accessing view '<view name>'.(SBL-DAT-00329"</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Note that <user id> is a placeholder for the user id, and <view name> is a placeholder for the view name.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This issue was reproduced by Oracle Technical Support in a standard 8.0.0.10 application by creating a test user who only had one custom responsibility, which contained only the FINS Home Page View.<br /></div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
Note - Testing has shown that this behavior did <strong>not </strong>happen in lower 8.0.0.x fix packs.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />A bug was logged to report this issue. Product defect bug 11846694 ( <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1314641.1&id=11846694" target="_blank">bug 11846694</a> ) was logged to report this issue.<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As of the publishing of this document, this issue reported in bug 11846694 ( <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1314641.1&id=11846694" target="_blank">bug 11846694</a> ) has been closed as not feasible to fix. However, there is a workaround for this issue.<br /><br /><strong>Workaround:</strong><br />The workaround for this issue is to ensure that all users have access to the default starting view, which will avoid this error.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.11 SIA [23030] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The OpenUI Mobile client is logging in intermittently on the mobile device : Samsung Galaxy Trend Plus<br /><br />The login will render this message after login :<br /><br />SBL-UIF-00335 We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.<br /><br />After 2 or 3 tries, the login is successful<br /><br />The problem occurs :<br /><br />- If HTTPS is enabled (with HTTP only, the login is always successful)<br /><br />- The Chrome browser is used on the device : Samsung Galaxy Trend Plus<br /><br /><br />Using a PC and Firefox (running with a user agent string emulation, to emulate the phone) - the login using HTTPS is consistently working<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The problem was caused by the use of a self-signed certificate.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Mobile phones deal with self-signed certificate differently to certificates from a Trusted Certificate Authority.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In this instance, the phone's native browser accepted the self-signed certificate consistently. However, the Chrome browser only accepted the self-signed certificate on an intermittent basis.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Using a valid certificate from a Trusted Certificate Authority resolved the issue.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The Mobile phone can consistently access the Siebel Open UI application using the Google Chrome browser, when a certificate from a Trusted Certificate Authority was used.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.7.1 [18306] and later<br />Information in this document applies to any platform.<br />Error Message Area:UI Framework - UIF<br /><br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00335: We are unable to process your request. This is most likely because you used the browser BACK or REFRESH button to get to this point.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>DETAILS</h2>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
Explanation</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1. If the error occurs when drilling down on a record, most likely the record has been deleted by other users.<br /><br />2. If the error occurs after clicking on the browser BACK or REFRESH button and then clicking on a link or button, it is because the original buscomp context cannot be fully restored.<br /><br />3. Maybe the request is to retrieve a frame layout that is supposed to be cached on the server but is not found for some reasons.</div>
<h3 class="km" style="background-color: white; color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
Corrective Action</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
If the error occurs when drilling down on a record, please try to search the record again. It may have been deleted by other users. </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The SBL-UIF-00335 error is a generic error that can have many different causes. It could be the environment setup, a custom configuration or an incorrect behavior, bug, with the Siebel product. The following information will help to narrow down the cause of this error.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Is this error reproducible or is it intermittent? If a user reports this frequently but can not reproduce the error, enable detailed logging to review their steps.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When did this error start occurring?</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Does this happen in all Siebel Environments? Production, QA, Dev? Does it reproduce only in the thin client, dedicated web client, or the mobile client? </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Is this an High Interactivity client (HI), Open UI client (OpenUI), Standard Interactivity (SI) client, or a Mobile client?</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
If the error is reproducible, first verify that there are no expired license keys in the Siebel application.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Production Down with Error SBL-UIF-50103 and Associated SBL-UIF-00369 and SBL-UIF-00335 <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=478529.1&id=1382256.1">(Doc: 1382256.1</a>)</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Test with a standard "out of the box" siebel_sia.srf (specific to the Siebel version past Siebel 8.1.1.10) on the most similar view to to see if SBL-UIF-00335 reproduces with the standard configuration.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
If the SBL-UIF-00369 only reproduces with the custom configuration, then test without Server Scripting, Browser Scripting and Open UI scripting customizations.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
These suggestions should help to define circumstances that cause the SBL-UIF-00335 errors.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://www.blogger.com/null" name="aref_section31"></a><a href="https://www.blogger.com/null" name="aref_section32"></a></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
If these suggestions do not help, please contact Siebel Technical Support and provide details about the steps used to cause the error especially with regard to navigation in the User Interface, and include relevant details about customizations made in the environment.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-43627470388077557582015-07-28T16:29:00.001-07:002016-02-15T14:01:02.025-08:00SBL-UIF-00313<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Finance - Version 8.1.1. and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">*** Checked for currency on 25 June, 2015 ***</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When attempting to Save Query as PDQ, the following error occurs:<br /><br /><span style="text-decoration: underline;"><strong>ERROR:</strong></span> SBL-UIF-00313<br /><br /><br /><span style="text-decoration: underline;"><strong>STEPS</strong></span><br />1. Login to the Siebel Callcenter application (Open UI)<br />2. Navigate to Account List Applet.<br />3. Click on Query Button : the Applet will change to query mode.<br />4. Click on Query Assistant Button.<br />5. Enter the criteria. example: Name starting with "Ac".<br />6. Click on Save Query button: You will be prompted for a Query Name.<br />7. Select one of the query Names listed and click Ok.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Result: Error <strong>SBL-UIF-00313</strong> displays.<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1605521.1&id=17589620" target="_blank">Bug 17589620</a> was logged to address this issue, however it was closed by the Product Engineering as "Not a Bug". <span 16340640="" 17589620="" a="" address="" br="" bug="" closed="" denied="" development="" engineering="" gt="" however="" id="3-3PVO7QV1386186881809" issue="" it="" logged="" nbsp="" not="" product="" saying="" span="" team="" the="" this="" to="" was=""></span><span 16340640="" 17589620="" a="" address="" br="" bug="" closed="" denied="" development="" engineering="" gt="" however="" id="3-3PVO7QV1386186881809" issue="" it="" logged="" nbsp="" not="" product="" saying="" span="" team="" the="" this="" to="" was=""><br /> </span></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span id="3-3PVO7QV1386186881809" span="">Issue can be resolved following the workaround below or by installing QF0001113.</span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="text-decoration: underline;"><strong>WORKAROUND:</strong></span><br />1. Open IE<br />2. Select Tools > Internet Options.<br />2. Click on "Browsing History" > settings.<br />3. Enable "Every time I visit the webpage" under ""check for newer version of stored webpage".<br />4. Log into Siebel and retest the issue.<br /><br />The issue is resolved by installing QF0001113:<br />Patch ID is 17585287 for 8.1.1.9<br />Patch ID is 17585289 for 8.2.2.2.<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF"></a>REFERENCES</h2>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel CRM - Version 8.0 [20405] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">z*OBSOLETE: Microsoft Windows Server 2003</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">"Checked for Relevance on 10-01-2015"</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
It was reported that certain odd navigation can cause SBL-UIF-00313 error.<br /><br />The steps to reproduce this issue are:<br />1. Log in to the Siebel High Interactivity (HI) client<br />2. Navigate to a list applet, such as Contacts -> Contact List<br />3. Right-click on the applet and select Columns Displayed<br />4. Click the Cancel button to cancel Columns Displayed<br />5. Access any pop up applet, such as the Account MVG.<br />6. Perform a browser back navigation while the pop up applet is in focus.<br />(For IE 6, this can be done with browser shortcut of the <strong>Backspace </strong>button on the keyboard)<br />(For IE 7 and higher this can be done with right-click on the pop up applet and then select "Back")<br />7. The Columns Displayed pop up is shown again, but it contains the following error message:<br /><br />The following error is displayed:<br /><img src="https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=536361.1&attachid=536361.1:CD_Error&clickstream=yes" style="max-width: 100%;" /><br /><br />The full error text is listed below:<br /></div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
We detected an Error which may have occurred for one or more of the following reasons:<br />An error happened during restoring the context for requested location (SBL-UIF-00313)</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This issue was reproduced by Oracle Support and reported as a product defect via bug 10511417 ( <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=536361.1&id=10511417" target="_blank">bug 10511417</a> ).<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As of the publishing of this document, no fix is available for this issue.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This issue is caused by odd navigation, which can be addressed as end user training. Browser back should not be utilized when a pop up applet has been opened. The pop up should be properly closed instead.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When this error occurs there is no data lost and the user is able to continue using the application.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Loyalty Engine - Version 8.1.1.6 [21233] to 8.1.1.8 [23012] [Release V8]<br />Information in this document applies to any platform.<br />An error happened during restoring the context for requested location (SBL-UIF_00313)<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Versions where the issue occurs:<br /><br />On : <strong>8.0.0.9 SIA, 8.1.1.2, 8.1.1.3, 8.1.1.4, 8.1.1.5 and 8.1.1.6</strong><br /><br />Version where this issue <em>was not faced: 8.0.0.10</em><br /><br />The Error <strong>SBL-UIF-00313</strong> might occur when:<br /><br />- Attempting to Fill Type with Redemption, Sub-Type with Product, then click on the Product picklist to choose a value the following error occurs.<br /><br />- When Changing a LOY transaction Status from "In Progress" to "Submitted" .<br /><br />- When a popup applet is displayed in some List Applets inside Loyalty or any other Siebel Industry Application.<br /><br />STEPS<br />-----------------------<br />The issue can be reproduced when using any of the following steps:<br /><br />Scenario A<br /><br />1. Go to Loyalty Member screen<br />2. Go to Transactions tab<br />3. Create a New record<br />4. Fill Type with Redemption, Sub-Type with Product, then click on the Product picklist to choose a value >> The error popped up.<br /><br />Scenario B<br /><br />1. Navigate to the vie Loyalty members > Transactions;<br />2. Create a transaction;<br />3. Select a employee in the field "Submit To";<br />4. Change the Status from "In Progress" to "Submitted";<br />5. A pickapplet is showed, click "Send" button;<br />6. The application sends an error and don't allow to change the status of the transaction.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Bug <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1384478.1&id=12794082">12794082</a>, Bug <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1384478.1&id=12605408%20">12605408 and </a><a alt="11678524" href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1384478.1&id=11678524" title="11678524"></a><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1384478.1&id=12605408%20">11678524</a><br />The Error SBL-UIF-00313 only occurs in List Applets.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Available Solutions:<br /><br /> 8.0.0.9 QF09AO Quick Fix<br /> 8.0.0.10 Fix Pack<br /> Based on Base Bug <a alt="11678524" href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1384478.1&id=11678524" title="11678524">11678524</a> issue is no longer observed in 8.'.'.'0 and 8.1.1.11.<br /><br />Available Workaround:<br /><br />Considering that error <em>SBL-UIF-00313</em> ONLY happens when a field change or a popup is triggered from *List* applet, a possible workaround is to educate the end users to change the field <em>from a Form applet</em> instead and/or <em>remove </em>the column/field that need to be changed from list applet, as short term relief of the problem.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.1.1.3[21219] and later<br />Information in this document applies to any platform.<br />""Checked for relevance on 02-SEP-2013""</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Siebel Version: 8.1.1.3<br /><br />Statement Of Issue: Error thrown when trying to select a record from Popup Applet in Clinical Protocol Site Payment Exceptions List Applet.<br /><br />Steps to Reproduce:<br />1. Click on Centre Management screen.<br />2. Go to Clinical Protocol Site Payment Exceptions Detail View.<br />3. Click on Copy FNB button on Clinical Protocol Site Payment Exceptions List Applet<br />4. In the Popup Applet, try to change the current record.<br /><br />Error Thrown:<br /><br />SBL-UIF-00313 An error happened during restoring the context for the requested location occurring when selecting a record in Popup Applet<br />SBL-UIF-00269: Cannot locate record within view: Clinical Protocol Site Payment Exceptions View applet: Clinical Protocol Site Payment Exceptions List Applet. - when trying to close the popup applet.<br /><br />Business Impact:<br />Copying FNB is a very important functionality for business users. As they copy the final negotiated budgets to few other centres.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The issue is caused due to wrong configuration of Popup Applet.<br /><br />The popup applets are configured for Detailed records in Master detail view. For example, Account Contact view, Popup applet can have records for the contacts for given account.<br />Customer is trying to configure a popup applet for Master record. It is not feasible to configure in that way.<br /><br />In customer environment, the parent BC is Clinical Protocol Site and the pop up applet invoked on child applet is based on Parent BC which is not accepted.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Make a copy of parent BC and use this BC for Popup Applet.<br /><br />1. Copy the parent BC: Clinical Protocol Site and name it as ETR Select Centres.BC<br />2. Use ETR Select Centres.BC as the BC for ETR Select Centres Applet.<br />3. Add ETR Select Centres.BC to the Clinical Protocol Site Business Object with no link.<br />4. Compile all the changes and retest the issue</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.10 [23021] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
ISSUE CLARIFICATION<br /><br />ISSUE STATEMENT<br />---------------<br />In currency code frequently ( not all the time) user get the error which cant be closed, user need to close the pick applet and reopen it again<br /><br />ERROR<br />---------------<br />"ObjMgrLog Error 1 00000002530709bc:0 2014-02-21 13:56:18 (cmdprcsr.cpp (1929)) SBL-UIF-00313: An error happened during restoring the context for requested location."<br /><br />ACTUAL BEHAVIOR<br />---------------<br />In currency code frequently user get the error which cant be closed. Also noticed that when this error is issued, users are not able to get back into the Currecny popup without first closing the Revenue Popup.<br /><br />EXPECTED BEHAVIOR<br />---------------<br />They should not face any error currency.<br /><br />ENVIRONMENT<br />---------------<br />Application & Version:8.1.1.10 Open UI<br />System Name<br />Production/Development/Test<br /><br />STEPS<br />---------------<br />The issue can be reproduced with the following steps:<br />1) Log into Open UI 8.1.1.10, and navigate to Opportunity -> Product.<br />2) Click on the icon in the Revenue Field<br />3) In the Revenue Popup, then click on the Currency Icon to bring up the Currency Popup.<br />4) Enter a Currency code in the "Starting With" query field, and then hit go.<br />5) The currency is found, and the Currency Popup Closed, and focus returned to the Revenue Popup.<br />6) At this point, the log has the SBL-UIF-00313 error, and if you attempt to click on the icon in the Currency field to bring back up the Currency Popup, it does nothing. You have to close the Revenue Popup and then re-open the Revenue popup to get the Currency icon to work again.<br /><br />IMPACT<br />---------------<br />User experience is impacting<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This is product defect. So logged the defect 18303283<br /><br />Issue reproducible with following steps: 8.1.1.10.<br /><br />The issue can be reproduced with the following steps:<br />1) Log into Open UI 8.1.1.10 with QF 2008 and navigate to Opportunity List Applet<br />2) Click on the icon in the Revenue Field<br />3) In the Revenue Popup, then click on the Currency Icon to bring up the Currency Popup.<br />4) Enter a Currency code in the "Starting With" query field, and then hit go.<br />5) The currency is found, and focus returned to focus returned to the Revenue Popup.<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Kindly apply QF 2008 on top of your 8.1.1.10 Open UI env and let me know your results.<br /><br />Patch Details:<br /><br />This issue has been resolved in the following Quick Fixes that can be downloaded from My Oracle Support > Patches and Updates.<br /><br />Fixed In: 8.1.1.10[23021] - Branch QF[0102008]<br />Platforms: Windows + Linux + Solaris + AIX + HPUX<br />Languages: All Supported Languages<br />Patch ID: 18117582<br /><br />Fixed In: 8.2.2.3[23021] - Branch QF[0102008]<br />Platforms: Windows + Linux + Solaris + AIX + HPUX<br />Languages: All Supported Languages<br />Patch ID: 18117583 </div>
</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-17713604395488402992015-07-28T16:26:00.000-07:002016-02-15T14:01:02.002-08:00SBL-UIF-00300<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel CRM - Version 8.1.1.4 SIA [21225] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">***Checked for relevance on 08-Jul-2014***</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When attempting to configure a dynamic drilldown, without destination view, when the conditions are not met, it should remain on the same view in the same row. But instead,<br />the following error occurs.<br /><br />ERROR<br />-----------------------<br />Cannot create business component 'Account Home Search Virtual' for applet 'Account Home Search Virtual Form Applet'. (SBL-UIF-00300)<br /><br />The below steps can be followed to reproduce the issue:<br />--------------------------------------------------------<br />(1) In Siebel Tools, go to the standard "Service Request List applet" object.<br />(2) In the drilldown objects, query for "Original".<br />(3) Blank out the value of the "View" property, which has the value as "Service Request Detail View"<br />(4) Set the "Business Component" property as "Service Request".<br />(5) Compile the changes.<br />(6) Start the application and go the Service Request screen -> Service Request List Applet.<br />(7) Drilldown on a Service Request record, which does not have "Type" value specified, to trigger the default drilldown.<br />(8) The above error, "SBL-UIF-00300: Cannot create business component 'Account Home Search Virtual' for applet 'Account Home Search Virtual Form Applet'.", is thrown.<br />(9) If the "Business Component" property of the Drilldown object is left blank, then error "View is not found. SBL-UIF-00403 " is thrown.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As per bookshelf - Siebel Object Types Reference > Siebel Object Types > Drilldown Object:<br /><br />"Property - View (O)<br /><br />Description or Usage - The view that appears when the user drills down. If the View property is left blank, you must specify a value in the Business Component property.<br /><br />Valid Values/Examples - If this property is left blank, the current view is maintained. This is used when drilling down from accounts into subaccounts, for example."<br /><br />So, when the view property is left blank and Business Component property is specified, the current view should be maintained.<br /><br />But, when the view property is left blank and Business Component property is specified, the error "SBL-UIF-00300: Cannot create business component 'Account Home Search Virtual' for applet 'Account Home Search Virtual Form Applet'." is thrown, when the default drilldown is triggered.<br /><br />This is an incorrect behavior.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This issue has been identified as new defect and new bug <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1333586.1&id=12378078" target="_blank">Bug: 12378078</a> has been raised.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As per the bug details the issue will be fixed in 8.1.1.12FP</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 7.8.2.4 [19224] and later<br />Information in this document applies to any platform.<br />""Checked for Relevance on 30-JUL-2013""<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The customer used a custom applet, which was a copy of standard applet 'Quote Totals Form Applet'. When they clicked the “Spread Discount” button on this custom applet they received the following error:<br />- - -<br />Cannot create business component 'ISS Spread Discount' for applet 'Quote Spread Discount Popup Applet'.(SBL-UIF-00300)<br />- - -</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In screen "Quotes" when they clicked the same button in standard applet 'Quote Totals Form Applet' there was no error.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In both standard and custom applet the "Spread Discount" button corresponds to the control 'bSpreadDiscount'. This control has "ShowPopup" as method invoked and the following user property:<br />- - -<br />Popup: Quote Spread Discount Popup Applet<br />Mode: Edit<br />- - -</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The applet 'Quote Spread Discount Popup Applet' is based on BC 'ISS Spread Discount'. In a standard Siebel repository this BC is used as BO component only in the following BOs:<br />- - -<br />Quote<br />Order Entry (Sales)<br />Order Entry<br />Service Agreement<br />- - -</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
However the customized applet was used in a view that was part of the "Opportunities" screen and belonged to BO 'Opportunity'. The BC 'ISS Spread Discount' had not been added as BO component to BO 'Opportunity' hence the error.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The issue was resolved once BC 'ISS Spread Discount' was added as BO component to BO 'Opportunity'.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-87981764432572281052015-07-28T16:23:00.001-07:002016-02-15T14:01:02.057-08:00SBL-UIF-00299<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 7.7.2 [18325] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">z*OBSOLETE: Microsoft Windows 2000</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Product Release: V7 (Enterprise)</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Version: 7.7.2 [18325]</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database: Microsoft SQL Server 2000 SP3</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Application Server OS: Microsoft Windows 2000 Professional</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database Server OS: Microsoft Windows 2000 Professional</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">This document was previously published as Siebel SR 38-1817252661.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Checked for Relevance on 30-Jan-2014</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In Service Request Contact Last Name and LOB (a custom field) are required fields. We have exposed these fields on the Service Request Add Applet in the Service Request Homepage. We are facing following two problems:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1. Whenever there are two contacts with same Last Name and we try to pick one out of these in the Add Homepage Applet and click "Add & Go" without filling the other required field it gives us the following error message:<br /><br />Wrong field values or value types detected in field Last Name. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)<br /><br />However, it should give the following the error message:<br /><br />'LOB' is a required field. Please enter a value for the field.(SBL-DAT-00498)<br /><br />We get this error messages correctly if we pick up a contact where single contact record exists with the particular Last Name.<br /><br />2. After it gives us the "Wrong field values" message, if we click on the contact last name pick applet again it just shows contacts with the last name that we picked up last time.<br /><br />We have been successful in replicating this error on Vanilla Application.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The behavior described by the customer is reproducible using standard Siebel application version 7.7 against the sample database. Here are the steps:<br /><br />1. Click the "Opportunities" screen tab to access the "Opportunities Home" page view.<br />2. In the "Add" applet open the "Pick Account" pick applet from the account field.<br />3. Select "SKF" (there is only one account with this name) and click "OK".<br />> This error will occur:<br />- - -<br />'Opportunity' is a required field. Please enter a value for the field.(SBL-DAT-00498)<br />- - -<br /><br />This error is expected since this field is required at BC level.<br /><br />4. Open again account pick applet and select "Harley-Davidson Inc" (there are several accounts with this name) and click "OK".<br />5. Select account "Harley-Davidson Inc" (there are several accounts with this name) and click "OK".<br />6. Click the "Add & Go" button:<br />> The following error occurs<br />- - -<br />Wrong field values or value types detected in field Account. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)<br />- - -<br /><br />This error is not expected.<br /><br />7. Open again the account pick applet:<br />> Only the accounts named "Harley-Davidson Inc" appear in the applet (15 records)<br /><br /><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=496091.1&id=10493528" target="_blank">BUG 10493528</a> has been logged to address this product defect.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Note that this behavior is also reproducible in the "Add" applet of the "Contacts Home" page view. However it does not occur in the "Orders Home" page view. The reason is a user property named 'Mirror Add Error Req Field'. This user property is defined in BC 'Opportunity Home Add Virtual' and 'Contact Home Add Virtual' and is set to "Write Mirror". It does not exist however in BC 'Order Entry - Orders Home Add Virtual'. When this user property is inactivated in the 2 BC mentioned above the issue does no longer occur.<br /><br />Note however that inactivating the 'Mirror Add Error Req Field' user property produces another unexpected behavior addressed by <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=496091.1&id=10482123" target="_blank">BUG 10482123</a> and described in <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=496091.1&id=495090.1">Note 495090.1</a>:<br />- - -<br />In the Quick Fill template on the Activity Home Page, the customer experienced that not entering a value in a mandatory field and clicking the 'Add&Go' button caused an expected error message, however prior to invoking the error message the values entered in the other fields were not retained.<br />- - -<br /><br />If the 'Mirror Add Error Req Field' user property is kept active then the solution to avoid the issue described above is to ensure that the required fields are filled before clicking the "Add & Go" button.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.0 [20405] and later<br />z*OBSOLETE: Microsoft Windows Server 2003<br />Product Release: V8 (Enterprise)<br />Version: 8.0 [20405] FRA Retail<br />Database: Oracle 10.2.0.1<br />Application Server OS: Microsoft Windows 2003 Server SP1<br />Database Server OS: Microsoft Windows 2003 Server SP1<br /><br />This document was previously published as Siebel SR 38-3406577713.<br /><br />Checked for Relevance on 24-February-2015</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
I need to access the standard field LOY Member.Contact Postal Code in read-write mode via script and/or UI. The field is displayed correctly but can't be updated. It works as if it tries to set the destination field of the first level MVLink (LOY Member/Contact) on the destination bus comp from the second level MVLink (Contact/CUT Address).<br /><br />The only relevant modification to vanilla pertaining to this issue has been setting popup update only=FALSE on the LOY Member/Contact MVLink.<br /><br />Is updating nth-level (n >= 2) MVFields a supported feature or is it considered bad design? I am trying to achieve this behavior for performance (one less query in one web service) / number of clicks (in the UI) reasons. Please advise.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 10527969</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The behavior described has been reproduced using standard Siebel application version 8.0 SIA against the sample database. Here are the steps:<br /><br /># Using Tools:<br /><br />Expose standard MVF 'Contact Postal Code' on applet 'LOY Member List Applet'<br /><br /># Using Siebel Loyalty:<br /><br />1. Click the "Loyalty Members" screen tab<br />2. Update the field "Contact Postal Code" and try saving the record<br />> You will get these errors:<br />- - -<br />[1] Wrong field values or value types detected in field Contact Postal Code. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)<br />[2] Field 'Personal Postal Code' does not exist in definition for business component 'CUT Address'.<br /><br />Please ask your systems administrator to check your application configuration.(SBL-DAT-00398)</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In BC 'LOY Member' the MVF 'Contact Postal Code' is mapped to field 'Personal Postal Code' in BC 'Contact' via the MVL 'Contact'. In BC 'Contact' the field 'Personal Postal Code' is a MVF mapped to field 'Postal Code' in BC 'CUT Address' via the MVL 'Personal Address'.<br /><br />> There are therefore 2 levels of MVF.<br /><br />- Same behavior using other MVFs mapped to a MVF (e.g. 'Contact City' mapped to 'Personal City' mapped to 'City').<br /><br />- Same behavior using other BC, e.g. 'Action' that has a similar 'Contact' MVL (test performed by adding a new MVF named 'Contact Postal Code' and mapped to field 'Personal Postal Code' and exposing it on applet 'Activity List Applet With Navigation').<br /><br />- Same behavior using versions 7.8.2.6 SIA, 7.7.2.8 SIA and 7.5.3.15 SIA.<br /><br />NOTE: Given the error message the following has been tested: add in BC 'CUT Address' a new field named 'Personal Postal Code' and mapped to the same column as field 'Postal Code', namely ZIPCODE.<br /><br />With this configuration it is possible to update the field "Contact Postal Code" and save the record without getting any error but the change is not taken into account. In fact the field is set back to its initial value when you save the record.<br /><br />Bug 10527969 /CR 12-1KEJ2FB has been logged to address the unexpected behavior observed when trying to update directly an MVF mapped to another MVF.<br /><br />The suggestion is to update the MVF 'Contact Postal Code' via the 'LOY Member Contact Mvg Applet' by exposing the field 'Personal Postal Code'. This MVG applet, based on BC 'Contact', is invoked from the MVF 'Contact Last Name' in the UI.<br /><br />For an update via scripting you can use the GetMVGBusComp method to get the MVG BC associated to field 'Contact Last Name', namely BC 'Contact', and query it using the appropriate methods (SetViewMode, ActivateField, ClearToQuery, SetSearchSpec, ExecuteQuery,...)</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Financial Services CRM - Version 8.1.1.11.11 [IP2013] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.1.1.11.11 [IP2013] version Open UI</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On Dedicated:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Issue can be seen once you change the DateFormat in Regional Settings with Short Date: "dd/mm/yyyy"</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The application will use "mm/dd/yyyy" for all the applets except Currency Popup applet which use "dd/mm/yyyy".</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Therefore on Currency Popup Applet (Write Record), validation will raise the errror.<br /><br />STEPS<br />-----------------------<br />The issue can be reproduced at will with the following steps:<br />1. Navigate to Events Plan<br />2. Drill-down on child applet<br />3. Go to Requested Budget field<br />4. Fill up the Amount field;<br />Trying to go back on previous applet is no more possible and the error raise</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
ERROR<br />-----------------------<br />"[1]Wrong field values or value types detected in field XXXX. Please re-enter your field values. If you need additional assistance, please refer to the documentation.(SBL-UIF-00299)<br />[2]The value '11-23-2001' cannot be converted to a date time value.(SBL-DAT-00359)"<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Code Defect logged under Bug 20569875 - SBL-UIF-00299 ERROR WHEN USING CURRENCY APPLET<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug is currently under work</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-31528331859677255402015-07-28T16:20:00.003-07:002016-02-15T14:01:02.011-08:00SBL-UIF-00289<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 8.0.0.12[20444] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Env: 8.0.0.12[20444]<br /><br />Error The applet field with name "s_3_2_9_0" doesn't exist(SBL-UIF-00289)<br />Issue happens when FinseCustomer application (SI) is accessed using a custom ASP page which redirects to siebel application<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
SBL-UIF-00289: El campo de applet "s_3_2_9_0" no existe seems to be a product defect as all known issues for SBL-UIF-00289: El campo de applet "s_3_2_9_0" no existe error point to 2 possible causes:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />1. Parameters for IE in Application > Administration > Browser was set correctly but still seeing the same issue.<br />2. Multiple mapping to the same Item Id, issue happens with standard SRF.<br /><br />Bug 19473853 - ERROR THE APPLET FIELD WITH NAME has been logged regarding to it, seems that when user is redirected to siebel from ASP page it is not able to get correct user agent information.<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Workaround would be to define first Browser which appears in Administration - Web Browser > Browsers, for example: 4thPass as follow.<br />(Note it should be the first Browse which appears in the list which seems to be used when user agent information is not correctly got)<br /><br />User-Agent =Mozilla/5.0<br />Parent = Mozilla 5.0<br />Accept =image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */*<br /><br />Restart siebel server, web server.<br /><br />****<br /><br />Bug 19473853 - ERROR THE APPLET FIELD WITH NAME is target for future version.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.2[21215] and later<br />Information in this document applies to any platform.<br />*** Checked for relevance on 22 Dec 2014 ***</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />After a previous session timed-out, and upon re-logging into the application and drilling down to some record, the following error message is displayed:</div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
The applet field with name "s_1_2_51_1" doesn't exist (SBL-UIF-00289).</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The issue has been reproduced internally, and is particular to the combination of Microsoft Windows 7 and Internet Explorer 8.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 10602769 was logged to address this issue, which concluded the issue was caused by incorrect <span class="kmfixedwidthfont" style="font-family: 'Courier New', Courier, monospace;">User-Agent</span> settings.<br /><br />Workaround Steps:</div>
<ol style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<li>When the issue appears, logoff from the application, or after a session timeout</li>
<li>Clear the browser cache, and close the browser</li>
<li>Re-login to the application</li>
</ol>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Permanent Solution Steps:</div>
<ol style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<li>Go to Site Map</li>
<li>Click on Administration - Web Browser > Browsers</li>
<li>Create a Browser with name: <span class="kmfixedwidthfont" style="font-family: 'Courier New', Courier, monospace;">MSIE 8.0</span><br /><br />For the browser add the following capabilities:<br /><br /><div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
<strong>User-Agent</strong> = Mozilla/4.0 (compatible; MSIE 8.<br /><strong>Parent</strong> = IE 8.0<br /><strong>Accept</strong> = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */*<br /><strong>JumpTab</strong> = True</div>
<br /><strong>Note:</strong> Although <span class="kmfixedwidthfont" style="font-family: 'Courier New', Courier, monospace;">User-Agent</span> value looks incomplete without the closing parenthesis, this is the correct value.</li>
</ol>
<div>
<span style="font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;"><br /></span></div>
<div>
<span style="font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;"><br /></span></div>
<div>
<span style="font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;"><br /></span></div>
<div>
<span style="font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;"><br /></span></div>
<div>
<span style="font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;"><br /></span></div>
<div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel CRM - Version 8.1.1.5 SIA [21229] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Issue:<br />------<br />Getting error "The applet field with name "s_1_2_51_1" doesn't exist.(SBL-UIF-00289)", when drill-down an any record in OpenUI, using Mozilla browser.<br /><br />Error:<br />------<br /> "The applet field with name "s_1_2_51_1" doesn't exist.(SBL-UIF-00289)"<br /><br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1.Go to SiteMap<br />2.Click on Adminstration> "Web Browser"<br />3. BrowsersIf not present,create a Parent Browser with name: "Mozilla 5"<br /><br />a) Set the “User-Agent" Capability Name to = Mozilla/5.0<br />b) Set the “Accept" Capability Name to = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */*<br /> </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Service - Version 8.1.1.4 [21225] to 8.2.2 SIA[22320] [Release V8]<br />Information in this document applies to any platform.<br />***Checked for relevance on 10-SEP-2012*** </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The following problem occurs with version 8.1.1.4 [21225] in the customer facing application (Standard Interactivity application "SI"), IE9 (IE version is 9.0.8112.16421) :<br /><br /><span style="text-decoration: underline;">Steps and Error Messages</span></div>
<ol style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<li>Before submitting a service request applet, clicking on the pick applet product name produced the following error:<br /><div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
We detected an error which may have occurred for one of more of the following reasons:<br />The applet field with name "s_1_2_94_0" doesn't exist. (SBL-UIF-00289)</div>
</li>
<li>When sorting a list of service requests, the following error is returned:<br /><div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
We detected an error which may have occurred for one of more of the following reasons:<br />Command requires a value for argument. (SBL-IUF-00279)</div>
</li>
<li>When exporting rows, the pop-up appears but it does not continue to the next step for performing the export.</li>
</ol>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Incorrect settings for the Siebel Administration - Browser<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The browser needs to satisfy the requirements stated in the System Requirements and supported platforms, also described at:<br />Siebel Support for Standard Interactivity Mode Clients (IE, Firefox, Mozilla, Safari) for versions 7.x - 8.1.x (Doc ID <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=1454260.1&id=1159335.1" target="_blank">1159335.1</a>)<br /><br />Further investigation revealed that the parameters for IE9.0 on Administration > Brower were not according to the document, which are:</div>
<ol style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<li>For IE 9: Create a Browser with name : <tt>MSIE 9.0</tt><ol type="a">
<li>Set the "User-Agent" Capability Name to “<tt>Mozilla/5.0 (compatible; MSIE 9.0)</tt>"</li>
<li>Set the “Parent" Capability Name to "<tt>IE 9.0</tt>"</li>
<li>Set the “Accept" Capability Name to “<tt>image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */*</tt>"</li>
<li>Set the “JumpTab" Capability Name to TRUE</li>
</ol>
</li>
</ol>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
After applying the above Siebel client parameters, and restarting the application, IE9 did not return errors to the application, regardless of IE9-side parameters.</div>
</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-79146886284718003792015-07-28T15:55:00.000-07:002016-02-15T14:01:02.046-08:00sbl-uif-00276<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 8.1.1.6 SIA [21233] to 7.5.1 [15041] [Release V8 to V7]</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As users navigate around an application or if a developer is reviewing an applet in Edit Web Template mode an error similar to the following can occur if there is a problem with web templates:<br /><br />Cannot open file:<br />D:\Program Files\Siebel\8.0\webclient\WEBTEMPL\CCAppletList_B_EL.swt(SBL-UIF-00276)</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This error can occur if the specified web template is missing from the WEBTEMPL folder. On a local dedicated/mobile client this is located in client \WEBTEMPL and on a server in siebsrvr\WEBTEMPL. Additionally if Siebel Tools is used the web templates can be found in the Tools\WEBTEMPL folder.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The error message indicates that a web template file (*.swt) is missing/ cannot be found in the indicated WEBTEMPL. If custom web templates have been created this can indicate that the custom web templates have not been migrated from the Tools\WEBTEMPL folder to the siebsrvr or client WEBTEMPL folders. Additionally if the error has occurred in Siebel Tools then the application may need to configured to point at the correct WEBTEMPL. This can be done by navigating to View> Options in the Development Tools Option dialog box select the "Web Template Editor" and in the Folder full path text box specify the correct folder.<br /><br />This error can also occur on obsolete objects, for example the "Product Feature List Applet (eSales)". While this applet is not actively in use by any view, if this applet were to be mapped to an active view the SBL-UIF-00276 would occur. This behavior occurs as the applet is mapped to the "Applet List Basic Headerless" web template, which no longer exists. To workaround this behavior the web template mapped to the applet would need to be updated, for example the"DotCom Applet List Tabbed" or another similar template. For this particular example the Bug: 10481485 :Missing web template and file for Product Feature applets for eSales" has been raised to address this behavior as this mapping still exist in the sample database.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.1 [21039] and later<br />Information in this document applies to any platform.<br />*** Checked for relevance on 12-JAN-2012 ***<br />Error Message Area:UI Framework - UIF<br />Version:Siebel 8.1<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00276: Cannot open file: %1.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>DETAILS</h2>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1"></a>Explanation</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The specified file cannot be opened. Most likely it's because the file does not exist or you don't have the read permission.</div>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2"></a>Corrective Action</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://www.blogger.com/null" name="aref_section31"></a><a href="https://www.blogger.com/null" name="aref_section32"></a></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Confirm that the specified file exists and that the read permission is set.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel System Software - Version 7.7.2 SIA [18325] and later<br />Oracle Solaris on SPARC (64-bit)<br />Product Release: V7 (Enterprise)<br />Version: 7.7.2 [18325] Pub Sect<br />Database: Oracle 9.2.0.2<br />Application Server OS: Sun Solaris 9<br />Database Server OS: Sun Solaris 9<br /><br />This document was previously published as Siebel SR 38-1699853721.<br /><br />***Checked for relevance on 07-Feb-2013*** </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
We are currently running some performance tests. During our run, we have 1 user being added every 25 seconds for a maximum of 50 users, which run until completion. At around the 28 minute mark and 35 users have entered the system, Siebel starts producing errors causing all subsequent users/transactions to fail. Some of the errors that are produced include: "Communication: User is not associated with any communication configuration in the database", "Unable to load message 0xffff", "Cannot open file: /opt/siebel/SBLSRVENV14A/siebsrvr/webtempl/CCError.swt".</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Configuration / Setup</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Customer was running a load test where the scenario consisted of a user logging into the Siebel Application, calls a business service/workflow that makes an external call to outside system, and brings data back to be evaluated and used by the user. They had one user login every 25 seconds, and the following errors occured around the 30 user mark or about 25 minutes into the run.<br /><br />[LOADTEST061] 686d688 Load Script from Attachment: Error: errCode=65535 errorMsg="Unable to load message 0xffff Parameter 1 = (SBL-GEN-00000)"<br /><br />(parser.cpp (3522)) SBL-UIF-00276: Cannot open file: /opt/siebel/SBLSRVENV14A/siebsrvr/webtempl/CCError.swt<br /><br />SBL-UIF-00276 was occuring due to the fopen limit as per "Siebel Processes that Read or Write to files on Solaris May Encounter Fopen() Behaviors (<a alt="Doc ID 477801.1" href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=545467.1&id=477801.1" title="Doc ID 477801.1">Doc ID 477801.1</a>)"</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />To resolve the behavior following workarounds were suggested:<br /><br />1) Turn off all extra logging for this Siebel Object Manager component (default settings). This will reduce the number of log files opened and written by this component.<br /><br />2) Decrease the number of tasks for each Siebel Object Manager process by increasing the number of MaxMTServers.<br /><br />Customer adjusted the Min MT Server and Max MT Servers for the Object Manager component to resolve the behavior.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Marketing Enterprise - Version 8.1.1.11.9 [IP2013] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.1.1.11 SIA [23030] version, Siebel Marketing<br /><br />When attempting to access the calender view it results in an error Cannot open file: d:\apps\sba81\siebsrvr\webtempl\CCAppletFormGridLayout_Gantt.swt.(SBL-UIF-00276)<br />the following error occurs.<br /><br />ERROR<br />-----------------------<br />Cannot open file: d:\apps\sba81\siebsrvr\webtempl\CCAppletFormGridLayout_Gantt.swt.(SBL-UIF-00276)<br /><br />STEPS<br />-----------------------<br />The issue can be reproduced at will with the following steps:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
1. Login to Siebel Marketing Application HI</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
2. Navigate to Marketing Calendar Screen.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
3. Drill down on the Events view</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
3a. Drill Down on Programs view</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
3b. Drill Down on Media View</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Drilling down on all these views leads to the following error - Cannot open file: d:\apps\sba81\siebsrvr\webtempl\CCAppletFormGridLayout_Gantt.swt.(SBL-UIF-00276)</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /><br />BUSINESS IMPACT<br />-----------------------<br />The issue has the following business impact: Cannot use the marketing calender affecting scheduling jobs<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This was observed as a defect because accessing the Event View under marketing Calender errors out with the swt error. The behavior occurs due to wrong Objects Configuration. It was later on observed to have affected the Program and Tactics View as well. where all these view leads to an error when being accessed.<br /><br />..<br />..<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Product Engineering and development team provided the following workaround. Kindly follows the step by step configuration and deploy this in your development environment. Perform a thorough testing procedures to make sure that the changes are working as expected before deploying them in you production environment.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="2" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 107px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 834px;">Repository Changes</th></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 834px;"><strong><span style="font-size: small;">Project :- Marketing Calender</span></strong></td></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 834px;"><span style="font-size: small;"><strong>TACTICS CALENDAR</strong></span></td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 176px; width: 850px;"><tbody>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;"><span style="font-size: small;">For below views:</span><br />
<span style="font-family: Wingdings; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"></span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - Tactics Ax Gantt Chart View - My</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - Tactics Ax Gantt Chart View - All</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"> Marketing Calendar - Tactics Ax Gantt Chart View - My Org</span><br />
<div class="MsoListParagraph" style="text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">1. 1. </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Change View “Visibility Applet” to “Tactics GanttChart Ax Applet” from “Marketing Tactics Gantt Applet “.<span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"> </span></span></div>
</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
2. Add/Modify these two items under View Web Template Item:</div>
<table border="1" cellpadding="3" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 97px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; text-align: center; vertical-align: top; width: 203px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Name</span></th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Item Identifier</span></th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Applet</span></th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 202px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Inactive</span></th></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Tactics Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;">1</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Tactics Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 202px;">N</td></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Tactics GanttChart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;">2</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 203px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Tactics GanttChart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 3px; vertical-align: top; width: 202px;">N</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 54px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 836px;"><br /><span style="font-size: small;">PROGRAMS CALENDAR</span></th></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 151px; width: 850px;"><tbody>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;"><span style="font-size: small;">For below views:</span><br />
<span style="font-family: Wingdings; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"></span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - Programs Ax Gantt Chart View - My </span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;">Programs Ax Gantt Chart View</span> - All</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"> Marketing Calendar - </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;">Programs Ax Gantt Chart View</span> - My Org</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">1. </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Change View “Visibility Applet” to “Programs GanttChart Ax Applet” from “Marketing Programs Gantt Applet “.<span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"> </span></span></td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
2. Add/Modify these two items under View Web Template Item:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 108px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Name</span></th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Item Identifier</span></th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Applet</span></th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 200px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Inactive</span></th></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Programs Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">1</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Marketing Programs Gantt Applet</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Programs GanttChart Ax Applet</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">2</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-size: small;"><span style="font-family: Calibri, sans-serif;">Programs GanttChart Ax Applet</span></span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 34px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 836px;">CAMPAIGNS CALENDAR</th></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 151px; width: 850px;"><tbody>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;"><span style="font-size: small;">For below views:</span><br />
<span style="font-family: Wingdings; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"></span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - <span style="font-size: 11pt;">Campaigns Ax Gantt Chart View </span>- My </span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;"><span style="font-size: 11pt;">Campaigns Ax Gantt Chart View</span></span> - All</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"> Marketing Calendar - </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;"><span style="font-size: 11pt;">Campaigns Ax Gantt Chart View</span></span> - My Org</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">1. </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Change View “Visibility Applet” to “Campiagns GanttChart Ax Applet” from “Marketing Campaign Gantt Applet “.<span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"> </span></span></td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div class="MsoListParagraph" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">2.</span><span style="font-size: 7pt;"> <span style="font-size: x-small;"> 2. </span></span><span style="font-family: Calibri, sans-serif; font-size: small;">Add/Modify these two items under View Web Template Item:</span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 110px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Name</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Item Identifier</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Applet</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">Inactive</th></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Campaign Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">1</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Media Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Campaigns Ganttchart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">2</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Campaign Activities Ganttchart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 44px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 836px;">MEDIA CALENDAR</th></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 89px; width: 850px;"><tbody>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;">For below views:<br />
<span style="font-family: Wingdings; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"></span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Media Calendar - <span style="font-size: 11pt;">Campaigns Ax Gantt Chart View </span></span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">1. Change View “Visibility Applet” to “Campaign Activities Ganttchart Ax Applet” from “Marketing Media Gantt Applet “.</span></td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"> 2.</span><span style="font-family: 'Times New Roman', serif; font-size: 7pt;"> </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Add/Modify these two items under View Web Template Item:</span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 113px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Name</span></th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Item Identifier</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Applet</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">Inactive</th></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Media Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">1</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Media Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Campaign Activities Ganttchart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">2</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Campaign Activities Ganttchart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 34px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 836px;">Events Calender</th></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 151px; width: 850px;"><tbody>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;"><span style="font-size: small;">For below views:</span><br />
<span style="font-family: Wingdings; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"></span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - <span style="font-size: 11pt;"><span style="font-size: 11pt;">Events Ax Gantt Chart View </span></span>- My </span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Calendar - </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;"><span style="font-size: 11pt;"><span style="font-size: 11pt;">Events Ax Gantt Chart View</span></span></span> - All</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"> Marketing Calendar - </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;"><span style="font-size: 11pt;"><span style="font-size: 11pt;">Events Ax Gantt Chart View</span></span></span> - My Org</span><br />
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">1. </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: 'Times New Roman'; font-size: 7pt; font-stretch: normal;"> </span></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Change View “Visibility Applet” to “</span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;">Events GanttChart Ax Applet</span>” from “Marketing </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Events Gantt Applet “.</span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-size: 11pt;"><span style="font-size: 11pt;"></span></span></span></td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="font-size: 7pt;"> </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">2. </span><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Add/Modify these two items under View Web Template Item:</span></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 105px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Name</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Item Identifier</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">Applet</th><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">Inactive</th></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Events Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">1</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Marketing Events Gantt Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Events GanttChart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;">2</td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 201px;"><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Events GanttChart Ax Applet</span></td><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 200px;">N</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 218px; width: 850px;"><tbody>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;"><a href="https://www.blogger.com/null" name="aref_section31"></a><h3 class="km" style="font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<span style="font-size: small;"> Inactivate Applet Toggle of below Applets</span><br /><br /><span style="font-size: x-small;">1. Marketing Tactics Gantt Applet</span></h3>
<br />2. Marketing Programs Gantt Applet<br />
<br />3. Marketing Campaign Gantt Applet<br />
<br />4. Marketing Media Gantt Applet<br />
<br />5. Marketing Events Gantt Applet<br />
</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 37px; width: 847px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; text-align: center; vertical-align: top; width: 833px;"><span style="font-size: medium;">Manifest Changes</span></th></tr>
</tbody></table>
<div class="MsoListParagraph" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; text-indent: -0.25in;">
<span style="font-size: 7pt;"> <span style="font-size: x-small;"> </span></span><span style="font-family: Calibri, sans-serif;"><br /></span></div>
<table border="1" cellpadding="4" cellspacing="1" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; height: 1179px; width: 850px;"><tbody>
<tr><th class="km" style="background-color: #dee6ef; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;"><span style="font-size: 7pt;"><span style="font-size: x-small;"></span></span><span style="font-family: Calibri, sans-serif;">Siebel Application, go to “Administration - Personalization --> Applets View”. Add below entries.</span></th></tr>
<tr><td class="km" style="border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; border-right-color: rgb(196, 209, 230); border-right-style: solid; border-right-width: 1px; padding: 4px; vertical-align: top; width: 836px;"><div class="MsoListParagraph" style="margin-left: 1in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">a)</span><span style="font-size: 7pt;"> </span><strong><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Name: Tactics GanttChart Ax Applet</span></strong></div>
<div class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span></div>
<div class="MsoNormal" style="margin-left: 1in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") < 1 OR GetProfileAttr("IsOpenUI") IS NULL</span></div>
<br />
<div class="MsoListParagraph" style="margin-left: 1in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">b)</span><span style="font-size: 7pt;"> </span><strong><span style="font-family: Calibri, sans-serif; font-size: 11pt;">Name:Marketing Tactics Gantt Applet</span></strong></div>
<div class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span></div>
<div class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") > 0</span></div>
<br />
<div class="MsoListParagraph" style="margin-left: 1in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">a) <strong>Name: Programs GanttChart Ax Applet</strong></span></div>
<div class="MsoListParagraph" style="margin-left: 1in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span></div>
<div class="MsoListParagraph" style="margin-left: 1in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") < 1 OR GetProfileAttr("IsOpenUI") IS NULL</span></div>
<br />
<div class="MsoListParagraph" style="margin-left: 1in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">b) <strong>Name:Marketing Programs Gantt Applet</strong></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") > 0</span></div>
<br />
<div class="MsoListParagraph" style="margin-left: 1in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">a) <strong>Name: Campaigns GanttChart Ax Applet</strong></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") < 1 OR GetProfileAttr("IsOpenUI") IS NULL</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"><br /></span></div>
<div class="MsoListParagraph" style="margin-left: 1in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">b) <strong>Name: Marketing Campaign Gantt Applet</strong></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") > 0</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"><br /></span></div>
<br />
<div class="MsoListParagraph" style="margin-left: 1in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">a) <strong>Name: Campaign Activities Ganttchart Ax Applet</strong></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") < 1 OR GetProfileAttr("IsOpenUI") IS</span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"> NULL</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"><br /></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">b) <strong>Name: Marketing Media Gantt Applet</strong></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") > 0</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"><br /></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">a) <strong>Name: Events GanttChart Ax Applet</strong></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") < 1 OR GetProfileAttr("IsOpenUI") IS NULL</span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;"><br /></span></div>
<div class="MsoListParagraph" style="margin-left: 1.25in; text-indent: -0.25in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">b) <strong>Name: Marketing Events Gantt Applet</strong></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span></div>
<div class="MsoListParagraph" style="margin-left: 1in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Start Date, End Date – Leave it Empty</span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span><span style="font-family: Calibri, sans-serif; font-size: 11pt;"></span></div>
<div class="MsoListParagraph" style="margin-left: 1in;">
<span style="font-family: Calibri, sans-serif; font-size: 11pt;">Conditional Expression: GetProfileAttr("IsOpenUI") > 0</span></div>
</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-9903743699086213252015-07-28T15:48:00.000-07:002016-02-15T14:01:02.070-08:00SBL-UIF-00275<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
PPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 8.0.0.5 [20420] - DO NOT USE and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Steps to reproduce the issue:<br /><br />1. Created a business Service "Sample Business Service"<br />2. Add following code<br /></div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
function Service_PreInvokeMethod (MethodName, Inputs, Outputs)<br />{<br /> if(MethodName == "Sample")<br /> {<br /> Outputs.SetProperty("URL", "/s/ap/20091204/ap_on_he_me/us_med_swine_flu/print")<br /> return(CancelOperation);<br /> }<br /> return (ContinueOperation);<br />}<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />3. In Contact List Applet created a Button and in the Applet_PreInvoke Event Add following code<br /></div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
function Applet_PreInvokeMethod (name, inputPropSet)<br />{<br /> if(name == "TestRecord")<br /> {<br /> try{<br /> var bs;<br /> bs = theApplication().GetService("Sample Business Service ");<br /> var psInputs = theApplication().NewPropertySet();<br /> var psOutputs = theApplication().NewPropertySet();<br /> psOutputs = bs.InvokeMethod("Sample",psInputs);<br /> var URL = psOutputs.GetProperty("URL");<br /> window.open("http://news.yahoo.com"+URL);<br /> }<br /> catch(e){<br /> alert(e.toString());<br /> }<br /> finally{<br /> }<br /> return("CancelOperation");<br /> }<br /> return ("ContinueOperation");<br />}</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /><br />4. Everything is working as expected.<br /><br /><br />5. But if you change the Business Service name from "Sample Business Service" to "Sample Business Service1" you will get following error<br /><br />"Cannot get service: Sample Business Service1(SBL-UIF-00275)"<br /><br />Also the URL is getting invoke. The URL should not get invoked as the error is encountered. It looks like it is bypassing the catch block in the browser Script<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
CR#10583049 [Try - Catch Block Error Handling not working in Browser Script] has been logged as Product Defect Bug to address this issue.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel System Software - Version 8.1.1.1 SIA [21211] to 8.1.1.8 [23012] [Release V8]<br />Information in this document applies to any platform.<br />This document was previously published as Siebel SR 38-3443949081.<br /><br />** Checked for relevance on 27-Feb-2012 **<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
SBL-UIF-00275</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Task Based UI.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Using Task Based UI, the following error message is thrown with the Siebel vanilla Business Service "Task UI Service (SWE)":</div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
"(swefrmgr.cpp (3258)) SBL-UIF-00275: Folgender Dienst ist nicht verfügbar: Task UI Service (SWE)</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<strong>Cannot get service: Task UI Service (SWE).(SBL-UIF-00275)</strong></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="text-decoration: underline;"><strong>STEPS</strong> to reproduce using standard Repository and sample DB:</span><br /><br />- From Siebel Tools, select object Menu in the Object Explorer<br />- Query for menu "Generic"<br />- Lock the project (Alt+L)<br />- Set the property 'Inactive' to True for Menu Item "Edit" of the menu "Generic"<br />- Compile this object into the SRF and launch application "Siebel Sales Enterprise" with this SRF, connected as SADMIN<br />- Navigate to Sitemap > Administration - Business Process > Task Deployment > Published Task<br />- In the top applet, search for task "FS Asset To Contract Task", click Activate<br />- Navigate to sitemap > Administration – Application > Tasks<br />- In the top applet, create a new record, open the pick applet on Task Name and select "FS Asset To Contract Task"<br />- In the bottom applet, add the "Siebel Administrator" responsibility<br />- In the top applet, click "Clear Cache"<br />- Navigate to site map > Agreements > List<br />- Open the task pane, you should see a task named "Assets to Agreement", try this task.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<em>Result:</em></div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
SBL-UIF-00275: Cannot get service: Task UI Service (SWE)</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The log file shows the error below.<br />GenericLog GenericError 1 00000002470d0894:0 2007-10-11 11:13:06 Invocation of Task UI Service (SWE)::StartTask is not allowed.<br />ObjMgrLog Error 1 00000002470d0894:0 2007-10-11 11:13:06 (swefrmgr.cpp (3258)) SBL-UIF-00275: Cannot get service: Task UI Service (SWE)<br /><br /><br />Even if the log file does show the error below about the menu, it is difficult to link both.<br /><br />ObjMgrSRFLog Error 1 00000002470d0894:0 2007-10-11 11:12:54 (objdef.cpp (9943)) SBL-DAT-00260: There is no menu item definition at position '20' specified as the parent for menu item 'Edit - Add New Record' in menu 'Generic'.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
If there is a menu object that is incorrect (i.e., an invalid Position sequence like twice the same position or a non-existing parent item), you cannot launch any task from the task pane.<br /><br />This occurs even if the menu is not the one used by the application you run. This occurs for any task and and any place from where the task is called.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.11 [23030] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />iHelp was setup and configured several months ago. Then, iHelp stopped working after a recent SRF compilation. iHelp fails in both the thin and thick clients.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The changed objects were reviewed; however, none of the objects were related either to iHelp or Task UI.<br /><br /><span style="text-decoration: underline;"><strong>STEPS</strong></span><br />1. Click<em><strong> iHelp</strong></em> icon in the Toolbar to open the iHelp items for a given Screen.<br />2. Click the hyperlink for any iHelp item.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Result: <strong>Error SBL-UIF-00275</strong> error pops up on the screen.</div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
Cannot get service: Task Assistant UI Service.(SBL-UIF-00275)</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span id="form1:panelPage1"> <span class="awizEndDelimiter"> </span></span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<strong>SBL-UIF-00230</strong> is logged in the object manager log. </div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
ObjMgrBusCompLog Error 1 00000002532a17f0:0 2014-03-20 09:33:05 (bcfile.cpp (1723)) SBL-UIF-00230: The file 0-30&Siebel Universal Agent.spf could not be found on any specified file system.</div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
<br /> 69232 ObjMgrSRFLog Error 1 00000002532a17f0:0 2014-03-20 09:33:03 (objdef.cpp (10099)) SBL-DAT-00260: There is no menu item definition at position '7.6' specified as the parent for menu item 'Tools - Reset Active Session Count' in menu 'CRA Generic WEB'.<br /><br /> 191173 GenericLog GenericError 1 00000002532a17f0:0 2014-03-20 09:33:56 Invocation of Task Assistant UI Service::LaunchTaskFromView is not allowed.<br /> 191175 ObjMgrLog Error 1 00000002532a17f0:0 2014-03-20 09:33:56 (swefrmgr.cpp (3603)) SBL-UIF-00275: Cannot get service: Task Assistant UI Service.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span id="form1:panelPage1"> <span class="awizEndDelimiter"> </span></span></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CHANGE"></a>CHANGES</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Objects were changed and the SRF was recompiled.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Issue is caused by behavior documented in the following bug:<br /><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1638407.1&id=10530804" target="_blank">Bug 10530804</a> - [CR#12-1LJ96SE][FR#12-1LJ96TU] SBL-UIF-00275 WHEN CALLING ANY TASK FROM THE TASK</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
If there is a menu object that is incorrect, such as having an invalid Position sequence (e.g., the same position listed twice or a non-existing parent item), then you can no longer launch any task from the task pane. This also affects iHelp.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This occurs even if the menu is not the one used by the application you launched.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In the Menu object<strong> CRA Generic WEB</strong>, the wrong position 7.7 was listed instead of position 7.6, as in the vanilla repository. This occurred after performing the 8.1.1.11 IRM upgrade process.<br /> </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Note:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This issue is not specific to standard Business Service 'Task UI Service (SWE)'.<br />This also occurs with custom browser script Business Services.<br /><br />The issue is reproducible with 8.1.1.11 and 8.1.1.14.5.<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="text-decoration: underline;"><strong>Workaround</strong></span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Activate the menu item "Help - About Record" at position 7.6 in menu 'CRA Generic WEB'.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Go to Siebel Tools:<br />1. In Object Explorer, Select Menu Object.<br />2. Query for "CRA Generic WEB".<br />3. Expand Menu to expose Menu Items.<br />4. Search for "Help - About Record", with Position Field = 7.6.<br />5. Set the Inactive Field to FALSE.<br />6. Recompile SRF.<br /> </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.11 SIA [23030] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
We are using an custom BS for our CTI integration. From the view of Siebel it's just an bookmark/static URL.<br /><br />Our BS is a very simple one. He does a query with busobject and then calls GotoView:<br /><br />function JumpToContact(Inputs, Outputs)<br />{<br />var sViewName = "Contact Detail View";//Inputs.GetProperty("ViewName");<br /> var sBusObject = "Contact";//Inputs.GetProperty("BusObject");<br /> var sBusComp = "Contact";//Inputs.GetProperty("BusComp");<br /> var sId = Inputs.GetProperty("Id");<br /> var bo : BusObject = TheApplication().GetBusObject(sBusObject);<br /> var bc : BusComp = bo.GetBusComp(sBusComp);<br /> bc.SetViewMode(5);//Organization->All Contacts<br /> bc.ClearToQuery();<br /> bc.SetSearchSpec("Id",sId);<br /> bc.ExecuteQuery(ForwardBackward);<br /> TheApplication().GotoView(sViewName, bo);<br /><br /> return (CancelOperation);<br />}<br /><br />Our CTI software generates an URL and paste this into the internet explorer in which is Siebel running. There is the URL for Contacts:<br /><br />http://<hostname>/sales_sso_deu/start.swe?SWECmd=InvokeMethod&SWEMethod=JumpToContact&SWEService=XXXXX+CTI+Business+Service&Id=1-2BE9B&SWERF=1<br /><br />We get the following error if we paste this URL in the internet explorer address bar<br />- - -<br />Cannot get service: XXXXX CTI Business Service (SBL-UIF-00275)<br />- - -<br /><br />I can call the BS via Business Service simulator and everything works fine.<br /><br />We are using version 8.1.1.11 with patchset 6 (8.1.1.11.6). With patchset 5 (8.1.1.11.5) this error doesn’t occur.<br /><br />NOTE:<br />- - -<br />This issue is reproducible using the HI and the Open UI clients.<br />This issue is reproducible using the dedicated client and the web client.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
In the log files provided by the customer the following error was found before the <span id="form1:panelPage1">SBL-UIF-00275 error</span>:<br />- - -<br />...<br />ObjMgrSRFLog Error 1 00000002536a0494:0 2014-05-07 13:35:36 (objdef.cpp (10099)) SBL-DAT-00260: There is no menu item definition at position '7.6' specified as the parent for menu item 'Tools - Reset Active Session Count' in menu 'CRA Generic WEB'.<br />...<br />- - -<br /><br />It appeared the menu 'CRA Generic WEB' was involved in the issue, more especially the child Menu Item 'Help - About Record' that has 7.6 as Position. Indeed a similar issue namely a scenario involving the error SBL-UIF-00275 and the menu 'CRA Generic WEB' has already been reported and is discussed in <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=1671218.1&id=1617023.1">Note 1617023.1</a>.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The customer resolved their issue by applying the configuration fix described in <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=1671218.1&id=1617023.1">Note 1617023.1</a>:<br /><br />In the customer repository, the Menu 'CRA Generic WEB' contained a child Menu Item 'Help - About Record' that was set to inactive ('Inactive' property set to TRUE). They set it to active ('Inactive' property set to FALSE), performed a full compilation and confirmed that their issue was resolved.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.0.0.6 [20423] and later<br />Information in this document applies to any platform.<br />Checked for Relevance on 12-Feb-2015</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Following steps are followed to invoke a custom business service from an external application via Web Client Automation Server:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
(1) Create a custom business service</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
(2) Add the custom business service in Application User Property as follow:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Name: ClientBusinessServiceX</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Value: BS_Name</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
(3) Create a Excel macro which calls the custom business service with Web Client Automation Server as documented in Object Interfaces Reference</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
However, when the excel macro is launched, following error message is displayed on Web Client:</div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
Cannot get service: BS_Name (SBL-UIF-00275)</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The cause of the issue is that the number in the Application User Property is not sequential. Since one of entries in Application User Property is set to Inactive=TRUE, the number in ClientBusinessServiceX is no longer sequential.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As documented in Bookshelf 'Object Interfaces Reference' at [Interfaces Reference]->[Application Methods]->[GetService Method], X in ClientBusinessServiceX must be sequential. Since one of the entries in the application user property was deactivated, the X skipped the number which was deactivated.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Once the entry is activated, or the X is modified to be sequential, the issue is resolved.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-92062190576806452792015-07-28T15:44:00.001-07:002016-02-15T14:01:02.067-08:00SBL-UIF-00272<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel System Software - Version 7.7.2.2 SIA [18356] to 8.1.1.7 SIA [21238] [Release V7 to V8]</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Oracle Solaris on SPARC (64-bit)</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Product Release: V7 (Enterprise)</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Version: 7.7.2.2 [18356] Auto</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database: Oracle 9.2.0.6</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">***Checked for relevance on 06-16-2014*** </span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Application Server OS: Sun Solaris 8</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database Server OS: Sun Solaris 9</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">This document was previously published as Siebel SR 38-3034921141.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
SBL-UIF-00272, SBL-DBC-00107, SBL-SEC-10018, SBL-SEC-10001</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Question :<br /><br />I am not able to log into the Siebel Web Dedicated Client.<br />Whenever I log in, it throws me an error message:<br /><br />SBL-UIF-00272: The user ID or password that you entered is incorrect.<br />Please check the spelling and try again.<br /><br />I am sure about the username and password, but unable to guess what is causing the error.<br />Checked the configuration and it looks good.<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Configuration/ Setup</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Solution :<br />According to the Dedicated Client log file, the Oracle error being trapped was:<br /><br /> ORA-12154: TNS:could not resolve the connect identifier specified<br /><br />This means that the value set on the ConnectString parameter of the CFG file could not be found in Oracle Client’s tnsnames.ora file.<br />However, customer’s tnsnames.ora file includes the alias being used, and the NAMES.DEFAULT_DOMAIN parameter is correctly set in sqlnet.ora file.<br />Customer could connect to the database using SQL*Plus, but ODBC Data Source Name was failing.<br /><br />This issue occurred because customer has multiple Oracle installations on the same client machine.<br />He had manually uninstalled an old Oracle Home, and left the environment variables untouched.<br />Both the ODBC Data Source Name and the Siebel Dedicated Client were searching for the tnsnames.ora file in the wrong location.<br /><br />We confirmed that the %TNS_ADMIN% environment variable was not set on this machine, and that the ORACLE_HOME key was correctly set under HKEY_LOCAL_MACHINE\Software\Oracle branch of the Windows Registry.<br />However, the %PATH% environment variable was showing the old %ORACLE_HOME%\bin directory ahead of the correct %ORACLE_HOME%\bin folder.<br /><br />By running the following command in command console, we could confirm that the wrong binaries were being used:<br /><br /> C:\> tnsping <TNSNAMES_ALIAS><br /><br />Since customer had not correctly uninstalled the old Oracle Home, going to Start > Programs > Oracle Installation Products > Home Selector, he was getting a message telling that there is only one ORACLE_HOME on this machine.<br /><br />In order to resolve this behavior, customer had to manually modify the %PATH% environment variable on Control Panel > System > Advanced > Environment Variables > System Variables, so that the correct %ORACLE_HOME%\bin directory appears ahead of the wrong one.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.1.1.1 SIA [21211] to 8.1.1.8 SIA [23012] [Release V8]<br />Information in this document applies to any platform.<br />***Checked for relevance on 30-Jan-2013*** </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="GOAL"></a>GOAL</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />=== ODM Question ===<br /><br />When user enters credentials for non-existent user that does not exist in the LDAP directory, following error is reported in the UI:<br /><br />"SBL-UIF-00272: The user ID or password that you entered is incorrect. Please check the spelling and try again.".<br /><br />In the object manager log file, you will see errors in following order:<br /><br />GenericLog GenericError 000000064ce4172c 1: 0 11.17.2010 19:04:51 (secmgr.cpp (2731) err = 4597526 sys = 0) SBL-SEC-10006: The authentication system cannot find the user with the username specified. Make sure you typed the user name correctly, or contact your system administrator for assistance.<br /><br />ObjMgrLog 000000064ce4172c Error 1: 0 17.11.2010 19:04:51 (mainlgin.cpp (1695)) SBL-UIF-00272: The logon username / password pair entered is incorrect.<br />Re-enter the logon parameters.<br /><br />How could we show force LDAP security adapter to display first error message SBL-SEC-10006 on the login page when non-existent user tries to login instead of last error message SBL-UIF-00272?<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />=== ODM Answer ===<br /><br />Currently, it is not possible to customize or force LDAP to return the second error message to the user. An enhancement request 12-E29NSZ was logged requesting to customize LDAP messages, however, Siebel Engineering had declined such request and it was recommended that customers write custom security adapter to trap the LDAP messages and customize it. In the vanilla product, it is not possible to customize messages. Siebel is showing message what comes out of LDAP and this is correct behavior.<br /><br />In conclusion, it is not possible to modify the error messages or custom configure what comes out of the LDAP security adapter.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel System Software - Version 7.8.2.5 [19227] and later<br />Siebel CRM - Version 8.1.1.11 [23030] to 8.1.1.11 [23030] [Release V8]<br />z*OBSOLETE: Microsoft Windows Server 2003<br />Product Release: V7 (Enterprise)<br />Version: 7.8.2.5 [19227]<br />Database: Oracle 10.1.0.4<br />Application Server OS: Microsoft Windows 2003 Server SP1<br />Database Server OS: Sun Solaris 9<br /><br />This document was previously published as Siebel SR 38-3383724421.<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
SBL-UIF-00272, SBL-SEC-10006</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Hello,<br /><br />We have an Active Directory Forest with the parent domain and a child domain.<br />We have created all Siebel staff users on the parent domain and Siebel service accounts on the child domain and are trying to use them to authenticate.<br />Any users from the parent domain can log into the child domain.<br /><br />We can display the Graphical User Interface.<br />However, if you attempt to log into Siebel while integrated to the child domain, you receive the following error message:<br /><br />The user ID or password that you entered is incorrect. Please check the spelling and try again.<br />(SBL-UIF-00272)<br /><br />If you check the domain controller on the child domain, it shows that same user authenticating successfully.<br />Why am I not able to log into Siebel?<br /><br />Thanks!</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 10462680</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
Message 1</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
For the benefit of other readers:<br /><br />The current ADSI Driver developed by Siebel was not designed to support an ADSI multi-domain environment, which means that the Siebel Security Adapter architecture currently does not allow multi-domain authentication via ADSI.<br />This functionality is not yet incorporated within the Siebel Application.<br />Also, please note that the use of Global Catalogs is not supported by Siebel Technical Support, since the ADSI Security Adapter was not designed to work with GC, and has not been tested by Siebel Engineering, or certified by our Quality Assurance Team to work with a Global Catalog.<br /><br />In this case, we recommend one of the following approaches, which are in agreement with how the ADSI Security Adapter is intended to work:<br /><br />1. Create all Siebel users under one single domain within Microsoft Active Directory, by moving all Service Accounts from the child domain to the parent domain, for example, and then pointing parameters ServerName and BaseDN to the parent AD Server.<br /><br />2. If you require to maintain Siebel users spread into two distinct domains, you can create a new Application Object Manager for each domain, through the use of distinct Named Subsystems for each AOM, each one pointing to its specific domain.<br /><br /><br />[CONT 1/2...]</div>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
Message 2</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://www.blogger.com/null" name="aref_section31"></a><a href="https://www.blogger.com/null" name="aref_section32"></a></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
[... CONT 2/2]<br /><br /><br />For further details on the use of multiple domains on ADSI, please refer to the following SupportWeb postings:<br /><br /> - <span class="x9s" style="text-decoration: underline;">Multiple Activer Directory Servers (Doc ID 528364.1)</span><br /> - <span class="x9s" style="text-decoration: underline;">ADSI Authentication Using Global Catalog Port 3268 (Doc ID 517259.1)</span><br /> <br />Bug 10462680 was previously logged to address this Enhancement Request, but they have not been implemented yet.<br />The information above is still true for Siebel Version 7.8 and 8.x.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel System Software - Version 8.1.1.2 to 8.1.1.3 SIA[21219] [Release V8]<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="text-decoration: underline;">ENVIRONMENT</span>Siebel 8.1.1.2 / Windows 2003<br /><br /><span style="text-decoration: underline;">STEPS</span><br />Siebel registered users are not able to modify their passwords once expired in Siebel Financial Services application version 8.1.1.2 being authenticated by a Custom Security Adapter on Windows. Rather than being presented with a Siebel screen view to modify the password, an error is presented to the user [1]. The Siebel application object manager (AOM) logfiles clearly indicate that the password for the Siebel user has expired. In the Siebel Dedicated Client the behavior is different - for user accounts with expired passwords - a popup dialog box is presented allowing the Siebel registered user to modify the password.<br /><br /><span style="text-decoration: underline;">EXPECTED BEHAVIOR</span><br />It is expected that the user is automatically directed to the Siebel View "Change Password View (SWE)". This behavior is controlled by the application object manager hidden parameter ChangePasswordView, which is set to "Change Password View (SWE)" by default.<br /><br /><span style="text-decoration: underline;">ERROR MESSAGES</span><br />1) SBL-UIF-00272: The user ID or password that you entered is incorrect. Please check the spelling and try again.<br />2) SBL-SEC-10018: SecurityLogin(): AuthenticationClient Error: 80050010 : AuthenticationService::ExpiredCredentials.<br />3) SBL-SEC-10005: Your password has expired. Please change your password.<br />4) SBL-UIF-00425: Your password has expired, please change it to enter the system.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="color: black;"><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1184476.1&id=10512510" target="_blank">Bug 10512510</a> (Change Request 12-1T2II25) was logged to address a Product Defect where no error or warning was displayed when an account password had expired in an external directory. This is specific to database authentication and not external authentication.<br /><br /><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1184476.1&id=12820579" target="_blank">Bug 12820579</a> has been logged to address an additional Product Defect specific to external authentication.</span></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="color: black;"><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1184476.1&id=10512510" target="_blank">Bug 10512510</a> (Change Request 12-1T2II25) has been fixed in Siebel 8.1.1.1 [21211] QF0154 as part of Fix Request 12-1WF6XDZ. This Quick Fix has since been accumulated into Siebel Fix Pack 8.1.1.3 as per the latest Maintenance Release Guide and available for download under Patch Number 9882361.<br />NOTE: Only applicable for DB authentication (DB2)<br /><br /><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1184476.1&id=12820579" target="_blank">Bug 12820579</a> is still open for external authentication.</span></div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-89903691431964289632015-07-28T15:40:00.001-07:002016-02-15T14:01:02.060-08:00SBL-UIF-00269<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Field Service - Version 8.1.1.7 SIA [21238] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
We are seeing an issue in Order Line Item action regarding Shipping.<br />When we are trying to ship an order line item in Shipping screen, we enter invalid serial number to ship and we get an error and shipping is not complete.<br />But Siebel is creating an Order Line Item action with Ship action. This should not happen.<br />Here are the steps to reproduce the issue:<br /><br />1. create an asset, associate a serializable product.<br />2. create a Service order, Type = Internal Order<br />3. create line item for the service order, pick a serializable product.<br />4. set source and destination in Fulfill<br />5. set asset number in Line Detail (optional)<br />6. click on 'fill all' in Line Items to generate pick ticket<br />7. drill down on pick ticket > shipping<br />8. drill down on pick ticket detail, 1 allocated line is displayed<br />9. click on New, enter Qty = 1<br />10. In Serial Numbers, pick Asset in step 1, click on Process Shipment, get<br />1s error:<br /><br />Asset Number "A10" is not a valid asset from source inventory "Service<br />Inventory".(SBL-SFS-00246)<br /><br /><br />"allocated lines" becomes blank.<br /><br />11. type bogus Serial# within Serial# field, try to step down, get 2nd error:<br /><br /><br />[1]Cannot locate record within view: Fs Shipping information from View<br />applet: FS Order Line Item Action Assets List Applet.(SBL-UIF-00269)<br />[2]Cannot locate record within view:applet:.(SBL-UIF-00269)<br /><br /><br />and application can't get out of the error. Need to end process to close the<br />application.<br />12. Go to Service Order->Line Item->Line Item action and you can see 'Ship'<br />action is created.<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
It is identified to be a new defect in the product.<br /><br />The "allocated lines" should not become blank after getting the 1st error.<br />And the bogus Serial# should not result in killing the application in order to end the 2nd error.<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Create the new BUG 16608115 - SHIPPING LINE ACTION IS GETTING CREATED EVEN IF THERE IS A ERROR IN SHIPPING SCR<br />for fixing the defect in 8.1.1.7 QF.<br />The patch ID: 16762436, which is for 8.1.1.7 21238 SIA QF07DD is available for download in My Oracle Support > Patches & Updates.<br />Just enter 16762436 for Patch Number and click on Search to find it. It is available for Windows and Linux platforms.<br /><br />In addition, it is fixed in 8.1.1.11FP, it is tracked by BUG 16538808.<br /><br />The patch fixes 2 problems reported in steps 10 and 11: Applet becoming blank, and Unable to edit the serial number. The step 12, "Go to Service Order->Line Item->Line Item action and you can see 'ship' action is created."<br />wont be fixed since this is not a bug and it is how application is designed to work.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.1.1.3[21219] and later<br />Information in this document applies to any platform.<br />""Checked for relevance on 02-SEP-2013""</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Siebel Version: 8.1.1.3<br /><br />Statement Of Issue: Error thrown when trying to select a record from Popup Applet in Clinical Protocol Site Payment Exceptions List Applet.<br /><br />Steps to Reproduce:<br />1. Click on Centre Management screen.<br />2. Go to Clinical Protocol Site Payment Exceptions Detail View.<br />3. Click on Copy FNB button on Clinical Protocol Site Payment Exceptions List Applet<br />4. In the Popup Applet, try to change the current record.<br /><br />Error Thrown:<br /><br />SBL-UIF-00313 An error happened during restoring the context for the requested location occurring when selecting a record in Popup Applet<br />SBL-UIF-00269: Cannot locate record within view: Clinical Protocol Site Payment Exceptions View applet: Clinical Protocol Site Payment Exceptions List Applet. - when trying to close the popup applet.<br /><br />Business Impact:<br />Copying FNB is a very important functionality for business users. As they copy the final negotiated budgets to few other centres.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The issue is caused due to wrong configuration of Popup Applet.<br /><br />The popup applets are configured for Detailed records in Master detail view. For example, Account Contact view, Popup applet can have records for the contacts for given account.<br />Customer is trying to configure a popup applet for Master record. It is not feasible to configure in that way.<br /><br />In customer environment, the parent BC is Clinical Protocol Site and the pop up applet invoked on child applet is based on Parent BC which is not accepted.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Make a copy of parent BC and use this BC for Popup Applet.<br /><br />1. Copy the parent BC: Clinical Protocol Site and name it as ETR Select Centres.BC<br />2. Use ETR Select Centres.BC as the BC for ETR Select Centres Applet.<br />3. Add ETR Select Centres.BC to the Clinical Protocol Site Business Object with no link.<br />4. Compile all the changes and retest the issue</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Call Center - Version 8.1.1.9 [23016] to 8.1.1.11 SIA [23030] [Release V8]<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On 8.1.1.9 Fix Pack when attempting to execute F9 integrated with MS Outlook from Service Request Detail Applet and with focus on a Service Request Attachment so the attachment file automatically get populated in MS Outlook client when F9 is invoked the MS Outlook Client pop up and is bring to front, but the attachment has only part of the original size and after that when going back to Siebel Application the following error occurs.<br /><br />The problem start to happen after upgrade from 8.0.0.9 to 8.1.1.9.<br /><br />The user can sucessfully download and open the attachment file from Service Request Attachment List Applet, the problem only happens when using F9 integrated with MS Outlook, the issue does not happens if user uses Siebel Email Client.<br /><br />The problem can NOT be reproduce when using HTTP, only when using HTTPS (SSL) for Siebel Application URL. As part of upgrade the Web Server were also moved to IIS 7.5 from previous IIS/Apache versions.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The issue can be reproduced at will with the following steps:<br />1. Go to Service Request detail view w/attachments applet<br />2. Select an attachment record<br />3. Click F9 integrated with MS Outlook.<br />4. MS Outlook client pop up, it show the attachment, but the size is not the same of the original file.<br />5. Going back to Siebel Application and the pop up error above appear:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
[1] Cannot locate record within view: Service Request detail view w/attachments applet: Service Request Attachment List Applet. (SBL-UIF-00269)<br />[2] An end of file error has occurred.<br />Please contact your system administrator to check your application configuration if the problem persists. (SBL-DAT-00393).<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The beahvior could be reproduced internally using IIS 7.5 with HTTPS (SSL). Using IIS 6.0 the behavior does NOT occur.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 17438761 - F9 WITH OUTLOOK FROM SIEBEL ATTACHMENT FAILS WITH IIS 7.5 AND HTTPS has been opened.<br /><br />The behavior could be reproduce in internal Laboratories and Oracle Engineer confirmed Bug 17438761 - F9 WITH OUTLOOK FROM SIEBEL ATTACHMENT FAILS WITH IIS 7.5 AND HTTPS<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 17438761 - F9 WITH OUTLOOK FROM SIEBEL ATTACHMENT FAILS WITH IIS 7.5 AND HTTPS has been fixed in:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
8.1.1.9/8.2.2.2 Quick Fix 0001125 Patch Number 17838139 for 8.1.1.9 and Patch Number 17838140 for 8.2.2.2.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
8.1.1.10/8.2.2.3 Quick Fix 0002114 Patch Number 17830147 for 8.1.1.10 and Patch Number 17830148 for 8.2.2.3.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
BUG 17832993 has been opened requesting a fix for the next 8.1.1.11/8.2.2.4 PatchSet available too.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
To apply the Quick Fix:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />1. Download and review the readme and pre-requisites for Patch Number above.<br /><br />2. Ensure that you have taken a backup of your system before applying the recommended patch.<br /><br />3. Apply the patch in a test environment.<br /><br />4. Retest the issue.<br /><br />5. Migrate the solution as appropriate to other environments.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Tools - Version 8.1.1.5 SIA [21229] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
On : 8.1.1.5 SIA [21229] version, Configuration - General<br /><br />Error when displaying eService view<br /><br />ERROR<br />-----------------------<br />Cannot locate record within view: PUB GOV Contact Case List View (eService) applet: PUB GOV Contact Case List Applet (eService).(SBL-UIF-00269)<br /><br />STEPS<br />-----------------------<br />User wants to allow eService Public Sector users to submit cases.<br />For that, they have added to the web layout of the PUB GOV eService Account Quick Links Applet, the out of the box control LinkNewCase, linking to the PUB GOV Contact Case List View (eService) view and applet PUB GOV Contact Case List Applet (eService) (specified by control user properties).<br /><br />When trying to access the view, the following error is returned:<br />Cannot locate record within view: PUB GOV Contact Case List View (eService) applet: PUB GOV Contact Case List Applet (eService).(SBL-UIF-00269)<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug: 14090993 was logged to address this issue.<br /><br />Steps to replicate the issue:<br /><br />1. Siebel Tools > Applet > PUB GOV eService Account Quick Links Applet.<br />2. Applet Web Template > Applet Web Template Item.<br />3. Add a control : LinkNewCase<br /><br />Name: LinkNewCase<br />Control: LinkNewCase<br />Item Identifier: 1,304<br /><br />5. This will link to the PUB GOV Contact Case List View (eService) view and applet PUB GOV Contact Case List Applet (eService) (specified by control user properties).<br />6. Compile the object.<br /><br />7. Login to Siebel Public Sector eService (cfg file: psesrv.cfg)<br />8. On the My Account, we can see "Submit a case" control.<br />9. Click on Submit a case.<br /><br />Error >><br /><br />Cannot locate record within view: PUB GOV Contact Case List View (eService) applet: PUB GOV Contact Case List Applet (eService).(SBL-UIF-00269)<br />Error Message: SBL-UIF-00269<br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Following repository fix exists for this behavior.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Object Configuration 1:<br /><br />1. Navigate to the Applet object and query for the Applet “PUB GOV eService Account Quick Links Applet”.<br />2. Navigate to the LinkNewCase control in the Control object.<br />3. Expand the Control object navigate to the Control User Prop object.<br />4. Change the value for the Applet User Property to "PUB GOV Submit Contact Case Form Applet (eService)".<br />5. Change the value for the View User Property to "PUB GOV Submit Contact Case View (eService)".<br />6. Navigate to the ImageNewCase control in the Control object.<br />7. Navigate to the Control User Prop object.<br />8. Change the value for the Applet User Property to "PUB GOV Submit Contact Case Form Applet (eService)".<br />9. Change the value for the View User Property to "PUB GOV Submit Contact Case View (eService)".<br />10. Save the changes.<br /><br />Object Configuration 2:<br /><br />1. Navigate to the Applet object and query for the Applet “PUB GOV Submit Contact Case Form Applet (eService)”.<br />2. Uncheck the No Insert property.<br />3. Save the changes.<br /><br />Object Configuration 3:<br /><br />1. Navigate to the View object and query "PUB GOV Submit Contact Case View (eService)".<br />2. Change the Bus Object property to "HLS Case".<br />3. Navigate to the View Web Template Item child object.<br />4. Set Inactive Property to true for both the Applets "PUB GOV Case Blank Salutation Applet (eService)" and "PUB GOV Contact Hidden Applet (eService)".<br />5. Save the changes.<br /><br />Compile all the three objects changes to the Siebel SRF and launch the application. Now, when the user drill-down from the Submit Case link, it will navigate to the Case view with Edit mode where user can key in the value and submit the Case.</div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
This is a sample configuration to create a new Case from eService. Please note that you can create new objects or modify existing objects to fit your requirement.<br /><br />Key Note:<br />The view should be based on the HLS Case object and the first applet in the view should refer to the Case Applet which captures the input from the user.<br /> </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel CRM - Version 8.0.0.5 SIA [20420] and later<br />Information in this document applies to any platform.<br />***Checked for relevance on 09-May-2012*** </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />Customized<br />=======<br />Customer has configured parent-child views , Association applet to add child records to the parent.<br /><br />When a user selects more than 10 records in the association applet and clicks OK, the records are added successfully.<br /><br />However, the field values in the parent applet are now all blank. And then when the user tries to select a record in the child applet, an error like this appears:<br /><br />[1] Cannot locate record within view: Contact Relationships View applet: Contact Relationship List Applet. (SBL-UIF-00269)<br />[2] An end of file error has occurred.<br /><br /><br />Standard<br />======<br />This particular error was produced using the vanilla Siebel SRF on the Contact > Relationships View, by clicking the New button in the Relationships applet and adding 11 contacts from the "Add Contacts" applet.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />This is product defect.<br /><br />I have tested this issue in house and got the same error.<br /><br />CR 10560501 has been created as product defect to address this issue. that the error pops up based on the HTML Number of Row Displayed Property of the Applet.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The issue you are facing is a Product Defect and will be addressed in future release.For the workaround for this issue is - add less then 10 records and then another record in this way this will work fine.<br /><br />Or select only first 10 record in pick applet then click Ok this is working fine.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
the following scripting work around has been found to work:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Added to assoc applets preinvokemethod:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
if (MethodName == "AddRecord") { var oBO = TheApplication().ActiveBusObject();<br />var oBC_Parent = oBO.GetBusComp(TheApplication().GetService("GS General Utilities").CurrentViewMainBC());<br />var oBC_Child = oBO.GetBusComp(this.BusComp().Name()); var oBC_Assoc = oBC_Child.GetAssocBusComp();<br />var iRecord = oBC_Assoc.FirstSelected();</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
while (iRecord)<br />{<br />try { oBC_Assoc.Associate(NewAfter); }<br />catch(e) { if (Clib.strstr(e.errText, "SBL-DAT-00357") == null) { throw e; } }<br />finally { iRecord = oBC_Assoc.NextSelected(); } } </div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
oBC_Child.InvokeMethod("RefreshRecord");<br />oBC_Child.FirstRecord();<br />oBC_Assoc = null; oBC_Child = null;<br />oBC_Parent = null; oBO = null;<br />this.InvokeMethod("CloseApplet");<br />return (CancelOperation); }</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Added to GS General Utilities BS: function CurrentViewMainBC()</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />{ var sMainBC = ""; var sMainApplet = ""; var globalCache = TheApplication().GetSharedGlobal("ViewMainBC" + TheApplication().ActiveViewName());<br />if ((globalCache != "") && (globalCache != null))<br />{ sMainBC = globalCache; }<br />else<br />{ var repBO = TheApplication().GetBusObject("Repository View");<br />var repBC = repBO.GetBusComp("Repository View"); with (repBC) { ActivateField("Name"); ActivateField("Sector0 Applet"); SetViewMode(AllView); SetSearchSpec("Name", "\"" + TheApplication().ActiveViewName() + "\"");<br />ExecuteQuery(ForwardOnly); if(FirstRecord())<br />{ sMainApplet = GetFieldValue("Sector0 Applet"); } }<br />repBC = null; repBO = null;<br />repBO = TheApplication().GetBusObject("Repository Applet");<br />repBC = repBO.GetBusComp("Repository Applet");<br />with (repBC) { ActivateField("Name");<br />ActivateField("Business Component");<br />SetViewMode(AllView);<br />SetSearchSpec("Name", sMainApplet);<br />ExecuteQuery(ForwardOnly);<br />if(FirstRecord()) { sMainBC = GetFieldValue("Business Component"); } }<br />repBC = null; repBO = null; }</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
TheApplication().SetSharedGlobal("ViewMainBC" + TheApplication().ActiveViewName(),sMainBC); return (sMainBC); }</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Also the CR has been fixed for 8.0.0.9 Fix Pack and 8.0.0.6 [20423]QF0624.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-80074842869932868102015-07-28T15:35:00.003-07:002016-02-15T14:01:02.050-08:00SBL-UIF-00230<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 7.8.2.14[19251] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Reviewed for relevance "6-SEP-2013".</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
For Service Request Business Component, I have added the "Deep Copy n" user property in order to copy child attachments of a copied SR. However, for the new-copied SR, I cannot open the attachments and the following error appears:<br /><br />SBL-UIF-00230: The file performance.txt could not be found on any specified file system.<br /><br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The cause of this issue is custom configuration. In custom environment, Deepcopy functionality configured on "Product Defect" & "Related Service Request" BCs. In Standard environment, Product Defect & Related Service Request BCs have parent-child relationship as many-to-many(M:M). As per Bookshelf note, Do not use Deep Copy when the parent-child relationship is many-to many (M:M). Because of the configuration, when user tried to open the attachments, the "SBL-UIF-00230" error occurred.<br /><br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
There are two ways to "Deepcopy" child BC records:<br />(1) By setting "No Copy" of the MVL to child BC to FALSE<br />(2) Using "Deep Copy" BC user property<br /><br />1) By setting "No Copy" of the MVL to child BC to FALSE:<br />With this configuration, the record being copied but "SAF" file is not generating in FS folder, so when we try to open the attached file it will give an error message. This is because the copy is done at the DB level, and since the file is in the files system, and not the DB, then the file itself is ignored. {Please check the Note: <a href="https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=1214003.1&id=1061595.1" target="_blank" title="1061595.1">1061595.1 </a>}<br /><br />2) Using "Deep Copy" BC user property:<br />To configure Deep copy functionality refer <a href="http://docs.oracle.com/cd/B40099_02/books/ToolsDevRef/ToolsDevRef_UserProps69.html#wp477875" target="_blank" title="Book shelf">Bookshelf: Siebel Developer reference>> User Properties >> Business Component User Properties>> Deep Copy n </a><br />Additionally for Service Request Attachment" BC > set ActivityFileName field property Nocopy=N .<br /><br />In customer environment, after disabling the Custom BC user properties (Deep copy3 (Product Defect), Deep copy4 (Related service request BC)) and correcting configuration settings the issue got resolved. Customer is able to open attached document without an error.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Applications - Version 8.1.1.11.5 [IP2013] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When Attachments are copied as child objects during the copy of a parent Project,the copied attachment is not accessible on the file system.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /><span style="text-decoration: underline;"><strong>STEPS</strong></span><br />1. Launch application.<br />2. Navigate to Site Map > Projects > List.<br />3. Create a new Project.<br />4. Drill down to the created Project Name.<br />5. Create an attachment at the child applet Attachments view tab.<br />6. Return to previous Project list applet.<br />7. From the applet view, select Menu item: Copy Record.<br />8. Provide a new name for the new record.<br />9. Drill down on the new record to the Attachments child applet.<br />10. Verify that a copy of the Attachment also exists.<br />11. Select the attachment file with mouse by clicking on the hyperlink.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<em>Result:</em> The following error message displays:</div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em;">
<span style="font-size: x-small;"><strong>"The file xxxx.xxx could not be found on any specified file system.(SBL-UIF-00230)"</strong></span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />The original attachment can launched, when selected; however, the copied Prpject's attachment is not accessible.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The following bug was created to address this behavior<strong>:</strong></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<strong></strong><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1940201.1&id=19022954" target="_blank">BUG 19022954</a> - WHEN COPYING PROJECTS CHILD RECORDS GET COPIED BUT NOT POPULATED PROPERLY<br style="font-size: medium;" /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1940201.1&id=19022954" target="_blank">BUG 19022954</a> "<strong>WHEN COPYING PROJECTS CHILD RECORDS GET COPIED BUT NOT POPULATED PROPERLY"</strong> is being reviewed by Engineering.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel System Software - Version 7.5.3 [16157] and later<br />z*OBSOLETE: Microsoft Windows 2000<br />Product Release: V7 (Enterprise)<br />Version: 7.5.3 [16157]<br />Database: Microsoft SQL Server 2000<br />Application Server OS: Microsoft Windows 2000 Server SP 3<br />Database Server OS: Microsoft Windows 2000 Server SP 3<br /><br />This document was previously published as Siebel SR 38-1166698961.<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The customer was importing a text document as an attachment to a Service Request, the document being part of a MIME Hierarchy. The attachment was imported and could be seen in S_SR_ATT and existed as an saf in the file system. When the attachment was selected in the client application by clicking on the hyperlink in the Service Request > Attachments, the following error was received:<br /></div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
<br />"The file "XXXX" could not be found on any specified file system [SBL-UIF-00230].</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The behavior was re-produced. Change Request <a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=519869.1&id=10474909" target="_blank" title="12-KI0SBD">10474909</a> was logged as a Product Defect. This is described as "Importing MIME documents via workflow doesn't allow attachment to be opened in client."<br /><br />The reason the error is generated is because the FILE_REV_NUM is not being used correctly in the saf naming (the naming convention should be: <Table Name> + <a href="https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=519869.1&attachid=Row%20Id&clickstream=yes" target="_blank">Attachment Row Id</a> + <File_rev_num>.SAF)</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; color: white; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The workaround is to inactive the component field: activityfilerev in the Service Attachments integration object.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-81155588369370560962015-07-28T15:33:00.004-07:002016-02-15T14:01:02.054-08:00SBL-UIF-00229: Error occurred while opening file '%1'<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 8.1.1 [21112] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Error Message Area:UI Framework - UIF</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Version:Siebel 8.1.1 and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Checked for Relevance on **Oct 10 2013**</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00229: Error occurred while opening file '%1'.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>DETAILS</h2>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1"></a>Explanation</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Unable to open the file attachment in the Siebel file system.</div>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2"></a>Corrective Action</h3>
<a href="https://www.blogger.com/null" name="aref_section31" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;"></a><a href="https://www.blogger.com/null" name="aref_section32" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;"></a><br />
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Ask the Siebel Administrator to check the Siebel file system folder and file attributes. The folder is specified by the FileSystem parameter in the configuration file (i.e. uagent.cfg).</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Enterprise Integration Manager - Version 7.5.2.100 [15252] to 8.2.2.4 SIA [23030] [Release V7 to V8]<br />Oracle Solaris on SPARC (64-bit)<br />This document was previously published as Siebel SR 38-987864251.<br />***Checked for relevance on 30-May-2014***<br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When an EIM job run to load an attachment, the following error appear:</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
SBL-UIF-00229</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This issue has been caused by missing file system and its sub-directories.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div class="km" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Customer was running an EIM job to load attachments and received the following error:</div>
<div class="km" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />“Error 420: Sub-process "Insert Att" failed to execute”<br />“Error in AttCopyExternal (UTLZipCompress)”<br /><br />While loading the attachments through EIM, please review the following:<br />1) The attachments exist in the correct directory (Default: <Siebel Home>\Input directory).<br />2) The File System has been created.<br /><br />In this case we found that the File System had not been created. Once the File System was created, the EIM load completed successfully.<br />Information regarding creating the File System can be found in the Bookshelf, Siebel Server Installation Guide for UNIX, Creating a File System.</div>
<div class="km" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div class="km" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div class="km" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel Email Response - Version 8.1.1.10 [23021] to 8.2.2.3 SIA [23021] [Release V8]<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
When attempting to send an Outbound Request from a workflow the email is sent, but Siebel fails to create the corresponding Email - Outbound activity record and the following error occurs in CommOutboundMgr component log:</div>
<div class="kmnotebox" style="background-color: #fff9d7; border: 1px solid rgb(193, 169, 13); font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small; padding: 10px;">
ObjMgrBusCompLog Error 1 00000004520a11a4:0 2013-08-13 05:04:08 (bcactivity.cpp (9689)) SBL-UIF-00229: Error occurred while opening file ''.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The issue only happens to particular email template that has a template item with more than 16KB. The Outbound Request in Site Map >Administration - Communications> Outbound Request Overview show the following status : "Imcompleted" and status message: "Sent 0 out of 0 messages. Error occurred while opening file ''.(<strong>SBL-UIF-00229</strong>)" .</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Also there are several Siebel Server running Communications Outbound Manager some execute the Outbound Request without any problems, some give the error above.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The problem could be reproduced internally and the root cause was a missing folder in Siebel Server Root Folder/BIN called outgoing on some Siebel Servers.<br /><br />When you install Siebel there is no siebsrvr/bin/outgoing folder. This is created when the Communications Outbound Manager Business Services executed a SendMessage method for example a F9 operation or Reply to an inbound email.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />But when you execute an Outbound Request with an email with more then 16KB of size it will create a temporary file on siebsrvr/bin/outgoing folder. This file will be used to create the Email - Outbound activity record with an attachment with name SiebelEmailLong.html. Now if the Siebel Server executing the Outboud Request do not have the siebsrvr/bin/outgoing folder already created the outbound request will fail since it expected the folder to exist.<br /><br /><br /> </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<span style="color: black;"><a href="https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1576175.1&id=17276565" target="_blank">BUG:17276565</a> - OUTBOUND REQUEST FAIL WITH SBL-UIF-00229 WHEN OUTGOING FOLDER IS NOT PRESENT to address this behavior since we can consistently reproduce the issue internally.</span></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As a workaround go to Siebel Server Root Folder/BIN and create a folder called outgoing.<br /><br />This should be done on all Siebel Servers that run CommOutboundMgr component and in the Siebel Server where Outbound Communications Manager Business Services is called with argument ProcessMode=Local.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
At this point in time the above bug has not been guiven the engineering solution for the current version, please apply the workaround and ontatct Technicall Support for more information on that matter.<br /> </div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-67285392629996550102015-07-28T15:32:00.000-07:002016-02-15T14:01:02.033-08:00SBL-UIF-00228<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Product Release: V7 (Enterprise)</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Version: 7.8.2.3 [19221]</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database: Microsoft SQL Server 2005</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Application Server OS: Microsoft Windows 2003 Server</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database Server OS: Microsoft Windows 2003 Server</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">This document was previously published as Siebel SR 38-3341715698.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">SBL-UIF-00228</span><br />
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Hi,<br /><br />We were trying to test the import of AICC Course. We have received a sample AICC course from the client.<br />We did the following as part of set-up:<br /><br />1.Created a new physical directory C:/AICCtestStd<br />2.Created a new virtual directory AICCtestStd with all permissions set; added MIME types:<br />.loc with a MIME type of text/xml<br />.sbs with a MIME type of text/xml<br />3.Placed the contents of the course in the folder C:/AICCtestStd.<br />4.Did the necessary restart.<br /><br />We tried importing the AICC course. In the field for URL of .AU file, we gave the value as "http://<hostname>/AICCtestStd/crs/Lectorakurs.au" and gave the Launch Type as HACP.The system gave me an error "The file 'http://<hostname>/AICCtestStd/crs/Lectorakurs.crs' could not be found.(SBL-UIF-00228)".<br /><br />I have uploaded the sample AICC course in siebel's ftp site in the "Upload" folder. The name of the folder is AICCIII. Could you please try to import the AICC course and see if it goes successfully for you? Please also let us know the detailed steps that you followed for the set-up as well as the procedure for import.<br /><br />Regards, </div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1">Message 1</a></h3>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">For the benefit of other users:</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">It was found that the file Lectorakurs.crs could not be opened using the virtual directory path, using</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">a) IIS</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">b) a browser with the virtual address of the file.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">When setting up the virtual and physical directory for AICC or SCORM training, please note the following:</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">1. The IIS process accesses the file using a different user from the logged-in user:</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">a) With Windows Authentication switched off, it uses its own login; in this case you must grant access to users IWAM_<hostname>, as well as IUSR_<hostname>.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">b) With Windows Authentication switched on, it uses the current user's login ON THE WEB SERVER - this might be the anonymous user login coming from the browser, or an explicit login.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Note that in both cases each directory in the whole directory path must grant this access.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">2. Furthermore, if the physical directory is on a different machine, this will only work for a domain account, because you can only grant access to a physical file for a user who is known on the system where the physical file resides.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">3. The course execution may also require that the following MIME types be added to the virtual directory:</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">.crs with a MIME type of text/xml</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">.cst with a MIME type of text/xml</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">.des with a MIME type of text/xml</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">... continued in next update</span><br />
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2">Message 2</a></h3>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">continued from previous update ...</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Once these changes had been applied to the customer's environment, the course would start successfully but later fail with the following errors:</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">a) Error: 'dragMgr' is undefined</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Code: 0</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">URL: http://<hostname>/AICCTraining/a001_finn_frem_drag_drop.htm</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">This error occurred for a number of different object names. However, the value assignments for each of the "undefined" objects existed file 'a001_finn_frem_drag_drop.htm'.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">b) Error: Object expected</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Code: 0</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">URL: http://<hostname>/AICCTraining/a001_finn_frem_drag_drop.html</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">This was found to be a matter of the course logic itself, and the customer was advised to contact their course provider as it seems that there is some error in the course logic, or the course may not be compatible with the customer's Java Runtime version.</span><br />
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;"><br /></span>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;"><br /></span>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 7.8.2 SIA [19213] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">z*OBSOLETE: Microsoft Windows Server 2003</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Version: 7.8.2 [19213] FRA Fin Svcs</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database: Microsoft SQL Server 2005</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Application Server OS: Microsoft Windows 2003 Server SP1</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Database Server OS: Microsoft Windows 2003 Server SP1</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">This document was previously published as Siebel SR 38-3001645811.</span><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br />In version 7.8.2 [19213] Financial Services, in Tools navigate to ‘ISS Product Administration View’. Admin Mode Flag is TRUE. In customer environment this behavior was reproduced with Admin Mode Flag equal to FALSE but I confirmed that this can be reproduced regardless of this property being TRUE or FALSE.<br /><br />In the BC associated to the applets of this view "Internal Product - ISS Admin", set No Insert, No Update, No Merge and No Delete, Owner Delete to FALSE.<br /><br />Also set No Delete and Owner Delete to FALSE at BC "ISS Product Details BusComp", because the business component "Internal Product - ISS Admin" calls the business component "ISS Product Details BusComp".<br /><br />Note: You may need to compile other related objects again (view, applets, etc) for changes to take effect.<br /><br />The following behavior is reproducible on standard configurations testing against sample database:<br /><br />1. Go to Administration – Document > Literature<br />2. Create a new record by specifying a file name<br />3. Go to Administration – Product<br />4. Go to Columns Displayed and expose Image File Name field<br />5. Create a new record and enter Image File Name (created in step 2)<br />6. After saving this record, try to copy a product record<br />7. The error SBL-UIF-00228 will be displayed: The file '%1' could not be found.<br /><br /><br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Bug 10507984 has been logged to address this behavior.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1"></a></h3>
<a href="https://www.blogger.com/null" name="aref_section31" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;"></a><br />
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
There is currently no configurable workaround.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-22825086447951481292015-07-28T15:30:00.001-07:002016-02-15T14:01:02.007-08:00SBL-UIF-00227: Generic Error in Compression Routine<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Siebel Tools - Version 8.1 [21039] and later</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Information in this document applies to any platform.</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">*** Checked for relevance on 02-AUG-2013 ***</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Error Message Area:UI Framework - UIF</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><span style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: x-small;">Version:Siebel 8.1</span><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;" /><br />
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_PURPOSE"></a>PURPOSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00227: Generic Error in Compression Routine.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_SCOPE"></a>SCOPE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This document is informational and intended for any user.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="REF_TEXT"></a>DETAILS</h2>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref1"></a>Explanation</h3>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Error during reading and compressing a chunk of file data into memory.</div>
<h3 class="km" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 13.6499996185303px; padding-top: 0.5em;">
<a href="https://www.blogger.com/null" name="aref2"></a>Corrective Action</h3>
<a href="https://www.blogger.com/null" name="aref_section31" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;"></a><a href="https://www.blogger.com/null" name="aref_section32" style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;"></a><br />
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
"If possible, get the problematic file and report the problem to Siebel Technical Support."</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
<br /></div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
APPLIES TO:</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Siebel System Software - Version 7.8.2.10 SIA [19241] and later<br />Information in this document applies to any platform.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>SYMPTOMS</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Background<br />-------------------<br />An inbound web service is invoked which is intended to create a Service Request, and optionally also attachment data.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
Problem<br />-------------<br />When just creating a Service Request there is no error. The application is creating errors when creating a Service Request and an Attachment record. The reported error is :-<br /><br />SBL-UIF-00227: Generic Error in Compression Routine<br /><br /><br />Environment<br />--------------------<br />Siebel version : 7.8.2.10<br />Database version : Oracle 10.2<br />OS version : Windows 2000</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="CAUSE"></a>CAUSE</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
The inbound message includes a file name, which the custom scripted Business Service underlying the web service tries to attach, for example "C:\Documents and Settings\mogalgs\Desktop\ABCD1234.csv".<br /><br />The error arises in the custom script trying to attach the file using the CreateFile method :-</div>
<div class="kmcodeblock" style="background-color: #e0eaf1; border: 1px solid rgb(196, 209, 230); font-family: 'Courier New', Courier, monospace; font-size: 11.6999998092651px; margin: 5px 0px 0px; overflow: auto; padding: 0.5em; width: 996.546875px;">
with (bcSRAtt)<br />{<br /> NewRecord(NewAfter);<br /> sReturn = InvokeMethod('CreateFile', sPath, 'ActivityFileName', 'N');</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
This code is running on the Siebel Server, and the file was only physically present on the machine from where the inbound web service was invoked.</div>
<h2 class="km" style="background-color: #777773; border-bottom-color: rgb(196, 209, 230); border-bottom-style: solid; border-bottom-width: 1px; font-family: Arial, Helvetica, sans-serif; font-size: 16.25px; padding-bottom: 6px; padding-left: 8px; padding-top: 6px; text-transform: uppercase;">
<a href="https://www.blogger.com/null" name="FIX"></a>SOLUTION</h2>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
As confirmed by customer, the attachment file was missing from the Siebel Server.</div>
<div style="background-color: white; font-family: Tahoma, Verdana, Helvetica, sans-serif; font-size: small;">
To resolve this, the action was :-<br /><br />1. Copy the file to the Siebel Server.<br />2. Re-run the web service, and ensure the file name passed into the inbound web service is the location of the file on the Siebel Server.</div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-76504429105132226342014-04-17T16:01:00.001-07:002016-02-15T14:01:02.039-08:00SBL-UIF-00212<div dir="ltr" style="text-align: left;" trbidi="on">
<span id="kmPgTpl:r1:ot71" style="color: black; font-size: x-small;"></span><br />
<h2 class="km">
Applies to: </h2>
Siebel Tools - Version 7.7.2.8 [18379] to 8.2.2 SIA[22320] [Release V7 to V8]<br />z*OBSOLETE: Microsoft Windows Server 2003<br />
Product Release: V7 (Enterprise)<br />
Version: 7.7.2.8 [18379]<br />
Database: Microsoft SQL Server 2000 SP4<br />
Application Server OS: Microsoft Windows 2003 Server SP1<br />
Database Server OS: Microsoft Windows 2003 Server SP1<br />
<br />
This document was previously published as Siebel SR 38-3531059381.<br />
<br />
*** Checked for Relevance on 14-NOV-2013 ***<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>Symptoms</h2>
We have a requirement to use the import object for importing records
into a custom table. But there seems to be a restriction of 2000 records
allowed, beyond which we receive this error:<br />
"The maximum number of records allowed for each import operation is
2000. Please break your import file into multiple files containing fewer
than 2000 records or use Siebel Interface Manager.(SBL-UIF-00212) "<br /> <br /> Please advice if there is any way we can overcome this limit.<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="CAUSE"></a>Cause</h2>
The customer had configured an Import Object using Siebel Tools to
import data using Client-side import in Siebel application (via the
applet-level menu import functionality).<br />
Client side import is documented in the Bookshelf 8.1: Configuring
Siebel Business Applications > Configuring Tables, Business
Components, Links, and Business Objects > Customizing a Business
Component Field > <a href="http://docs.oracle.com/cd/E14004_01/books/ConfigApps/ConfigApps_Procedures124.html" target="_blank">Configuring Client-Side Import to Update a Business Component Field</a><br />
<br />
NOTE: In the standard Siebel repository the BC 'Contact' is
configured as an Import Object with fields defined as Import Field child
objects. In standard Siebel application client-side import is available
in "Contacts" screen.<br /> <br /> The customer received the following error when importing data:<br /> - - -<br />
The maximum number of records allowed for each import operation is
2000. Please break your import file into multiple files containing fewer
than 2000 records or use Siebel Interface Manager.(SBL-UIF-00212).<br /> - - -<br /> <br />
The behavior observed when trying to import more than 2000 records is
expected and cannot be changed. This behavior is documented in the
Bookshelf 8.1: Siebel Fundamentals > Sharing Information > <a href="http://docs.oracle.com/cd/E14004_01/books/Fundamentals/Fund_sharinginformation7.html" target="_blank">Importing Data</a><br />
...<br /> You can import a maximum of 2000 records at one time.<br /> ...<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="FIX"></a>Solution</h2>
<br />
If you need to import more than 2000 records at one time the
suggestion is to use Siebel Enterprise Integration Manager (EIM).
Currently, there is no workaround for this.<br />
<a href="https://support.oracle.com/epmos/faces/BugDisplay?id=10515045">Bug 10515045</a> - "Maximum upload capability for the Import Functionality" has been already logged as an enhancment request with no ETA.<br />
</div>
Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-5176827930400549727.post-77662810698622995522014-04-17T15:57:00.002-07:002016-02-15T14:01:02.042-08:00SBL-UIF-00210.You are not connected to a valid file server<div dir="ltr" style="text-align: left;" trbidi="on">
<span id="kmPgTpl:r1:ot71" style="color: black; font-size: x-small;"></span><br />
<h2 class="km">
Applies to: </h2>
Siebel CRM - Version 7.5.2 [16007] to 7.8.2 [19213] [Release V7]<br />Generic Windows<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>Symptoms</h2>
SBL-UIF-00210, SBL-GEN-05009<br />
While hosting the Siebel File System on a Solaris Box and the SAP
Connector Siebel Server on a Windows 2000 machine the following error
was observed when the <a href="http://download.oracle.com/docs/cd/E14004_01/books/ConnSAP/ConnSAPeAIQueue.html" target="_blank" title="EAI Queue">EAI Queue</a> attempted to access the filesystem :<br />
<div class="kmcodeblock">
... ObjMgrLog Error 4 ... (SBL-UIF-00210) You
are not connected to a valid file server. Please contact your system
administrator. ...</div>
<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="CAUSE"></a>Cause</h2>
<br /><br />
<div class="kmnotebox">
Name resolution (DNS) to the gateway server was
incorrect, preventing proper communication with the component File
System Manager ('FSMSrvr')</div>
<br /><br />The 'SAP BAPI tRFC Receiver' component was running on a
Siebel Server (Windows platform) without direct access (file share) to
the Siebel File System.<br />The Siebel File System was hosted by the central Siebel Server instance, installed on the Unix machine (Sun Solaris).<br />The
Siebel File System access for all Sever components (on Windows and Unix
Siebel Servers) was provided via the File System Manager 'FSMSrvr')
component approach (<strong>'Siebel File System' = '*FSM*'</strong> parameter setting).<br /><br />This
is the typical way in Siebel Application version 7 to allow Siebel
Object Manager (like SAP BAPI tRFC BAPI Receiver) to access the Siebel
File System content (for example for work with business component file
attachments).<br /><br />Following diagnostics was provided from Oracle Support, after analyzing the BAPI Receiver detailed log:<br /><br />The
inability to work with the Siebel File System Manager component (*FSM*)
on Solaris machine was just follow-up because of Siebel Gateway
communication problem.<br /><br />The latter, in turn was caused, since the
TCP/IP stack on Windows machine was not able to resolve the not-fully
qualified name (like: 'abc') of the Siebel Gateway host to a valid IP
address:<br /><br /><br /><br />
<div class="kmcodeblock" style="width: 95%;">
"...<br />SisnNetGeneric SisnNetGeneric 3 ... 2768: [TCPIP-client] failed to resolve hostname: abc (err=11001 | <NULL>)<br /><br />GenericLog GenericError 1 ... NSC - ErrCode 5009 SysErr 0<br /><br />GenericLog GenericError 1 ...(scbconn.cpp 5(107) err=5009 sys=0) SBL-GEN-05009: Unable to connect to gateway server<br />...<br /><br />ObjMgrLog
Error 4 ... (SBL-UIF-00210) You are not connected to a valid file
server. Please contact your system administrator. ...<br />..."<br /></div>
<br /><br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="FIX"></a>Solution</h2>
<br /> <br /> The reported behaviour was solved by providing a
full-quailified name of the Siebel Gateway host (like 'abc.xyz.de') in
the Siebel Enterprise Parameters, used by this Siebel Server /
Component:<br /><br /> via named sub-system: 'ServerDataSrc', parameter: 'DSGatewayAddress'<br /> via named sub-system: 'GatewayDataSrc', parameter: 'DSConnectString'<br />
<div class="kmnotebox">
<strong></strong><span id="pt1:sd_r1:0:dv_rDoc:ot71" style="color: black; font-size: x-small;"><strong>WARNING</strong>: Support for this connector is near or at end of life. Please review Document : <a alt="1455674.1" href="https://support.oracle.com/DocumentDisplay?id=1455674.1" target="_blank" title="1455674.1">1455674.1</a> - Siebel CRM Application Connectors (SAP, Oracle Applications) Statement of Direction</span></div>
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-43225993340133399372014-04-17T15:55:00.000-07:002016-02-15T14:01:02.020-08:00SBL-UIF-00146<div dir="ltr" style="text-align: left;" trbidi="on">
<span id="kmPgTpl:r1:ot71" style="color: black; font-size: x-small;"></span><br />
<h2 class="km">
Applies to: </h2>
Siebel Tools - Version 8.0.0.9 SIA[20433] and later<br />Information in this document applies to any platform.<br />
""Checked for Relevance on 23-Jan-2014""<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>Symptoms</h2>
<br /> Siebel Version: 8.0.0.9 SIA<br /> <br /> Statement Of Issue: When
trying to export many records from a VBC based grand child applet error
is thrown. The same is working fine when exporting single record.<br /> <br /> Steps to Reproduce:<br /> 1. Go to Accounts screen<br /> 2. Drilldown on record to go to Invoices history<br /> 3. Export All rows in Query.<br /> <br /> Error Thrown: No rows returned by current BusComp query to export (SBL-UIF-00146)<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="CAUSE"></a>Cause</h2>
<br /> <a href="https://support.oracle.com/epmos/faces/BugDisplay?id=10498588">Bug 10498588</a> [CR#12-ZD6UFU][FR#12-ZUKWOM] EXPORT ON 4TH LEVEL APPLET BASED ON VBC RAISES AN E has been reported for the issue.<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="FIX"></a>Solution</h2>
<br /> 1. Create a button called "Custom Export" Method:"MyExport"<br /> 2. Query Business component for records and write to a file, record by record.<br /> Snap shot of sample code:<br />
<div class="kmcodeblock" style="width: 95%;">
function WebApplet_PreInvokeMethod(MethodName)<br /> {<br /> <br /> If (MethodName == "MyExport")<br /> {<br /> // Logging<br /> fp = Clib.fopen("export.txt",'a');<br /> // Get the Account business object<br /> var AccountBO = TheApplication().GetBusObject("Account"); <br /> // Get the Account business component<br /> var AccountBC = AccountBO.GetBusComp("Account");<br /> with(AccountBC)<br /> {<br /> var Record;<br /> // Clear to query<br /> ClearToQuery();<br /> // Set the required search specification<br /> SetSearchSpec("Id",TheRequiredAccountId);<br /> // Execute query<br /> ExecuteQuery();<br /> if(FirstRecord())<br /> {<br /> // Do while loop scrolling along the records<br /> do<br /> {<br /> Record = GetFieldValue("Id") +","+ GetFieldValue("Name")<br /> Clib.fprintf(fp,"%s\n", Record);<br /> }<br /> while(NextRecord());<br /> Clib.fclose (fp);<br /> }<br /> }<br /> }</div>
<h2 class="km">
<a href="https://www.blogger.com/null" name="REF"></a>References</h2>
<a href="https://support.oracle.com/epmos/faces/BugDisplay?id=10498558">BUG:10498558</a> - [CR#12-ZD6UFU][FR#12-ZSQ5UW] EXPORT ON 4TH LEVEL APPLET BASED ON VBC RAISES<br />
<br />
<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel Financial Services CRM - Version: 8.0.0.1 SIA [20408] and later [Release: V8 and later ]<br />Information in this document applies to any platform.<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="SYMPTOM"></a>Symptoms</h2>
I am trying to export all Activities rows and all columns to Excel.<span> </span>The systems issues the following error message:<br />
"No rows returned by current BusComp query to export!(SBL-UIF-00146)".<br />
It works fine when exporting only visible columns.<br />
There are no problems when exporting all Accounts or All Contacts.<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="CAUSE"></a>Cause</h2>
<br />Menu Export of All Activities (Columns to Export: All) returns
error message only happening in version 8.0. and CR 10534861 has been
raised as Product defect . <br />
This was found to be a configuration defect in Siebel SIA
<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="FIX"></a>Solution</h2>
This issue tested with standard srf , able to reproduce the issue in in-house testing.<br />
Bug has been raised the Bug#10534861Issue will be fixed in Siebel
version 8.0.0.12. The fix request for this matter is addressed in: BUG
11798902 - MENU EXPORT OF ALL ACTIVITIES (COLUMNS TO EXPORT: ALL)
RETURNS ERROR MESSAGE<br />
workaround <br />
1) Display all column in list applet -
select all columns in visible by using column display then Export. I
have tested with this.This<span> </span>is working fine.<br />
This was found to be a configuration defect in Siebel SIA :<br /><br />Business
component 'Action' has a join 'S_INCIDENT' for which the Outer Join
Flag is not set. The field 'Incident Name' is based on this join.<br />So what is happening is the following:<br />-
when you are going to the applet, the field Incident Name is not
exposed, so this join is not used for the query and you will find
activities.<br />- likewise if you export with the visible columns only,
since this field is not visible the join will not be added and you will
still find all activites.<br />- but if you export with all columns, you
will ask for this field 'Incident Name' too, so the join will be added
to the query and as it is not an outer join it will lead to an inner
join. Since the activities don't have matching incidents, the query
returns no row and this explains the error observed.<br /><br />In order to correct this defect, please open Siebel Tools against your repository and change the configuration as follows:<br />1. Go to the Join definitions below business component 'Action'.<br />2. Select join 'S_INCIDENT' and set the Outer Join flag.<br />3. Compile the change. <br /><br />This will eliminate the error on the file export in a standard Siebel SIA environment.<br />
<h2 class="km">
<a href="https://www.blogger.com/null" name="REF"></a>References</h2>
<a href="https://support.oracle.com/epmos/faces/BugDisplay?id=10534861">BUG:10534861</a> - [CR#12-1MZ3F6V][FR#12-1MZ3F7P] MENU EXPORT OF ALL ACTIVITIES</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-28792520111659818952013-04-05T17:11:00.003-07:002014-01-23T11:36:06.020-08:00SBL-SVR-01074<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km">
Applies to: </h2>
Siebel Assignment Manager - Version: 7.5.3 [16157] and later [Release: V7 and later ]<br />z*OBSOLETE: Microsoft Windows 2000<br />
Product Release: V7 (Enterprise)<br />
Version: 7.5.3 [16157]<br />
Database: Oracle 9i<br />
Application Server OS: Microsoft Windows 2000 Server SP 2<br />
Database Server OS: Redhat Linux Advanced Server 2.1<br />
<br />
This document was previously published as Siebel SR 38-1464958381.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
Customer getting the following messages in the Assignment Manager Log<br /><br />021
2004-07-28 22:41:53 2004-08-20 18:44:08 -0700 00000005 001 001f 0001 09
AsgnSrvr 31802 4964 792 C:\sea752\siebsrvr\log\AsgnSrvr_31802.log 7.5.3
[16157] ENU ServerLog LstnObjInherit 3 <br />2004-07-28 22:41:53 Inherited listening object for port 49159 ServerLog LstnObjPrivCreate 3 <br />2004-07-28
22:41:53 Created port 49177 for Assignment Manager
GenericLog GenericError 1 2004-08-20 18:43:36 (scirkey.cpp
13(819) err=2001074 sys=0) SBL-SVR-01074: Routing key All AM Rule Set
was not found GenericLog GenericError 1 2004-08-20
18:43:36 (scirkey.cpp 13(285) err=2001074 sys=0) SBL-SVR-01074:
Routing key (null) was not found
GenericLog GenericError 1 2004-08-20 18:43:36 (scirkey.cpp
13(1020) err=2001074 sys=0) SBL-SVR-01074: Routing key (null) was not
found<br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CHANGE"></a>Changes</h2>
some assignment rules were changed when the error started
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
<br />This is a benign error in the log file and can be ignored.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
To avoid this error message in the log file, Please set the logging level to minimal for the assignment manager component.<br /><br />There is an existing change request 12-M7NBG9 logged for this error messages in the log file.<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel Test Automation Interfaces - Version 8.0 SIA [20405] to 8.2.2.2 SIA[23016] [Release V8]<br />Information in this document applies to any platform.<br />
Checked for relevance 28-02-2012
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="GOAL"></a>Goal</h2>
<br />How to change advanced component parameter using srvrmgr, e.g. set MaxSkillsAge to 60 for comp AsgnSrvr?<br /><br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Fix</h2>
<br />Please note that you will need to specify the "advanced" keyword
when listing the parameter but not when changing or modifying the
parameter setting. The command should be used as below.<br /><br />srvrmgr> list advanced param MaxSkillsAge for comp AsgnSrvr<br /><br />srvrmgr> change param MaxSkillsAge=60 for comp AsgnSrvr<br />
<br />
<br />
Note:<br />
Running the following command will give error:<br />
srvrmgr>change advanced param MaxSkillsAge=60 for comp AsgnSrvr <br />SBL-GEN-00001: (svradml.cpp: 222) error code = 1, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null) <br /><br /><br />There were following Generic Error in AsgnSrvr logs:: <br /><br />GenericLog
GenericError 1 0 2010-08-30 22:17:19 (scirkey.cpp (286) err=2001074
sys=0) SBL-SVR-01074: Routing key All AM Rule Set was n <br />ot found. <br />GenericLog
GenericError 1 0 2010-08-30 22:17:19 (scirkey.cpp (1021) err=2001074
sys=0) SBL-SVR-01074: Routing key All AM Rule Set was <br />not found. <br />Generic Error 1 0 2010-08-30 22:17:19 Could not deregister default key "All AM Rule Set" <br />
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-10334729581056863102013-04-05T17:04:00.002-07:002014-01-23T11:36:06.014-08:00SBL-SVR-01069<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km">
Applies to: </h2>
Siebel Scheduling - Version: 7.8.2.2 SIA [19219] and later [Release: V7 and later ]<br />IBM AIX on POWER Systems (64-bit)<br />
Product Release: V7 (Enterprise)<br />
Version: 7.8.2.2 [19219] NLD Pub Sect<br />
Database: Oracle 10g<br />
Application Server OS: IBM AIX 5L 5.2<br />
Database Server OS: IBM AIX 5L 5.2<br />
<br />
This document was previously published as Siebel SR 38-3035897353.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
The customer had created a new Siebel environment and copied the
database from another existing environment to this new environment.<br />-
The initial server key mappings for the Appointment Booking Service
(ABS) were in the database when it was copied to the new environment.
This means that the new environment had server key mappings which
pointed to a non-existing server.<br />- When it was first started, ABS errored out due to the fact that the server key mappings were invalid.<br />-
The server key mappings were updated with the new Siebel server name,
and the Siebel service was restarted after changing the server key
mappings.<br />- When the Siebel server is restarted, the ABS tries to start but fails with SIGABRT.<br /><br />The Siebel server log says:<br />..<br />ServerLog
ProcessCreate 1 0 2006-05-10 16:03:18 Serverproces met
meerdere threads aangemaakt (PID besturingssysteem = 376842) voor
Appointment Booking Engine met taak-ID 6306<br />ServerLog ProcessExit
1 0 2006-05-10 16:04:02 ApptBook 6306
SBL-OSD-02006 Process exited with error - Proces beëindigd vanwege
ontvangen van signaal SIGABRT.<br />..<br />After 10 retries it gives up.<br /><br />In the ApptBook log it says:<br />..<br />GenericLog
GenericError 1 0 2006-05-09 18:21:30 (scirkey.cpp (215)
err=2001069 sys=0) SBL-SVR-01069: Deze component, die gebruikmaakt van
unieke sleutels, probeert een bestaande sleutel vast te leggen (1-URXGL)<br />GenericLog
GenericError 1 0 2006-05-09 18:21:30 (scirkey.cpp (987)
err=2001069 sys=0) SBL-SVR-01069: Deze component, die gebruikmaakt van
unieke sleutels, probeert een bestaande sleutel vast te leggen (1-URXGL)<br />Execution
Warning 2 0 2006-05-09 18:21:30 De engine kan
serviceregio 1-URXGL (1) niet registreren bij Siebel Server SRCWIT102.<br />Execution
Warning 2 0 2006-05-09 18:21:30 De engine kan geen
serviceregio registreren bij Siebel Server SRCWIT102.<br />..<br />This behavior happens when executing the BusSvcMgrInit and ReloadServiceRegion methods.<br /><br />Translation of error messages:<br />* SBL-OSD-02006 - Process exited because it received signal SIGABRT.<br />* SBL-SVR-01069 - This component is using unique keys and it is trying to register an existing key (1-URXGL)<br />* SBL-ABS-00109 - The engine failed to register any service region with Siebel server 'SRCWIT102'
<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
<br />The behavior was caused by the previously existing server key mappings pointing to a different environment. <br />It
seems that somewhere the server key mapping is stored and even after
updating it and restarting the Siebel server, it still has not
deregistered the previous server key.<br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
Just changing the server key mappings to the correct Siebel server did not resolve the behavior.<br />It was necessary to recreate the mappings by deleting and adding the correct lines.<br /><br /><br />
Keywords: SBL-ABS-00109, SBL-ABS-00110, Server Key Mappings, Register,
Service Region, BusSvcMgrInit, ReloadServiceRegion, ApptBook, ABS,
Optimizer<br />
<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel Scheduling - Version: 8.0.0.8 SIA[20430] and later [Release: V8 and later ]<br />Information in this document applies to any platform.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
ABS is not loading the service regions on all Siebel Servers upon Siebel Server service or ApptBook component restart.<br />
<br />
Specific Error Message:<br />
<br />
GenericLog GenericError 1 000000054ca3f0fe:0 2010-09-29 17:39:06
(scirkey.cpp (232) err=1311789 sys=0) SBL-SVR-01069: This component is
using unique keys and it is trying to register an existing key
(1-8E7-113)<br />
GenericLog GenericError 1 000000054ca3f0fe:0 2010-09-29 17:39:06
(scirkey.cpp (1047) err=1311789 sys=0) SBL-SVR-01069: This component is
using unique keys and it is trying to register an existing key
(1-8E7-113)<br />
Execution Warning 2 000000054ca3f0fe:0 2010-09-29 17:39:06 The
engine failed to register service region '1-8E7-113 (1)' with Siebel
Server 'aixprd10'.<br />
GenericLog GenericError 1 000000054ca3f0fe:0 2010-09-29 17:39:06
(scirkey.cpp (232) err=1311789 sys=0) SBL-SVR-01069: This component is
using unique keys and it is trying to register an existing key
(1-8E7-100)<br />
GenericLog GenericError 1 000000054ca3f0fe:0 2010-09-29 17:39:06
(scirkey.cpp (1047) err=1311789 sys=0) SBL-SVR-01069: This component is
using unique keys and it is trying to register an existing key
(1-8E7-100)<br />
Execution Warning 2 000000054ca3f0fe:0 2010-09-29 17:39:06 The
engine failed to register service region '1-8E7-100 (2)' with Siebel
Server 'aixprd10'.<br />
<br />
Sequence of Event:<br />
<br />
1. Restart Siebel Server service or ApptBook component.<br />
The ApptBook component is enabled and online.<br />
2. Service Regions are loaded in ABS cache with error SBL-SVR-01069.<br />
<br />
What is working:<br />
<br />
Click on Load ABS on each Service Region to reload all the service
regions, and all are loaded and registered successfully without error
SBL-SVR-01069. <br />
<br />
<br />
Environment:<br />
<br />
Affecting Assignment Booking in both UAT and Production environments.<br />
Siebel version: 8.0.0.8 SIA [20430] QF0858 , Siebel Server: IBM AIX on POWER Systems (32-bit), Database: Oracle 10.2.0.4<br />
UAT has one Siebel Server 'aixuat06', it is a multi-processor machine.<br />
Production has two Siebel Servers 'aixprd10' and 'aixprd14', both are multi-processor machines.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
On multiprocessor machine, Service Regions can be mapped to ApptBook
component on multiple processess, and each process is represented by a
process#. It is accomplished by setting MinMTServers = MaxMTServers >
1for ApptBook component, e.g., MinMTServers = MaxMTServers = 4 for
ApptBook component. And the error SBL-SVR-01069 in loading Service
Regions only happens to Service Regions mapped to multiple processes,
i.e., more than one process#. If Service Regions are mapped to ApptBook
component on one process only which is accomplished by setting
MinMTServers = MaxMTServers = 1, then the error SBL-SVR-01069 doesn't
happen when loading Service Regions.<br />
<br />
<br />
The service regions loaded in the very 1st process don't have the error,
and in ApptBook log for Process 1 doesn't have any error, this can be
seen in ApptBook_0025_26214403.log from Logs_101310.zip:<br />
<br />
Execution Trace 3 000000054cb670ee:0 2010-10-13 16:11:27 The engine
registered service region '1-EEUQWC (1)' with siebel server 'aixuat06'.<br />
Execution Trace 3 000000054cb670ee:0 2010-10-13 16:11:27 The engine
registered service region '1-EEUQWO (1)' with siebel server 'aixuat06'.<br />
<br />
The service regions loaded after 1st process have the error, because for
each process ApptBook always starts with all service regions with
Service Region's ROW_ID and Process# in ascending order, we can see from
ApptBook_0027_28311555.log from Logs_101310.zip the SQL being executed
in the log that select all service regions with Service Region's ROW_ID
in ascending order, and the error:<br />
<br />
ObjMgrSqlLog Detail 4 000000054cb6901c:0 2010-10-13 16:11:26 SELECT statement with ID: 3056F2F8<br />
SELECT /*+ ALL_ROWS */<br />
T2.CONFLICT_ID,<br />
T2.LAST_UPD,<br />
T2.CREATED,<br />
T2.LAST_UPD_BY,<br />
T2.CREATED_BY,<br />
T2.MODIFICATION_NUM,<br />
T2.ROW_ID,<br />
T2.COMPONENT_ID,<br />
T1.NAME,<br />
T2.PROCESS_NUM,<br />
T2.SERVER_NAME,<br />
T2.SRV_REGN_ID<br />
FROM <br />
SIEBEL.S_SRM_ACTION T1,<br />
SIEBEL.S_SCH_SRV_MAP T2<br />
WHERE <br />
T2.COMPONENT_ID = T1.ROW_ID AND<br />
(UPPER(T2.SERVER_NAME) LIKE UPPER(:1) AND T1.NAME = :2)<br />
ORDER BY<br />
T2.PROCESS_NUM, T2.SRV_REGN_ID<br />
ObjMgrSqlLog Detail 4 000000054cb6901c:0 2010-10-13 16:11:26 Bind variable 1: aixuat06<br />
ObjMgrSqlLog Detail 4 000000054cb6901c:0 2010-10-13 16:11:26 Bind variable 2: ApptBook<br />
<br />
GenericLog GenericError 1 000000054cb6901c:0 2010-10-13 16:11:27
(scirkey.cpp (232) err=1311789 sys=0) SBL-SVR-01069: This component is
using unique keys and it is trying to register an existing key
(1-EEUQWC)<br />
GenericLog GenericError 1 000000054cb6901c:0 2010-10-13 16:11:27
(scirkey.cpp (1047) err=1311789 sys=0) SBL-SVR-01069: This component is
using unique keys and it is trying to register an existing key
(1-EEUQWC)<br />
Execution Warning 2 000000054cb6901c:0 2010-10-13 16:11:27 The engine
failed to register service region '1-EEUQWC (1)' with Siebel Server
'aixuat06'.<br />
<br />
The ones already loaded will get the error, as shown as above error,
until it gets to the ones to be loaded on the designated process#, and
then load them successfully in the designated process#:<br />
<br />
Execution Trace 3 000000054cb6901c:0 2010-10-13 16:11:27 The engine
registered service region '1-EEUQVX (2)' with siebel server 'aixuat06'.<br />
Execution Trace 3 000000054cb6901c:0 2010-10-13 16:11:27 The engine
registered service region '1-EEUQWX (2)' with siebel server 'aixuat06'.<br />
<br />
And it goes like this until all Service Regions in all processes are loaded.<br />
<br />
<br />
<br />
<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
1. Use the existing Service Region configuration in place which is multiple server processor mappings, no changes needed:<br />
<br />
- MinMTServers = MaxMTServers = 4 for ApptBook component on each Siebel Server.<br />
- Map Service Regions to one of the 4 process#: 1, 2, 3, 4 for ApptBook
component on Siebel Servers in Server Key Mappings In client application
> Site Map > Administration - Scheduling:<br />
<br />
PROCESS_NUM SERVER_NAME SRV_REGN_ID COMPONENT_ID<br />
4 aixuat06 1-EEUQVL 1-35D5<br />
4 aixuat06 1-EEUQVO 1-35D5<br />
3 aixuat06 1-EEUQVR 1-35D5<br />
3 aixuat06 1-EEUQVU 1-35D5<br />
2 aixuat06 1-EEUQVX 1-35D5<br />
3 aixuat06 1-EEUQW0 1-35D5<br />
3 aixuat06 1-EEUQW3 1-35D5<br />
3 aixuat06 1-EEUQW6 1-35D5<br />
4 aixuat06 1-EEUQW9 1-35D5<br />
1 aixuat06 1-EEUQWC 1-35D5<br />
4 aixuat06 1-EEUQWF 1-35D5<br />
3 aixuat06 1-EEUQWI 1-35D5<br />
3 aixuat06 1-EEUQWL 1-35D5<br />
4 aixuat06 1-EEUQX0 1-35D5<br />
1 aixuat06 1-EEUQWO 1-35D5<br />
3 aixuat06 1-EEUQWR 1-35D5<br />
4 aixuat06 1-EEUQWU 1-35D5<br />
2 aixuat06 1-EEUQWX 1-35D5<br />
<br />
<br />
2. The error SBL-SVR-01069 in loading Service Regions in the multiple
processor mappings should be benign and can be ingored. The Service
Region's Server Key Mappings should be correct. The Documentation
Enhancement CR 10602873 has been created to document the following in
Siebel Field Services Guide:<br />
<br />
=====<br />
Multiple Processor Support documentation needs to include the following:<br />
<br />
Restarting Siebel Server which restarts ApptBook component, you get
error SBL-SVR-01069 in Process 2 trying to load the Service Region
already loaded on Process 1:<br />
<br />
SBL-SVR-01069: This component is using unique keys and it is trying to register an existing key (1-CSIQ)<br />
The engine failed to register service region '1-CSIQ (1)' with Siebel Server 'siebsrvr1'.<br />
<br />
Book an appointment with service region 1-CSIQ right after without
reloading by executing Load ABS on 1-CSIQ, and it is successful.<br />
<br />
Explanation is as long as Service Regions are mapped to multiple
processes, you will get SBL-SVR-01069 for higher process# > 1 because
Service Regions are loaded sequentially starting with lowest process#
during ApptBook component starts up, the error SBL-SVR-01069 is
informational, it is benign.<br />
=====<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel Scheduling - Version: 7.5.3.4 SIA [16180] and later [Release: V7 and later ]<br />z*OBSOLETE: Microsoft Windows 2000<br />
Product Release: V7 (Enterprise)<br />
Version: 7.5.3.4 SIA [16180] and above<br />
Database: Any Database<br />
Application Server OS: Any Application Server OS<br />
Database Server OS: Any Database Server OS<br />
<br />
<br />
This document was previously published as Siebel SR 38-2743675661.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
<br />Customer created a workflow process which uses the "Server Request"
business service to submit a request to the Appointment Booking Service
(ABS) to run the ReloadServiceRegion method. This workflow process is
scheduled to run every day at 5:00 AM.<br /><br />When the Siebel Server
services first come up, the Appointment Booking Engine is also online
and the ApptBook component is able to register each service region and
load each service region into cache. Users are then able to book
appointments throughout the day. However, once the workflow process to
reload service region is executed the following happens:<br /><br />a. The resulting ApptBook task that attempts to reload service regions fails with error message:<br />GenericLog
GenericError 1 2005-12-16 05:02:33 (scirkey.cpp 13(986)
err=2001069 sys=0) SBL-SVR-01069: This component is using unique keys
and it is trying to register an existing key ((null))<br />Execution
Warning 2 2005-12-16 05:02:33 The engine failed to register
service region '1-1J6MMA (1)' with Siebel server 'V04751S846'.<br /><br />b.
The ApptBook component stopped returning appointments to the users.
Rather, the ApptBook component returned an error message to the user as
follows: <br />ApptBook with key [1-1J6MMA] is not available<br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
<br />Upon checking the customer's log files, they revealed the following:<br /><br />----------------------------------------<br /><br />[1] The ApptBook component came up when Siebel Server started:<br /><br />ServerLog
ProcessCreate 1 2005-12-15 16:49:30 Created multithreaded
server process (OS pid = 3032) for Appointment Booking Engine with task
id 51265<br />....<br />ServerLog ProcessCreate 1 2005-12-16
05:02:18 Created server process (OS pid = 2836) for Siebel Server
Scheduler with task id 51499<br />; A new ApptBook process started here,
before the original one even completed. It is unclear at this time why a
new ApptBook process was started.<br />....<br />ServerLog ProcessExit 1 2005-12-16 05:17:05 ApptBook 51265 SUCCESS Process completed Successfully<br />; After 15 minutes the original ApptBook process was shutdown.<br /><br />----------------------------------------<br /><br />[2]
In the ApptBook_51265.log component log file for the above old process,
we can see all 4 service regions registered and loaded:<br /><br />2021
2005-12-15 16:49:31 2005-12-16 05:17:05 -0500 00003f99 001 001f 0001 09
ApptBook 51265 3032 3028 C:\sea752\siebsrvr\log\ApptBook_51265.log
7.5.3.12 [16272] ENU<br />....<br />Execution Trace 3 2005-12-15
16:50:06 The engine registered service region '1-1J6MMA (1)' with
siebel server 'V04751S846'.<br />Execution Trace 3 2005-12-15
16:50:06 The engine registered service region '1-1J6MMB (1)' with
siebel server 'V04751S846'.<br />Execution Trace 3 2005-12-15
16:50:06 The engine registered service region '1-1LFGZZ (1)' with
siebel server 'V04751S846'.<br />Execution Trace 3 2005-12-15
16:50:06 The engine registered service region '1-1LFH00 (1)' with
siebel server 'V04751S846'.<br />....<br /><br />----------------------------------------<br /><br />[3] For the new ApptBook process, the component tried to register a service region with the Server Request Broker but failed:<br /><br />2021
2005-12-16 05:02:18 0000-00-00 00:00:00 -0500 00000000 001 001f 0001 09
ApptBook 51499 2836 2812 C:\sea752\siebsrvr\log\ApptBook_51499.log
7.5.3.12 [16272] ENU<br />....<br />GenericLog GenericError 1
2005-12-16 05:02:33 (scirkey.cpp 13(214) err=2001069 sys=0)
SBL-SVR-01069: This component is using unique keys and it is trying to
register an existing key (1-1J6MMA)<br />GenericLog GenericError 1
2005-12-16 05:02:33 (scirkey.cpp 13(986) err=2001069 sys=0)
SBL-SVR-01069: This component is using unique keys and it is trying to
register an existing key ((null))<br />Execution Warning 2
2005-12-16 05:02:33 The engine failed to register service region
'1-1J6MMA (1)' with Siebel server 'V04751S846'.<br />ObjMgrBusCompLog Delete 4 2005-12-16 05:02:33 BusComp was deleted d8bd578 "Scheduler Server Keys"<br />SQL SQL 4 2005-12-16 05:02:33 4 row(s) retrieved by ID: D9DDB20<br />Execution
Warning 2 2005-12-16 05:02:33 The engine failed to register
any service region with Siebel server 'V04751S846'.<br />ObjMgrBusServiceLog
InvokeMethod 4 2005-12-16 05:02:33 Business Service
'Appointment Booking Service' invoke method 'BusSvcMgrInit' Execute
Time: 0.178 seconds.<br />....<br /><br />It seems that the original ApptBook
process/pid was up along with the Siebel Server services and it was
working fine. However, somehow another ApptBook process got started and
caused the original one to shutdown. The new pid was not able to
register with SRBroker as SRBroker already saw the same key from the
earlier ApptBook task, and it cannot register an existing key.<br /><br />----------------------------------------<br /><br />[4] When checking one of the ApptBook log files that had some parameter information, this information was found:<br /><br />TaskConfig TaskCfgParamInit 4 2005-12-16 05:02:18 Maximum MT Servers : 5<br />TaskConfig TaskCfgParamInit 4 2005-12-16 05:02:18 Memory-based multithread component recycling : FALSE<br />TaskConfig TaskCfgParamInit 4 2005-12-16 05:02:18 Process memory usage limit : 1500<br />TaskConfig TaskCfgParamInit 4 2005-12-16 05:02:18 Minimum MT Servers : 1<br />TaskConfig TaskCfgParamInit 4 2005-12-16 05:02:18 Maximum Tasks : 20<br /><br />Note how Max MT = 5, meaning that if needed, there can be 5 ApptBook concurrent processes running.<br />Min MT = 1, meaning that when ApptBook component first comes online, only one ApptBook process is running.<br /><br />Maximum
Tasks = 20, meaning that 1 process can only handle 20 concurrent tasks.
If the 21st request comes into ApptBook, then a new ApptBook process is
started up to handle the 21st - 40th concurrent tasks. This is the
reason why the new ApptBook process was automatically started while the
original ApptBook process was still running.<br /><br />However, the new
ApptBook process could not register itself nor the service regions with
SRBroker because the Server Key Mappings says that all service regions
are running on ApptBook process # 1 (Process # 1 being the 1st ABS
process that was started from the Siebel server services startup).<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<br />In order to address this behaviour, customer was suggested to do the following:<br /><br />1.
Customer currently has all service regions registered to Process # 1 of
ABS. Thus, they should only have Minimum MT Server = 1. If it is
expected that there would be more than 20 concurrent tasks for ABS, the
Maximum Tasks parameter value on on ABS can be increased to 100 tasks.<br /><br />2.
Then, change the Maximum MT Server on ABS to 1, so that there is only
one ABS process running on the system since all the service regions in
this case are registered to only 1 process anyway.<br /><br />3. After applying above changes, restart the Siebel servers.<br /><br />If
having Min and Max MTS = 1 and Maximum Tasks = 100 is not able to
support the number of concurrent requests for ABS, another alternative
is to do the following:<br /><br />Set Min and Max MTS = 4<br />Update the Service Region's Server Key Mapping to have 1 Service Region per ApptBook Process #:<br /><br />Service Region 1 -> Process # 1<br />....<br />Service Region 4 -> Process # 4<br /><br />This way, the load can be distributed across multiple ApptBook processes according to service regions.<br /><br />This
customer applied the approach to set Min MT = 1, Max MT = 1, Max Tasks =
100, all 4 service regions mapped to Process # 1 of ApptBook component,
and this setting helped resolve the behaviour they were seeing. When
their workflow runs to reload service regions, each service region was
reloaded successfully. In addition, the ApptBook component continued to
work properly to return appointments to the users after the service
region cache was updated.<br /><br /><br />Search keywords: ABS, apptbook,
book appointment, reload service region, workflow, submit, request,
error, failure, component, restart, shutdown, recycle, startup, This
component is using unique keys and it is trying to register an existing
key , The engine failed to register service region, ApptBook with key,
is not available, process, multiple, MTS, MT, minimum, maximum, tasks<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel System Software - Version: 7.7.2 [18325] and later [Release: V7 and later ]<br />z*OBSOLETE: Microsoft Windows Server 2003<br />
Product Release: V7 (Professional)<br />
Version: 7.7.2 [18325] FRA<br />
Database: Microsoft SQL Server 2000 SP3<br />
Application Server OS: Microsoft Windows 2003 Server<br />
Database Server OS: Microsoft Windows 2003 Server<br />
<br />
This document was previously published as Siebel SR 38-1889334041.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
SBL-SVR-01069
Dear support,<br /><br />For your general understanding:<br />LoyEngineBatch is configured with following parameters:<br />LOY - Engine Queue Objects: Transaction:500,Tier:15<br />LOY - Engine Number of Runs: - 1<br />We have defined 50 server Keys and assigned them to 2 processes<br /><br />we need to find the way to submit component request, which would:<br />1. process transactions (in order to update member field attributes)<br />2.
process tiers (the search spec takes into account member field
attributes which are updated by the processing of transactions)<br /><br />Would it be possible that only one object type would get processed with the dos cmd below ?<br /><br />a) We have processed transactions and tiers with following dos cmd:<br /><br />start task for component LoyEngineBatch<br />start task for component LoyEngineBatch<br />sleep 60<br />start task for component LoyEngineBatch<br />start task for component LoyEngineBatch<br />start task for component LoyEngineBatch<br />start task for component LoyEngineBatch<br /><br />b)
We have queried in the database and realised that for members which
were assigned to process 2, transactions were processed but not the
tiers.<br /><br />c) we have shutdowned the component and resumed our test: tiers were all processed.<br /><br />How can we avoid this from happening ?<br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<h3 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1"></a><a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1">Message 1</a></h3>
For the benefit of the readers,<br /><br />Question: During the
implementation of the Loyalty environment, some questions were raised
about the starting of tasks from the command line. The reproduction of
this behavior and the troubleshooting of this lead to the following
information raised/clarified.<br /><br />Resolution:<br /> *You need to set
the MinMTServer=MaxMTServer=<Number of Loyalty Process on your
Siebel server>=2 for the sake of the example. This is independent on
the number of Server Key you will associate to each pair server/process.<br /> *In
order to start the Loyalty Batch Engine, you can either run a "Workflow
Process Manager" job for the process "LOY Engine - Start Engine" in
which you will set the number of processes and the number of thread per
process to the value required for your environment. Both are set to 1 by
default. This will start a number of Batch Engine tasks as per the
formula (1 + (1 + Thread/Process #)) * # of Processes which is a minimum
of 3 tasks per process. This makes 6 tasks in our example. <br />*You can alternatively start these tasks manually as per the customer description.<br />The
first task will make the MTServer determine to which process it will be
associated. In our example the second task will be associated to the
2nd key. The only way to confirm that is by reading the log in which the
SRMRouting event has been set to 4.<br /><br />Enhancement Change Request
12-VM0YFD: "Please add a way to read the process associated to a task
via the srvrmgr" has been opened to have an easier way of verification.<br />Enhancement
Change Request 12-VLY7CK: "Error SBL-SVR-01069 while choosing the
process to work for the LoyEngineBatch tasks" has been opened to remove
this message which is the expected behavior.<br />*Please note that a the
startup of your server, you will have one log file per MTServer has this
process require to start its listener on a TCP port.<br />*Please also
note that in the Server Administration task view, you will see the
entries from the S_SRM_REQUEST table which are requests for tasks and
not tasks.<br />*When you activate a Promotion, this will generate a
request for a task in order to update the Cache in the Batch Engine
MTServer.<br />*If you do this when the Engine Tasks are not fully
started, this will result in left over request that will need to be
cleaned up with the component SvrTblCleanup.
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-88235122920027095652013-04-05T17:03:00.002-07:002014-01-23T11:36:06.039-08:00SBL-SVR-01068<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km">
Applies to: </h2>
Siebel System Software - Version: 7.8.2.3 SIA [19221] and later [Release: V7 and later ]<br />Oracle Solaris on SPARC (64-bit)<br />
Product Release: V7 (Enterprise)<br />
Version: 7.8.2.3 [19221] Com/Med<br />
Database: Oracle 9.2.0.6<br />
Application Server OS: Sun Solaris 9<br />
Database Server OS: Sun Solaris 9<br />
<br />
This document was previously published as Siebel SR 38-3199007053.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
SBL-SVR-01068We are getting frequent SIGABRT error for "Workflow Proc Batch Mgr" comp and on checking its
corresponding logs of each of the exited tasks.It is giving the below error:<br /><br />PS:exited
tasks are the one which is leading to a crash and generating a
core.<br /><br />GenericLog GenericError 1 0 2006-11-14
07:56:55 (scirkey.cpp (121) err=2001068 sys=0) SBL-SVR-01068: This
component is not enabled for "Key Based Routing"<br /><br /><br />I've gone through the Supportweb and
found a solution mentioned bellow : I tried to implement the same,though it gave successful
change message,but it didn't reflect the change on listing the value.<br /><br />FYI:<br /><br />change
param KeyBasedEnabled = TRUE for comp WfProcBatchMgr<br /><br /> *This allowed
the component to run without this error but still the Tier changes were not
changed.<br /><br /><br />I've even tried to compare this with other test enviornment but could see it
as TRUE or False on some of the instances.Kindly help us in understanding this parameter
further.<br /><br /><br />Regards
<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
Configuration/ Setup
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<h3 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1"></a><a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1">Message 1</a></h3>
For the benefit of other users,<br />
<br />
The customer was running a Siebel 7.8.2.3 eCommunications environment
and had recently started seeing SIGABRT errors which appeared to result
from Workflow Process Batch Manager instances running on the enterprise.
In addition to the SIGABRT errors the crashing processes also reported
the following error :<br />
<br />
GenericLog GenericError 1 0 2006-11-14
07:56:55 (scirkey.cpp (121) err=2001068 sys=0) SBL-SVR-01068: This
component is not enabled for "Key Based Routing"<br />
<br />
The error message suggests that the component should be enabled for
'Key-Based Routing' but this specific form of request routing based on a
generated key for particular instances of a component is restricted in
its use. It was not expected that the WfProcBatchMgr component would
make use of this functionality and the error message appears to be
misleading. For further information on Key-Based Routing please refer to
'Siebel Field Service Guide > Scheduling and Dispatch >
Scheduling Administration > Setting Up Server Processes, Performance,
and Key-Based Routing' and Technical Note 641: How Assignment Manager,
Rule Group, and Server Key Mapping Interact.<br />
<br />
Following comparison of the component configuration between this and
other functioning environments it was established that a number of LOV
entries were missing in the problematic Test environment and which were
required by the Workflow Process being run. (continued...)<br /><br />
This appeared to result in the SIGABRT errors in the component and
misleading error messages being seen in the log files. Once the customer
migrated the missing LOV entries the processes functioned correctly.<br /><br />
Keywords : Key, Based, Routing, enabled, Key-Based, SBL-SVR-01068, WfProcBatchMgr, SIGABRT, LOV, List of Values, KeyBasedEnabled<br />
<br />
<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel Loyalty Engine - Version: 7.7.2.2 SIA [18356] and later [Release: V7 and later ]<br />IBM AIX on POWER Systems (64-bit)<br />
Product Release: V7 (Enterprise)<br />
Version: 7.7.2.2 [18356] Travel<br />
Database: IBM DB2 8.1 FixPack 5<br />
Application Server OS: IBM AIX 5L 5.2<br />
Database Server OS: IBM AIX 5L 5.2
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
SBL-LTY-00109, SBL-SVR-01068
Hi siebel support<br /><br />We have created a custom version of the
eLoyalty Processing Engine with Name = eLoyalty Tier Processing engine.
Purpose of this is to process tier changes nightly.<br />Creation of this
and how to make it run was discussed in other service request but we
managed to make it run in our Test envinronment. Now that we have
created the exact same component in UAT, it errors when trying to start
it.<br />The errormessage in the logfile is:<br />"SBL-LTY-00109: The
process was unable to find an available server routing key to register.
Please check the loyalty server key definition of your system."<br />And:<br />"SBL-SVR-01068: This component is not enabled for "Key Based Routing""<br /><br />These messages comes right after this SQL:<br />SELECT<br /> T1.CONFLICT_ID,<br /> T1.LAST_UPD,<br /> T1.CREATED,<br /> T1.LAST_UPD_BY,<br /> T1.CREATED_BY,<br /> T1.MODIFICATION_NUM,<br /> T1.ROW_ID,<br /> T1.PROCESS_NUM,<br /> T1.SERVER_NAME<br /> FROM <br /> siebel.S_LOY_SRV_MAP T1<br /> WHERE <br /> (T1.SERVER_NAME = ?)<br /> ORDER BY<br /> T1.PROCESS_NUM<br />ObjMgrSqlLog Detail 4 0 2005-09-20 19:29:26 Bind variable 1: uat_loy<br /><br />Which returns my Server Key map i run directly against the database.<br /><br />Please see attached logfile.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
The cause was the copied component did not copy all component parameters correctly <br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
Symptoms: After creating a new Loyalty Batch Engine Component, it does not start and gives the error message :<br /> "SBL-LTY-00109:
The process was unable to find an available server routing key to
register. Please check the loyalty server key definition of your
system."<br /> "SBL-SVR-01068: This component is not enabled for "Key Based Routing""<br /><br />Troubleshooting:<br /> *The List of Values LOY_ENGINE_COMPONENT_KEYED for the component LoyTierEngineBatch is present in the system.<br /> *Indirect SupportWeb search lead to find that the SBL-SVR-01068 was caused by the advanced parameter KeyBasedEnabled. <br /><br /><br />Resolution:<br /> By using the srvrmgr command line utility :<br /> list advanced param KeyBasedEnabled for comp LoyEngineBatch<br /> ->True<br /> list advanced param KeyBasedEnabled for comp LoyTierEngineBatch<br /> -> False<br /> change param KeyBasedEnabled = TRUE for comp LoyTierEngineBatch<br /> *This allowed the component to run without this error but still the Tier changes were not changed.<br /> *Copying of component is very sensitive as there are many parameters to review.<br /> *By using again the srvrmgr command line utility:<br /> spool <myspool1.out><br /> list param for comp LoyEngineBatch<br /> spool off<br /> spool <myspool2.out><br /> list param for comp LoyTierEngineBatch<br /> spool off<br /> *By comparing the 2 spool files, it was found out that the Maximum Tasks had been left to 1 instead of 20.<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel Loyalty Engine - Version: 7.8.2.3 SIA [19221] and later [Release: V7 and later ]<br />z*OBSOLETE: Microsoft Windows Server 2003<br />
Product Release: V7 (Enterprise)<br />
Version: 7.8.2.3 [19221] SVE Transp<br />
Database: Microsoft SQL Server 2000 SP3<br />
Application Server OS: Microsoft Windows 2003 Server<br />
Database Server OS: Microsoft Windows 2003 Server<br />
<br />
This document was previously published as Siebel SR 38-3073606491.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
SBL-SVR-01068, SBL-BPR-00162Customer had an issue with the component ‘eLoyalty Processing Engine -
Realtime’. <br /><br />On the server, we try to process a transaction with the Realtime component
using the 'Process' button in the GUI. We get the following error:<br />[1] Error invoking service
'LOY Processing Engine', method 'SubmitObjectForProcessing' at step 'Invoke Submit
Object'.(SBL-BPR-00162)<br />[2] Could not route message to LoyEngineRealtime with registered key
(null)<br />[3] no other server<br />
Processing the transaction on the dedicated
client, the transaction is processed successfully.<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
The Loyalty component was not assigned and synchronised on the server
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
Unassigning and re-assigning the Loyalty Batch Engine component, then
synchronising the componets resolved the issue for this customer</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-11904406124884132422013-04-05T17:00:00.005-07:002014-01-23T11:36:06.016-08:00SBL-SVR-01054<div dir="ltr" style="text-align: left;" trbidi="on">
<span id="pt1:sd_r1:0:dv_rDoc:ot71" style="color: black; font-size: x-small;"></span><br />
<h2 class="km">
Applies to: </h2>
Siebel Enterprise Integration Manager - Version 8.0.0.2 [20412] and later<br />Information in this document applies to any platform.<br />
***Checked for relevance on 04-Dec-2012***
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
<br />The EIM DELETE task does not complete successfully when deleting
rows from S_CON_ADDR using EIM_ADDR_PER. The following errors are seen
in the Server Manager Command line window when the EIM task is executed
from the same:<br /><br />SBL-ADM-60070: Error reported one server “SIEBEIM8” follows:<br />SBL-SVR-01054: The task exited without sending has response. <br />In attachment, a file log, a print screen and an ifb.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
<br />The following entry in the EIM-Log file is relevant:<br /><br />"...<br />* [Del MyDelete] batch 100, step 2, pass 107: locate by user key<br />* (started at 6/9/08 3:03)<br />*/<br /><br />UPDATE dbo.EIM_ADDR_PER<br />SET T_CON_ADDR__RID = <br />(SELECT MIN(BT.ROW_ID)<br />FROM dbo.S_CON_ADDR BT<br />WHERE (BT.RELATION_TYPE_CD = IT.CONADDR_RELATIONTY AND<br />(BT.START_DT = IT.CONADDR_START_DT OR<br />(BT.START_DT IS NULL AND IT.CONADDR_START_DT IS NULL)) AND<br />BT.ADDR_PER_ID = IT.T_CON_ADDR_ADDRPE AND<br />(BT.ACCNT_ID = IT.T_CON_ADDR_ACCNTI OR<br />(BT.ACCNT_ID IS NULL AND IT.T_CON_ADDR_ACCNTI IS NULL)) AND<br />(BT.CONTACT_ID = IT.T_CON_ADDR_CONTAC OR<br />(BT.CONTACT_ID IS NULL AND IT.T_CON_ADDR_CONTAC IS NULL)) AND<br />(BT.ORG_GROUP_ID = IT.T_CON_ADDR_ORGGRO OR<br />(BT.ORG_GROUP_ID IS NULL AND IT.T_CON_ADDR_ORGGRO IS NULL))))<br />FROM dbo.EIM_ADDR_PER IT<br />WHERE (CONADDR_RELATIONTY IS NOT NULL AND<br />T_CON_ADDR_ADDRPE IS NOT NULL AND<br />IF_ROW_BATCH_NUM = ? AND<br />IF_ROW_STAT_NUM = 0 AND<br />T_CON_ADDR__STA = 0)<br />?1: 100<br />go<br />..."<br /><br />The problem is that the UPDATE statement from above is also checking for<br />S_CON_ADDR.ACCNT_ID/EIM_ADDR_PER.T_CON_ADDR_ACCNTI<br />and<br />S_CON_ADDR.START_DT/EIM_ADDR_PER.CONADDR_START_DT<br />respectively.<br /><br />If
those columns are not considered for the EIM_ADDR_PER load then the
DELETE EXACT operation is failing as seen in the EIM-Log file:<br /><br />"...Process [Del MyDelete] had 1 row fail<br />on EIM_ADDR_PER for batch 100 in step 2, pass 107:<br />Exact specification of rows were not found. (severity 4, row eliminated)<br /><br />Rows which were specfied using exact deletion were not found by the user keys<br />specified in the interface table. Check that the key values specified in the IF<br />table exactly match a row in only one base table.<br /><br />The rows were eliminated from further processing in this IF table. Processing<br />will continue for other rows in this interface table..."<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<br />Considering the S_CON_ADDR.ACCNT_ID and S_CON_ADDR.START_DT
columns via their respective EIM_ADDR_PER columns resolves the
behaviour. A sample script and IFB-File is shown below:<br /><br />INSERT INTO EIM_ADDR_PER<br />(ROW_ID,<br />IF_ROW_BATCH_NUM,<br />IF_ROW_STAT,<br /><br />AP_ADDR_NAME, -- S_ADDR_PER<br />AP_ALIGNMENT_FLG,<br />AP_DISACLEANSE_FLG,<br />AP_NAME_LOCK_FLG,<br />AP_PREMISE_FLG,<br /><br />CONADDR_RELATIONTY, --S_CON_ADDR<br />CONADDR_START_DT,<br />CONADDR_ACTIVE_FLG,<br />CONADDR_BLADDR_FLG,<br />CONADDR_FRAUD_FLG,<br />CONADDR_MAINADDRFL,<br />CONADDR_SHIPADDRFL,<br /><br />CONADDR_ACCNT_BU, -- S_CON_ADDR.ACCNT_ID<br />CONADDR_ACCNT_LOC,<br />CONADDR_ACCNT_NAME<br />)<br />VALUES<br />(1,<br />100,<br />'FOR_DELETE',<br /><br />'MyAccntStreetAddress1, MyAccntCity1', -- S_ADDR_PER<br />'N',<br />'N',<br />'N',<br />'N',<br /><br />'ContactPointUsage',<br />'2008-06-09',<br />'Y','N','N','N','N',<br /><br />'Default Organization',<br />NULL,<br />'MyAccnt1'<br />)<br /><br />-------<br /><br />[Siebel Interface Manager]<br />USER NAME="SADMIN"<br />PASSWORD="SADMIN" <br />PROCESS = Del MyDelete<br /><br />[Del MyDelete]<br />TYPE = DELETE<br />BATCH = 100<br />TABLE = EIM_ADDR_PER<br />DELETE EXACT = TRUE<br />ONLY BASE TABLES = S_CON_ADDR<br />
<br />
<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel Enterprise Integration Manager - Version: 8.0.0.1 SIA [20408] and later [Release: V8 and later ]<br />Information in this document applies to any platform.<br />
Product Release: V8 (Enterprise)<br />
Version: 8.0.0.1 [20408] Life Sci<br />
Database: Microsoft SQL Server 2005<br />
Application Server OS: Microsoft Windows 2003 Server SP2<br />
Database Server OS: Microsoft Windows 2003 Server SP2<br />
<br />
This document was previously published as Siebel SR 38-3460398791.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
I'm getting the following error when trying to run EIM. This .ifb used to work.<br />
<br />
SBL-ADM-60070: Error reported on server 'SblCRMDev01' follows: <br />
SBL-SVR-01054: The task exited without sending a response. <br />
<br />
The only difference that I know of is that we have extended EIM_CONTACT
several times. We didn't have a problem for the other ones, though.<br />
<br />
I've attached the ifb file I'm using, the log file produced when logging was turned up and the crash file.<br />
<br />
Let me know if you have any questions. Thanks.<br />
<br />
Ken Ratzlaff<br />
425-478-1951<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
Configuration/ Setup
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<h3 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1"></a><a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1">Message 1</a></h3>
For the benefit of othere readers,<br />
<br />
Customer experienced issues with columns created with the 'Case Insensitivity' wizard.<br />
<br />
It has been determined that Customer ran the 'EIM Mapping Wizard'
sometime after running the 'Case Insensitivity' wizard. For this reason
the EIM mapper created eim columns and mappings for the case insensitive
columns.<br />
<br />
In order to avoid the above issue you should always make sure that the EIM Mapping wizard does not take such columns in account.<br />
<br />
Additional Keywords: Case Insensitivity, EIM Mapping<br />
<br />
<br />
<br />
<br />
<span id="pt1:sd_r1:0:dv_rDoc:ot71" style="color: black; font-size: x-small;"></span><br />
<h2 class="km">
Applies to: </h2>
Siebel CRM - Version 8.0.0.13 SIA [20448] and later<br />Information in this document applies to any platform.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
On : 8.0.0.13 SIA [20448] version, ADM - App. Deployment Manager<br /><br />When
attempting to export data using ADM command line using ADMbatchProc
component, the component crashes and the following error occurs:<br /><br />ERROR<br />-----------------------<br />SBL-ADM-60070: Error reported on server 'WFMDEVAPP1' follows:<br />SBL-SVR-01054: The task exited without sending a response.<br />SBL-SCL-00131: Either the RC2 or the AES cryptography engine is not initialized.<br /><br /><br />STEPS<br />-----------------------<br />The issue can be reproduced at will with the following steps:<br />1. login using srvrmgr<br />2. Execute following command to export LOV records using ADM.<br /><br />run
task for comp admbatchproc with admpath="C:\ADM\output_xml",
admfilter='[Value] LIKE "SR_AREA*"', admdatatype=LOV,
admeaimethod=upsert, admprefix=ADM_SR_AREA<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
Cause of the issue is identified as product defect.<br /><br />Issue is replicated in-house and a product defect <a href="https://support.oracle.com/epmos/faces/ui/km/BugDisplay.jspx?id=14460219">14460219</a> - ADM BATCH PROC EXPORT FAILS WITH SBL-SCL-00131 ERROR is raised to address the issue.<br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
Defect#<a href="https://support.oracle.com/epmos/faces/ui/km/BugDisplay.jspx?id=14460219">14460219 </a>is fixed by engineering and a QF is now available in My Oracle Support.Please find the details of the fix below:<br /><br />Because 800x code line is in extended support, this QF is protected with a password.<br /><br />Summary:<br /><br />Patch ID: 14686221<br /><br />Platform Available: SOLARIS, WINDOWS<br />Product Certified: SIA<br />Languages Certified: Language Independent<br />Base Required: FIX PACK 8.0.0.13[20448]<br /><br />Patch Abstract:<br />8.0.0.13 20448 sba QF0D25 sebl_aru<br /><br />QF Install Doc:<br /><br />Doc is named README.html and is located under<br /><br />p14686221_800_SOLARIS64_1of2.zip<br /><br />p14686221_800_WINNT_1of2.zip<br /><br />
<br /><br />
<span id="pt1:sd_r1:0:dv_rDoc:ot71" style="color: black; font-size: x-small;"></span><br />
<br />
</div>
Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-5176827930400549727.post-66183431699031070472013-04-05T16:59:00.005-07:002014-01-23T11:36:06.027-08:00SBL-SVR-01051<div dir="ltr" style="text-align: left;" trbidi="on">
<h2 class="km">
Applies to: </h2>
Siebel Handheld - Version 7.5.3.9 PDA [16194_2] to 8.2.2.3 SIA [23021] [Release V7 to V8]<br />Microsoft Windows CE<br />
Product Release: V7 (Enterprise)<br />
Version: 7.7.0.1 [AN307]<br />
Database: Oracle 9i<br />
Application Server OS: Microsoft Windows 2003 Server<br />
Database Server OS: Sun Solaris 9<br />
<br />
This document was previously published as Siebel SR 38-1719219591.<br />
***Checked for relevance on 27-Mar-2013***<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
SBL-SVR-01051, SBL-NET-01218<br />
We are experiencing problems syncronising our Siebel Handheld devices
with the Server using DSS. It has worked in the past, but since the
server went down during a sync, we can't get it to work again.<br /><br />We continue to get these error, taken from the log on the HH device.<br /><br />SYSTEM 0xd290894e 01/17/2005 10:00:40 Loading Metadata.<br />ERROR 0xd290894e 01/17/2005
10:00:40 0x7766: Failed to load configuration. Metadata file is
absent or invalid. Siebel Handheld Sync will be launched now.<br />SYSTEM 0xB3605DE2 01/17/2005 10:00:41 Initializing SyncClient.<br />SYSTEM 0xd290894e 01/17/2005 10:00:41 Terminating Siebel application.<br />ERROR 0xD2BB26E6 01/17/2005 10:01:13 0x65aa: Server returned NOTOK<br />ERROR 0xD2BB26E6 01/17/2005 10:01:13 Server returned NOTOK<br />ERROR 0xD2BB26E6 01/17/2005
10:01:13 The server may be busy. Please try again later. Contact
your administrator if the problem persists.<br />ERROR 0xD2BB26E6 01/17/2005 10:01:13 Fatal Error, Shutting Down Session<br />SYSTEM 0xB3605DE2 01/17/2005 10:01:26 Exiting SyncClient.<br /><br />Any
ideas what may be causing this. We thought that it may still have an
active sync task running, but we have started and stopped the server and
it still conitnues to error out.<br /><br />Many Thanks<br /><br />Andy <br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
As cause was identified the entry for the handheld application in
eapps_sia.cfg file. All sections for handheld applications require the
additional line 'EnableExtServiceOnly = TRUE'. The standard eapps*.cfg
files do contain this line.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref_section31"></a><h3 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1"></a>Message 1</h3>
For the benefit of other users:<br /><br />The object manager log file showed following errors a couple of times:<br />SBL-NET-01218: The connection was refused by server gal-rtw-app-16. No component is listening on port 49160.<br />SBL-SVR-01051: SISNAPI connection is refused by the Siebel server: (null)<br /><br />As
cause was identified the entry for the handheld application in
eapps_sia.cfg file. All sections for handheld applications require the
additional line 'EnableExtServiceOnly = TRUE'. The standard eapps*.cfg
files do contain this line. In the case here for some reason this line
was missing. After correcting this the handheld synchronization worked properly.<br />
<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel System Software - Version: 7.5.3 [16157] and later [Release: V7 and later ]<br />Information in this document applies to any platform.<br />
Error Message Area:Server Common Layers - SVR<br />
Version:Siebel 7.5.3
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="REF_PURPOSE"></a>Purpose</h2>
This document is intended to provide cause and corrective action
information about Siebel Error Message SBL-SVR-01051: SISNAPI connection
refused, the server could be down: %1<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="REF_SCOPE"></a>Scope</h2>
This document is informational and intended for any user.<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="REF_TEXT"></a>SBL-SVR-01051: SISNAPI connection refused, the server could be down: %1</h2>
<h3 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1"></a><a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1">Explanation</a></h3>
Cannot connect to the Siebel Server machine to start a process. The
Siebel Server machine might not be available over the network or the
Siebel Server process may not be started. The details of the error from
the SISNAPI layer replaces the %1 in the error message.<br />
<h3 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref2"></a><a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref2">Corrective Action</a></h3>
Make sure the Siebel Server machine is up and running and that the Siebel Server process is running.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<span id="pt1:sd_r1:0:dv_rDoc:ot71" style="color: black; font-size: x-small;"></span><br />
<h2 class="km">
Applies to: </h2>
Product Release: V7 (Enterprise)<br />
Version: 7.7.1 [18306]<br />
Database: Oracle 9.2.0.4<br />
Application Server OS: Microsoft Windows 2000 Server<br />
Database Server OS: Sun Solaris 8<br />
<br />
This document was previously published as Siebel SR 38-1557600801.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
SBL-SVR-01051, SBL-SMI-00049, SBL-NET-01218Hi Support,<br /><br />We have created new Object Managers for PRM Portal (for 8 different
languages). As part of this, we have created new virtual directories, new components, new entries
in the eapps.cfg. And finally, we synchronized the components.<br /><br />But, when we try to access
the new OM, it says 'Page can not be displayed'.<br /><br />For example, we created new OM:
echannelObjMgr_enu_eidm and when we access it through:<br /><br />http://hostname/prmportal_enu_eidm
we get a 'Page can not be displayed' message.<br /><br />We see that the URL gets re-directed to
homepage like:
<br /><br />http://hostname/prmportal_enu_eidm/start.swe?SWECmd=Start&SWEHo=hostname<br /><br />I
think the OM is not responding to the request that has passed through SWSE. <br /><br />Please let us
know your ideas on this.<br /><br />Thanks,<br />Jagadeesh
<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<h3 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="aref1">Message 1</a></h3>
For the benefit of other user:<br />
<br />
The customer has created new Object Managers for PRM Portal (for 8
different languages). As part of this, he has created new virtual
directories, new components, and new entries in the eapps.cfg. And
finally, he synchronized the batch server components.<br />
<br />
But, when he tried to access the new Object Manager, it says "Page can not be displayed".<br />
<br />
The problem has been resolved after the customer modified the web server (IIS) parameters as follows:<br />
1. Open IIS (Start menu --> Program Files--> Administrative Tools--> Internet Services Manager)<br />
2. Expand default web site<br />
3. Choose Virtual directory created (for the custom component) and right click and go to Properties<br />
4. In Virtual directory tab, choose Configuration button. Click that<br />
5. You get another pop up- choose tab - App mappings. Highlight .swe and click on edit<br />
6. Another pop up opens - At the bottom, there is a check box - "Check that file exists"<br />
7. Uncheck the check box <br />
8. Repeat this for .swef <br />
<br />
Documentation Enhancement request 12-QAWCBM (Update the "Creating a New
Virtual Directory" section from Siebel Installation Guide for MS
Windows) was logged to address this matter.<br />
<br />
<br />
<br />
<h2 class="km">
Applies to: </h2>
Siebel CRM - Version: 7.5.3 [100] to 8.1.1.7 [21238] - Release: V7 to V8<br />Information in this document applies to any platform.<br />
Product Release: V7 (Professional)<br />
<br />
Application Server OS: Microsoft Windows 2000 Server SP 4<br />
Database Server OS: Microsoft Windows 2000 Server SP 4<br />
<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
It was reported that there were problems using drag drop
functionality in the Siebel application. When the user was trying
to save an attached document, the system was displaying the following
error message:<br />
<div class="kmcodeblock" style="width: 95%;">
<code class="km">Session
Warning: The server you are trying to access is either busy or
experiencing difficulties. Please close the Web browser, open a new
browser window, and try logging in again.</code></div>
After this error, the user is usually logged out of the application.<br /><br />The issue was only present in the thin client and could not be reproduced in the dedicated client.<br />
The same error was observed in the thin client using both DB authentication and ADSI authentication.<br /><br />The following messages were displayed in the SWE logs:<br />
<div class="kmcodeblock" style="width: 95%;">
<code class="km">ProcessPluginRequest ProcessPluginRequestError 1 0 2006-04-18
17:15:22 5116: [SWSE] RPC coming in without a user session<br /><br />ProcessPluginRequest ProcessPluginRequestError 1 0 2006-04-18
17:15:22 5116: [SWSE] Failed to obtain a session ID. NOT OK<br /><br />ProcessPluginRequest ProcessPluginRequestError 1 0 2006-04-18
17:15:22 5116: [SWSE] Set Error Response (Session: Error: 00065535
Message: NOT OK)</code></div>
<br /><br />The following error messages may also be seen for the end user or in the logs related to this issue:<br /><em>SBL-UIF-00401,
SBL-SCR-00141, SBL-DAT-00215, SBL-DAT-00712, SBL-SVR-01051,
SBL-SCM-00022, SBL-SMI-00033, SBL-NET-01023, SBL-BPR-00125,
SBL-BPR-00151 </em><br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
The cause of this issue was determined to be an underscore "_" character in the naming of the servers.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
The workaround for this issue is to use the IP address of the server instead of the server name.<br /><br /><a href="https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=477993.1">Document 477993.1</a> has additional information regarding problems using a dash/hyphen in the Siebel Server Name. <br />
<a href="https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=477993.1">Document 477993.1</a> was previously referred to as Alert 1067.<br />
<br />
<br />
<br />
<span id="pt1:sd_r1:0:dv_rDoc:ot71" style="color: black; font-size: x-small;"></span><br />
<h2 class="km">
Applies to: </h2>
Siebel Financial Services Call Center - Version: 7.7.2.10 SIA [18385] and later [Release: V7 and later ]<br />Information in this document applies to any platform.<br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="SYMPTOM"></a>Symptoms</h2>
<br />Web client not working after migration with CUSTOM srf. It works fine with STANDARD srf.<br />
<br />
OM logs were misleading indicating following errors:<br />
2010-02-01 13:58:57 4848: [TCPIP-client] connect() to drlmrsie07p:49164 failed (err=10061 | Connection refused.) <br /><br />2010-02-01
13:58:57 (srmconn.cpp (905) err=1801218 sys=49164) SBL-NET-01218: The
connection was refused by server drlmrsie07p. No component is listening
on port 49164. <br /><br /><br />2010-02-01 13:58:57 (srmconn.cpp (905)
err=2001051 sys=126) SBL-SVR-01051: SISNAPI connection is refused by the
Siebel server: (null) <br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CHANGE"></a>Changes</h2>
Customer was in the process of building a Siebel disaster recovery (DR)
environment, which mimics their production environment. They built the
environment from a fresh installation of Siebel. The vanilla Siebel web
client worked perfect, however, after doing a database refresh from
production, as well as repository migration (including repository
import, copying over SRF, bscript, image and CSS files from production),
the web client stopped working.
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="CAUSE"></a>Cause</h2>
<br />Custom srf was failing because Firstlogic was not installed<br /><br />
<h2 class="km">
<a href="http://www.blogger.com/blogger.g?blogID=5176827930400549727" name="FIX"></a>Solution</h2>
<br />Installed Firstlogic and web client started working with custom srf.
<br /><br />
<span id="pt1:sd_r1:0:dv_rDoc:ot71" style="color: black; font-size: x-small;"> </span>
</div>
Unknownnoreply@blogger.com0