[FEATURE] Client: Added filter above the main grid for easier accessibility. Added filter options Exit code, Result and Status as well which lets you filter on failed Jobs for example.

👍 This is very nice!

😊 If you use the task filter in combination with the job filter, jobs can be shown with empty tasks, shouldn't those jobs be hidden to make a better overview?

Regards,
Erik

Unfortunately it is impossible as it is now to hide the parent.

By the way, did you look at the real time Job history log?

---

Hi,

I looked at the realtime log and I like it. Nice addition indeed.

Not showing the matched jobs is working when I use the job filter, but I uderstand now this is not possible as you say.
But if you know the task, you know the parent and there are properties to hide the job right? Or am I missing something?

I do like the filter here. It is what we discussed before and this will increase finding the right job/task.

Regards
Erik

---

Hi,

I looked at the realtime log and I like it. Nice addition indeed.

Not showing the matched jobs is working when I use the job filter, but I uderstand now this is not possible as you say.
But if you know the task, you know the parent and there are properties to hide the job right? Or am I missing something?

I do like the filter here. It is what we discussed before and this will increase finding the right job/task.

Regards
Erik

We think it is important to see the parent Job if you search for a Task. I guess this opinion might differ between users.

Edit: I see know that it is possible to hide that Jobs band. But still I am not sure if it is right.

---

Version updated. Changes:

[FEATURE] Client/Server: Added System restore - Perform system restore Task
[FEATURE] Client/Server: Added System restore - List restore points Task
[FEATURE] Client/Server: Added System restore - Create restore point Task
[FEATURE] Client/Server: FTP action->List files

---

Hi Henrik

Ooops - a minor hiccup I think? FTP List is giving an exception in the server log file and not returning anything to STDOUT (or STDERR). Exception is:

==========================================================================================================
23/02/2012 14:34:18 Err Unhandled exception in ProcessTaskFTP.Run: System.IO.FileNotFoundException: Could not load file or assembly 'Communications, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'Communications, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.OBNIPPAGHDDHPOBHOGBJLEANJJPFMKFFKJEF..ctor(TaskProcessClass )
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.FJNDGAAMHPBCPDMHCNHGOGBCGPDLLJGOOFLF.Run()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
======================================================================================================

Probably something I have done (or forgot to do!) :-)

Cheers

Andy

Hi Henrik

Ooops - a minor hiccup I think? FTP List is giving an exception in the server log file and not returning anything to STDOUT (or STDERR). Exception is:

==========================================================================================================
23/02/2012 14:34:18 Err Unhandled exception in ProcessTaskFTP.Run: System.IO.FileNotFoundException: Could not load file or assembly 'Communications, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'Communications, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.OBNIPPAGHDDHPOBHOGBJLEANJJPFMKFFKJEF..ctor(TaskProcessClass )
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.FJNDGAAMHPBCPDMHCNHGOGBCGPDLLJGOOFLF.Run()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
======================================================================================================

Probably something I have done (or forgot to do!) :-)

Cheers

Andy

This seems like a build error which have slipped through testing. Hold on and we will rebuild it.

---

Andy,

we have rebuilt the setup now and hopefully it works better. Thanks for the heads up and sorry for waiting.

---

Hi Henrik

Excellent - it is working fine now.

Thanks so much for turning this around

Cheers

Andy

[FEATURE] Client/Server: FTP action->List files

Tested this one and I expected to see only the files in the output, but saw also all the responses of the ftp server. If I want to use the output for a lopping task it can't be done this way.
Might be that the requester of this feature is happy with this output, but an other checkbox in the task showing only the filenames would be great.
I like the full path option, hand when using the include subdirs.

Regards,
Erik

---

Hi Erik

That's a little strange - when I run it I get a straight forward list of files in STDOUT, and full path names when I select that. I don't see any FTP messages at all.....

Cheers

Andy

That is something to look into I think.😊

Regards,
Erik

---

[FEATURE] Client/Server: FTP action->List files

Tested this one and I expected to see only the files in the output, but saw also all the responses of the ftp server. If I want to use the output for a lopping task it can't be done this way.
Might be that the requester of this feature is happy with this output, but an other checkbox in the task showing only the filenames would be great.
I like the full path option, hand when using the include subdirs.

Regards,
Erik

I think the problem is that you are using Logging on the Connection - then that will be added to the log as well. Try turning it off.

---

True, I'm using the log.
I always want to see the log when uploading / downloading files.
If I turn the loggin off I indeed get only the filenames, but now my other tasks using this connection don't have logging anymore.

So looks like not an ideal situation.
What about a 'discard logging setting' checkbox at this ftp list task? 😕

Regards,
Erik

---

True, I'm using the log.
I always want to see the log when uploading / downloading files.
If I turn the loggin off I indeed get only the filenames, but now my other tasks using this connection don't have logging anymore.

So looks like not an ideal situation.
What about a 'discard logging setting' checkbox at this ftp list task? 😕

Regards,
Erik

---

True, I'm using the log.
I always want to see the log when uploading / downloading files.
If I turn the loggin off I indeed get only the filenames, but now my other tasks using this connection don't have logging anymore.

So looks like not an ideal situation.
What about a 'discard logging setting' checkbox at this ftp list task? 😕

Regards,
Erik

Yes, that might be a good idea. Requires some work though as they are logging on different levels. Could you please make a feature request about this?

---

Yes, that might be a good idea. Requires some work though as they are logging on different levels. Could you please make a feature request about this?

Done, see: feature request post 

Regards,
Erik

---

After upgrading to 6.0.7 we experienced that we were unable to add StdOut from a Execute (DOS) task into an email (as text content).

We got an index array error. Apparently it looked like the Execute task added some magic character to the end of the output.

Example:
1) Execute: Let a VBscript output something
2) Email: Take the output from 1) and use it in email

Task 2) results in an error.

Best regards,
René

Thank you all for testing this version 6.0.7 for a month. Unfortunately, a bug slipped through testing from our side. We released version 6.0.8 today to patch this.

The bug could cause different kinds of problems and is associated with a particular set of combined settings. We have seen the following problems:

- "handle invalid" - error in different Tasks
- crashes outside of .NET environment

We strongly suggest that you upgrade to 6.0.8 and we are sorry if this causes any problems.

---

After upgrading to 6.0.7 we experienced that we were unable to add StdOut from a Execute (DOS) task into an email (as text content).

We got an index array error. Apparently it looked like the Execute task added some magic character to the end of the output.

Example:
1) Execute: Let a VBscript output something
2) Email: Take the output from 1) and use it in email

Task 2) results in an error.

Best regards,
René

Output was not fully captured here. We have fixed this as well. Please try 6.0.8.

---

Hi Henrik

Just want to make sure I'm not losing my mind - 6.08 is not posted yet?

Cheers

Andy

Hi Henrik

Just want to make sure I'm not losing my mind - 6.08 is not posted yet?

Cheers

Andy

It is not posted as beta. It is in the Download page.

---

Aaaah - Got it! Thanks Henrik