Siebel Error Code 简介

来源:http://blog.sina.com.cn/qinlianhao

开发时会经常配到的Siebel Error Code，这里简单说明一下它的含义，至于每个Error Code都应该怎么调试，从网上收集了一下，但是个人觉得收集的调试不给力，还是需要再精炼一下，我以后慢慢再补。

另外推荐一个关于Siebel Error Code的网站，这里比较详细，调试方法给的也很详细：

http://www.error-codes.info

 

Error Code的格式：

SBL-<Component>-<Error Code>

比如: SBL-BPR-00162

 

比较常见的有"DAT","BPR"，"SC","UIF"，"EAI"，这里DAT代表Data, BPR代表Business Process, SCH代表Scheduler, UIF代表User Interface，EAI代表EAI。

 

常见错误：

 

SBL-DAT-00393

An end of file error has occurred. Please continue or ask your systems administrator to
check your application configuration if the problem persists.(SBL-DAT-00393)

Steps for Troubleshooting:

1. Check the script where it failed and check for the rowid.
2. Now go to the place in script where the web_reg_save_param () is placed and select
the succeeding request in the script.
3. Go to tree view and check the ordinal No of the particular Row-id in the Recorded
Server Response you have correlated.
4. If the Ordinal Number (no of occurrence) changes, then you need to change in the
corresponding correlation statement.
5. Re-run the script to ensure that the error is resolved.

 

SBL-DAT-00225

The value entered in field <Field Name> of buscomp <BusinessComponent> does not
match any value in the bounded pick list PickList <Pick list name>.(SBL-DAT-00225)

Steps for Troubleshooting:

1. Select the request where the error happens.
2. Check for the values which you have given input (most probably thru
parameterization or correlation).
3. The values given as input could be narrowed down if we check in item data with
name as “s_1_2_2_0”.
4. Change the values in parameter file in accordance with the pick list.

 

SBL-DAT-00523

The selected record has been modified by another user since it was retrieved. Please
continue. (SBL-DAT-00523)

Steps for troubleshooting:

1. Select the request and check for the parameter that is getting passed.
2. Open the Siebel Application and navigate thru the workflow to check if the value has
been already used for the particular scenario. If yes, delete the value in Parameter
file and run it.
3. Other way to troubleshoot this case is, Do a web_reg_find() above the failing request
to check for “ `Status`Error`”. If the web_reg_find passes, insert a logout/login code
so that the next iteration starts using the next value in the parameter list.
4. Pre-requisites for this case is:
1. Disable the “status_error1” in the content check. Instead use
web_global_verification()
2. In the parameter settings, make sure that you have sequential/each iteration for
that parameter.

 

SBL-BPR-00162

Error invoking service '<Service Name>', method '<Method Name>' at step '<Step
Name>'.(SBL-BPR-00162)

Steps for troubleshooting:

1. Check for the status of the stubs for this scenario or contact the administrator for the
same.
2. You can also handle this error by sending a message in the log file for better
scripting knowledge.

 

SBL-SCH-00127

Error in Date/time format.

Steps for troubleshooting:

1. Select the request where the error happens.
2. Check for the value you have provided for the date/time.
3. This error happens when the LR date format doesn’t match with the Siebel date
format.
4. If you had given the date/time using parameter, change the format so that the
formats match
5. Instead you can use lr_save_datetime() for passing the date in required format.

 

SBL-UIF-00348

Method <MethodName> is not allowed here

Steps for troubleshooting:

1. This error happens if there is any change in UI while replaying the scenario.
2. This could not be troubleshot, instead it could be handled.
3. Do a web_reg_find() searching for the specific text you noticed while recording @
the failing step. And save the count to a variable.
4. Place a if-condition on basis of the variable. For Ex
Web_reg_find(“Text=pop-up”,”SaveCount=abc”,LAST);
If (abc==1)
{
Place the Pop-up request here;
}
Else
{
Goto Nextstep;
}
Nextstep:

 

SBL-UIF-00335

Back or refresh

Steps for troubleshooting:

1. This is the most popular error code and also most time-consuming to
troubleshoot.
2. This error happens due to difference in SWEC values or uncorrelated SWEC
values.
3. Make sure that you correlate the SWEC values and use it in subsequent requests
or follow the addition approach used in LR.

 

SBL-UIF-00313

An Error occurred while resetting context of the application

Steps for troubleshooting:

1. This error happens if the length of the row-Id differs every time.
2. Re-record the scenario without enabling auto-correlation.
3. Check for the SWEP value @ the failing request.
4. You might notice that a value changes if the rowid is different. That’s the length of
the row id.

5. If there is a Row-id in it, then correlate it and capture the length of the row id using
web_save_param_length().
6. Use the length you have captured in value obtained in SWEP.

 

SBL-UIF-00299

Wrong field values or value types detected in field %1. Please re-enter your field values. If
you need additional assistance, please refer to the documentation.

Steps for troubleshooting:

1. You can find the Fields in Item Data with name as “s_1_2_2_0”. Copy this value and
scroll up to the preceding web_url()
2. Open the same in tree view and copy-paste in front page or HTML editor.
3. Search for the value you have copied and you would find the fieldname associated
with it.
4. If the Fieldname you were searching for, is found, Check for the values you have
provided as input.
5. Change the values for that field and run the script again.

 

SBL-DAT-00498

<Fieldname> requires a value.

Steps for troubleshooting:

1. You can find the Fields in Item Data with name as “s_1_2_2_0”. Copy this value and
scroll up to the preceding web_url()
2. Open the same in tree view and copy-paste in front page or HTML editor.
3. Search for the value you have copied and you would find the fieldname associated
with it.
4. If the Fieldname you were searching for, is found, Check for the values you have
provided as input.
5. Change the values for that field and run the script again.