Hi, We are seeing the below errors in our WebFOCUS environme...

[VisuaLizeFOCUS .]

While looking in RS logs :

com.ibi.ibfs.error.IBFSException: Function RunItem not implemented IBFS:

getting this error.

[VisuaLizeFOCUS .]

Hi,

We are seeing the below errors in our WebFOCUS environments:-

Unexpected exception: System.InvalidOperationException: Unexpected web exception: System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at WFRestLib.WFRestService.SendRequest(String httpMethod, String requestUri, String requestBody, WebHeaderCollection httpHeaders, String userAgent) > System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at WFRestLib.WFRestService.SendRequest(String httpMethod, String requestUri, String requestBody, WebHeaderCollection httpHeaders, String userAgent) End of inner exception stack trace at WFRestLib.WFRestService.SendRequest(String httpMethod, String requestUri, String requestBody, WebHeaderCollection httpHeaders, String userAgent) at WFRestLib.WFRestService.SendRequest(String httpMethod, String requestUri, String requestBody, WebHeaderCollection httpHeaders) at WFRestLib.WFRestService.SendWFRequest(String httpMethod, String requestUri, String requestBody, WebHeaderCollection httpHeaders) at WFRestLib.WFRestService.SendWFRequestWithCheck(String httpMethod, String requestUri, String requestBody, WebHeaderCollection httpHeaders) at WFRestLib.WFRestService.AddUserToGroup(String userId, String groupId) at WFRestLib.WFAdminHelper.AddUserToGroup(WFUserGroupInfo groupInfo, WFRestService service)

To give a little background - We run an ETL job that syncs Users data (new and Updated) with GROUP information from our Data-warehouse to WebFOCUS using WebFOCUS Restful web Services.

Any thoughts

Thanks.

[Manoj Chaurasia]

Rajesh

I saw you opened a case on this. I could not find any others besides yours with this error.

[Toby Mills]

Hey Raj

Was this working for you before and only recently started having trouble

I was thinking about your issue and figured it was worth passing along an idea.

I did a google search on your .net HTTP 400 and I saw one thing that caught my eye. Maybe you need to define a bigger max size for the call

The following led me to the next thing

The remote server returned an error: (400) Bad Request

Toward the bottom of that, the suggestion was made about needing a bigger maximum size - the original poster said upping the max size of data allowed.

Heres the post the guy with the answer referenced.

WCF Error 400 Bad Request when POST some data

One of your .net guys might know what this all means - its just a guess on my part that makes sense - IF this usually works for you and only recently started dying (your data could be growing from month to month).

 

You must set maxReceivedMessageSize and readerQuotas (if needed) on the service when posting data from client. Your client configuration has modified maxReceivedMessageSize which works for getting data from service but when you send large amount of data to the service you must modify its configuration as well.

 

Hope we get lucky and this was helpful.