My Oracle Support Banner

Get HTTP Bad Request Error 400 When Loading Browser Scripts After Upgraded From Siebel 19.4 to 20.8 or Above (Doc ID 2723376.1)

Last updated on AUGUST 30, 2021

Applies to:

Siebel CRM - Version 20.8 to 21.5 [Release V17]
Information in this document applies to any platform.

Symptoms

After upgraded from Siebel 19.4 to 20.8, all requests for Browser Scripts were failing with HTTP Bad Request Error 400 in the Browser Console.

All the old srf_* browserscript folders from the AI \applicationcontainer\webapps\siebel folder have been deleted.

ERROR:


The issue can be reproduced at will with the following steps:
1. Upgrade from Siebel 19.4 to 20.8
2. Log into the 20.8 application and navigate to a View that triggers Browser Scripts
3. The above 400 Error shows in the Browser console

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.