Geek Answers Handbook

WCF "Server did not give a meaningful answer"

I have no ideas, so I hope someone can help. Here is what I have:

  • WCF service that has only the basicHttpBinding endpoint.
  • There is only a service interface, all other [DataMember], [FaultContract] are concrete types.
  • When I launch it directly from Visual Studio (using the WCF test client or my own application), everything works (I send a request and get a response). This usually takes a second or two.
  • I published it on IIS 6 server.
  • Can I successfully open http: //server/WebService/WebService.svc? WSDL
  • I can successfully open http: //server/WebService/WebService.svc/mex (same output as above)
  • WCF Validation Client and My User Application Can Add Service Link Successfully
  • Whenever I try to call a service method, it waits for about 15 seconds and I get a terrible error "without a meaningful answer."
  • I launched Fiddler and I got a result of 202, which will seem to be successful.
  • It does not return more than 65536 bytes.
  • It returns an array, but it is small
  • I tried remote debugging but can't get this to work, possibly due to a firewall (but port 80 is open, I can get WSDL)
  • I have included system.diagnostics, nothing.
  • I have an IErrorHandler that usually logs things, nothing.

Here's the endpoint configuration:

<endpoint address="" binding="basicHttpBinding" contract="Enterprise.IMyService" bindingNamespace="http://ourdomain.com/MyService/"> <identity> <dns value="localhost" /> </identity> </endpoint>

Anything else I can try? This is probably a simple setup, but I can't figure it out.

Edit:

Raw response script:

 HTTP/1.1 202 Accepted Date: Thu, 15 Apr 2010 19:02:45 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Length: 0
+3
source share
1 answer

I get it! This had nothing to do with WCF. When I moved it to the server, the database connection string ceased to be valid. The error logging configuration (for email) also ceased to be valid and used an exception. It took 15 seconds to answer, because the time during which the SQL server connection took time.

+1
source

More articles:


All Articles