[kylepyro]

ok - well I guess I have several thoughts about that.

1) I re-downloaded the task from the server with the exact same code and it performs properly now.

2) If the variable $LocalPath$ didn't contain the correct value then the file wouldn't be found and the task should encounter an error, post a log entry in its error log and terminate. It doesn't do that. It just ignores the statement. I know it hits this statment because of the various things I've done to debug it. I see it hitting the statements just prior to and subsequent to the rename.

3) I use this method, rename and then copy with this $LocalPath$ variable in other tasks, so I know this is a valid technique, unless your stating that there is something special about the rename function itself or something unreliable about the engine interpreting this code. This is the only task I have that encounters this problem and even its fixed now by visually identical code.

I can do the rename manually, so I know its not a windows rights problem. Any other ideas?