SBL-BPR-00530: An internal error has occured while handling the following exception. The current task has been canceled as a result.

Applies to:

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




Symptoms

It was found that the presence of an Output Argument with Type = Business Component on a Task View after a Siebel Operation Insert step with DeferWrite = True caused the record to be saved early and SBL-BPR-00530 error occured.

The full error message is:



[1]. An internal error has occurred while handling the following exception. The current task has been canceled as a result. (SBL-BPR-00530)




This issue only happens in a task which has a Siebel Operation Insert step with DeferWrite = True, and a corresponding Task View with an Output Argument of Type = Business Component.



Cause

This issue was reproduced in minimally configured standard application and reported as a product defect.

This issue was found to happen on version 8.0.0.7 through version 8.0.0.10.

This issue was found to be a product regression as the same task configuration worked in 8.0.0.6 fix pack without any errors.

The product defect Change Request (CR) for this is:
CR: 10591413 (BUG 10591413)
CR Summary: Task View Output Argument Type BC causes early record save and SBL-BPR-00530


Solution

There is a workaround for this issue. It is usually possible to modify the task configuration by removing the task view's output argument which triggers the defective behavior. It is usually possible to pass this information to a task property in a later step.

There are also Quick Fixes (QF's) available for this issue.

8.0.0.9 Quickfix   QF0955,  8.0.0.9 [20433]QF0955 Bug ID: SBA: 10045559
8.0.0.10 Quickfix QF0A10, 8.0.0.10 [20436] QF0A10 BugID: SBA: 10311424

As of the publishing of this document, this issue is planned to be fixed in the 8.0.0.11 Fix Pack.





If you face this issue on a different version and the workaround is not acceptable, please contact Oracle technical support if you need assistance in determining if there is a fix available for your version or to determine if the fix is available in a higher fix pack.

If you face this issue on a lower fix pack for this version, please consider moving to higher fix pack to utilize one of the QF's which are listed above and are readily available. Please note that any QF which lists one of the QF's above as an obsolete QF should also contain the fix for this issue.


References

BUG:10591413 - TASK VIEW OUTPUT ARGUMENT TYPE BC CAUSES EARLY RECORD SAVE AND SBL-BPR-00530


PATCH:10045559 - 8.0.0.9 20433 SBA QF0955 SEBL_ARU


PATCH:10311424 - 8.0.0.10 20436 SBA QF0A10 SEBL_ARU



















Applies to:

Error Message Area:Business Processes/Workflow - BPR


Version:Siebel 8.0


Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-BPR-00530: An internal error has occured while handling the following exception. The current task has been canceled as a result.


Scope

This document is informational and intended for any user.


SBL-BPR-00530: An internal error has occured while handling the following exception. The current task has been canceled as a result.

Explanation

Task controller encountered some internal error while executing the task and had to cancel the task.


Corrective Action

Please try starting a new task.






















Applies to:

Siebel eCommunications - Version: 8.0.0.3 [20416] - Release: V8

Information in this document applies to any platform.




Goal

In TBUI when the task flow reaches an error step the following error is displayed:

[1] An internal error has occured while handling the following exception. The current task has been canceled as a result.(SBL-BPR-00530)
[2] <custom error message>(SBL-BPR-00131)



Can the first error be translated or changed?

Solution


The first error message (SBL-BPR-00530) displayed in a error step is hard coded and can not be changed. The error message passed to the custom error appears in the second error displayed (SBL-BPR-00131).



CR#10560755 has been opened to enhance the product so that the first error message displayed can be changed.


תגובות

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

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

Profile Attributes and Open UI

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

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - Version: 7.5.3 [16157] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3 [16157] Database: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא