WU refers to nonexistent app version: '(app-name)' '(version)'

From Unofficial BOINC Wiki

Contents 1 General 2 Version Information 3 Example Log(s) 3.1 Can't Link Result In Scheduler Reply 3.1.1 Line-By-Line Explanation 3.2 Can't Link Result In State File 4 Other Related Messages

[edit] General

Message Type: Error Message

The BOINC Client Software is unable to connect information in the state file to the Science Application's physical presence on the Participant's Computer. Basically, the "bookkeeping" indicates that there should be a specific Science Application of the Work Unit on the Disk Drive, but the BOINC Daemon cannot locate it.

Causes include:

• The Science Application was deleted by some other program or Participant action.
• The Application Information File contains incorrect information.

[edit] Version Information

• None.

[edit] Example Log(s)

[edit] Can't Link Result In Scheduler Reply

6/17/2005 11:25:00 PM|SETI@home|WU refers to nonexistent app_version: setiathome 418
6/17/2005 11:25:00 PM|SETI@home|Can't link workunit 29fe04aa.5344.5106.686074.118 in sched reply
6/17/2005 11:25:00 PM|SETI@home|Can't link result 29fe04aa.5344.5106.686074.118_0 in sched reply

Line-By-Line Explanation

• WU refers to nonexistent app_version: '(app-name)' '(version)'

The information in the Scheduler Reply Message for the Work Unit refers to a specific version of a Science Application and that version of the Science Application is not available.

• Can't link workunit '(wu-name)' in sched reply

The Work Unit cannot be linked to the required Science Application Version.

• Can't link result '(result)' in sched reply

Because the Work Unit was not available (because the Application Version was not available), the Result cannot be linked to the correct Work Unit.

[edit] Can't Link Result In State File

Because of an error in the Application Information File, all the work that was in-progress on the Participant's Computer is deleted. You don't see the other messages that I deleted for brevity's sake, but there were about 10-15 Results that were lost due to this one error.

2005-05-19 13:26:58 [SETI@home] Found app_info.xml; using anonymous platform
2005-05-19 13:26:58 [SETI@home] WU refers to nonexistent app_version: setiathome 409
2005-05-19 13:26:58 [SETI@home] Can't link workunit in state file
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
2005-05-19 13:26:58 [SETI@home] link_result: nonexistent WU 30dc04ab.18554.20210.317312.3
2005-05-19 13:26:58 [SETI@home] Can't link result 30dc04ab.18554.20210.317312.3_1 in state file
-+-+/\/\/\/\/\ Log Break /\/\/\/\/\-+-+-
2005-05-19 13:26:58 [SETI@home] ACTIVE_TASK::parse(): result not found

Line-By-Line Explanation

• Found app_info.xml; using anonymous platform

This message tells us that the Science Application to be used for this Project (SETI@Home) is not the standard, Project provided Science Application.

'Unfortunately ...

• WU refers to nonexistent app_version: '(app-name)' '(version)'

The information in the State File for the Work Unit refers to a specific version of a Science Application and that version of the Science Application is not available. Because the Application Information File does not contain the correct information for the Work Unit and the BOINC Daemon cannot start the Science Application required by this Work Unit.

• Can't link workunit in state file

The Work Unit cannot be linked to the required Science Application Version.

• link_result: nonexistent WU '(work unit)'

Because the earlier link between the Work Unit and the Science Application failed, the Work Unit was deleted and therefor does not exist.

• Can't link result '(result)' in state file

Because the Work Unit was deleted, the Result cannot be linked to the correct Work Unit.

• ACTIVE_TASK::parse(): result not found

As a final result of all of this, the Active Task could not be found.

[edit] Other Related Messages

• None.