corrut database durring 6.7.24 to 6.8.7

[enamelrod]

trying to upgrade to version 6.8 and i got a database corruption error because conversion failed! what do i do next?

[jordansparks]

I'm guessing you didn't let it run long enough and you thought that it had hung when it was really still in the middle of the conversion? Or did it just suddenly fail on you? Either way, restore a COPY of a backup. Then, if you just need to give it longer, run the conversion again. If, instead, it suddenly failed on you, look at the details of the error, and copy the entire thing so that you can tell us what the error was.

[enamelrod]

no sorry, it stopped and said your database is now corrupt call open dental. i took the copy and tried to restore it. when i run od it continues then says conversion failure. SO i took the copy put it on another machine with mysql and it thinks the old machine is still running its upgrade.

[jordansparks]

Do you have a tool that you can run this query in?
UPDATE preference SET ValueString='' WHERE PrefName='UpdateInProgressOnComputerName'

We'll need a copy of that database that didn't convert properly.

[enamelrod]

ok jordan i figured this one out. And i have talked to you and nathan about this before. when i go to update it downloads the latest copy to my linux server but all the workstation computers thinks its on a different version. the manifest on the workstations vary and are reading 6.6.21-6.7.24 and the server has version 6.8.7. after running the database integrity tool it corrected the errors and it took 20minutes to upgrade but it worked. now i think i should remove all the copies and folders from the workstations and do all new installs.

[jordansparks]

Some sort of security issue with the manifest file on the server? This may be a good enough reason to switch to a Windows 'file server' or an embedded Linux NAS so that you don't have to deal with permission issues. I don't know.