Ask a questionAsk a question
 

AnswerWhy do I get InternalServiceFault very often?

  • Thursday, October 08, 2009 8:18 AMSergey Demyanov Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi. 

    I'm using MT SOAP API in my server side application. 
    Last days it fails almost always. Here're are request and response from server: 

    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><Translate xmlns="http://api.microsofttranslator.com/v1/soap.svc"><appId>HIDDEN_APP_ID</appId><text>tes</text><from>en</from><to>ru</to></Translate></s:Body></s:Envelope>

    <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="en-US">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>

    How can I diagnose the issue? Can this be due to a translations limitation of a free account or the response should be more meaning full?

    -Sergey

Answers

  • Friday, October 09, 2009 4:05 AMVikram DendiMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Sergey it is possible that you might have hit the service at the exact time period when we were rolling out a new version. Can you try it again and see if this is still an issue?


    Vikram Dendi, Biz, Product Strategy & UX
    Microsoft Translator

All Replies

  • Friday, October 09, 2009 4:05 AMVikram DendiMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Sergey it is possible that you might have hit the service at the exact time period when we were rolling out a new version. Can you try it again and see if this is still an issue?


    Vikram Dendi, Biz, Product Strategy & UX
    Microsoft Translator