FeedReader Work Item Rss Feed

Commented Issue: External RSS site goes down causing Webpart to shut down page [21059]

naiban — Fri, 20 Nov 2009 15:45:01 GMT

I just had an external site providing a feed go down and this caused the page in which I had the feed displayed to showed the web part problem page. Anyone else have this problem?

Created Issue: '=' is an uxpected token [25327]

audunms — Fri, 13 Nov 2009 15:05:36 GMT

Hi, I get the attached error message on some RSS feed. Most RSS feeds works fine though.
I am grateful for any feedback on this.

Commented Issue: External RSS site goes down causing Webpart to shut down page [21059]

sasquatch — Tue, 03 Nov 2009 14:22:09 GMT

I just had an external site providing a feed go down and this caused the page in which I had the feed displayed to showed the web part problem page. Anyone else have this problem?
Comments: ** Comment from web user: sasquatch **

Same error, Any fix or workaround for this?

Commented Issue: Feed symbol cannot be changed [25098]

timheuer — Mon, 26 Oct 2009 17:01:22 GMT

Hi there,

we just installed your FeedReader webpart in our SharePoint Services. We have two instances on out page displaying two different feeds. There is one problem we encountered: The path to the new symbol replacing the default RSS symbol is not stored. I don't know if we misconfigured something or if it's a bug? Please let us know if you have a solution!

Kind regards,
Sebastian Wramba

edit:
If I open the default.aspx in SharePoint Designer and have a look at the source code, there is an XML tag called "PartImageSmall" which containts the correct location to the symbol. I think, the problem relies on those lines in RSSWebPart.cs:

//Set Catalog and Title icons
this.CatalogIconImageUrl = this.ClassResourcePath + "/feedicon-16.png";
this.TitleIconImageUrl = this.ClassResourcePath + "/feedicon-16.png";
Comments: ** Comment from web user: timheuer **

