SBL-UIF-00335: BACK or REFRESH

APPLIES TO:

Siebel CRM - Version 8.0.0.4 SIA [20417] and later
Information in this document applies to any platform.

SYMPTOMS

On : 8.0.0.4 SIA [20417] version, Client Functionality

SBL-UIF-00335 on dedicated client

During debugging, the customer killed one of the session, from then on, every time they use dedicated client the web browser would show below. error message

'Encountered an error.
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.(SBL-UIF-00335)'

They cleaned the cache/history and restart the pc and tried to clear the log but the issue was not resolved.

CAUSE

The cause of the issue was resolved by the customer , they found from reviewing of their Templates that some were missing and after replaceing the missing templates the issue was resolved.

No further details as to which templates were missing so you should confirm that all are present .

SOLUTION

 Replace missing Templates

APPLIES TO:

Siebel Healthcare Service - Version 8.0.0.6 [20423] and later
Information in this document applies to any platform.

SYMPTOMS

It was reported that when the default homepage view for the application is not part of the user's responsibilities, that a white page and SBL-UIF-00335 error is shown. In this case, the application did not load, and a white page was shown instead.

This is illustrated below:



The text of this error is listed below:

Encountered an error.
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.(SBL-UIF-00335)

EXPECTED RESULT:
The expected behavior in this scenario is that instead of a white page and the SBL-UIF-00335 error, the application should load properly and a SBL-DAT-00329 error should be shown. When the user does not have access to the default starting view of the application, the user should be able to continue to use the application and access the other views which they have been granted access by responsibilities.

The expected error message is shown below:



(Note that in this example, the test user has access to only one view in the Contact screen.)

The text of the expected error for this situation is listed below:

We detected an Error which may have occurred for one of the following reasons:
The responsibility of user '<user id>' does not allow accessing view '<view name>'.(SBL-DAT-00329"

Note that <user id> is a placeholder for the user id, and <view name> is a placeholder for the view name.

CAUSE

This issue was reproduced by Oracle Technical Support in a standard 8.0.0.10 application by creating a test user who only had one custom responsibility, which contained only the FINS Home Page View.

Note - Testing has shown that this behavior did not happen in lower 8.0.0.x fix packs.

A bug was logged to report this issue. Product defect bug 11846694 ( bug 11846694 ) was logged to report this issue.

SOLUTION

As of the publishing of this document, this issue reported in bug 11846694 ( bug 11846694 ) has been closed as not feasible to fix.  However, there is a workaround for this issue.

Workaround:
The workaround for this issue is to ensure that all users have access to the default starting view, which will avoid this error.

APPLIES TO:

Siebel CRM - Version 8.1.1.11 SIA [23030] and later
Information in this document applies to any platform.

SYMPTOMS

The OpenUI Mobile client is logging in intermittently on the mobile device : Samsung Galaxy Trend Plus

The login will render this message after login :

SBL-UIF-00335 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.

After 2 or 3 tries, the login is successful

The problem occurs :

- If HTTPS is enabled (with HTTP only, the login is always successful)

- The Chrome browser is used on the device : Samsung Galaxy Trend Plus


Using a PC and Firefox (running with a user agent string emulation, to emulate the phone) - the login using HTTPS is consistently working

CAUSE

The problem was caused by the use of a self-signed certificate.

Mobile phones deal with self-signed certificate differently to certificates from a Trusted Certificate Authority.

In this instance, the phone's native browser accepted the self-signed certificate consistently.  However, the Chrome browser only accepted the self-signed certificate on an intermittent basis.

 

SOLUTION

Using a valid certificate from a Trusted Certificate Authority resolved the issue.

The Mobile phone can consistently access the Siebel Open UI application using the Google Chrome browser, when a certificate from a Trusted Certificate Authority was used.

APPLIES TO:

Siebel Tools - Version 7.7.1 [18306] and later
Information in this document applies to any platform.
Error Message Area:UI Framework - UIF

PURPOSE

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-UIF-00335: 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.

SCOPE

This document is informational and intended for any user.

DETAILS

Explanation

1. If the error occurs when drilling down on a record, most likely the record has been deleted by other users.

2. If the error occurs after clicking on the browser BACK or REFRESH button and then clicking on a link or button, it is because the original buscomp context cannot be fully restored.

3. Maybe the request is to retrieve a frame layout that is supposed to be cached on the server but is not found for some reasons.

Corrective Action

If the error occurs when drilling down on a record, please try to search the record again. It may have been deleted by other users. 

The SBL-UIF-00335 error is a generic error that can have many different causes.  It could be the environment setup, a custom configuration or an incorrect behavior, bug, with the Siebel product.  The following information will help to narrow down the cause of this error.

Is this error reproducible or is it intermittent? If a user reports this frequently but can not reproduce the error, enable detailed logging to review their steps.

When did this error start occurring?

Does this happen in all Siebel Environments? Production, QA, Dev? Does it reproduce only in the thin client, dedicated web client, or the mobile client? 

Is this an High Interactivity client (HI), Open UI client (OpenUI), Standard Interactivity (SI) client, or a Mobile client?

If the error is reproducible, first verify that there are no expired license keys in the Siebel application.

Production Down with Error SBL-UIF-50103 and Associated SBL-UIF-00369 and SBL-UIF-00335 (Doc: 1382256.1)

Test with a standard "out of the box" siebel_sia.srf (specific to the Siebel version past Siebel 8.1.1.10) on the most similar view to to see if SBL-UIF-00335 reproduces with the standard configuration.

If the SBL-UIF-00369 only reproduces with the custom configuration, then test without Server Scripting, Browser Scripting and Open UI scripting customizations.

These suggestions should help to define circumstances that cause the SBL-UIF-00335 errors.

If these suggestions do not help, please contact Siebel Technical Support and provide details about the steps used to cause the error especially with regard to navigation in the User Interface, and include relevant details about customizations made in the environment.