Wednesday, January 19, 2011

SBL-BPR-00537: Task controller encountered another error

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-00537: Task controller encountered another error while trying to handle the following error. Please use the Pause button to pause the task, or the Cancel button to cancel the task.


Scope

This document is informational and intended for any user.


SBL-BPR-00537: Task controller encountered another error while trying to handle the following error. Please use the Pause button to pause the task, or the Cancel button to cancel the task.

Explanation

Task controller encountered another error while trying to handle an error in task execution. The current task needs to be paused or canceled.


Corrective Action

Please use the Pause button to pause the task, or the Cancel button to cancel the task.






















Applies to:

Siebel Tools - Version: 8.1.1 SIA [21111] - Release: V8
Information in this document applies to any platform.




Symptoms


Tested this Issue in 8.1.1 SIA with Sample DB





Steps to reproduce the issue





1. Created a Task Base UI with one Step which has Contact Form Applet


2. In this Applet there are two MVG's. One MVG is based on Account BC and another MVG is based on CUT Address.


3. Started the Task Base UI and Opened the Account MVG. Added the Record and removed the same record.


4. Closed the MVG and Click the Submit Button.


5. Following Error is encountered








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


Siebel


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


[1] Task controller encountered another error while trying to handle the following error. Please use the Pause button to pause the task, or the Cancel button to cancel the task.(SBL-BPR-00537)


[2] An error has occurred committing the record 1-1YH of business component 'Account'. The user key of the record is


Party Name = ""


Location = "Outlet"


Primary Organization Id = "1-1DG"


S_ORG_EXT_SS.Conflict Id = ""


(SBL-DAT-60241)


[3] An internal error occurred retrieving a field value for ''. The field has an invalid logical index.(SBL-DAT-00430)





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


OK


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







Solution

For the benefit of the others readers:

CR#10576600 and the FR#12-1V0NEIB was created as a product defect for this issue.

Following QF need to apply to rectify the issue 8.1.1 [21112] QF0060 BugID: SBA: 9037942

Thank you,
Siebel Technical Support


References

BUG:10576600 - MVG IN TASK UI IS GIVINING FOLLOWING ERRORS SBL-DAT-60241 AND SBL-DAT-00430



SBL-BPR-00539: The workflow task step %1 specified in the long running workflow %2 does not have a recipient specified.

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-00539: The workflow task step %1 specified in the long running workflow %2 does not have a recipient specified.


Scope

This document is informational and intended for any user.


SBL-BPR-00539: The workflow task step %1 specified in the long running workflow %2 does not have a recipient specified.

Explanation

Recipient is required for a workflow task step.


Corrective Action

Please specify a valid recipient for the workflow task step.






SBL-BPR-00536: An error has occurred while restoring task instance '%1'.

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-00536: An error has occurred while restoring task instance '%1'.


Scope

This document is informational and intended for any user.


SBL-BPR-00536: An error has occurred while restoring task instance '%1'.

Explanation

Task controller failed to restore the task due to some error.


Corrective Action

Please refer to lower level error messages for more detailed explanation and correction actions.
























Applies to:

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




Symptoms

SBL-BPR-00536 and SBL-BPR-00524 errors occur when task is resumed from the inbox after being paused.

The specific error message is:



Error:
[1] An error has occurred while restoring task instance '<task name>'. (SBL-BPR-00536)
[2] Cannot find step '<task step>' in the task definition (SBL-BPR-00524)


This issue only happens when the task has two or more subtasks and the task has been paused in the main task flow after going through the steps in the second subtask or subsequent/later subtasks.



This is a regression issue which was shown to be happening in version 8.0.0.10 and 8.0.0.9, and the same task had no issue in version 8.0.0.7.


Cause

This issue has been reproduced in minimally configured standard application on version 8.0.0.10 and 8.0.0.9 and has been reported as a product defect via Change Request (CR) 12-20227ZN BUG 10601938.

The issue was shown to not be present in 8.0.0.7.



Solution

A Quick Fix for 8.0.0.9 is available for this issue.
8.0.0.9 20433 SBA QF0980 SEBL_ARU
You can find this QF by searching for patch number/name = 10305746

As of the publishing of this document, this issue is planned to be fixed in version 8.0.0.11 fix pack.

If you face this issue on a different version, please contact Oracle technical support if you need assistance determining if there is a fix available for your version, or determining if the fix is available in any 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 the QF listed above which is readily available. Please not that any QF which lists the QF above as an obsolete QF should also contain the fix for this issue.


CR: 10601938 BUG 10601938


CR summary: SBL-BPR-00536 SBL-BPR-00524 on PAUSE/RESUME when Task has 2 or more subtasks









References

BUG:10601938 - SBL-BPR-00536 SBL-BPR-00524 ON PAUSE/RESUME WHEN TASK HAS 2 OR MORE SUBTASKS


PATCH:10305746 - 8.0.0.9 20433 SBA QF0980 SEBL_ARU





















Applies to:

Siebel Communications, SPE - Version: 8.0 [20405] - Release: V8

Information in this document applies to any platform.




Symptoms

Basically what we do is we try to pause and resume the task many times. and the error "An error has occurred while restoring task instance '1-5FLU5'.(SBL-BPR-00536)" was produced.
Step to reproduce:




1. Initiate the tas
2. Click next
3. Click pause
4. Go to Inbox view
5. Resume the task
6. Click Pause
7. Click next or previous
8. Try to repeat step 5 to 7 to produce this error:
An error has occurred while restoring task instance '1-5FLU5'.(SBL-BPR-00536)

Cause


This is product defect in siebel 8.0 version.Bug CR#10551424 was opened to address this problem and Reproduced problem in standard Siebel 8.0. version

Solution


In order to workaround the problem in your system we recommend to disable the pause button for all task views in the affected tasks except one. This will avoid the scenario that leads to the error messages. You can do this by setting the task step attribute "Disable Pause".

Created FR 12-1QYIXBD for 8.0.0.2 QF ENU under the CR#10551424.

FR has been fixed, 8.0.0.2 [20412] QF0283 BugID: SBA: 7611911

References

BUG:10551424 - ERROR WHEN PAUSING A TASK





SBL-BPR-00535: An error has occurred while initializing task '%1'.

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-00535: An error has occurred while initializing task '%1'.


Scope

This document is informational and intended for any user.


SBL-BPR-00535: An error has occurred while initializing task '%1'.

Explanation

Task controller failed to initialize the task due to some error.


Corrective Action

Please refer to lower level error messages for more detailed explanation and correction actions.






SBL-BPR-00534: Cannot restore task instance '%1' since it is not in Paused status.

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-00534: Cannot restore task instance '%1' since it is not in Paused status.


Scope

This document is informational and intended for any user.


SBL-BPR-00534: Cannot restore task instance '%1' since it is not in Paused status.

Explanation

Only task instances in Paused status can be restored.


Corrective Action

If the task instance to be restored has been corrupted, please delete it and start a new task.






SBL-BPR-00533: An error has occurred building a task view.

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-00533: An error has occurred building a task view.


Scope

This document is informational and intended for any user.


SBL-BPR-00533: An error has occurred building a task view.

Explanation

A task view cannot be built, possibly because the view definition is not valid.


Corrective Action

Please use the Previous button to go back, correct the error and continue, or use the Pause/Cancel button to pause/cancel the task.





Wouldnt you need to go back to the design time environment to fix.. Gives me the impression I can fix from the client.






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.