H
hommer
Hi, all experts,
Can some one give me a hint on how to pinpoint the issue I have here?
I am batch faxing access report through code. Most of these reports are 1
page long.
Occassionaly (about 1 out of 100), one of them got stuck, meaning the app
went to sleep, no error, no time out, and also not in no respose mode under
task manager, and the fax driver property showing the job in spooling status
but other jobs sent to the same driver from other process got through. I have
left it siting there overnight, and it never went through.
I have also stopped the process, say 5 minutes into the spooling mode, then
restart it, or bring the reprot with the questionable record back in single
mode (i.e. preview, print or even fax just that one), and the operations are
all successful. That tells me this is not caused by bad data in the record.
Also, I have pulled all the data into a staging table just for the
reporting, so there should not have any issue of deadlock on the db. We
watched the sql db server, network and fax server log, but did not find any
thing.
Finally, if I clicked the Cancel button on the Printing message box, I got
the typical Action has been cancled message, and the process went on to the
next record.
Thanks!
Can some one give me a hint on how to pinpoint the issue I have here?
I am batch faxing access report through code. Most of these reports are 1
page long.
Occassionaly (about 1 out of 100), one of them got stuck, meaning the app
went to sleep, no error, no time out, and also not in no respose mode under
task manager, and the fax driver property showing the job in spooling status
but other jobs sent to the same driver from other process got through. I have
left it siting there overnight, and it never went through.
I have also stopped the process, say 5 minutes into the spooling mode, then
restart it, or bring the reprot with the questionable record back in single
mode (i.e. preview, print or even fax just that one), and the operations are
all successful. That tells me this is not caused by bad data in the record.
Also, I have pulled all the data into a staging table just for the
reporting, so there should not have any issue of deadlock on the db. We
watched the sql db server, network and fax server log, but did not find any
thing.
Finally, if I clicked the Cancel button on the Printing message box, I got
the typical Action has been cancled message, and the process went on to the
next record.
Thanks!