My Oracle Support Banner

OSN Client Access Fails with Various Errors Ending in "Server returned HTTP status: 400 bad request" after Upgrade of Instance from R12 to R13. (Doc ID 2413611.1)

Last updated on JULY 02, 2018

Applies to:

Oracle Social Network Cloud Service - Version 11.13.18.02.0 and later
Information in this document applies to any platform.

Symptoms

After upgrading to Rel 13, OSN client access fails.

Failure occurs when accessing OSN through any of the client connections for OSN such as: OSN Outlook Add-on, Mobile Devices, Browsers and Desktop Clients.

Errors seen on iPhone are like the following:
 1) Failed to load the gadget count. Server returned HTTP status: 400 bad request.
 2) Failed to get profile. Server returned HTTP status: 400 bad request.
 3) Failed to access the server instance. Server returned HTTP status: 400 bad request.
 4) Failed to get list of Conversations for Overview. Server returned HTTP status: 400 bad request.


Above errors are seen when attempting to log into OSN on the Mobile device with predefined Username, Password and R12 OSN URL:

Changes

 Change In POD hostname (URL) structure occurred in Release 13. 

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!


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