Siebel Error Handling

We would like to share how the errors are being classified in the Siebel Application before
we give you some picture on the errors.

Each error in Siebel comes with an Error code with the format SBL-<Component>-<Error
code>

For Example: SBL-BPR-00162

The usual error codes which the load runner displays during the run-time are of
“DAT”,”BPR”,”SCH”,”UIF”, where DAT stands for Data, BPR for Business Process, SCH for
Scheduler, UIF for User Interface.

Now coming to Error codes and the steps to overcome/troubleshoot them, we have collated
the below list of codes

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.
 Script Handling Tips!!!

If doing a Siebel Correlation a tough job, then making it to run successfully is a

tougher job. Here are some of the tips which we had faced/understood while doing
the scripting.

• Usage of for – loops at places where the record which you select from an applet
changes its position randomly. We need to use for – loop as we would have
correlated according to the server response during recording. This could be
implemented at instances where you need to select the specific record also.

• If – Conditions would be useful while doing a check for a pop-up or in the above
case.

• While Correlating SWERowids, make sure that the Ordinal is according to the
SWEMethod found in the script.

• Web_url contains the HTML code of a page. If we closely observe, we could find
the fieldnames mapped with an Object id which in turn are displayed as
“s_1_2_1_0” in the succeeding requests appearing in script. This would be
helpful while troubleshooting some errors like “invalid Field value”.

• If the script takes a long time to process a request, then make sure that you
don’t face a time-out issue. In order to over-come this issue, you would need to
change the time-out seconds to higher value. Default is 120 Sec. You would find
it in Run-time Settings > Preferences > Options > General list > Step
Download timeout (sec).

• If you decide to correlate the Siebel Dynamic values manually then, make sure
that you use star array for correlating SWERowid appearing in the script.
Because, the star array would have all the necessary details about the record
manipulated/selected. There will be also a same value appearing with `i` as
Left Boundary and ` as right boundary which would not be suitable for
correlation in rare cases.

• One more advantage of using star array is, you can correlate the field values for
the same record and reduce using the parameterization for those.

• Mostly the values which need correlation are listed below

1. SWETS  Siebel Web Extension Time Stamp

 This can be correlated by using web_reg_save_timestamp() just above the
request and pass it.

2. SWEC  Siebel Web Extension Click count

This can be correlated by increment method followed in LR or using the

web_reg_save_param().

3. SWERowid  Siebel Web Extension Row id

This needs to be correlated according to the Ordinal (no of occurrence and

mode of occurrence). Mode of occurrence refers to the way which the Row id
is selected. If it appears in `Value Array` or `v` Array, then we opt for Star
Array. Else we opt for usual way of choosing LB and RB as `i` and `
respectively.

4. SWEACn  Siebel Web Extension Applet count.

This value usually appears in web_url() and you can correlate @ first
occurrence in the start and replace all other occurrences with the correlated
variable name.

5. Siebel Session Id.

This value appears @ the start and most probably twice in whole script. This
needs to be correlated if the script requires QA.

6. SWERowids  Siebel Web Extension Rowids

Kindly note this value is not same as the one mentioned earlier. This value
would correspond with the SWEMethod implemented/used in the step. So the
Ordinal No depends on the SWEMethod in the Server Response.

• On Rare occasions, these values needs to be correlated

1. SWEBMC  Siebel Web Extension Book Mark Count

 If the Siebel application has the feature of book mark/levels of application
being accessed by the user, ex: Siebel Order Applet > Order –Sales New.

Then we need to correlate this value.

2. SWEP  Siebel Web Extension Path

This value is usually zero or not mentioned in the script. But if this variable is
populated with some value, and then make sure that you correlate it.

3. SWEVLC  Siebel Web Extension View Layout Count

This value usually remains the same throughout the script. But if the Script is
lengthier or more applets/views are visited in the scenario, then correlating
this value would do well.

• Normally the star array is correlated by LR taking `v` and ` as LB and RB

respectively. The correlation would be stronger if you provide the RB as `i` (if it
occurs as `v`<Star Array Elements>`i`<Other Element>` format.