Quote:
Originally Posted by Inker
Your database is corrupt.
Stop putting the database on the LAN, this is not supported and the most likely reason this happened, which is also why its not supported.
Seriously.
Thread closed.
Ok, lets see if we can have a civilised discussion without one person being aggressive and deciding it upon themselves to shut the thread down in less than 12 hours!!!! Way to go to make a relative noob feel welcome!
This is nothing to do with a LAN issue. As the original topic starter mentioned, his database is local, and even if the log shows a reference to a //**PC**/ LAN address, the router would tell the PC to look locally. Test this yourself, by copying a file from a local drive to another local folder using the "Network" path.
As for the database, had the thread been allowed to function for more than 12 hours, it would have been mentioned that this is not an isolated case. Many people on another forum have mentioned this, as well as some here, and this includes myself!!!
It has been narrowed down to the db3 format being the issue. If windows updates or crashes or for any other reason the machine is interupted while the db3 file is being written to, it will corrupt the file, period! the only way to tackle this permanently is to switch to SQL. On a temporary basis, take regular backups of the db3 file for TV Series and just drop it back in if it corrupts itself.
Any other people found a better solution?

Originally Posted by Inker
Your database is corrupt.
Stop putting the database on the LAN, this is not supported and the most likely reason this happened, which is also why its not supported.
Seriously.
Thread closed.
Ok, lets see if we can have a civilised discussion without one person being aggressive and deciding it upon themselves to shut the thread down in less than 12 hours!!!! Way to go to make a relative noob feel welcome!
This is nothing to do with a LAN issue. As the original topic starter mentioned, his database is local, and even if the log shows a reference to a //**PC**/ LAN address, the router would tell the PC to look locally. Test this yourself, by copying a file from a local drive to another local folder using the "Network" path.
As for the database, had the thread been allowed to function for more than 12 hours, it would have been mentioned that this is not an isolated case. Many people on another forum have mentioned this, as well as some here, and this includes myself!!!
It has been narrowed down to the db3 format being the issue. If windows updates or crashes or for any other reason the machine is interupted while the db3 file is being written to, it will corrupt the file, period! the only way to tackle this permanently is to switch to SQL. On a temporary basis, take regular backups of the db3 file for TV Series and just drop it back in if it corrupts itself.
Any other people found a better solution?