Welcome to MilkyWay@home

"The handle is invalid. (0x6) - exit code 6 (0x6)" on Win7 64-bit machine


Advanced search

Message boards : Number crunching : "The handle is invalid. (0x6) - exit code 6 (0x6)" on Win7 64-bit machine
Message board moderation

To post messages, you must log in.

AuthorMessage
Jim1348

Send message
Joined: 9 Jul 17
Posts: 54
Credit: 6,062,974
RAC: 1,624
5 million credit badge2 year member badge
Message 67857 - Posted: 31 Oct 2018, 17:45:28 UTC

I just reattached my Win7 64-bit machine to N-body, and am getting only errors.
I note that they are completing OK on Win10 and Ubuntu machines, but failed on the only other Win7 machine I see thus far.

Does anyone know what is going on?
https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=737912&offset=0&show_names=0&state=6&appid=

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
The handle is invalid.
 (0x6) - exit code 6 (0x6)</message>
<stderr_txt>
<search_application> milkyway_nbody 1.72 Windows x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 6 max threads on a system with 8 processors
Failed to move file 'nbody_checkpoint_tmp_4892' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

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

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

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

<search_application> milkyway_nbody 1.72 Windows x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 6 max threads on a system with 8 processors
Failed to move file 'nbody_checkpoint_tmp_4676' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

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

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

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

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

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

Failed to move file 'nbody_checkpoint_tmp_4676' 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)
13:38:52 (4676): called boinc_finish(6)
ID: 67857 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2236
Credit: 259,751,112
RAC: 41,282
200 million credit badge10 year member badgeextraordinary contributions badge
Message 67858 - Posted: 1 Nov 2018, 10:58:59 UTC - in response to Message 67857.  

I just reattached my Win7 64-bit machine to N-body, and am getting only errors.
I note that they are completing OK on Win10 and Ubuntu machines, but failed on the only other Win7 machine I see thus far.

Does anyone know what is going on?
https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=737912&offset=0&show_names=0&state=6&appid=

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
The handle is invalid.
 (0x6) - exit code 6 (0x6)</message>
<stderr_txt>
<search_application> milkyway_nbody 1.72 Windows x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 6 max threads on a system with 8 processors
Failed to move file 'nbody_checkpoint_tmp_4892' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

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

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

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

<search_application> milkyway_nbody 1.72 Windows x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 6 max threads on a system with 8 processors
Failed to move file 'nbody_checkpoint_tmp_4676' to 'nbody_checkpoint' (6832): This object is not allowed to be opened in a transaction.

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

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

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

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

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

Failed to move file 'nbody_checkpoint_tmp_4676' 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)
13:38:52 (4676): called boinc_finish(6)


Stop doing the n-body units and try the regular cpu units instead.
ID: 67858 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jim1348

Send message
Joined: 9 Jul 17
Posts: 54
Credit: 6,062,974
RAC: 1,624
5 million credit badge2 year member badge
Message 67864 - Posted: 2 Nov 2018, 16:42:33 UTC - in response to Message 67858.  

Stop doing the n-body units and try the regular cpu units instead.

I certainly will. I did not know there were any other CPU work units; I thought all the others were GPU. Thanks.
ID: 67864 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : "The handle is invalid. (0x6) - exit code 6 (0x6)" on Win7 64-bit machine

©2019 Astroinformatics Group