Changes so far:

[FEATURE] Client/Server: Added support for return error if no files are found in the List files Task. Please note that the default behavior is returning error.
[FEATURE] Client/Server: Added basic support for custom branding VisualCron. Contact sales for more information.
[FEATURE] Client/Server: Added content-type header support for the HTTP Task
[FEATURE] Client/Server: Added "duplicate file delay" property for File Trigger
[BUGFIX] Server: Fixed and issue where Logoff User Task reported error even though it succeeded
[BUGFIX] Server: Fixed a problem with adding parameters in DTS and SSIS Task
[BUGFIX] Server: Fixed an issue connection and executing against Oracle (SQL Task)
[BUGFIX] Server: Fixed with Sharepoint file upload and commit
[BUGFIX] Server: Fixed and issue with high session value and the execution context dialog
[BUGFIX] Server: Fixed a problem preventing negative values in the Crystal reports Task
[BUGFIX] Server: Fixed an issue with WebDAV Download Task and .NET 4.0
[BUGFIX] Server: Fixed a problem with remote execute reporting back (reverting to a previoius solution)
[BUGFIX] Installer: Fixed an issue pointing to wrong version of .NET

---

I had put this in the 6.1.7 Beta thread, but since 6.1.7 is now released, I thought I'd copy/paste my concern here (If its already fixed, sorry, I just returned from vacation and have not yet moved beyond 6.1.5)

---

Just thought i'd see if there was anything you could do in the next version or two that would resolve the issues described in this post:

http://www.visualcron.co...ts&m=13780#post13780 

Basically, if you have an FTP task and use a variable as your source path, if either the variable or the line in which you use your variable, end in a backslash '\' it will fail with some oddly joined strings of text.

If I just type the following as my Path it works fine:

C:\Temp\

If I use a variable set to the following, it works:

C:\Temp

If I use a variable set the following, it fails:

C:\Temp\

If I use a variable set to C:\Temp and then add a \ after the variable on the line, it fails:

MyPath = c:\Temp
Source = {USERVAR(MyPath)}\

Brian

I am not sure what you mean. It sounds like you want to have support for double slashes, i.e.

MyVariable have a value of c:\temp\

{USERVAR(MyVariable)}\folder2

FTP is very sensitive for double slashes and I think it is hard to find every place you use double slashes. Or am I misunderstanding you?

I had put this in the 6.1.7 Beta thread, but since 6.1.7 is now released, I thought I'd copy/paste my concern here (If its already fixed, sorry, I just returned from vacation and have not yet moved beyond 6.1.5)

---

Just thought i'd see if there was anything you could do in the next version or two that would resolve the issues described in this post:

http://www.visualcron.co...ts&m=13780#post13780 

Basically, if you have an FTP task and use a variable as your source path, if either the variable or the line in which you use your variable, end in a backslash '\' it will fail with some oddly joined strings of text.

If I just type the following as my Path it works fine:

C:\Temp\

If I use a variable set to the following, it works:

C:\Temp

If I use a variable set the following, it fails:

C:\Temp\

If I use a variable set to C:\Temp and then add a \ after the variable on the line, it fails:

MyPath = c:\Temp
Source = {USERVAR(MyPath)}\

Brian

---

New version:

[FEATURE] Client/Server: Added support for return error if no files are found in the List files Task. Please note that the default behavior is returning error.
[FEATURE] Client/Server: Added basic support for custom branding VisualCron. Contact sales for more information.
[BUGFIX] Server: Fixed an issue connection and executing against Oracle (SQL Task)

---

I am not sure what you mean. It sounds like you want to have support for double slashes, i.e.

MyVariable have a value of c:\temp\

{USERVAR(MyVariable)}\folder2

FTP is very sensitive for double slashes and I think it is hard to find every place you use double slashes. Or am I misunderstanding you?

