By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
462,363 Members | 602 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 462,363 IT Pros & Developers. It's quick & easy.

Exe behaves differently when run as a job

P: 1
I have developed an exe to cut image files from a dumped folder and paste them in some other folder(categorized into subfolders) on a different machine. I have also coded to generate a text file at the end of the operation to provide a kind of report. The exe also reports the error no. & procedure name through the same text file (when it encounters any error/exception)
Now, the exe performs all the reqd tasks properly when run but when I try to run the same exe as a job it fails to create any text file although the file transfer is handled properly and it shows 'executing' in its status & never finishes. However, the exe(when run as a job) creates the desired text file when it encounters any error/exception. The code to generate the text file is absolutely identical for both error log & reports. When I run the exe I do not provide any info abt the path or anything related to the generation of text file(its all hard coded). When I run it as a job i provide some info thru arguments reqd for the file transfer which is correctly executed.
I am at a loss to understand why the same exe behaves differently when run as a job. Its not that it doesnt do anything - it handles the file transfer but ceases before creating a text file.
Has anybody faced a similar condition?
Please help...
Nov 11 '08 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.