I have a step (call it RunEXE) in a package (call it PackageA). RunEXE executes another Package (call it PackageB) passing two global variables. PackageB outputs some data to a text file then, using the CreateProcessTask, calls an executable on another server within the LAN. The path to the executable is specified using UNC. The data output is to the same location on the other server. Now can this can be working fine one moment and then the next (quite often the next day) it fails stating that the executable has returned a result code of 1 rather than 0. When this happens the executable isn't performing any function (i.e. the first line of code in the exe creates a text file and that file doesn't get created - if an error occurs creating the file then executable returns a result code of 2 not 1). If I rename the executable I get the expected error of "file not found". The only way I've found to get it working again is to open PackageB, double click on the CreateProcessTask, browse the executable, click OK and save the Package. This one is driving me mad.