The last few days I get the error "Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE: General error: 1 Can't create/write to file 'C:\WINDOWS\TEMP\#sql_39c_0.MYD' (Errcode: 13)' in H:\GedView\includes\classes\class_pgv_db.php:835 Stack trace: #0 : PDOStatement->execute(Array) #1 H:\GedView\includes\classes\class_pgv_db.php(835): call_user_func_array(Array, Array) #2 : PGV_DBStatement->__call('execute', Array) #3 H:\GedView\includes\functions\functions_db.php(762): PGV_DBStatement->execute(Array) #4 H:\GedView\includes\functions\functions_mediadb.php(353): fetch_linked_fam('M1872', 'OBJE', '1') #5 H:\GedView\media.php(851): get_medialist(true, 'media/Bilder Pe…') #6 {main} thrown in H:\GedView\includes\classes\class_pgv_db.php on line 835"
This never occurred before. What to do? Thanks for any help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you check the integrity of your OBJE M1872 ?
Is it corrupt? Why not copy the image file elsewhere and remove it from the server and delete the MEDIA OBJE?
Then add it back again as a new, linked OBJE to wherever you had it linked/attached.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The actual error is that the file C:\WINDOWS\TEMP\#sql_39c_0.MYD can't be created or written to. This error is completely outside PGV, and is not a PGV problem.
If PGV worked OK previously and this error has just started to appear, you need to verify that the directory C:\WINDOWS\TEMP is fully writable by all users on your Windows computer. You should also verify that the named file does not exist and that you have not run out of hard drive space.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The directory C:\WINDOWS\TEMP is wide open for all users but the error persists.
The note about checking OBJE M1872 perhaps revealed the reason for the error: Lately I created two other GEDCOMS in PGV and linked some of the existing media-OBJE to INDIs in these new GEDCOMS. I think this doing messed the whole thing up.
I killed the new GEDCOMS but the error still appears in logged in mode only.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
elf
Did you export a copy of the GEDCOM and do a search for M1872 ? You may still have an unlinked or strange/corrupted pointer. You may need to re-import the exported (downloaded) GEDCOM to clear this from the database. You might also use phpmyadmin to search the DB for this pointer, M1872, to see what references it has recorded, but if you don't understand the DB, or the GEDCOM standard well, you may only do more damage. -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stephen
Thanks again for your help. You did put me on the right track. phpMyAdmin was an enormous help in clearing all these incorrect links within the DB. But I still ask myself how this mess could happen.
EJF
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The last few days I get the error "Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE: General error: 1 Can't create/write to file 'C:\WINDOWS\TEMP\#sql_39c_0.MYD' (Errcode: 13)' in H:\GedView\includes\classes\class_pgv_db.php:835 Stack trace: #0 : PDOStatement->execute(Array) #1 H:\GedView\includes\classes\class_pgv_db.php(835): call_user_func_array(Array, Array) #2 : PGV_DBStatement->__call('execute', Array) #3 H:\GedView\includes\functions\functions_db.php(762): PGV_DBStatement->execute(Array) #4 H:\GedView\includes\functions\functions_mediadb.php(353): fetch_linked_fam('M1872', 'OBJE', '1') #5 H:\GedView\media.php(851): get_medialist(true, 'media/Bilder Pe…') #6 {main} thrown in H:\GedView\includes\classes\class_pgv_db.php on line 835"
This never occurred before. What to do? Thanks for any help!
Try deleting everything in the "C:\WINDOWS\TEMP" directory. You might need to start Windows in Safe mode to do this.
Thanks for the good idea but unfortunately it did not help. Any other suggestions?
Did you check the integrity of your OBJE M1872 ?
Is it corrupt? Why not copy the image file elsewhere and remove it from the server and delete the MEDIA OBJE?
Then add it back again as a new, linked OBJE to wherever you had it linked/attached.
The actual error is that the file C:\WINDOWS\TEMP\#sql_39c_0.MYD can't be created or written to. This error is completely outside PGV, and is not a PGV problem.
If PGV worked OK previously and this error has just started to appear, you need to verify that the directory C:\WINDOWS\TEMP is fully writable by all users on your Windows computer. You should also verify that the named file does not exist and that you have not run out of hard drive space.
Hi, thank you all.
The directory C:\WINDOWS\TEMP is wide open for all users but the error persists.
The note about checking OBJE M1872 perhaps revealed the reason for the error: Lately I created two other GEDCOMS in PGV and linked some of the existing media-OBJE to INDIs in these new GEDCOMS. I think this doing messed the whole thing up.
I killed the new GEDCOMS but the error still appears in logged in mode only.
elf
Did you export a copy of the GEDCOM and do a search for M1872 ? You may still have an unlinked or strange/corrupted pointer. You may need to re-import the exported (downloaded) GEDCOM to clear this from the database. You might also use phpmyadmin to search the DB for this pointer, M1872, to see what references it has recorded, but if you don't understand the DB, or the GEDCOM standard well, you may only do more damage.
-Stephen
Stephen
Thanks again for your help. You did put me on the right track. phpMyAdmin was an enormous help in clearing all these incorrect links within the DB. But I still ask myself how this mess could happen.
EJF