Reading Uplinger's posts, don't think we need to further report the -161 errors. The issue is identified and will be programmatically fixed.

Credit as you will have noticed is awarded for known science app caused faults.

thx for your patience and understanding.

You should find it. You probably looked for it before it had been reported by the client.
If you want to try again use the Status filter on Error in your Results Status page. If you have lots of results that will make the search easier.
Once you find it click on the Error link and you should see a Result Log like this:
Nom du résultat: erlc_ e059_ pr02a1_ 4--
<core_client_version>6.6.40</core_client_version>
<![CDATA[
<stderr_txt>
Calling gridPlatform.init()
INFO: No state to restore. Start from the beginning.
called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>erlc_e059_pr02a1_4_2</file_name>
<error_code>-161</error_code>
</file_xfer_error>

</message>
]]>

As Sekerob said this is a normal case which will be reworked by the techs for not using the exit code to report it.
Everything is OK and you should get a few credits (about 4) later on when the specialized script will have caught it.

Cheers. Jean.

Question for the techs on this -161 error.

This morning the client received a repair job that failed after 0.9 hours. It listed with the -161 error. Just now received a repair job, copy 4, where 1/2 failed with -161 too, number 3 not yet returned [actually it did after hitting F5]. The odd thing is that the failed result of this morning has disappeared from the RS pages. Anyway, it smells like the validator is now able to catch them since the one just now exiting at 0.2 hours has gone into PV state and a message log that does not show this fail. Bit strange as the version number is still 6.17 presuming the science app writes the result log, not the server filtering out the undesirable line.

erlc_ e104_ pqa002_ 4-- - In Progress 30-3-10 21:33:30 3-4-10 21:33:30 0.00 0.0 / 0.0
erlc_ e104_ pqa002_ 3-- 617 Pending Validation 30-3-10 20:54:59 30-3-10 21:32:36 0.20 3.6 / 0.0 < moi
erlc_ e104_ pqa002_ 2-- 617 Error 30-3-10 12:08:03 30-3-10 21:33:28 0.20 3.0 / 0.0
erlc_ e104_ pqa002_ 1-- 617 Error 27-3-10 04:52:47 30-3-10 12:07:58 0.14 4.4 / 0.0
erlc_ e104_ pqa002_ 0-- 617 Error 27-3-10 04:52:45 30-3-10 20:52:15 0.12 2.5 / 0.0


Result Log

Result Name: erlc_ e104_ pqa002_ 3--
<core_client_version>6.10.36</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
called boinc_finish

</stderr_txt>
]]>

Anyway, if this is proof of concept, Hip Hip Hurray

Yes - we released the fix to the -161 issue late yesterday (the file that isn't produced will not cause an error if it doesn't exist and the validator can check this condition properly). I apologize for not posting about it here. There are two other categories of errors that we are looking into. However, those occur with less frequency. These are the errors that are listed as '193', '-1073741819' or '29'. 193 and -1073741819 appear to be the same error (193 occurs on Linux while -1073741819 occurs on Windows). We are continuing to investigate these.

mweisensee, that's what I demonstrated with the post I made and the shorter list of errors, then 2 valids. That was the object, to not have them rejected and causing them to cycle through the error sequence till reaching 7.