title: "Access is Denied" when consuming a web service over SOAP
body: <p>I have created an .NET 3.5 web service application project that will be hosted under IIS 7.5 on a Windows Server 2008 R2 server.</p>
  
  <p>I am able to consume the service from an ASP.NET application hosted on the same server and other server throughout our network without any issues.  When another employee tries to consumes the service using the SOAP protocol, they receive the following error:</p>
  
  <blockquote>
    <p>XML Parser failed at linenumber 0, lineposition 0, reason is: Access
    is denied.</p>
  </blockquote>
  
  <p>The authentication configuration is set to Integrated Windows Authentication and the consumer will need to provide a service account's credentials when trying to consumer the service.    </p>
  
  <p>Has anyone else experienced this issue and do they know how to resolve it?</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>After speaking with my co-worker and vendor's customer service regarding consuming my web service, they revealed there are limitations within their INVOKE SOAP step.  According to the vendor:</p>
  
  <blockquote>
    <p>The Invoke SOAP object cannot interpret WSDL's containing In/Out
    parameters if the WSDL message definition contains identical part
    names for the input an output messages and identical data types.</p>
  </blockquote>
  
  <p>The web service API contain a method and output parameter that were the same name.  If you look at the web service method in a browser, it had the following structure in the response:</p>
  
  <pre><code>&lt;soap:Body&gt;
      &lt;MyServiceResponse&gt;
          &lt;MyServiceResponse&gt;
              &lt;property&gt;...
  </code></pre>
  
  <p>The question now....Is this a common behavior while using the SOAP protocol or is this just limited to how vendor's product parses the SOAP message?</p>