KR Plant Archiver

KR Plant Archiver

Description
This application automatically or manually pulls archives from a configurable list of KRC4 robots. Execute the application automatically from a scheduled task manager using the following command line switches:

/DAY {x} - (optional) This switch downloads the archive to the
specified day. Example /DAY Wednesday

/UNZIP {x} - (optional) This switch chooses whether to unzip the
archive to the configured archive folder.
Note: The unzip folder will use the string
designated in the /DAY switch as well.
Example: /UNZIP TRUE

/MINIMIZED - (optional) This switch runs the application minimized
to the task bar.

/START - (required) This switch actually starts the archival and
unzip process. It must be present to start the
archival process from the task scheduler.

Examples:
KRPlantArchiver /Start
KRPlantArchiver /Start /Unzip False
KRPlantArchiver /Start /Unzip False /MINIMIZED
KRPlantArchiver /Start /Unzip False /MINIMIZED /Day Friday

Requirements
-WinXP, Win7x, Win8x
-512 MB Ram
-.NET 3.0 Framework
-Administrator Rights

Screenshots

====================================================================
Release Notes
====================================================================
--------
v1.0.4.0
--------
*-Added code to automatically retry to archive robots that fail to
archive. The maximum limit is 10 times.
*-Set the operation timeout to 5 minutes for the binding so the
archive has enough time to download.

--------
v1.0.3.0
--------
*-Added code to display a notification object in the tool bar when
the application is started with the command line switch /START
*-Fixed issue preventing the application from cleaning up the unzip
folder.

--------
v1.0.2.0
--------
*-Fixed issue that caused the application to crash when the stream
object shut or the socket object aborted.
*-Added code to output an archive summary text file when the archive
task finishes. The archive summary text file appears in the folder
of the archive day.
*-Removed the 'Loading System Settings' message because it was creating
an additional log file because the message shows prior to the desired
log file directory being loaded.

--------
v1.0.0.1
--------
*-Fixed issue that caused the interface to fail to update when the
application was launched from the task scheduler.