I've noticed that both seti and einstein produce messages like this:

2/7/2008 6:11:07 AM|SETI@home|Task 30dc06ae.32427.890.14.6.91_1 exited with a DLL initialization error.

The client seems to heal itself, and the work units seem to get processed correctly in the end. In at least one case the messages were produced when Vista was doing a shadow copy during a scheduled backup.

Is this something I need to worry about?

What BOINC version are you using?

---

What BOINC version are you using?

Version 5.10.30, the latest officially released one. thx.

(and yes the wu's seem to finish correctly, but there is no obvious reason for the error message being issued to begin with.)

I run XP SP3 and BOINC 5.10.45 and I get this message on just about every task i do for proteins, Rosetta, SETI and climateprediction.

Normally it means starting the unit over again and hoping that the unit is completed before the error occurs again. Quite often a unit is restarted as many as three times before it will actually complete.

It must be fixed ASAP, it is basically wasting resources.

I run XP SP3 and BOINC 5.10.45 and I get this message on just about every task i do for proteins, Rosetta, SETI and climateprediction.

Normally it means starting the unit over again and hoping that the unit is completed before the error occurs again. Quite often a unit is restarted as many as three times before it will actually complete.

It must be fixed ASAP, it is basically wasting resources.

Did you get it with XP SP2? I believe none of the developers has tested BOINC under SP3...

---

I run XP SP3 and BOINC 5.10.45 and I get this message on just about every task i do for proteins, Rosetta, SETI and climateprediction.

Did you get it with XP SP2? I believe none of the developers has tested BOINC under SP3...

;-)

I'm getting these "Task *** exited with a DLL initialization error. If this happens repeatedly you may need to reboot your computer." messages on WinXP SP2 with 5.10.45 nearly regularly (more often yes than no) after nearly each resume from hibernation, apparently when the machine is too long busy with the wakeup process. In this case all in-memory Boinc apps are restarted, I call it "small Boinc exodus".

Peter

I think one has been put into V6.

---

Nicolas wrote:
Did you get it with XP SP2? I believe none of the developers has tested BOINC under SP3...

Ask for the Build number of the SP3, there are many testing and pre-release versions of SP3 for XP...

I run XP SP3 and BOINC 5.10.45 and I get this message on just about every task i do for proteins, Rosetta, SETI and climateprediction.

You should not select "Leave applications in memory".
The value of "Switch between applications every xx minutes" should be set higher.

I'm getting these [...] messages on WinXP SP2 with 5.10.45 nearly regularly (more often yes than no) after nearly each resume from hibernation, apparently when the machine is too long busy with the wakeup process. In this case all in-memory Boinc apps are restarted...

On Vista there is a service option to Automatic start With Delay. That might fix it (worked for me and improved overall boot speed).

Remember, I wrote about resuming from hibernation. In such situation the service is already running (for hours or days long).

I'm afraid that in my case probably only lengthening the heartbeat interval "under some specific circumstances" would help. (Heartbeat debugging messages could possibly help on problem detection - it's on my todo list. Except it is already implemented.) Variable heartbeat intervals were mentioned some 1-2 weeks ago on the mailinhg lists.

(Once I'm on Vista, I'll for sure use the startup delay option, I hope it should somehow cure the memory contention during the boot process. But again, it is for OS boot. BTW, my exits with DLL init errors do never happen during boot.)

Peter

Back to the topic.

PhonAcq wrote:

I've noticed that both seti and einstein produce messages like this: "Task *** exited with a DLL initialization error." [...] In at least one case the messages were produced when Vista was doing a shadow copy during a scheduled backup.

I'd like to believe that the system was too busy with (higher priority) I/O and the lowest priority Boinc applications did not receive heartbeat in time. Then the "DLL init error" would be a false message.

In which else situation did you observe it happening?

Andy_KOA wrote:

I run XP SP3 and BOINC 5.10.45 and I get this message on just about every task i do for proteins, Rosetta, SETI and climateprediction.

When does it happen, arbitrarily or in any specific OS situation?

Peter