01-30-2013 01:45 PM
09-26-2013 01:25 AM
I've also encountered this error in DI Studio and when running in LSF. Sometimes the job runs successfully and next time this error comes out.
What could be the possible cause of this? Is there a specific setting for this type of error? Is this related to network?