search

falc410 / pysimplesoap

Automatically exported from code.google.com/p/pysimplesoap
0 stars 0 forks source link

VS2010 WCF service application can not parsed #85

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
just start a new VS2010 WCF service application

> "C:\Python27\python.exe" -u "D:\Play\soapClient\soapClient.py" 
Importing schema http://tempuri.org/ from 
http://localhost:16115/Service1.svc?xsd=xsd0
Importing schema http://schemas.datacontract.org/2004/07/hellWorld from 
http://localhost:16115/Service1.svc?xsd=xsd2
Importing schema http://schemas.microsoft.com/2003/10/Serialization/ from 
http://localhost:16115/Service1.svc?xsd=xsd1
--------------------------------------------------------------------------------
POST http://localhost:16115/Service1.svc
SOAPAction: "http://tempuri.org/IService1/GetData"
Content-length: 344
Content-type: text/xml; charset="UTF-8"

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Header/>
<soap:Body>
    <GetData xmlns="http://tempuri.org/Imports">
    <value>0</value></GetData>
</soap:Body>
</soap:Envelope>

status: 500
content-length: 734
x-aspnet-version: 4.0.30319
server: ASP.NET Development Server/10.0.0.0
connection: Close
cache-control: private
date: Fri, 02 Nov 2012 06:58:34 GMT
content-type: text/xml; charset=utf-8
<s:Envelope 
xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode 
xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation
/dispatcher">a:InternalServiceFault</faultcode><faultstring 
xml:lang="zh-CN">The server was unable to process the request due to an 
internal error.  For more information about the error, either turn on 
IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from 
the &lt;serviceDebug&gt; configuration behavior) on the server in order to send 
the exception information back to the client, or turn on tracing as per the 
Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace 
logs.</faultstring></s:Fault></s:Body></s:Envelope>
================================================================================
Traceback (most recent call last):
  File "D:\Play\soapClient\soapClient.py", line 22, in <module>
    print client.GetData(0);
  File "C:\Python27\lib\site-packages\pysimplesoap\client.py", line 147, in <lambda>
    return lambda *args, **kwargs: self.wsdl_call(attr,*args,**kwargs)
  File "C:\Python27\lib\site-packages\pysimplesoap\client.py", line 331, in wsdl_call
    response = self.call(method, *params)
  File "C:\Python27\lib\site-packages\pysimplesoap\client.py", line 219, in call
    raise SoapFault(unicode(response.faultcode), unicode(response.faultstring))
pysimplesoap.client.SoapFault: a:InternalServiceFault: The server was unable to 
process the request due to an internal error.  For more information about the 
error, either turn on IncludeExceptionDetailInFaults (either from 
ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on 
the server in order to send the exception information back to the client, or 
turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and 
inspect the server trace logs.

Original issue reported on code.google.com by mymobile...@gmail.com on 2 Nov 2012 at 6:59

GoogleCodeExporter commented 9 years ago 
thanks for the report.

do you have any valid XML request to compare and see where the problem could be?

A working example or documentation could help also.

Original comment by reingart@gmail.com on 2 Nov 2012 at 7:04

GoogleCodeExporter commented 9 years ago 
This looks like an error in the WCF Service.  As the error message indicates, 
can you adjust the 'IncludeExceptionDetailInFaults' or <serviceDebug> 
configuration parameters and provide more detail?

Original comment by donspaul...@gmail.com on 9 Apr 2013 at 3:34

GoogleCodeExporter commented 9 years ago 
recent changes in trunk should solve this issue, so this issue is closed due 
inactivity, if the problem persist, please fill a new issue

Original comment by reingart@gmail.com on 13 Sep 2013 at 3:38