How to solve "Connection could not be made because the target machine actively refused it." exception. It's coming when port is get called twice using net.tcp of wcf service.

Question

0.00/5 (No votes)

See more:

<configuration>
<appsettings>
<add key="LCDIP" value="192.168.1.92">
<add key="LCDPort" value="8102">

<system.servicemodel>
<bindings>
<nettcpbinding>
<binding name="NetTcpBinding_FLBServiceProvider" closetimeout="00:01:00">
openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
transactionFlow="false" transferMode="Buffered" transactionProtocol="OleTransactions"
hostNameComparisonMode="StrongWildcard" listenBacklog="10" maxBufferPoolSize="524288"
maxBufferSize="65536" maxConnections="10" maxReceivedMessageSize="65536">
<readerquotas maxdepth="32" maxstringcontentlength="8192" maxarraylength="16384">
maxBytesPerRead="4096" maxNameTableCharCount="16384" />
<reliablesession ordered="true" inactivitytimeout="00:10:00">
enabled="false" />
<security mode="None">
<transport clientcredentialtype="Windows" protectionlevel="EncryptAndSign"> <message clientcredentialtype="Windows">

<client>
<endpoint address="net.tcp://axdesk51:8101/FLBWCFService" binding="netTcpBinding">
bindingConfiguration="NetTcpBinding_FLBServiceProvider" contract="FLBWCFServices.FLBServiceProvider"
name="NetTcpBinding_FLBServiceProvider" />

<startup><supportedruntime version="v2.0.50727" sku="Client">

Posted 20-May-14 1:46am

Nawabpasha

Add a Solution

Comments

Stephen Hewison 20-May-14 8:14am

This is a generic error you often get when working with WCF and has nothing to do with the actually problem. I would enable WCF tracing to investigate further. http://stackoverflow.com/questions/4271517/how-to-turn-on-wcf-tracing

Vedat Ozan Oner 20-May-14 15:30pm

it is not a generic error. it means the endpoint you trying to connect doesn't exist. you said the second trial fails. I think your first call put the service into faulted state. successive calls will fail. therefore, you must have a bug in that method which makes your service faulty.

Nawabpasha 21-May-14 0:27am

thanks for you help , can you help me tofix this issue where it is failing and how to configure end point.

Vedat Ozan Oner 21-May-14 4:00am

you have a bug in your method where your service stops and you have to debug it. I cannot know the solution without any code. I don't think you have an error in your config file since you can reach it at least one call. what I would do is to separate business logic code from service implementation and debug them separately to locate the error more easily.

Nawabpasha 21-May-14 5:49am

Thank you vedat Ozan, sure i will try in this manner

Vedat Ozan Oner 21-May-14 6:55am

you are welcome

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)

Rob Philpott · Answer 1 · 2014-05-20T06:30:00

Solution 1

This isn't anything to do with WCF per se. It simply means that the port you are trying to connect to isn't accepting connections.

Almost always because the service isn't running.

Posted 20-May-14 6:30am

Rob Philpott