Hi, I have an valid orchestration that runs when installed on another person's computer but when i install it on mine I get
An I/O exception occurred during the post operation: Connection refused : connect. I have looked and the port 80 is not listening. In fact I don't even see it when I run netstat command. I am running Cast Iron version 184.108.40.206 with windows 7 operating system. The person whose installed it is running with windows XP.
I even tried stopping Symantec Endpoint protection but still no result
Hoping someone has seen this and knows how to fix or at least knows how to get port 80 to listen.
This topic has been locked.
2 replies Latest Post - 2012-04-26T19:18:59Z by SystemAdmin
Pinned topic Receive error message Connection refused :connect error during post operati
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-04-26T19:18:59Z at 2012-04-26T19:18:59Z by SystemAdmin
Sathya400 2700057BXV13 PostsACCEPTED ANSWER
Re: Receive error message Connection refused :connect error during post operati2012-04-21T20:12:39Z in response to SystemAdminDid any one got solutions for this issue.? I am trying to test my 1st orchestrations which has DB asset thru studio Orchestrations-->Run Orchestrations and then Tools-->HTTP Post Utility.
I keep getting either one of this error below..
An I/O Exception encountered during the post operation: Software caused connection abort: socket write error
An I/O Exception encountered during the post operation: Connection reset by peer: socket write error
I know this is some basic tweak do with connections. Can some on help please.
SystemAdmin 110000D4XK1250 PostsACCEPTED ANSWER
Re: Receive error message Connection refused :connect error during post operati2012-04-26T19:18:59Z in response to SystemAdminCan you see if you are getting any exception in the studio error.log? This file is located typically in the installation directory. Something like "C:\Program Files\Cast Iron Systems\Cast Iron Studio 220.127.116.11\error.log"
Did you try configuring the orchestration to listen on another port say 8080?