Databases
StackOverflow2013
Postsdbo
POPowershell: Error consuming WCF services with MTOM message encoding
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPowershell: Error consuming WCF services with MTOM message encoding
    primarykey
    data
    text
    <p>I'm currently exploring powershell capabilities, but I have encountered a problem that I have not been able to solve. Any quick tips would be greatly appreciated =)</p> <p>My goal: Invoke methods from a WCF service (configured with MTOM message encoding) from powershell v2.0 (hopefully using the new-webserviceproxy cmdlet)</p> <p>My problem: the new-webserviceproxy cmdlet cannot parse the service's response correctly when message encoding is set to Mtom. I receive the following error:</p> <p><strong>PowerShell</strong>: </p> <p><code> $proxyObject = New-WebServiceProxy -URI "<a href="http://myserver.com/AccessService.svc?wsdl" rel="noreferrer">http://myserver.com/AccessService.svc?wsdl</a>"<br> $proxyObject.TestWebServiceConnection() </code></p> <blockquote> Exception calling "TestWebServiceConnection" with "0" argument(s): "Client found response content type of 'multipart/related; type="application/xop+xml";start="&lthttp://tempuri.org/0&gt";boundary="uuid: <br/>4001d529-32b9-4560-9f4b-550c35c67b03+id=4";start-info="text/xml"', but expected 'text/xml'. <br/>The request failed with the error message: <br/>-- <br/>--uuid:4001d529-32b9-4560-9f4b-550c35c67b03+id=4 <br/>Content-ID: &lthttp://tempuri.org/0&gt <br/>Content-Transfer-Encoding: 8bit <br/>Content-Type: application/xop+xml;charset=utf-8;type="text/xml" <br/>&lts:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"&gt <br/>&lts:Body&gt <br/>&ltTestWebServiceConnectionResponse xmlns="http://myserver.com/"&gt <br/>&ltTestWebServiceConnectionResult&gtsuccess&lt/TestWebServiceConnectionResult&gt <br/>&lt/TestWebServiceConnectionResponse&gt <br/>&lt/s:Body&gt <br/>&lt/s:Envelope&gt <br/>--uuid:4001d529-32b9-4560-9f4b-550c35c67b03+id=4-- <br/>--." <br/>At line:1 char:38 <br/>+ $proxyObject.TestWebServiceConnection &lt&lt&lt&lt () &gt&gt error.txt <br/> + CategoryInfo : NotSpecified: (:) [], MethodInvocationException <br/> + FullyQualifiedErrorId : DotNetMethodException </blockquote> <p><strong>Note</strong> I am able to consume the WCF service through other clients and even the wcfclient tool provided by Microsoft. You can see that the <strong>TestWebServiceConnectionResult</strong> returned <em>success</em>, but it doesn't seem like the proxy object was able to parse the response. </p> <p><strong>Behavior</strong>:</p> <blockquote> &ltserviceBehaviors&gt <br/> &ltbehavior name="MyServiceBehavior"&gt <br/> &ltserviceThrottling maxConcurrentCalls="100" maxConcurrentSessions="100"/&gt <br/> &ltserviceMetadata httpGetEnabled="true" httpsGetEnabled="false"/&gt <br/> &ltserviceDebug includeExceptionDetailInFaults="false"/&gt <br/> &lt/behavior&gt <br/>&lt/serviceBehaviors&gt </blockquote> <p><strong>Binding</strong>(I've excluded the timeout values/ reader quota and message sizes since the permutations of their values do seem not relevant to my problem):</p> <blockquote> <br/>&ltbasicHttpBinding&gt <br/> &ltbinding name="basicHttpEndpointBinding" messageEncoding="Mtom"&gt <br/> &ltsecurity mode="None"&gt <br/> &lttransport clientCredentialType="None"/&gt <br/> &lt/security&gt <br/>&lt/basicHttpBinding&gt </blockquote> <p><strong>Service</strong> </p> <blockquote> &ltservice behaviorConfiguration="MyServiceBehavior" name="MyService.AccessService"&gt <br/> &ltendpoint address="" binding="basicHttpBinding" bindingConfiguration="basicHttpEndpointBinding" name="basicHttpEndpointAccessService" bindingNamespace="http://myserver.com/" contract="MyService.IAccessService"/&gt <br/> &ltendpoint address="mex" binding="basicHttpBinding" bindingConfiguration="basicHttpEndpointBinding" name="mexEndpointAccess" contract="IMetadataExchange"/&gt <br/>&lt/service&gt </blockquote>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKiquenet
    1. USTung
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPowershell: Error consuming WCF services with MTOM message encoding
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPowershell: Error consuming WCF services with MTOM message encoding
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPowershell: Error consuming WCF services with MTOM message encoding
      1. USAndrew Shepherd
      1. VTFavorite
    1. COAs a test, can you change the service message coding to text and see if it starts working? (This would prove that the MTOM encoding is the source of the problem)
      singulars
      1. POPowershell: Error consuming WCF services with MTOM message encoding
      1. USAndrew Shepherd
    2. COI think the encoding for WCF must be the same when sending and receiving (see http://stackoverflow.com/questions/284149/how-do-i-mix-message-encoding-types-text-mtom-in-the-request-response-of-a-we). New-WebServiceProxy might only use text/xml. You could try creating a wrapper class in .NET that invokes the service, and use that class within PowerShell?
      singulars
      1. POPowershell: Error consuming WCF services with MTOM message encoding
      1. USBob
    3. COBob, I do believe this is the case, but I cannot seem to find any sort of property that would allow me to set the message encoding used by the object returned by this cmdlet. Creating wrapper method in .Net will probably work (just slightly disappointed that there's no way to do this with the already-provided cmdlet). I actually leaning towards writing some functions in powershell to call svcutil on the wsdl, compile the generated proxy class, then specify my own binding (with desired configuration) and endpoints.
      singulars
      1. POPowershell: Error consuming WCF services with MTOM message encoding
      1. USTung
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload