Changes so far in this version:

[FEATURE] Client/Server: HTTP Task->Added support for Client certificates
[FEATURE] Client: Server settings->Improved loading speed
[FEATURE] Client: Connection explorer->Improved loading speed
[FEATURE] API: Added Server.ExportSettings method
[BUGFIX] Client/Server: SQL Task->Removed ;1 from ODBC stored procedures
[BUGFIX] Client/Server: Several improvements to Job/Task progress
[BUGFIX] Client/Server: Desktop Macro Task->Fixed various problems related to UAC
[BUGFIX] API: Foreground execution->Execute Task->Fixed a problem killing child processes
[BUGFIX] Server: SFTP->Download->Fixed a problem with preserving Modified date
[BUGFIX] Server: Fixed convert of (old) Tasks when importing
[BUGFIX] Client: Job/Task progress update fixes
[BUGFIX] Client/Server: Fixed a lot of issues concerning Foreground execution and auto logon
[BUGFIX] Server: Execute Task->Now keeping exit code even though "Non zero exit code" is checked (to suppress errors)
[BUGFIX] Server: Archive - Compress->Fixed overwrite/append issue
[BUGFIX] Server: Connections->SQL->Fixed problem with default value "Convert data types"
[BUGFIX] Server: Archive Decompress->Fixed file lock on archive if decompress failed because of broken archive
[BUGFIX] Client: Handled crash when trying to add same Job Variable key twice
[BUGFIX] Server: Conditions->Fixed a problem with setting and using UniqueProcessId
[BUGFIX] Server: AD - Create group Task->Fixed property issues
[BUGFIX] Server: SCP Task->Fixed a problem causing multiple SCP instances running in memory

---

New build, changes:

[BUGFIX] Client/Server: SQL Task->Removed ;1 from ODBC stored procedures

---

New build, changes:

[BUGFIX] Client/Server: Several improvements to Job/Task progress
[BUGFIX] Client/Server: Desktop Macro Task->Fixed various problems related to UAC
[BUGFIX] API: Foreground execution->Execute Task->Fixed a problem killing child processes

---

New build, changes:

[FEATURE] Client: Server settings->Improved loading speed
[FEATURE] Client: Connection explorer->Improved loading speed
[BUGFIX] Server: SFTP->Download->Fixed a problem with preserving Modified date
[BUGFIX] Server: Fixed convert of (old) Tasks when importing

---

New build, changes:

[BUGFIX] Client: Job/Task progress update
[BUGFIX] Client/Server: Fixed a lot of issues concerning Foreground execution and auto logon

---

New build, changes:

[BUGFIX] Server: Execute Task->Now keeping exit code even though "Non zero exit code" is checked (to suppress errors)

---

I have a test job that I run each time I install a new beta version. It appears that the latest change to the 8.1.1 beta (Now keeping exit code even though "Non zero exit code" is checked (to suppress errors) is causing the "77777" failure code on file tasks such as Copy and List even when the task runs successfully. I have a very simple task that copies files from one folder to another. It is now returning the "77777" error code even though the copy process is successful.

I have a test job that I run each time I install a new beta version. It appears that the latest change to the 8.1.1 beta (Now keeping exit code even though "Non zero exit code" is checked (to suppress errors) is causing the "77777" failure code on file tasks such as Copy and List even when the task runs successfully. I have a very simple task that copies files from one folder to another. It is now returning the "77777" error code even though the copy process is successful.

Thanks - we will look at this!

---

I have a test job that I run each time I install a new beta version. It appears that the latest change to the 8.1.1 beta (Now keeping exit code even though "Non zero exit code" is checked (to suppress errors) is causing the "77777" failure code on file tasks such as Copy and List even when the task runs successfully. I have a very simple task that copies files from one folder to another. It is now returning the "77777" error code even though the copy process is successful.

Thanks - we will look at this!

We could not reproduce this right away. Can you share your settings in the On error tab? Because, when using default settings and just copying a file we do not get this.

---

Here are the On Error settings. These settings have not changed.

Need to figure out what happened with regards to the Archive file task when you have multiple sources for content. See this post for details:

http://www.visualcron.co....aspx?g=posts&t=6688 

Brian

Here are the On Error settings. These settings have not changed.

Something is special with your Job. Please let me know if you just create one Job with one Task that copies a file, lets say a txt file between two folders, can you reproduce it then?

---

Here are the On Error settings. These settings have not changed.

Something is special with your Job. Please let me know if you just create one Job with one Task that copies a file, lets say a txt file between two folders, can you reproduce it then?

There is nothing special about this job. Running the same job prior to the latest beta did not produce this error. Running it with the latest version gets the 77777 error. Something changed in the latest beta to cause this.

Here are the On Error settings. These settings have not changed.

Something is special with your Job. Please let me know if you just create one Job with one Task that copies a file, lets say a txt file between two folders, can you reproduce it then?

There is nothing special about this job. Running the same job prior to the latest beta did not produce this error. Running it with the latest version gets the 77777 error. Something changed in the latest beta to cause this.

Ok, but please perform the Copy test we suggested.

---

Here are the On Error settings. These settings have not changed.

Something is special with your Job. Please let me know if you just create one Job with one Task that copies a file, lets say a txt file between two folders, can you reproduce it then?

There is nothing special about this job. Running the same job prior to the latest beta did not produce this error. Running it with the latest version gets the 77777 error. Something changed in the latest beta to cause this.

Ok, but please perform the Copy test we suggested.

I performed the Copy test you suggested with the same results. The copy is successful but the 77777 error code is returned and the Result is "Failed". I'm now also seeing that other tasks (such as Execute) are returning the 77777 error code and a "Failed" result even though the task is successful. Obviously, something in this last beta version of 8.1.1 is causing this. Please let us know when this is fixed.

New build, changes:

[BUGFIX] Server: Execute Task->Now keeping exit code even though "Non zero exit code" is checked (to suppress errors)
[BUGFIX] Server: Archive - Compress->Fixed overwrite/append issue

---

New build, changes:

[BUGFIX] Server: Execute Task->Now keeping exit code even though "Non zero exit code" is checked (to suppress errors)
[BUGFIX] Server: Archive - Compress->Fixed overwrite/append issue

I just installed this latest build and the issue with the 77777 error code appears to be fixed. I've run several tests and haven't found any issues so far. Thanks!

New build, changes:

+ added more logging to SAP Task

---

I found a bug in the latest beta that i need addressed. It actually is also occurring in our production install of 7.2.1, so i tried the latest 8.1.1 beta to see if it was happening and it is.

If you have a corrupt zip file (i.e. take a .txt file and rename it to .zip, just for testing), and you do a File - Archive -Extract task. It will fail but the problem is, the file is now locked. I cannot delete the bad zip file. I assume i'd have to actually restart the VisualCron Service to free up the open handle on the corrupt file and that's fairly inconvenient to me. I just found it because of a new production process we went live with and were testing a few failure scenarios (such as a bad zip file). but now i'll have to restart the service so i can delete the bad file.

Error in the task:



i'll attach the example job. Again, I just renamed brian.txt to brian.zip and tried to simply extract the zip. That's all you have to do to reproduce this. then, try to delete the bad zip file. you can't.

  TestExtract-BadFile.zip (3kb) downloaded 63 time(s).

Brian

I found a bug in the latest beta that i need addressed. It actually is also occurring in our production install of 7.2.1, so i tried the latest 8.1.1 beta to see if it was happening and it is.

If you have a corrupt zip file (i.e. take a .txt file and rename it to .zip, just for testing), and you do a File - Archive -Extract task. It will fail but the problem is, the file is now locked. I cannot delete the bad zip file. I assume i'd have to actually restart the VisualCron Service to free up the open handle on the corrupt file and that's fairly inconvenient to me. I just found it because of a new production process we went live with and were testing a few failure scenarios (such as a bad zip file). but now i'll have to restart the service so i can delete the bad file.

Error in the task:

Exception in Task: System.Exception: SevenZip.SevenZipArchiveException: Invalid archive: open/read error! Is it encrypted and a wrong password was provided?
If your archive is an exotic one, it is possible that SevenZipSharp has no signature for its format and thus decided it is TAR by mistake.
   at SevenZip.SevenZipBase.ThrowException(CallbackBase handler, Exception[] e)
   at SevenZip.SevenZipExtractor.OpenArchive(IInStream archiveStream, ArchiveOpenCallback openCallback)
   at SevenZip.SevenZipExtractor.GetArchiveInfo(Boolean disposeStream)
   at SevenZip.SevenZipExtractor.ExtractArchive(String directory)
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.IJDAGFJMLJFNHKOCGKCOJOBFEPMLKABILLJK.CDJMFGBLNJDPDEJFDKHPAHBBBBMJAIAOLEGJ() in C:\sourcefiles\code\VisualCronService\Jobs\TaskProcesses\File\Archive\clsProcessTaskArchiveDecompress.vb:line 208 - file: c:\temp\Folder1\brian.zip

i'll attach the example job. Again, I just renamed brian.txt to brian.zip and tried to simply extract the zip. That's all you have to do to reproduce this. then, try to delete the bad zip file. you can't.

  TestExtract-BadFile.zip (3kb) downloaded 63 time(s).

Brian

Thanks, we have now fixed this for the next build.

---

New build, changes:

[BUGFIX] Client: Handled crash when trying to add same Job Variable key twice

---

New build, changes:

[BUGFIX] Server: Conditions->Fixed a problem with setting and using UniqueProcessId
[BUGFIX] Server: AD - Create group Task->Fixed property issues

---

New build, changes:

[FEATURE] API: Added Server.ExportSettings method
[BUGFIX] Server: SCP Task->Fixed a problem causing multiple SCP instances running in memory

---

Final version of 8.1.1 was released today - thank you for your testing!

---

Can I make a suggestion? Just to be VERY sure people are using the correct build of 8.1.1, When you release a full version, can you include the final build number in the original post for the prod release?

Brian