WU "stuck" in SETI Driver's cache?

[TheGrandHooHa]

I have a workunit here that appears to be stuck; SETI Driver continually claims that there is 1 to transmit, 1 to fill. Every subsequent WU that gets done is transmitted fine, and its spot is quickly filled. But this one WU appears to be stuck. I have tried different SETI Queues and everything but it just won't send. Has anyone seen this before?

Thanks,
Chris

 

[Soggysocks]

Yep. I had to delete that wu from the seti folder on my 'C' drive download and start a new one.

 

[amdxborg]

What Soggy said, think I had the same prob a while ago...Or maybe you can just move it to another folder and put it back after another one has been downloaded, maybe then it will send. Plz ask if the prob still exists.

 

[TheGrandHooHa]

Sorry for the blated reply:

How do I know which WU is causing trouble? I don't want to go around arbitrarily deleting my cache directories (I have my cache set at 30), so is there any way to tell what it is currently processing and what needs to be sent?

Thanks,
Chris

 

[Assimilator1]

I believe the lattest version of SD creates a .txt file that says something like 'processing work unit' ,also SD usually creates a 'transmitloopdetect.txt file when a WU gets stuck.
So you should be able to find it fairly easily