The following changes has been made so far:

[FEATURE] Client/Server: SSIS Task->Added support for MSSQL 2014 SSIS package execution
[FEATURE] Client/Server: Added Task->Amazon EC2 - Create snapshot
[FEATURE] Client/Server: Added Task->Amazon EC2 - List snapshots
[FEATURE] Client/Server: Added Task->Amazon EC2 - Delete snapshot
[FEATURE] Client/Server: Added Task->Amazon EC2 - List addresses
[FEATURE] Client/Server: Added Task->Amazon EC2 - List key pairs
[FEATURE] Client/Server: Added Task->Amazon EC2 - List security groups
[FEATURE] Client/Server: Added Task->Amazon EC2 - List volumes
[FEATURE] Client/Server: Added Task->Amazon EC2 - Reboot instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - Start instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - Stop instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - Terminate instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - List instances
[BUGFIX] Client/Server: Popup Task->Fixed input handling problem with radio boxes
[BUGFIX] Server: Fixed a problem with renaming strings which could come up in different Task types
[BUGFIX] Server: Dynamics CRM general->Fixed a general returning description for some entity types
[BUGFIX] API: Fixed issue with Adding/Updating Job Variables
[BUGFIX] Client: Loops->Fixed resizing error in window
[BUGFIX] Server: Email Task/Notification->Fixed error "User authentication failed: No SASL mechanisms supported by both the client and the server (error code is 0)"
[BUGFIX] Client: Desktop Macro Task->Fixed a problem which could occur when saving the macro
[BUGFIX] Server: Fixed a small database cleanup issue
[BUGFIX] Server: FTP Task->Fixed Copy/Move files sub folders issue

---

Hi Henrik,

You should be getting some client crash emails from me, please let me know if they don't come through with the details you need.

Haven't been able to correlate to a particular client action from me, seems to occur even in an idle client.

This seems to occur also in 7.2.0 Released (Current Testing is on the 7.2.1 Beta).

I have not observed this behaviour in the 7.1.9 Client.

Hi Henrik,

You should be getting some client crash emails from me, please let me know if they don't come through with the details you need.

Haven't been able to correlate to a particular client action from me, seems to occur even in an idle client.

This seems to occur also in 7.2.0 Released (Current Testing is on the 7.2.1 Beta).

I have not observed this behaviour in the 7.1.9 Client.

Is Client and Server of same version?

---

New build, changes:

[BUGFIX] Server->Dynamis CRM general->Fixed a general returning description for some entity types
[BUGFIX] API->Fixed issue with Adding/Updating Job Variables

---

Hi Henrik,

Not always.

Client has been either 7.2.0 Released or 7.2.1 Beta
Initial Testing has matching Client and Server Versions.
Servers (Production) are 7.1.6.

So Test is aligned (Client and Server) but we also test against our production version, as long as the Protocol is compatible.

As we have discussed previously, deploying across a number of servers when the protocol changes enforces a much more compressed schedule of rollout.

Both are listed Protocol 7.0.0 ? but perhaps there is an inconsistency here ?

We are intending to upgrade servers soon, perhaps sooner than we think !

Thanks

Kevin

Hi Henrik,

Not always.

Client has been either 7.2.0 Released or 7.2.1 Beta
Initial Testing has matching Client and Server Versions.
Servers (Production) are 7.1.6.

So Test is aligned (Client and Server) but we also test against our production version, as long as the Protocol is compatible.

As we have discussed previously, deploying across a number of servers when the protocol changes enforces a much more compressed schedule of rollout.

Both are listed Protocol 7.0.0 ? but perhaps there is an inconsistency here ?

We are intending to upgrade servers soon, perhaps sooner than we think !

Thanks

Kevin

Normally there should not be a problem. We really try to be backwards compatible but sometimes we need to cleanup/change some things.

---

New build, changes:

[BUGFIX] Client->Loops->Fixed resizing error in window
[BUGFIX] Server->Email Task/Notification->Fixed error "User authentication failed: No SASL mechanisms supported by both the client and the server (error code is 0)"

