This project is read-only.


Error began yesterday


Request failed. Unexpected response data from server null
Is there a fix on the way?


sjbosley wrote May 22, 2014 at 5:46 PM

Looks like more and more people are experiencing this issue. We started seeing it this morning. Unfortunately it doesn't seem like the author is monitoring this site any more. If you are then please respond to one of these posts. We need to understand if anyone can fix this or whether we need to look for another news app. Thx.

OlivierCarpent505 wrote May 22, 2014 at 6:42 PM

Thanks for your bug report, sorry for the delay and this behavior. This app is open source and provided as is, without support. But i will try to identify the issue because a lot of people report this bug during the last days. First the app code and version has not be updated during the last days.

I'm not able to reproduce it on my tenants, but I'm working on it currently. Can you give me please your kind of site (site model, for example : Team Site) where the app is published, the culture of site ?

Can you please give me the number of news in your list ?

I think that this issue can occur because of a large number of news if your list.

Stay connected in this thread for update. Sorry again.



OlivierCarpent505 wrote May 22, 2014 at 6:50 PM

*** Important note *** *

Please note that this error could occured because of two major reasons :
  • Too many news in your list -> my advice is to remove unused news
  • Performance issue in O365 -> please contact your Microsoft support and check your tenant health admin
  • New conflits between App's Javascript and SharePoint online Javascript -> I will try to identify & fix it asap and I will publish a new version of the App


dgollom wrote May 22, 2014 at 7:05 PM

We are on a Team Site . It's a brand new site with very little data and low traffic. We only have 8 items in our news list and 2 are disabled. Thank you for providing some support.

OlivierCarpent505 wrote May 22, 2014 at 7:31 PM

Thanks a lot.

Can you confirm me that the JS error "Request failed. Unexpected response data from server null" occured in line

"clientContext.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed)); "

in the CarouselAppPart.js ?

simonandrewes59 wrote May 22, 2014 at 8:09 PM

Hi Olivier.

Thanks from me as well for looking at this - it's a great app why is why we're keen to keep it going.

My instance is on a Publishing Site, again very little data (three items) and low traffic. We haven't noticed any performance problems elsewhere on the site.

I'm afraid I wouldn't know how to confirm where the JS error occurred (without some guidance anyway) but I'm sure others will.

2bike wrote May 22, 2014 at 9:02 PM

Hi Oliver, I wonder if this is issue is being caused by a recent update on O365/SharePoint as a couple of other 3rd party web/app parts broke at the same time. These issues seemed to be associated with not being able to pull licensing/external data from external data sources.

One of the other developers pointed us to issue #SP6978. It references InfoPath forms that utilize Web Servers to make calls to external data sources.

Anyway, don't know if the problem on the Corp News App is the same, but all started about the same time (20th/21st).

OlivierCarpent505 wrote May 23, 2014 at 6:44 AM

Thanks a lot for this report.

Really strange behavior. In fact, corporate news app uses only 1 Javascript call to SharePoint web service (with SharePoint Javascript Object Model) to retrieve the news list items. This call is simple and only manage few items.

The "Request failed. Unexpected response data from server null" occured when this web service request failed.

Could be a performance error or after a change on SharePoint Online services. I'm still investigating. Thanks everybody for feedbacks and help in troubleshooting about this bug.

OlivierCarpent505 wrote May 23, 2014 at 9:51 AM

I can now reproduce the issue, my tenants are now affected too. Thanks everybody for feedbacks, I will try to identify if a fix is possible or not.

wrote May 23, 2014 at 10:39 AM

ekapic wrote May 23, 2014 at 12:56 PM

I have been trying to reproduce the issue and in my test environment (Office 365 site with publishing activated) it intermittently works well or raises an error, on random basis. I've been analyzing the traffic and there is no difference in the requests.

Can you try to reload (F5) the page several times to see if it works? If so, then we have to wait until MS provides us with an update about what's causing the "Bad Request" response from o365.


