Testing Siebel Business Applications > Automating Load Tests >

Troubleshooting Load Testing Issues

This section provides tips for resolving common issues associated with recording and running automated load test scripts.

NOTE:  The causes and fixes described for these common issues are those that are most often encountered. However, they might not be the only such causes or fixes.

The following issues are addressed:

• Back or Refresh Error
• No Content HTTP Response
• Same Values Error
• Restoring the Context Error
• Cannot Locate Record Error
• End of File Error

Back or Refresh Error

The Siebel application displays an error applet indicating the following:

We detected an Error which may have occurred for on or more of the following reasons:
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.

Cause

This issue can be caused by the following conditions:

• The SWETS was not parameterized for the current request.
• The SWEC was not correlated correctly for the current request.
• The request was submitted twice to the Siebel server without the SWEC being updated.
• The frame was not created on the server, possibly because the SWEMethod has changed since the script was recorded. A previous request should have set up a frame for the browser to download.

Fix

To resolve this issue, try the following fixes:

• Make sure that SWETS is parameterized.
• Make sure that you reset the SWE Count to the SWEC value of the first request in the iteration at the beginning of the iteration.

If these fixes do not resolve the issue, rerecord the script.

No Content HTTP Response

The server returns an error like the following:

HTTP/1.1 204 No Content
Server: Microsoft-IIS/5.0
Date: Fri, 31 Jan 2003 21:52:30 GMT
Content-Language: en
Cache-Control: no-cache

Cause

The row ID is not properly correlated.

Fix

Manually correlate the row ID.

Same Values Error

The server returns an error like the following:

@0`0`3`3``0`UC`1`Status`Error`SWEC`10`0`1`Errors`0`2`0`Level0`0`ErrMsg`The same values for 'Name' already exist. If you would like to enter a new record, please ensure that the field values are unique.`ErrCode`28591`

Cause

One of the values in this request (in the previous code example, it is the value for the Name field) is the same as a value in another row in the database table.

Fix

You must replace this value with a unique value for each iteration for each user. The recommended solution is to use the row ID parameter for the value; this causes the value to be unique.

Restoring the Context Error

The server returns an error like the following:

@0`0`3`3``0`UC`1`Status`Error`SWEC`9`0`1`Errors`0`2`0`Level0`0`ErrMsg`An error happened during restoring the context for requested location`ErrCode`27631`

Cause

The row ID is not properly correlated.

Fix

Manually correlate the row ID.

Cannot Locate Record Error

The server returns an error like the following:

@0`0`3`3``0`UC`1`Status`Error`SWEC`23`0`2`Errors`0`2`0`Level0`0`ErrMsg`Cannot locate record within view: Contact Detail - Opportunities View applet: Opportunity List Applet.`ErrCode`27573`

Cause

The input name SWERowId does not contain a row ID for a record on the Web page. This input name should have been parameterized. The parameter's source value may have changed its location.

Fix

Manually correlate the row ID.

End of File Error

The server returns an error like the following:

@0`0`3`3``0`UC`1`Status`Error`SWEC`28`0`1`Errors`0`2`0`Level0`0`ErrMsg`An end of file error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.`ErrCode`28601`

Cause

The input name SWERowId does not contain a row ID for a record on the Web page. This input name should have been parameterized. The parameter's source value may have changed its location.

Fix

Manually correlate the row ID.