Sebastian -- correct, it is essentially hard-coded -- you *can* go into where the web part is deployed (look at the resulting URL for the web part and just put new icons in that folder with the same name as a work around.

Created Issue: Feed symbol cannot be changed [25098]

sebastian_wr — Mon, 26 Oct 2009 09:47:51 GMT

Created Issue: Page broken when a RSS site is down [24931]

Mylene — Thu, 15 Oct 2009 15:08:51 GMT

When a RSS site is down, the page where is the Reader is not accessible. Do you plan to fix it?

Commented Issue: Does the web part support ATOM?

fabrice69 — Thu, 03 Sep 2009 13:49:11 GMT

I took a quick look at the source code and I do see what looks to be support for ATOM. However the two feeds I've tried both display errors.

http://www.atomenabled.org/atom.xml
http://www.povertylaw.org/clearinghouse-review/atom.xml (this is the one I really want)

Here is the error that's displayed below the other feeds in the web part:

http://www.atomenabled.org/atom.xml had a problem reading the feeds from the URL.
Error returned from FeedReader: Object reference not set to an instance of an object.:SmilingGoat.SharePoint.WebParts.Rss
Comments: ** Comment from web user: fabrice69 **

Hi Tim,
Your component is really great, but a lot of Blog site use the ATOM spec, as for example the BlogSpot or Blogger
Thanks for your help for this request.
Fabrice Romelard [MVP]

Commented Issue: The remote server returned an error: (401) Unauthorized

ParagMahalley — Fri, 14 Aug 2009 14:43:58 GMT

Hi
so far I used 3.0.0.0 without any problems. After (Dec 20st) installing dotnet 3.5 and patching to the newest level (windows server 2003) I can no longer access news from the server where RSS FeedRead is installed .(e.g.https://www.mydom.ch/site/_layouts/listfeed.aspx?List=%7B4BCA266B%2D3A43%2D4BEB%2D90EB%2DFAF3A49F7B15%7D).
I decided to upgrade to 3.1.0.1 today and found the same Problem. Besides paching an installing 3.5 framwork I have not changed anythig.
The webpart works perfectly if directed to an externa feed.
The internal feeds work perfectly if accessed through Internet Explorer. Changeing from https to http does change anything.
I have attached a screenshot of the error message.
An clue what's wrong?
Thomas
Comments: ** Comment from web user: ParagMahalley **

Tim, I'm working with Mike (above) - we still have to resolution to why this would not work consistenly in production.

The service account has read access to the list, and its feed. The mysterious thing is that, it works if we refresh the page abt 4-5 times.

So there are 3 behaviors we see:
1. Page errors out with: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest.GetResponse() at Argotic.Common.SyndicationEncodingUtility.CreateWebResponse(Uri source, ICredentials credentials, IWebProxy proxy) at Argotic.Common.SyndicationEncodingUtility.CreateSafeNavigator(Uri source, ICredentials credentials, IWebProxy proxy, Encoding encoding) at Argotic.Syndication.GenericSyndicationFeed.Load(Uri source, ICredentials credentials, IWebProxy proxy, SyndicationResourceLoadSettings settings) at Argotic.Syndication.GenericSyndicationFeed.Load(Uri source, ICredentials credentials, IWebProxy proxy) at SmilingGoat.SharePoint.WebParts.RssFeedReader._RefreshFeedCache() at SmilingGoat.SharePoint.WebParts.RssFeedReader.UpdateCache(Object sender, EventArgs args) at System.Web.UI.Control.OnPreRender(EventArgs e) at Microsoft.SharePoint.WebPartPages.WebPart.OnPreRender(EventArgs e) at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

2. Page loads but the web part errors out with single line unauthorized 401 message.

3. Page and web part load as expected (without absolutely any changes). This has been going on for over six months now.. Please provide insight into what we could change to debug/understand and fix this. Is there another web part that we could use instead??

Thanks! Parag

Commented Issue: The remote server returned an error: (401) Unauthorized

peter_dy_tane — Fri, 12 Jun 2009 02:00:18 GMT

Hi Tim,

We are experiencing the same problem. We are using a SharePoint RSS feed. Everything worked fine in other environments, but started failing in staging. We were using host headers in the staging environment, not in our dev environment. When I started using host headers in our dev box, we were able to replicate. I fixed it in dev by following the steps in the KB article on loopback restriction (http://support.microsoft.com/kb/896861). We tried the same for staging, but it didn't work.

Staging is load-balanced. NTLM authentication. Do you have some hints on how we can fix this issue? Thank you.

Created Issue: Having same page as Feed url.

creativemanix — Tue, 24 Feb 2009 10:41:12 GMT

Added same page URL as feed url and the site came dead slow, and some time even it stoped my application pool.

One of our user done this configuration!.

Also what will happen if:
1) page 1 webpart has url of Page2
2) and Page2 has url of page 1

I understand this is an common problem with web request.

Commented Issue: External RSS site goes down causing Webpart to shut down page

rjh — Tue, 17 Feb 2009 15:17:05 GMT

Yes I have just had this occur. The RSS feed site is throwing an internal 500 server error and the subsequent Feed Reader Webpart pointed at it is causing the SharePoint page to come up with a "Unexpexted error". Is there any work around for RSS sites going down?

Created Issue: External RSS site goes down causing Webpart to shut down page

grfehr — Mon, 09 Feb 2009 17:05:48 GMT

I just had an external site providing a feed go down and this caused the page in which I had the feed displayed to showed the web part problem page. Anyone else have this problem?

Created Issue: Does the web part support ATOM?

timheuer — Mon, 19 Jan 2009 03:04:48 GMT

Commented Issue: The remote server returned an error: (401) Unauthorized

Mike78 — Mon, 12 Jan 2009 23:18:40 GMT

Thanks Tim. We built the latest version which uses the Argotic library. Again, it works fine in our dev, testing, and staging environments, but fails in production part of the time (but still works sometimes). Now it is failing with a generic "The remote server returned an error: (401) Unauthorized. "

(Sorry for the delay in replying - it took us awhile to get the latest version into the production environment due to the release process here).

Commented Issue: The remote server returned an error: (401) Unauthorized

timheuer — Thu, 08 Jan 2009 04:09:52 GMT

TJF: I'm sure the switch to port 80 made life easier instead of SSL (perhaps a self-signed certificate was in the way?)

Mike78: Anything that returns an error with SmilingGoat.Syndication is an older version. The syndication library that I wrote is now pretty old and never handled auth feeds very well consistently. The current version uses an open source syndication library that is widely used...perhaps give that a try?

Commented Issue: The remote server returned an error: (401) Unauthorized

Mike78 — Wed, 07 Jan 2009 19:00:07 GMT

We are getting this same (or a very similar error), with a few differences. We are using version 3.0.0.2 currently. In our case, the web part works fine in all environments except our production environment. In the production environment, it works fine sometimes and errors out other times, and we haven't been able to find a consistent pattern.

Our production environment does have two WFE servers which are load-balanced with an F5. The error can occur on either server, though. We are not currently using SSL (so everything is over port 80). Any ideas on what the issue might be? Error is below:

http://ourdomain.com/departments/humanresources/_layouts/listfeed.aspx?List=7ade4d1e-2f66-44cf-9ff9-e02e9a212ac7 does not appear to be a valid RSS feed. If the feed is valid, please ensure your proxy server settings are correct if you use a proxy server.
Error returned from FeedReader: The remote server returned an error: (401) Unauthorized.:SmilingGoat.Syndication

Thanks,
Mike

Commented Issue: The remote server returned an error: (401) Unauthorized

TJF — Mon, 05 Jan 2009 22:08:20 GMT

Thank you for your quick answer.
Requires authentication? Yes, it does. The account for the worker process, the timer and search is a member of a group the has full access on the whole site.
It now works. What did I do? I changed the URL to use port 80 instead of 443 - that's all. So for the internal access behind the firewall this is ok (port 80 is blocked).
Thank you for all your efforts providing us with this webpart.

Commented Issue: The remote server returned an error: (401) Unauthorized

timheuer — Mon, 05 Jan 2009 17:09:50 GMT

Does that feed URL require some authentication? Is the account that is used for the Sharepoint worker process able to access that feed?

Created Issue: The remote server returned an error: (401) Unauthorized

TJF — Mon, 05 Jan 2009 13:48:24 GMT

Created Issue: No Trace of FeedReader

resmonde — Sat, 27 Dec 2008 00:03:50 GMT

Hi and thanks for the web part. I need a tiny bit of advice. I'm running Sharepoint WSS v3.0. we upgrade from v2.0 about a year ago. Multiple forums and blogs made mention of the RSS Feed Reader so I installed it to my Sharepoint v3.0 WSS server per your instructions and the stadm tool reported success.

So, as far as I know everything worked but when I go to add the web part to a team site I can't see it anywhere. So I backout and go to my parent team site and under Site Settings I look for Web Parts and list them. They all have a *.dwp suffix but I see no reference to RSS Feed Reader. I checked my central admin area and I have Feeds enabled so where is this web part hiding or what i have I forgotten to do or not do. I followed your README to the letter. No one else is reporting this madness so I can only assume I am doing something incredibly stupid? Any advice would be greatly appreciated.