Hello,
Upgraded to v8.2.8 and was getting connection error "Invalid address (error code is 96260)" on SSH task. Went in and changed my hostname to the FQDN ( SRV001 --> SRV001.my.host.name.com) and it worked properly. Not sure if that is as intended but it may be worth checking. I have not done any substantial testing to test across my other VisualCron servers. This does not occur on my production servers on v8.2.2.

Thanks,

Thanks for the report. We heard similar from another customer using SMTP Task. We have upgrade a component for these two and it seems to produce this error. We have reached out to the vendor now for answers.

---

Any response to this? I have upgraded our UAT server to 8.2.8 (from 8.2.3) and we're now also getting the same error...

Exception in Task: SBSocket.EElSocketError: Invalid address (error code is 96260)
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.MDEKAJKIMOLGBKMCCEEANLMMGLNFDIFNOHOC.Run() in C:\sourcefiles\code\VisualCronService\Jobs\TaskProcesses\Net\clsProcessTaskSSH.vb:line 25

*edit*: Changing the server name to the FQDN fixes the issue. Just wondering if this will be the fix going forward, or if the internal component will be fixed to allow regular server names

Any response to this? I have upgraded our UAT server to 8.2.8 (from 8.2.3) and we're now also getting the same error...

Exception in Task: SBSocket.EElSocketError: Invalid address (error code is 96260)
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.MDEKAJKIMOLGBKMCCEEANLMMGLNFDIFNOHOC.Run() in C:\sourcefiles\code\VisualCronService\Jobs\TaskProcesses\Net\clsProcessTaskSSH.vb:line 25

*edit*: Changing the server name to the FQDN fixes the issue. Just wondering if this will be the fix going forward, or if the internal component will be fixed to allow regular server names

We will fix this for the next build. For now use IP or FQDN.

---

Please let us know if it works better in this build:

https://www.visualcron.c....aspx?g=posts&t=7498 

---