5
Vote

The remote server returned an error: (401) Unauthorized

description

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

file attachments

comments

timheuer wrote Jan 5, 2009 at 4:09 PM

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

TJF wrote Jan 5, 2009 at 9:08 PM

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.

Mike78 wrote Jan 7, 2009 at 6:00 PM

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

wrote Jan 7, 2009 at 6:17 PM

wrote Jan 7, 2009 at 6:19 PM

timheuer wrote Jan 8, 2009 at 3:09 AM

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?

Mike78 wrote Jan 12, 2009 at 10:18 PM

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).

peter_dy_tane wrote Jun 12, 2009 at 2:00 AM

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.

ParagMahalley wrote Aug 14, 2009 at 2:43 PM

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

thenox wrote Feb 2, 2010 at 8:22 AM

Im getting the same error.

It works perfectly on every test and development enviroment I have, but as soon I deploy it to the production enviroment it fails.

The only thing that is different from my other enviroments to production is that there is 2 frontend servers end the architechture is 64 bit.

Any ideas ?

wrote Feb 4, 2010 at 11:08 AM

RCE_WI wrote May 5, 2010 at 7:34 PM

I'm still having this problem. I have two WFE servers using NTLM and are load balanced with a Cisco Netscaler. I've verified that each server's web.config file is identical. The RSS web part points to the load balanced URL. On one server the web part works fine (the server that I used to load the solution), the second server the web part doesn't work upon the initial page. I have to refresh the data on the web part several times for the data to be displayed. The URL is plain and looks like this: http://sharepoint.domain.com/depts/is/CloudComputing/blog/_layouts/listfeed.aspx?List={AB59691F-B973-4835-B3BC-2D9DFE2D0B84}. Can anyone help?

wrote Jan 24, 2012 at 9:00 AM

wrote Feb 14, 2013 at 2:26 AM