Databases
StackOverflow2013
Postsdbo
PODebugging WCF Web Service Faults
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODebugging WCF Web Service Faults
    primarykey
    data
    text
    <p>I am trying to debug a web service exception. I have both the client and the service running in debug mode in Visual Studio 2010, C#, .net 4.0 framework.</p> <p>When I run the client, and get it to call the web service, I get an exception:</p> <blockquote> <p><strong>Type:</strong> System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]] <strong>Error Message:</strong> The type initializer for 'myService.Service' threw an exception.<br> <strong>Source:</strong> mscorlib</p> </blockquote> <p>However, the service shows no exceptions whatsoever.</p> <p>The stack trace that I got seems to indicate that the call was made, and the reply was being handled (even if the reply was an exception):</p> <blockquote> <p>Server stack trace: <br><br> at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)<br><br> at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc&amp; rpc) <br><br> at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) <br><br> at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)<br><br> at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)</p> </blockquote> <p>Can someone give pointers on what else I need to do to debug this?</p> <p>I'm currently setting up the <a href="http://msdn.microsoft.com/en-us/library/ms732023.aspx" rel="nofollow">Service Trace Viewer</a> tool to see if that will tell me anything more.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USPeter K.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODebugging WCF Web Service Faults
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODebugging WCF Web Service Faults
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe trace viewer would help you. There seems to be some configuration issue. It could be as simple as mis-spelled service name in the web.config.
      singulars
      1. PODebugging WCF Web Service Faults
      1. USamit_g
    2. COWhat binding are you using? If it's an http supported binding, try to navigate to the URL it's being hosted at locally in your browser to see if that succeeds. Usually if it doesn't, it's a configuration setting problem.
      singulars
      1. PODebugging WCF Web Service Faults
      1. USJustin Skiles
    3. CO@jskiles: That's part of the problem. It's browser-navigable quite happily, so *most* of the configuration is fine.
      singulars
      1. PODebugging WCF Web Service Faults
      1. USPeter K.
 

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