This has happened a few times when splitw runs in the task manager. What is the possible real cause. The output file name is not illegal nor is the disk full.
Your task should be set to trigger "After File Closed" to make sure Loggernet does not still have the file open for writing data.
I had a customer with computer backup software causing the error, because it was copying the files at the same time SplitW was trying to access them.
Thanks
I've changed the trigger now it happens everytime the split runs