An Unexpected Error Occurred Processing Your Request Rss Sharepoint
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: An unexpected error occurred processing your request. Check the logs for details and correct the problem. SharePoint > SharePoint 2013 - General Discussions and Questions Question 0 Sign in to vote Hi All, I am configuring RSS Viewer webpart to SP 2013. But i am getting an error "An unexpected error occurred processing your request. Check the logs for details and correct the problem." I looked for solution of this error. i got to know, we need to set proxy server in web.config file. So, in order to resolve this i put the following set of code in web.config and save the file "
Chris O'Brien CleverWorkarounds Search Nuggets SharePoint Connections Todd Baginski Wouter Archives August 2013 June 2013 January 2013 December 2012 October 2012 May 2011 April 2011 March 2011 February 2011 July 2010 October 2009 June 2009 January 2009 October 2008 September 2008 August 2008 June 2008 May 2008 April 2008 March 2008 January 2008 December 2007 October 2007 September 2007 August 2007 Categories Ajax ASP.NET branding c# Code Design Development FAST Funny Mac music Presentation ramble search Service Sharepoint sharepoint 2013 sharepoint2010 Strategy togaf Travel Uncategorized Video webparts Fixing the Sharepoint RSS Proxy issue in a VMWare environment I found this to be a total pain to figure out how to fix, but once done, the solution is actually very simple. My setup: Most people doing https://social.technet.microsoft.com/Forums/office/en-US/1aacfb9d-61be-4594-ab8d-e0033afdb652/an-unexpected-error-occurred-processing-your-request-check-the-logs-for-details-and-correct-the?forum=sharepointgeneral Sharepoint development will be doing so in a proper networked environment (setup by a proper network admin). In which case this article is unlikely to apply to you and this article, can probably point you in the right direction (hint: you need to set your web.config proxy settings). I am running a Sharepoint development environment at my house, using VMWare, with a minimal win2k3 setup. I'm not a server admin and I'm conscious hits to performance so http://www.neilrichards.net/sharepoint/fixing-the-sharepoint-rss-proxy-issue-in-a-vmware-environment the environment is very lightweight. No Domain Controller, no Active Directory. I'm a developer not a sysadmin. The problem: Unfortunately, Sharepoint cares not for my developing ways and when I tried adding an RSS webpart to a Sharepoint page got the following on-screen error: An unexpected error occured processing your request. Check the logs for details and correct the problem. Crapola. First I thought dodgy rss. Nope. Then I thought, the IIS account doesn't have web access. Nope. So then I looked at the million and one "Sharepoint rss proxy" articles on Google to no avail. They all want you to make changes to the defaultProxy entry in your Sharepoint's web.config. Nope. The cause: For some reason, if you don't have a proxy setup, Sharepoint throws it's toys out the pram and won't work. It won't even try to make a network call (I checked using WireShark). Even when I tried to tell the defaultProxy entry to bypass all addresses, it ignored me. The solution: Setup your own proxy. It's actually very simple (trust me I hate server admin stuff) disable Windows firewall (should have a firewall on your host anyways) I then followed the instructions on support.microsoft.com as best I could under the "Installing the Routing and Remote Access Service" heading. Then magically my rss webparts worked Also important is to make sure you use a proper RSSViewer part in
for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://sharepoint.stackexchange.com/questions/113496/rss-viewer-web-part-not-working developers or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top RSS viewer web part not working up vote 3 down vote favorite 1 We have had a site an unexpected collection set up in SharePoint 2010 where we added quite a few RSS feeds that showed content from other parts of the site collection. When we upgraded the site collection to SharePoint 2013 (with 2010 layout) all the RSS feeds stopped working. On our 'pure' 2013 test environment, I tried setting up an RSS-viewer that just showed an external RSS feed. No success. It seems as if some kind of feature needs to be enabled in 2013 an unexpected error that wasn't needed in 2010? On the site collection feeding the RSS, I have checked that RSS is enabled on the site collection level. On the site collection receiving the RSS, I have checked that RSS is enabled on the site collection level. SharePoint Server Standard Site Collection feature is enabled Lists that feed have RSS enabled The error we get on the 2013 in 2010 layout site collection is: - The RSS Web Part does not support approved RSS sources (roughly translated from the Danish error message) The error we get on the 'pure' 2013 site collection is: - An unexpected error occured when processing your request. See logs for further information and correct the error (roughly translated from the Danish error message) Anyone know what might be the cause of this? 2013 web-part rss share|improve this question asked Aug 29 '14 at 7:40 thewolf 779 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote Have you tried the content query application? If you only want to collect RSS feeds within your site collection this is the only tool of which I know will do the job. Unless you have Kerberos set up. share|improve this answer edited Feb 5 '15 at 14:00 Robert Lindgren♦ 19.2k62951 answered Feb 5 '15 at 13:52 Erik Tellman 167 Hi. It's not much of a problem any