none
While calling WCF method from client getting below error message? RRS feed

  • Question

  • Hi,

    Calling WCF method from client, i am getting below error message-

    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.

    Any approach for the same...

    Tuesday, April 2, 2013 10:23 AM

Answers

  • Can you please post some code?

    ViBi

    • Marked as answer by Maggy111 Tuesday, April 2, 2013 2:37 PM
    Tuesday, April 2, 2013 11:21 AM
  • Turn the IncludeExceptionDetailFaults = true in configuration. Make sure to update the service reference in client side.

    Enable tracing to troubleshoot the issue.

    //Traces can be utilised for trouble shooting. Add below //in WCF service configuration and open this trace file //using WCF Trace Viewer.
    
    <system.diagnostics>
      <sources>
          <source name="System.ServiceModel.MessageLogging"
                   switchValue="Information, ActivityTracing, Error">
            <listeners>
                     <add name="messages"
                     type="System.Diagnostics.XmlWriterTraceListener"
                     initializeData="messages.svclog" />
              </listeners>
          </source>
        </sources>
    </system.diagnostics>
    
    
    
      <system.serviceModel>
      
        <diagnostics>
        <messageLogging
             logEntireMessage="true"
             logMalformedMessages="true"
             logMessagesAtServiceLevel="true"
             logMessagesAtTransportLevel="true"
             maxMessagesToLog="3000"
             maxSizeOfMessageToLog="2000"/>
      </diagnostics>


    Apriori algorithm [association rule]

    • Marked as answer by Maggy111 Tuesday, April 2, 2013 2:37 PM
    Tuesday, April 2, 2013 2:05 PM

All replies

  • Can you please post some code?

    ViBi

    • Marked as answer by Maggy111 Tuesday, April 2, 2013 2:37 PM
    Tuesday, April 2, 2013 11:21 AM
  • Turn the IncludeExceptionDetailFaults = true in configuration. Make sure to update the service reference in client side.

    Enable tracing to troubleshoot the issue.

    //Traces can be utilised for trouble shooting. Add below //in WCF service configuration and open this trace file //using WCF Trace Viewer.
    
    <system.diagnostics>
      <sources>
          <source name="System.ServiceModel.MessageLogging"
                   switchValue="Information, ActivityTracing, Error">
            <listeners>
                     <add name="messages"
                     type="System.Diagnostics.XmlWriterTraceListener"
                     initializeData="messages.svclog" />
              </listeners>
          </source>
        </sources>
    </system.diagnostics>
    
    
    
      <system.serviceModel>
      
        <diagnostics>
        <messageLogging
             logEntireMessage="true"
             logMalformedMessages="true"
             logMessagesAtServiceLevel="true"
             logMessagesAtTransportLevel="true"
             maxMessagesToLog="3000"
             maxSizeOfMessageToLog="2000"/>
      </diagnostics>


    Apriori algorithm [association rule]

    • Marked as answer by Maggy111 Tuesday, April 2, 2013 2:37 PM
    Tuesday, April 2, 2013 2:05 PM