I had put this in the 6.1.7 Beta thread, but since 6.1.7 is now released, I thought I'd copy/paste my concern here (If its already fixed, sorry, I just returned from vacation and have not yet moved beyond 6.1.5)

---

Just thought i'd see if there was anything you could do in the next version or two that would resolve the issues described in this post:

http://www.visualcron.co...ts&m=13780#post13780 

Basically, if you have an FTP task and use a variable as your source path, if either the variable or the line in which you use your variable, end in a backslash '\' it will fail with some oddly joined strings of text.

If I just type the following as my Path it works fine:

C:\Temp\

If I use a variable set to the following, it works:

C:\Temp

If I use a variable set the following, it fails:

C:\Temp\

If I use a variable set to C:\Temp and then add a \ after the variable on the line, it fails:

MyPath = c:\Temp
Source = {USERVAR(MyPath)}\

Brian

I think we've still got a misunderstanding. You're assuming that I want to select a subfolder, i.e. \Folder2 after my source directory.

What if My sourcedirectory was ONLY listed as this:
{USERVAR(MyVariable)}

If 'MyVariable' is equal to 'c:\Temp' it works just fine, but if its equal to 'c:\temp\' it will fail. Its a continuity issue.

Why can I type, instead of using a variable, 'c:\temp\' and have it work, yet when I use a variable equal to that exact string of 'c:\temp\' it fails horribly? Thats the concern.

Obviously I agree with you that double slashes is not ideal haha. I would never put 'c:\temp\\folder' so I would expect that if 'MyVariable' was equal to 'c:\temp\' that I could not use 'MyVariable' along with a subfolder as you have described. The issue is why does introducing a variable cause the issue when I can type it myself just fine?

We now updated to 6.1.8 from 6.1.3, and the Oracle connection appears to work when run from the tasks. However when I test the connection from the connection wizard I still the following error:
Provider not specified
InternalTestConnection

We now updated to 6.1.8 from 6.1.3, and the Oracle connection appears to work when run from the tasks. However when I test the connection from the connection wizard I still the following error:
Provider not specified
InternalTestConnection

Please re-download again. We have fixed this now. Thanks for the report.

---

New version, changes:

[FEATURE] Client/Server: Added content-type header support for the HTTP Task
[FEATURE] Client/Server: Added "duplicate file delay" property for File Trigger
[BUGFIX] Server: Fixed with Sharepoint file upload and commit
[BUGFIX] Server: Fixed and issue with high session value and the execution context dialog
[BUGFIX] Server: Fixed a problem preventing negative values in the Crystal reports Task
[BUGFIX] Server: Fixed an issue with WebDAV Download Task and .NET 4.0
[BUGFIX] Server: Fixed a problem with remote execute reporting back (reverting to a previoius solution)
[BUGFIX] Installer: Fixed an issue pointing to wrong version of .NET

---

All of a sudden my Powershell scripts now give me an error:

Exception in Task: The Windows PowerShell snap-in 'Microsoft.Exchange.Management.PowerShell.E2010' is not installed on this machine.

All it does is:

$string = "{REGEX(MatchGetGroup|{TASK(fb83de28-f6e6-4284-8239-c62753ea3432,StdOut)}|Cpr=(.*?)&|1)}";
echo $string;

Why does it need an Exchange snap-in in order to work?

All of a sudden my Powershell scripts now give me an error:

Exception in Task: The Windows PowerShell snap-in 'Microsoft.Exchange.Management.PowerShell.E2010' is not installed on this machine.

All it does is:

$string = "{REGEX(MatchGetGroup|{TASK(fb83de28-f6e6-4284-8239-c62753ea3432,StdOut)}|Cpr=(.*?)&|1)}";
echo $string;

Why does it need an Exchange snap-in in order to work?

Sorry, some test code was not deleted from code. Please download again.

---

That indeed has fixed the issue. Thank you. 🙂

That indeed has fixed the issue. Thank you. :)

Thanks for the feedback. We released this officially today.

---