Hi All,
We have a VB exe for compressing PNG file to TIFF file .
Program runs fine when directly invoked (by double clicking).
We are now configuring this exe as a windows scheduled job .
But the program fails with "OUT OF MEMORY" error.
Can anyone explain why there is a difference in behavior in both cases.
Note that we have also tried converting the EXE in to windows service and we get the same error as Scheduled jobs .
We have a VB exe for compressing PNG file to TIFF file .
Program runs fine when directly invoked (by double clicking).
We are now configuring this exe as a windows scheduled job .
But the program fails with "OUT OF MEMORY" error.
Can anyone explain why there is a difference in behavior in both cases.
Note that we have also tried converting the EXE in to windows service and we get the same error as Scheduled jobs .