Open Source Document Management System | OpenKM

Hi Folks

Uploading a document in a folder (already populated with variuos files) as okmAdmin user, the uploading failed and while all the files already there disappeared a screen with this error it's present whenever any user try to oper or access to this folder.
What can be appened?

OpenKM Version: 5.1.8 (build: 7363) with MySQL database
Windows XPpro SP3

Error has been originated in documentService and the cause is the path has not been found.
Could be caused because you're trying to uploading a document to a folder that not exist, other user has moved / deleted or changed permissions meanwhile you're trying to uploading. remember several users acts with openkm, and you've got a static view, each time you make some click this view refreshing - that's the idea - and could be the origin of the cause.

If happens other time, take a look at server.log that contains more information about what could happened. If you've lost a folder take a look at trash .. if no found it some user trash ( search with okmAdmin user who has accessing to al user trash ) then take a look at activity log ( all user operations are registered there and you'll discover who deleted it ).

Hi
thank you for te replay;
Actually i'm the only user of the system so it's 100% sure that none else has deletes the prevoius existing files in that folder before the failed upload.
Meanwhile was impossible to export the repository (the operation give an error) until the folder was deleted.
Since now i'm testing this system and everything was working perfectly, but now i'm quite worried because what it's appened (few existing files disappeared in failed upload) can appens for thousands of files!!!


P.S. a daily backup will prevent this kind of nightmare

That's not normal, here has been other problem. Deleted files always going to trash if are not directly deleted by administrator with advanced repository tools. Could happens a hard disk problem ( strange but possible too ). Really in this system should be done some respository test integrity.
Can you take a look at okm_activity table in order looking for your lost files ... do you have any name ? and take a look trace what could be happened, really uploading files is not possible losing information.

Hi
any operation made on the focused folder (upload and/or deleting and even repository export) showed me a "error in repository" or "file already exist" (but not show), so i decided to export the entire repository and restart with a fresh installation and let OpenKM working with the Hypersonic database.
I hope to have better luck than using MySQL!!!

We always install OpenKM + MySQL for our costumer, so I'm pretty sure there is no issues with this database. The problem may be due to a installation or configuration issue, or another problem. Please, attach the servler.log (zipped, please) to see what happened.

I'm sorry for delay....
Here attached the server.log of 5 days (don't be afraid: it's very little activity )


P.S. trying the last chance to reindex the database (following wiki istructions), OpenKM doesn't start anymore. I saved the entire directory just for future studies.

from Wiki:
REINDEX
Stop JBoss
Delete $JBOSS_HOME/repository/repository/index and $JBOSS_HOME/repository/workspaces/default/index directories
Start JBoss again

This is the windows that appearing after the login

This only reindex lucene archives, there hat not relation with Mysql.

Did you made any OpenKM upgrade ?

The version with i was working wad 5.1.8 upgraded from 5.1.7.
After this trouble i've "freezed" the entire directory because it's impossible to do anything (see last screenshot i've uploaded).
I use to save all my automatic scanned document (tif) before proceding to pdf conversion to upload in OpenKM and so i did rebuilt the 90% of the database in a new OpenKM 5.1.8-2 upgraded to Version: 5.1.9-SNAPSHOT (build: 7416) installation, (the rest of documents they where docc, jpg and others). By the way i've lost some metadata and versioning.

I can't guess what happened to your repository without see a bunch of logs, and even in that case I don't know the configuration step you did. This is a good reason because costumer want support.