---

New build, changes:

[FEATURE] Client/Server: SSIS Task->Added support for MSSQL 2014 SSIS package execution

---

Hi Henrik,

Thanks for that, and appreciate your efforts on keeping the Protocol changes down.

Its *really* helpful if the Protocol changes that you let us know, preferably in the Beta Log of changes as you have done in the past, and in the Protocol Number.

The ones that matter here are not extensions for new tasks, but changes to existing tasks of course . . .

i.e. 7.0.0 Beta

"[NOTE] Client/Server: Protocol has been updated - server and client needs to be on same version 7.0.0"

If the protocol changes then the impact analysis, testing , and the deployment change. . . .

We were intending to deploy 7.2.0 but pulled out when we hit issues with the new clients talking to the existing Protocol 7.0.0 servers . . . . . with unchanged Jobs and Tasks.

Now we *know* we will look to deploy 7.2.1 client and server once released as sets and manage the transition.

So we had no issues with 7.0.0 - 7.1.9 with <our Jobs> . . . . so 7.2.0 and 7.2.1 are using a revised <7.2.0 ?> Protocol

As a side issue, a solution to having a single PC easily talk to multiple server versions (either a fancier client that supports multiple protocols, or clear instructions & support for running multiple clients on the same PC during transition) is still something that would be helpful when this happens.

http://www.visualcron.co...sts&t=3297#post15769 

New build, changes:

[BUGFIX] Client: Desktop Macro Task->Fixed a problem which could occur when saving the macro

---

New build, changes:


[FEATURE] Client/Server: Added Task->Amazon EC2 - Create snapshot
[FEATURE] Client/Server: Added Task->Amazon EC2 - List snap shots
[FEATURE] Client/Server: Added Task->Amazon EC2 - List addresses
[FEATURE] Client/Server: Added Task->Amazon EC2 - List key pairs
[FEATURE] Client/Server: Added Task->Amazon EC2 - List security groups
[FEATURE] Client/Server: Added Task->Amazon EC2 - List volumes
[FEATURE] Client/Server: Added Task->Amazon EC2 - Reboot instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - Start instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - Stop instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - Terminate instance
[FEATURE] Client/Server: Added Task->Amazon EC2 - List instances
[BUGFIX] Server: Fixed a small database cleanup issue
[BUGFIX] Server: FTP Task->Fixed Copy/Move files sub folders issue

---

New build, changes:

[FEATURE] Client/Server: Added Task->Amazon EC2 - Delete snapshot

---

7.2.1 was released officially today. Thank you for your testing.

---

Hi

The new version caused a failure in one of our ftp download jobs. The job downloads a zip file over port 21. After we upgraded to 7.2.1 the taks fails with the following error:



Exception in Task: Unaccepted server reply (error code is 426)
Error (5) downloading file(s): stamdata.zip, err: Unaccepted server reply (error code is 426) (426 Connection closed; transfer aborted. Transferred 835,584 bytes in 83 seconds. 9KB/second.
), error code: 426
Exception in Task: No file(s) downloaded


There is a file there, and the connection works. I tried downloading using FileZilla and it went fine. After rolling back to 7.2.0, everything worked as it should.


Thomas

Hi

The new version caused a failure in one of our ftp download jobs. The job downloads a zip file over port 21. After we upgraded to 7.2.1 the taks fails with the following error:



Exception in Task: Unaccepted server reply (error code is 426)
Error (5) downloading file(s): stamdata.zip, err: Unaccepted server reply (error code is 426) (426 Connection closed; transfer aborted. Transferred 835,584 bytes in 83 seconds. 9KB/second.
), error code: 426
Exception in Task: No file(s) downloaded


There is a file there, and the connection works. I tried downloading using FileZilla and it went fine. After rolling back to 7.2.0, everything worked as it should.


Thomas

We have contacted you through email. Please setup up 7.2.1 on other computer and we will help testing why this happens.

---