(400) Bad Request. Object reference not set to an instance of an object

abhinav-maheshwari / sharepoint-facebook-wall

Automatically exported from code.google.com/p/sharepoint-facebook-wall

0 stars 0 forks source link

(400) Bad Request. Object reference not set to an instance of an object #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

I have updated with the latest package (4.1) after having problems with Issue 
16. Everything worked fine, but now I suddenly get:

"The remote server returned an error: (400) Bad Request.Object reference not 
set to an instance of an object."

Any suggestions?

Kind regards
Jenny

Original issue reported on code.google.com by jenn...@live.se on 25 Apr 2012 at 12:44

GoogleCodeExporter commented 9 years ago

Login to Facebook. 
Regenerate the "Access Code".
Put the new "Access Code" in WebPart.

This solves the issue.

Original comment by ashok.sa...@gmail.com on 25 Apr 2012 at 2:22

GoogleCodeExporter commented 9 years ago

How to regenerate the Access Code???

Original comment by dhaneshm...@gmail.com on 26 Apr 2012 at 3:09

GoogleCodeExporter commented 9 years ago

I did this and still receive the (400) Bad Request.  The webpart was working 
fine earlier today.

Original comment by techta...@gmail.com on 26 Apr 2012 at 2:29

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Same here. I got it to work fine the 1st time. Half an hour later I checked 
back and it was returning a 400 error. I regenerated the Access Code and put it 
into the WebPart. Still getting a 400 error. Please let me know if there is 
anything I can do to remedy this. I had it working for days, then needed to 
change the app to a new one in a different FB account. It worked but then 
stopped about 30 min later. Any insight would be great!

Thanks,
Bryan

Original comment by djloo...@gmail.com on 27 Apr 2012 at 8:59

GoogleCodeExporter commented 9 years ago

Please try our new version 4.2

Original comment by niting@brickred.com on 4 May 2012 at 9:16

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Hello,

I've downloaded and deployed the new package, but the error still remains. 
Anything else that I need to update?

Kind regards
Jenny

Original comment by jenn...@live.se on 6 May 2012 at 8:54

GoogleCodeExporter commented 9 years ago

Any news regarding this issue?

BR
Jenny

Original comment by jenn...@live.se on 11 May 2012 at 7:59

GoogleCodeExporter commented 9 years ago

Original comment by niting@brickred.com on 14 May 2012 at 7:47

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Hi Jenny,

Please send your webpart settings to niting@brickred.com. We need to debug this 
issue at our environment to find out the exact problem.

Nitin Gupta

Original comment by niting@brickred.com on 14 May 2012 at 7:58

GoogleCodeExporter commented 9 years ago

any updates for this issue?  appreciate your feedback

Original comment by ranne...@yahoo.com on 18 May 2012 at 9:02

GoogleCodeExporter commented 9 years ago

Hi Jenny,

Can you please confirm if our solution solves your issue so that we can mark 
fix to this issue

Sumit Kanchan

Original comment by niting@brickred.com on 1 Jun 2012 at 10:17

GoogleCodeExporter commented 9 years ago

I have same problem and I can not update

Original comment by i...@student.silkwood.qld.edu.au on 18 Jun 2012 at 1:36

GoogleCodeExporter commented 9 years ago

Please try our new package 4.3 with the issue resolved.

Sumit kanchan

Original comment by niting@brickred.com on 28 Jun 2012 at 8:17

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Hi,

First off, the solutions is great, thanks for making it available to us.

I'm getting the 400 bad request error from version 4.0 and 4.3 of the 
Sharepoint Facebook Wall web part. I contacted FB and they've come back to say 
that it's because we have hit their rate limiter on the number of connections 
from our IP. They've recommended using FB's own API but to be honest I prefer 
the solution provided by you guys...is there any way around this to limit the 
number of times the web part/solution poll's the FB wall?

Thanks
Stuart

Original comment by anotherb...@gmail.com on 11 Jul 2012 at 9:12

GoogleCodeExporter commented 9 years ago

Hello,

I have downloaded the new version, installed it, even created a new FB 
application and configured the web part, but I still get the 400 error. Could 
it be due to the issue tht Stuart mentioned? Any solution for this?

Kind regards
Jenny

Original comment by jenn...@live.se on 13 Aug 2012 at 6:52