Sign in
Microsoft.com
 
SharePoint Products TechCenter
 
 
 
SharePoint Products TechCenter > SharePoint Products and Technologies Forums > SharePoint - Setup, Upgrade, Administration and Operation > RSS from a MOSS list will not render. "ProtocolError occured trying to complete the request."
Ask a questionAsk a question
Search Forums:
 

AnswerRSS from a MOSS list will not render. "ProtocolError occured trying to complete the request."

  • Monday, November 02, 2009 3:53 PMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,


    My MOSS install has been migrated to a new datacenter.

    After the migration an RSS web part no longer works. Instead of rendering the content which is from a MOSS wiki on the same install it now displays this error:

    "ProtocolError occured trying to complete the request. The server returned a status code of : InternalServerError and the status description is : "Unknown Host""

    Steps tried:

    Making sure the RSS feed works in IE - yes it does
    Making sure that the web.config has the proxy added - yes it does
    Replicating the error on a test site on the same install - yes it raises the same error

    I have been reading blogs all day about this and they all just mention adding the proxy to web.config - i've done this.

    I am using:

    Software = MOSS standard + Windows Server 2003 R2 Standard x64 with SP2
    Hardware = Xeon 3.0 GHz - 3.75GB RAM

    What else can I try to resolve this?


    Thanks,


    Steve



    • Edited byMike Walsh MVPMVP, ModeratorMonday, November 02, 2009 5:02 PM" " around the error code's text. No need for Error: prefix.
    • Edited byMike Walsh MVPMVP, ModeratorMonday, November 02, 2009 5:01 PMNo need to quote the entire error message in the Title. Far too long title results.
    •  
     

Answers

  • Tuesday, November 10, 2009 4:03 PMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi John,



    Thanks for your question.

    Yes I did manage to get this one resolved...

    The problem was being caused by the local proxy - so adding this:

         <bypasslist>
           <add address="haysnet.hays.loc" />
         </bypasslist>

    To both web.config files referenced by IIS on both web front ends so resulting in this system.net node:

    <system.net>
        <defaultProxy>
          <proxy usesystemdefault="false" proxyaddress="http://10.173.10.6:8080" bypassonlocal="true" />
         <bypasslist>
           <add address="haysnet.hays.loc" />
         </bypasslist>
    </defaultProxy>
    </system.net>

    Was the final resolution!

    :)


     

All Replies

  • Monday, November 02, 2009 4:59 PMJohn Timney Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    If you have moved to another datacentre, and it worked before the move its more likely to be a problem in the way your requests are being routed back into the MOSS service - more likely a comms issue so check your network settings on the server(s) for primary DNS.

    As a trial, log in to the server and request the RSS URL from IE using localhost and then the URL and see what happens.  It sounds like a local loopback problem as described here http://support.microsoft.com/default.aspx?scid=kb;EN-US;896861 
    but there isn't a lot of reason why that would suddenly start to happen other than probably DNS changes.

    Regards

    John Timney
    • Edited byJohn Timney Monday, November 02, 2009 5:00 PMtypos corrected
    •  
     
  • Tuesday, November 03, 2009 9:35 AMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks for your feedback John - much appreciated - amazed you have time to answer here with everything else you do!

     
  • Tuesday, November 03, 2009 9:37 AMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks Mike W. for your comments too!
     
  • Tuesday, November 03, 2009 3:32 PMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi John,


    I have checked primary DNS between the old and the new servers - they are different so i added the old primary dns to the new server - same error...

    I do not think using localhost in the url to access the RSS feed while on the server will work as http://localhost renders an "Under Construction" standard IIS error (possibly because this is what happens when you browse the default web site in IIS)

    I have added all variations to the local hosts file - using the loopback IP and the actual IP for the WFE...I have also installed the fix mentioned on the link above...

    The same error remains...any ideas please? DNS changes sound plausible but how can i test this? I thought this is what the local hosts file was for - well if it is i have added the IP mappings to it....so why does that not allow the web part to render...?

    This did work on the old environment in London but not in the new datacenter in Manchester...

    Thanks in advance to anyone who has time to reply.


    Thanks,

    Steve


     
  • Tuesday, November 03, 2009 11:55 PMJohn Timney Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Localhost entries should get round any DNS errors between the webpart and the RSS feed being requested.  If you've not changed your sharepoint instance, logic suggests it is likely to be a network problem.

    I've seen this when network changes enabled V6 IP addresses when they were not enabled before, but I've only seen it surface on 2008, not 2003.  You could try to disable V6 addresses in TCP/IP, then run an IISreset.  Theres another cause of this I am vagually aware of, but I'll need to dig it out from some old documentation and if it looks helpful I'll post it here.

    Regards

    John Timney
     
  • Wednesday, November 04, 2009 9:26 AMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Thanks very much for your reply John - I'll check what you say and report back.

     
  • Wednesday, November 04, 2009 10:10 AMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi John,


    I just checked and V6 IP addresses are not being used - thanks again for the tip.

    Oh and it is definitely a network issue - but what issue and what is the fix/workaround is what I am trying to find out...

    I was wondering if the DNS name servers in the old environment and the new one were not synchronised....or at least the new one might be missing a key record...

    Hmmm....
     
  • Monday, November 09, 2009 11:20 PMJohn Timney Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Any luck Steve?

    Regards

    John Timney
     
  • Tuesday, November 10, 2009 4:03 PMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi John,



    Thanks for your question.

    Yes I did manage to get this one resolved...

    The problem was being caused by the local proxy - so adding this:

         <bypasslist>
           <add address="haysnet.hays.loc" />
         </bypasslist>

    To both web.config files referenced by IIS on both web front ends so resulting in this system.net node:

    <system.net>
        <defaultProxy>
          <proxy usesystemdefault="false" proxyaddress="http://10.173.10.6:8080" bypassonlocal="true" />
         <bypasslist>
           <add address="haysnet.hays.loc" />
         </bypasslist>
    </defaultProxy>
    </system.net>

    Was the final resolution!

    :)


     
  • Tuesday, November 10, 2009 8:10 PMJohn Timney Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    DOH!  You started the thread by saying you'd already done the proxy fix.

    Glad you have it sorted.  Coffee is on you then old chap (beer I mean really!!).

    Regards

    John Timney
     
  • Thursday, November 12, 2009 10:59 AMSteve Howlett Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    :)

    Yes I did didn't I? However I thought initially that this was enough proxy info in the web.config:

    <system.net>
        <defaultProxy>
          <proxy usesystemdefault="false" proxyaddress="http://10.173.10.6:8080" bypassonlocal="true" />
    </defaultProxy>
    </system.net>

    My incorrect assumption was that if there is a proxy in sharepoint's web.config then sharepoint would automatically not route internal RSS via the proxy!

    So I thought I had done all the proxy bits to the web.config - only later did i realise that this was incorrect and so added this:

         <bypasslist>
           <add address="haysnet.hays.loc" />
         </bypasslist>

    So explicitly telling sharepoint not to route internal RSS via a proxy...All this makes me wonder why you would want internal RSS to route via a proxy...any idea? I guess there must be a scenario where this is a good idea...


    But sure no problem I can buy you beer! :)

     

    Thanks,

    Steve