Last post Jan 22, 2020 04:54 AM by carlhyde
Jan 28, 2016 09:47 PM|sapator|LINK
But the issue here is that I am using a post request trough an WCF app.
This will work fine on my home PC call(web form - web app) - from the work PC call.
It will not work from the WCF service I use that uses LOCAL IIS 7 or my work PC (that an app I created works fine through my local PC).
So I tried various IIS manipulations, made it iis express, made it visual studio IIS, made it local IIS, made it https, http, nada.
When debugging the code and it goes to the getrequest - from site line, it will break.
What is going on here? Is it the IIS? The wcf works flawlessly on about 20.000 lines of code but the post call to another vendor will break.
Jan 29, 2016 08:39 AM|Zhi Lv - MSFT|LINK
No connection could be made because the target machine actively refused it
As for this issue, I suggest you check the firewall settings, unblock the port to see if this solve the issue. Perhaps the port is blocked by the windows firewall.
Besides, here are some relevant threads with the same problem, you could refer to them:
Jan 29, 2016 03:46 PM|sapator|LINK
Will read an see if i can sort something out.
I have 2 quyestions if you may.
1)The connection error can be thrown from the WCF service I am creating or only from the calling web service?
Meaning, if I block my own port, there may be a message saying that the other web service I am calling is refusing the connection but it is actually my closed port, firewall etc that is causing the issue?
2)I've read about myServiceHost.Open() on an answer given. However this is not a web application but a WCF servce, so I do not see a
myServiceHost.Open() event somewhere.
Or do I need to implement it myself?
Jan 30, 2016 04:41 PM|sapator|LINK
OK ,just confirmed that this is not a WCF problem.
I created a web application and i tried to call the web service from the IIS and I got the same error.
The service will run fine if I use the Visual Studio server that opens a random port.
Feb 02, 2016 02:21 AM|lextm|LINK
The error message can be caused by a few factors, so as you noticed you need to do further digging.
One possible approach (if that service you post to does not require HTTPS) is to utilize a network capture tool such as Wireshark to analyze the packets. That can easily tell the TCP/HTTP conversation and how it closes.
Feb 03, 2016 01:52 PM|sapator|LINK
Thanks for the answer.
I was talking to our administrator and next week I will be at the office so I can do further test there.
Will post for further issues.
Jan 22, 2020 04:54 AM|carlhyde|LINK
This error is a network-related error occurred while establishing a connection to the Server. It means that the error is occurring because there is no server listening at the
hostname and port you assigned. It literally means that the machine exists but that it has no services listening on the
specified port .
Generally, it happens that something is preventing a connection to the port or hostname. Either there is a
firewall blocking the connection or the process that is hosting the service is
not listening on that specific port. This may be because it is not running at all or because it is listening on a different port. More...no connection