Link to home
Start Free TrialLog in
Avatar of acadenilla
acadenilla

asked on

WCF Error calling service method

hi,

I get the following error when calling method from my client (client.Authenticate)

"The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state."

Note that the WCF service is hosted by a vendor. I have generated the necessary files using svcutil

see code below


using (MailingListClient client = new MailingListClient("WSHttpBinding_IMailingList"))
                {
                    client.Authenticate(accountId, password);     
}

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of p_davis
p_davis

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of acadenilla
acadenilla

ASKER

davis,

You think its in the service side? Unfortunately as stated the service is by a third party vendor.

Though i was able to get in contact with my vendor and they have received my code.

Is there anything i can do with my end to troubleshoot some more?

Thanks

Allan
unfortunately, it all depends on your error logging framework. i imagine if it is implemented it is logged where the service is hosted. but maybe you can call your vendor and see if they have any event logs that could point to the issue. if it is service side and you don't have control over it then there isn't much you can do from the client side.

in my mind it has to be service side related. either you have sent a parameter that doesn't contain the information needed (ie something is null wouldn't it shouldn't be) or the service has a defect in it. otherwise you would be receiving the error on the client side, and not from the service model. and this could be in the method you posted or a method that uses the service before this method.

do you utilize the sendorpostcallback framework?
No, i did not utilize the sendorpostcallback framework.

I agree with you unless i am sending them bad parameters it must be on there side.

Best thing to do right now is wait for there response


good luck. i know how frustrating it is with service issues -- and we control ours. i can't imagine someone else having that control.
I error was from the service side, which comes from a third party. After consulting with them they were able to figure out the issue