Changes for far in this version:

[FEATURE] WebClient: Mixed new features
[FEATURE] Server: Email Task->Added communication log to output when using Task debugging
[FEATURE] Client/Server: New Trigger->Network change
[FEATURE] Client/Server: Email Trigger->Added optional forwarding
[FEATURE] Client/Server: Task CPU affinity->CPU usage on each Task can now be controlled through main settings of Task->Set affinity
[FEATURE] Client: Triggers->Added optional "auto description"
[FEATURE] Client: Connections->Added filtering
[FEATURE] Client/Server: File Trigger->Added folder exclusing mask
[FEATURE] Client/Server: Web service Task->Added security protocol selection
[FEATURE] Client/Server: Sharepoint Tasks->Added security protocol selection in the Connection
[FEATURE] Client/Server: Robot Task->Many improvements and new actions
[BUGFIX] Server: External DB logging fixes
[BUGFIX] Client: Fixed issue with Test Job button
[BUGFIX] Server: Box->Fixed download issue
[BUGFIX] Server: Archive - Compress->Fixed issue with compressing folders
[BUGFIX] Server: Execute Task->Fixed a potential problem when checking if process is already running
[BUGFIX] Server: MFT Trigger->Fixed issue with MFT Trigger not Triggering in some situations
[BUGFIX] API: Fixed an issue with Trigger result Variables
[BUGFIX] Client/Server: Sharepoint Tasks->Fixed various listing and download issues
[BUGFIX] Server: Slack Trigger->Fixed Text equals Condition
[BUGFIX] API: Fixed issue with Count occurencies Variable
[BUGFIX] Client: Fixed a problem with adding/cloning Default flows
[BUGFIX] Server: PGP Tasks->Fixed Variable problem in password fields
[BUGFIX] Client: SAP->Fixed problem adding multiple steps of the same kind
[BUGFIX] Server: FTP Task->Fixed problem with deleting temp files (copy/move)
[BUGFIX] Server: FTP Task->Fixed problem with uploading locked files
[BUGFIX] Client: SQL Explorer->Fixed a problem showing tables for som MySQL versions
[BUGFIX] Server: Archive compress/decompress: Fixed issue aborting Task
[BUGFIX] Server: Web service API->Fixed certificate issue
[BUGFIX] Server: Slack - Send message: Fixed support for multi line
[BUGFIX] Server: MFT->Fixed issue with transferring 0 byte files
[BUGFIX] Server: Email Tasks->Fixed issues with date condition
[BUGFIX] Server: .NET Execute Task->Fixed problem stopping the Task
[BUGFIX] Client: Failed Jobs->Fixed "days back issue"
[BUGFIX] Client: Event log->Fixed wrong server name issue when connected to multiple machines
[BUGFIX] Server: REST API->Fixed issue with text output in REST API in some scenarios

---

External DB Logging (Create Tables) still Greyed out when trying to Log to External SQL DB.

External DB Logging (Create Tables) still Greyed out when trying to Log to External SQL DB.

Can you attach a screenshot of the whole window?

---

External DB Logging (Create Tables) still Greyed out when trying to Log to External SQL DB.

Can you attach a screenshot of the whole window?

With or without credentials, still greyed out.

We just upgraded in DEV to resolve the folder archive issue and we are now having a problem where the client no longer remotely connects to the server. It works locally and through the web interface but not the client.

External DB Logging (Create Tables) still Greyed out when trying to Log to External SQL DB.

Can you attach a screenshot of the whole window?

With or without credentials, still greyed out.

Did you try the latest build? Is the Test button working on Connection? You might need a Credential if you use Integrated auth.

---

We just upgraded in DEV to resolve the folder archive issue and we are now having a problem where the client no longer remotely connects to the server. It works locally and through the web interface but not the client.

Can you telnet both locally on the machine and remote machine to port 16444?

---

We just upgraded in DEV to resolve the folder archive issue and we are now having a problem where the client no longer remotely connects to the server. It works locally and through the web interface but not the client.

Can you telnet both locally on the machine and remote machine to port 16444?

Successful in both instances. Appears not to be any kind of firewall issue. This was working previous to the 8.3.7 upgrade.

We just upgraded in DEV to resolve the folder archive issue and we are now having a problem where the client no longer remotely connects to the server. It works locally and through the web interface but not the client.

Can you telnet both locally on the machine and remote machine to port 16444?

Successful in both instances. Appears not to be any kind of firewall issue. This was working previous to the 8.3.7 upgrade.

It does not make sense if you can telnet from both client machine and server machine. What error do you get then?

---

We just upgraded in DEV to resolve the folder archive issue and we are now having a problem where the client no longer remotely connects to the server. It works locally and through the web interface but not the client.

Can you telnet both locally on the machine and remote machine to port 16444?

Successful in both instances. Appears not to be any kind of firewall issue. This was working previous to the 8.3.7 upgrade.

It does not make sense if you can telnet from both client machine and server machine. What error do you get then?

We get the connection failed dialog.

Hi

Minor bug in the "failed job" view. It always shows all failed jobs, even if you want
it to only show 1 Day back.



No biggie 😄

We just upgraded in DEV to resolve the folder archive issue and we are now having a problem where the client no longer remotely connects to the server. It works locally and through the web interface but not the client.

Can you telnet both locally on the machine and remote machine to port 16444?

Successful in both instances. Appears not to be any kind of firewall issue. This was working previous to the 8.3.7 upgrade.

It does not make sense if you can telnet from both client machine and server machine. What error do you get then?

We get the connection failed dialog.

What about telnet locally and remotely?

---

As previously noted, Telnet worked both locally and remotely.

As previously noted, Telnet worked both locally and remotely.

Please confirm again that you can write:

telnet remotehostname 16444

---

For the 3rd time - telnetting to that socket results in a successful connect.

For the 3rd time - telnetting to that socket results in a successful connect.

I think we need to do a screen share to see this in action. We have noticed that some has hardened security on their servers so .NET 4.7.1 might need to be installed. Please try that. After trying that please send email to support@visualcron.com so we can schedule a screen share.

---

No change after installing 4.7.1

I can confirm we are experiencing the same issue with 8.3.7.

Hi

Minor bug in the "failed job" view. It always shows all failed jobs, even if you want
it to only show 1 Day back.



No biggie 😄

It would seem that it is now longer possible to view the Job histor or Task History in version 8.3.7. The Date and Get buttons are greyed out.

Issue with wrong host reference in the events window.
It is reporting the last connected host instead of the host that the job is located at.
attached screenshot.

It would seem that it is now longer possible to view the Job histor or Task History in version 8.3.7. The Date and Get buttons are greyed out.

Please try again now. We are doing some changes to support External databases better which affects internal database.

---

Issue with wrong host reference in the events window.
It is reporting the last connected host instead of the host that the job is located at.
attached screenshot.

Thanks for the report - please test the latest build.

---

Hi,

Is there and estimation of when the new version of cron comes out? we would like to use the external database logging which in 8.3.6 does not work....

Thanks,
Bas

Hi,

Is there and estimation of when the new version of cron comes out? we would like to use the external database logging which in 8.3.6 does not work....

Thanks,
Bas

Thanks, it was released today.

---

Hi

When upgrading from 8.3.6 to 8.4.0 out SSH connection failed. It's a simple echo command for renewing a Kerberos ticket on a Linux server. We used to have the servername in the adress field, eg NJ-XXX. This failed with the message 'invalid address'. When we changed with the ip adress in the address field, it worked again. Do you know of any changes that would lead to this?