Hey, so i keep getting this error on all "Milkyway@home N-Body Simulation with Orbit Fitting" WUS. Any fix for this?

CPU: GenuineIntel
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz [Family 6 Model 140 Stepping 1]

GPU: NVIDIA NVIDIA GeForce MX450 (2047MB) driver: 566.14 OpenCL: 3.0
INTEL Intel(R) Iris(R) Xe Graphics (6434MB) OpenCL: 3.0

OS: Windows 11

The log:

<core_client_version>8.0.4</core_client_version>
<![CDATA[
<message>
The handle is invalid.
 (0x6) - exit code 6 (0x6)</message>
<stderr_txt>
<search_application> milkyway_nbody 1.86 Windows x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 7 max threads on a system with 8 processors
Running MilkyWay@home Nbody v1.86
Optimal Softening Length = 0.000081491176379 kpc
Dwarf Initial Position: [5.822574307990490,10.301453423572546,2.562879417177238]
Dwarf Initial Velocity: [87.322876952222316,179.965243770208701,1.891474917010984]
Running MilkyWay@home Nbody v1.86
Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to update checkpoint 'nbody_checkpoint' with temporary (0): No error
Failed to write checkpoint
Error running system: NBODY_CHECKPOINT_ERROR (64)
strftime() failed called boinc_finish(6)

</stderr_txt>
]]>

What antivirus are you using? Try excluding BOINC data dir from scanning (usually C:\ProgramData\BOINC\ on Windows), something is blocking access to the new checkpoint file, so it can't be renamed to it's final file name, this is likely your antivirus program.

---

It's not your system.
It is something internal in their system.

I had 222 tasks canceled by the server. If I look at the work unit it does not exist anymore.
Check your account and see if this task got pulled or not. If so then it was part of a batch that had a serious bug in it. If it still exists it is another error that they have not got enough results back to see it en mass.

Hey, so i keep getting this error on all "Milkyway@home N-Body Simulation with Orbit Fitting" WUS. Any fix for this?

CPU: GenuineIntel
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz [Family 6 Model 140 Stepping 1]

GPU: NVIDIA NVIDIA GeForce MX450 (2047MB) driver: 566.14 OpenCL: 3.0
INTEL Intel(R) Iris(R) Xe Graphics (6434MB) OpenCL: 3.0

OS: Windows 11

The log:

<core_client_version>8.0.4</core_client_version>
<![CDATA[
<message>
The handle is invalid.
 (0x6) - exit code 6 (0x6)</message>
<stderr_txt>
<search_application> milkyway_nbody 1.86 Windows x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 7 max threads on a system with 8 processors
Running MilkyWay@home Nbody v1.86
Optimal Softening Length = 0.000081491176379 kpc
Dwarf Initial Position: [5.822574307990490,10.301453423572546,2.562879417177238]
Dwarf Initial Velocity: [87.322876952222316,179.965243770208701,1.891474917010984]
Running MilkyWay@home Nbody v1.86
Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction. It was still busy setting up and had not started crunching yet.
Check to see if that task shows up in your errors section of the tasks on your profile. If it is still there then they have not seen enough of that error. I have over 200 tasks pulled by the server and they do not exist on the system anymore. So if yours is like that, then there was a critical error with that batch and they removed all of them.


Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to move file 'nbody_checkpoint_tmp_20824' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

Failed to update checkpoint 'nbody_checkpoint' with temporary (0): No error
Failed to write checkpoint
Error running system: NBODY_CHECKPOINT_ERROR (64)
strftime() failed called boinc_finish(6)

</stderr_txt>
]]>

It's not your system.
It is something internal in their system.

It's not, all the error tasks were completed successfully by at least one other computer, most of them already validated.

I had 222 tasks canceled by the server. If I look at the work unit it does not exist anymore.

Cancelled by server means usually someone returned their result a bit late, but before your computer started to crunch it.

---

Im using Avasta Antivirus. As you said i excluded boinc dir from it. Hopefully it will work now.

Im using Avasta Antivirus. As you said i excluded boinc dir from it. Hopefully it will work now.

You mean Avast I hope, without that "a" at the end. Well, your choise, but the last time I used it was 2008 or 2009, after they added lots of crap to it and I switched to Microsoft Security Essentials, now called Microsoft Defender.

Anyway, I see one completed and validated WU after your post, so I guess it worked.

---

Im using Avasta Antivirus. As you said i excluded boinc dir from it. Hopefully it will work now.

You mean Avast I hope, without that "a" at the end. Well, your choise, but the last time I used it was 2008 or 2009, after they added lots of crap to it and I switched to Microsoft Security Essentials, now called Microsoft Defender.

Anyway, I see one completed and validated WU after your post, so I guess it worked.

I run with a antivirus and windows defender or whatever it is called. I don't have that problem.

It's not your system.
It is something internal in their system.

It's not, all the error tasks were completed successfully by at least one other computer, most of them already validated.

I had 222 tasks canceled by the server. If I look at the work unit it does not exist anymore.

Cancelled by server means usually someone returned their result a bit late, but before your computer started to crunch it.

But there is no record of the workunit period. It is as if never existed.

But there is no record of the workunit period. It is as if never existed.

Whatever it was in your case, it has nothing to do with the issue Herobrine37440 had, those tasks were still there and all could be completed by at least one other computer, so there was nothing wrong with the tasks.

---

But there is no record of the workunit period. It is as if never existed.

Whatever it was in your case, it has nothing to do with the issue Herobrine37440 had, those tasks were still there and all could be completed by at least one other computer, so there was nothing wrong with the tasks.

yeah I see that now. I was in a rush last time.
He gets a The handle is invalid. (0x6) - exit code 6 (0x6)
Einstein has a thread on that (from 2007 is the only reference to BOINC I find) The short version of that therad is spyware catcher or antivirus.
He also has a bunch of abandoned tasks on computer 2 which created the error he is talking about.
But it did return a valid result after that error. So maybe he turned off his antivirus or something.