endamcnamee wrote May 23, 2014 at 1:45 PM

Hi Guys,

I have come across the same issue today and found a fix. Looking at your code you were using the same data access method as me. In the CarouselAppPart.js file, in the sharePointReady function change the data access to use the cross domain library:

Hope this helps.


OlivierCarpent505 wrote May 23, 2014 at 3:42 PM

Thanks a lot.

"Request failed. Unexpected response data from server null" errors can occure because of bad context init or a bad request format. The request seems good and I think that may be the cross domain init can help (but the corporate news app requests only list in the App web, not the parent web site).

I will test it, but I also study to request lists with REST API, not the JavaScript Object Model API. It could be better, because this method is more stable, and could work with O365 public site too.



OlivierCarpent505 wrote May 24, 2014 at 9:48 AM

Good news, I find a way to fix this issue raised by last SharePoint Online updates. The JS behavior is not fix by Microsoft, so I decided to change the way to request items in the code (REST and not JS Object Model).

The downside is that I need to publish a new version of the application with the fix. Therefore, update your environments with these new version.

In the next few hours:
1: I will publish a new version of the code fixed in TFS on codeplex
2: I will publish a version available on codeplex
3: I will update the application in the Office Store, but this should take a few days before be revalidated

Sorry to all fans of this application for the inconvenience.

OlivierCarpent505 wrote May 24, 2014 at 9:57 AM

The fix is now published and I submitted for approval the App in the market place, but the update will be available only in few hours/days.

OlivierCarpent505 wrote May 24, 2014 at 5:59 PM

This bug is fixed with version

kazzam wrote May 26, 2014 at 12:49 AM

Thank you Olivier, I will wait for the published update on App Store.

OlivierCarpent505 wrote May 26, 2014 at 9:59 PM

The app is now published and approved in the Store.

  • This version was a critical fix posted previous saturday. In our code release, this is the version
  • Now, the current version in the codeplex site is the version, more stable.
  • The version has been pubished today in the market place, and will be probably available in 2 days
So our advice is :
  • If you can wait because your web site is in production, update the App in version, but don't forget to update one more time because the stable recommended version is the
  • If you can wait still some days, you can wait the version available in the market place to update.
I will publish in this thread a message when the will be available in the Office Store.

OlivierCarpent505 wrote May 27, 2014 at 12:29 PM

I received this morning confirmation, the version has been accepted in the SharePoint / Office Store. It will be available in the next hours.

jcooper88 wrote May 27, 2014 at 7:25 PM

We are still getting the error message with v. 1.6.0 and 1.6.2. It was working for a while this morning with 1.6.0 but now it seems that we are getting the error with both versions.

2bike wrote May 27, 2014 at 9:51 PM

I believe this is the issue that is causing the problems with this and a couple other 3rd party web/app parts.

As reported in O365 Dashboard

SP6994 May 23, 2014 2:41 PM Restoring service Current Status: Engineers have identified an issue in which SharePoint Online Web applications intermittently fail to render. Engineers have developed a fix and are deploying it across the environment to remediate end-user impact.

Customer Impact: Affected customers may experience intermittent SharePoint Web Application render failures

Workaround: As a workaround, customers can refresh the Web Application until it renders correctly.

Estimated Time to Resolution: The deployment process is expected to complete by Wednesday, May 28, 2014, at 8:00 PM UTC.

Next Update: Tuesday, May 27, 2014, at 8:00 PM UTC

OlivierCarpent505 wrote May 27, 2014 at 11:54 PM

Please, if after an update you still have the issue :

Can you save your data and reinstall the App ?

It's very important to be able to identify if the problem come from a bad update process or if the fix doesn't work everytime.

Sometime, an update of an app can still keep the old files (like CSS, JS, etc.). I recommand to uninstall and install the app. Sorry for the inconvenience for your data to recreate

simonandrewes59 wrote May 29, 2014 at 5:14 PM

Olivier - it's working well so far for me after uninstalling and reinstalling the latest version. Thank you for resolving this.