<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Iis on Matt Thornton</title>
    <link>http://localhost:1313/tags/iis/</link>
    <description>Recent content in Iis on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Mar 2012 14:35:11 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/iis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web Service access &#43; internal traffic &#43; 407 Proxy Authentication Required</title>
      <link>http://localhost:1313/tech/web-service-access-internal-traffic-407-proxy-authentication-required/</link>
      <pubDate>Fri, 02 Mar 2012 14:35:11 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/web-service-access-internal-traffic-407-proxy-authentication-required/</guid>
      
        <description>&lt;p&gt;This had me stumped for a while. I was developing a SharePoint-based client to consume a simple web service. I started by writing a console app version of the code before deploying to SharePoint. Fairly straight-forward - added a web reference to my VS2010 project, and used&lt;/p&gt;
&lt;pre&gt;MyWebService srv = new MyWebService();
srv.DoSomething();
&lt;/pre&gt;
&lt;p&gt;Early on in the project, I didn&amp;rsquo;t give much to the fact that when calling the method on the web service, I was given a 407 Proxy Authentication Error. I just setup a simple proxy for it:&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>SSRS error: Operation is not valid due to the current state of the object</title>
      <link>http://localhost:1313/tech/ssrs-error-operation-is-not-valid-due-to-the-current-state-of-the-object/</link>
      <pubDate>Fri, 10 Feb 2012 12:27:50 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/ssrs-error-operation-is-not-valid-due-to-the-current-state-of-the-object/</guid>
      
        <description>&lt;p&gt;If you&amp;rsquo;re using SSRS in SharePoint integrated mode, you may come across this error when using report parameters that have a high number of items in them. A &lt;a href=&#34;http://technet.microsoft.com/en-us/security/bulletin/MS11-100&#34;&gt;recent security bulletin&lt;/a&gt; highlighted some issues and vulnerabilities in ASP.net, and a patch was released to cover some of the items. One of these was the maximum number of items you can have in a collection. If you exceed the limit, then you&amp;rsquo;ll likely get an error like:&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>