wcf exception occur in client side

Question

1.00/5 (1 vote)

See more:

following exception occur

C++

An exception of type 'System.Reflection.TargetInvocationExcep… occurred in System.ni.dll but was not handled in user code

client side

C#

private void TrackLocation_Click(object sender, RoutedEventArgs e)
{
ServiceReference1.GetPositionClient client = new ServiceReference1.GetPositionClient();

client.getData1Completed += new EventHandler<servicereference1.getdata1c…>
client.getData1Async(11.1,11.1);

}

void client_getData1Completed(object sender, ServiceReference1.getData1CompletedEvent… e)
{
LongitudeTextBlock.Text = e.Result;
}

server side

C#

public class GetPosition : IGetPosition
{
public string getData1(double lat,double lon)
{ return "updated sucessfully"; }
}

Posted 8-Sep-13 0:33am

zohaib khan niazi

Updated 8-Sep-13 0:53am

André Kraak

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 8-Sep-13 11:42am

This is by far not a comprehensive exception information. It also has message, stack trace, inner exception, parameters, and sometimes exception-type specific information. Did you find out in what line? Used the debugger?
—SA

zohaib khan niazi 8-Sep-13 18:32pm

thnx for quick rply
call trace:
> PhoneApp11.DLL!PhoneApp11.ServiceReference1.GetPositionClient.GetPositionClientChannel.EndgetData1(System.IAsyncResult result) Line 253 C#

public string EndgetData1(System.IAsyncResult result) {
object[] _args = new object[0];
string _result = ((string)(base.EndInvoke("getData1", _args, result)));//exception occur in this line
return _result;
}

Sergey Alexandrovich Kryukov 9-Sep-13 0:54am

Thank you for additional information, but...

What is "call trace"? I mention exception stack trace, which is a path of the propagation of the exception on the stack, which is itself a stack of points in the call stack, with lines of the source code indicating lines where the exception propagates. Please see Exception.StackTrace property, which is just a string. Exception message and other properties are also important...

—SA

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)

Nitin Singh India · Answer 1 · 2013-09-08T21:29:00

It seems that the exception is in the wiring of the service reference. If the service side throws any error and its not getting passed to thec client, you need to put

C#

includeExceptionDetailsInFaults = true

for the serviceDebug attribute in server side configuration.

I believe that the service atleast gets hit by the client. However, to debug this scenario, try to load your service through browser and manually hit the method. If it returns fine, then the issue is in client side configuration. By including this attribute, you can be more clear about what's happening.

Also update your service reference once so that you are sure that you have a latest copy of wsdl just in case you updated the service after creating the service reference.

Once you get the actual stack trace, identify the points where it shows about the application (ignore the framework lines) and the post those.