I had 2 WU's that would not upload while all other worked just fine.

I was able to get one of them to upload by doing this.

added <http_1_0>1</http_1_0> to the options section of cc_config

The final WU will still not upload after 2 days of trying.
I'm getting this error saying the upload handler is not found.

1/23/2013 5:40:05 AM | GPUGRID | [file_xfer] Couldn't start upload of I5R39-NATHAN_RPS1120801_N-106-111-RND3594_0_4
1/23/2013 5:40:05 AM | GPUGRID | [file_xfer] URL http://www.gpugrid.org/PS3GRID_cgi/file_upload_handler: not found
1/23/2013 5:40:05 AM | GPUGRID | Backing off 3 hr 43 min 12 sec on upload of I5R39-NATHAN_RPS1120801_N-106-111-RND3594_0_4

It appears to be saying http://www.gpugrid.org/PS3GRID_cgi/file_upload_handler is not the correct URL for the file upload handler. If I had a GPUgrid task in my cache I could compare the file upload handler URL for my task with your URL to see if they match. Unfortunately I don't have a task. That URL is stored in client_state.xml in a block of XML code that also contains the name of that task. If you happen to have another GPUgrid task on your host you could shutdown BOINC client and open client_state.xml in a text editor and search for that other task's name. It will appear in several places. One of those places will also give the file upload handler URL for the task. Then you could compare that URL with the apparently bad URL to see if they are the same. It's possible the URL got corrupted somehow. I've seen it many times before, all you have to do is correct the URL in client_state.xml then retry the upload and it will work.

Unfortunately, if you have another task to use for comparing the two URLs then it may also have a corrupted URL. If they happen to be different, however, then you know only the one is corrupt.

It appears to be saying http://www.gpugrid.org/PS3GRID_cgi/file_upload_handler is not the correct URL for the file upload handler. If I had a GPUgrid task in my cache I could compare the file upload handler URL for my task with your URL to see if they match. Unfortunately I don't have a task. That URL is stored in client_state.xml in a block of XML code that also contains the name of that task. If you happen to have another GPUgrid task on your host you could shutdown BOINC client and open client_state.xml in a text editor and search for that other task's name. It will appear in several places. One of those places will also give the file upload handler URL for the task. Then you could compare that URL with the apparently bad URL to see if they are the same. It's possible the URL got corrupted somehow. I've seen it many times before, all you have to do is correct the URL in client_state.xml then retry the upload and it will work.

Unfortunately, if you have another task to use for comparing the two URLs then it may also have a corrupted URL. If they happen to be different, however, then you know only the one is corrupt.

Check whether the file "I5R39-NATHAN_RPS1120801_N-106-111-RND3594_0_4" is actually present in your project directory.

I think I've come across this before, and it's a bad error message. Try reading it as if it's two separate messages:

I've been told to upload a file to <url>

I can't find the file I was told to upload

Thank you everyone for your efforts.
The file in question is missing from the project folder, good call Richard.
It did not upload and still appears as in progress with a deadline in 3 days.
I'm sure it will end up going past the deadline and be sent to another user.
The only thing I can figure is the file must have been clobbered somehow.
And to think it almost made it, it was 99.19% uploaded when it was lost!

It's a 2 step process: first the result, later the report. Even if a result uploads the task will show as In Progress on the server until the report is sent. Is it possible the client quit logging the upload progress at 99.01% and that the upload actually completed? I mean for some reason the client thought it should delete the result and that reason might be the upload actually reached 100% and the server acknowledged it received the upload intact with the correct CRC ( I believe that's the protocol). I can't account for why the client would then want to retry the upload but I wonder if what Richard suggested might work and that is to stop the client and edit the states of the task/result to the states that would match those of an uploaded but not yet reported result. Then start the client. Client will then upload the report. If the server has the result it will then give the task the "complete but awaiting verification" status. If the server does have the task it will give a "wtf?" and flag Bruce Kennedy as a cheater. No, just kidding. I don't know what would happen other than the task would be resent.

I don't recall exactly how the states should be modified in client_state.xml but I'll peek at an uploaded but unreported task in my client_state.xml and look for the numbers.

Because each task uploads multiple files, and only the _4 file has gone missing, Bruce should be able to compare the file info for that one with the data for the other files from the same task and adjust it to match.

The precise nature of the file reference structure changed between BOINC v6 and v7, but the key lines

<status>0</status>
<uploaded/>