C# the server was unable to process the request due to an internal error.

Question

0.00/5 (No votes)

See more:

I’m consuming a web-service. I’m sending almost 20 requests per a day and receiving the response successfully. however, sometimes the client didn’t receive any response and I’m getting the below error while sending the request, but when I try later for the same request it will be sent successfully.
I checked the web-service and it seems the both requests have been received successfully and the responses also have send to the client without any error.

Quote:
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 SDK documentation and inspect the server trace logs.

Source: mscorlib

Stack Trace:
Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at webService.UploadDocument(UploadDocumentRequest ReqDto)
   Actions.Utilities.SendData(Model model, String& respCode, String& respDesc, Int64& documentNumber) in C:\Actions\Utilities.cs:line 46

What I have tried:

I don’t know what’s the issue exactly

Posted 10-Nov-20 20:51pm

Member 11400686

Updated 10-Nov-20 22:02pm

Add a Solution

Comments

[no name] 11-Nov-20 2:55am

If it's "indeterminate", you build a retry mechanism in your error handling.

Member 11400686 11-Nov-20 2:58am

That’s what I’m doing but I need to figure out what’s the root cause for this issue

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2020-11-10T22:04:00

Quote:
That’s what I’m doing but I need to figure out what’s the root cause for this issue

So read what it says, and do it:

Quote:
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 SDK documentation and inspect the server trace logs.

Without actual information - and we have none, and can get none - nobody can tell what the problem might be.
So step one of debugging applies: gather information! Without it, you have no idea where to start looking.