HTTP Error 400 error at Description as Reported (Doc ID 1933445.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Argus Safety Japan - Version 6.0.5 and later
Information in this document applies to any platform.

Symptoms

On 症例フォーム >> 有害事象 tab (Japanese language screen of Case Form >> Events tab),
when entered a double byte space (Japanese zen-kaku space) character to the コード化される事象名 (Description as Reported) field then saved,
error message is displayed on a pop-up window.

Error Message:
------------------
Bad Request

HTTP Error 400. The request is badly formed.
------------------

Sample Event texts:
-----------------------
肺炎 --- Successfully saved.
肺 炎 --- Bad Request / HTTP Error 400. The request is badly formed.
テストテスト --- Successfully saved.
テスト テスト --- Bad Request / HTTP Error 400. The request is badly formed.

 

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms