Hi,

this WU was trying to error out with the following message in std_err:

<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>

That's all, nothing else. I recovered it for now by editing the client_state.xml and suspended it, don't want to waste those 8MB.

The app is the AP6_win_x86_SSE_CPU_r555.exe, the CPU supports SSE, so that should be fine.

My app_info looks like that:

<app_info>
 <app>
  <name>setiathome_enhanced</name>
 </app>
 <file_info>
  <name>KWSN_2.4V_SSE_MB_FFTW.exe</name>
  <executable/>
 </file_info>
 <app_version>
  <app_name>setiathome_enhanced</app_name>
  <version_num>603</version_num>
  <flops>2875950000</flops>
  <file_ref>
   <file_name>KWSN_2.4V_SSE_MB_FFTW.exe</file_name>
   <main_program/>
  </file_ref>
 </app_version>
 <app>
  <name>astropulse_v6</name>
 </app>
 <file_info>
  <name>AP6_win_x86_SSE_CPU_r555.exe</name>
  <executable/>
 </file_info>
 <app_version>
  <app_name>astropulse_v6</app_name>
  <version_num>601</version_num>
  <file_ref>
   <file_name>AP6_win_x86_SSE_CPU_r555.exe</file_name>
   <main_program/>
  </file_ref>
 </app_version>
</app_info>

Any ideas?


EDIT: BTW, that was in BOINC log, the task errored out instantly at start up:

23-Jan-2013 23:13:28 [SETI@home] Starting ap_25jn12ac_B5_P1_00089_20130120_15039.wu_1
23-Jan-2013 23:13:28 [SETI@home] Starting task ap_25jn12ac_B5_P1_00089_20130120_15039.wu_1 using astropulse_v6 version 601
23-Jan-2013 23:13:29 [SETI@home] Computation for task ap_25jn12ac_B5_P1_00089_20130120_15039.wu_1 finished
23-Jan-2013 23:13:29 [SETI@home] Output file ap_25jn12ac_B5_P1_00089_20130120_15039.wu_1_0 for task ap_25jn12ac_B5_P1_00089_20130120_15039.wu_1 absent

---

Hi,

this WU was trying to error out with the following message in std_err:

<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>

That's all, nothing else. I recovered it for now by editing the client_state.xml and suspended it, don't want to waste those 8MB.

Error 0xc0000135 translates as "The application failed to initialize properly", and is usually related to a missing DLL file (no, not the dotNET framework, google users - we don't use dotNET here - but any other missing DLL will cause the same error).

Funnily enough, I was typing exactly the same explanation around this time yesterday. Then, I invited the ATI hardware/driver gurus to investigate: this time it needs the third-party AP application crew.

Error 0xc0000135 translates as "The application failed to initialize properly", and is usually related to a missing DLL file (no, not the dotNET framework, google users - we don't use dotNET here - but any other missing DLL will cause the same error).

Funnily enough, I was typing exactly the same explanation around this time yesterday. Then, as now, I invited the ATI hardware/driver gurus to investigate.

This one is for a CPU, AMD but not ATi.

The most likely cause is that libfftw3f-3.dll is missing. The application requires it, but we left it out of the aistub for what seemed at the time adequate reasons. The 0.40 installer does supply it, but it's not clear exactly how Link has arrived at the configuration of that system.

                                                                  Joe

Error 0xc0000135 translates as "The application failed to initialize properly", and is usually related to a missing DLL file (no, not the dotNET framework, google users - we don't use dotNET here - but any other missing DLL will cause the same error).

Funnily enough, I was typing exactly the same explanation around this time yesterday. Then, as now, I invited the ATI hardware/driver gurus to investigate.

This one is for a CPU, AMD but not ATi.

The most likely cause is that libfftw3f-3.dll is missing. The application requires it, but we left it out of the aistub for what seemed at the time adequate reasons. The 0.40 installer does supply it, but it's not clear exactly how Link has arrived at the configuration of that system.

                                                                  Joe

Argh - you caught me before my edit :-)

Agreed - it has to be a manual app_info creation, not an installer-generated one. AP6_win_x86_SSE_CPU_r555.exe arrived in the installer with v0.40 and APv6 compatibility (March 2012), but the antediluvian KWSN_2.4V_SSE_MB_FFTW.exe had been retired long before that.

The most likely cause is that libfftw3f-3.dll is missing. The application requires it, but we left it out of the aistub for what seemed at the time adequate reasons. The 0.40 installer does supply it, but it's not clear exactly how Link has arrived at the configuration of that system.

That was it. I haven't know I need that file too when I extracted it from the installer using 7-zip. It would be indeed helpful if all needed files would be included in the aistub files for those of us who update manually for whatever reason.

Thanks a lot!

---

I was having this problem too on AP6 on an ATI card using Lunatics, quick search here, quick copy/paste from the backup folder Lunatics created when it installed and no more problem.

Thanks for the info!

To clarify a comment in the thread though, it is not just a manual install problem. Lunatics .40 actually removed the dll (put it in the backup folder it creates) so it was an easy fix.

---