You are viewing limited content. For full access, please sign in.

Question

Question

Word documents not being updated

asked on February 20, 2015

We have the environment of Windows 7 and Office 2013.  (In our previous versions of windows and office we had the same issue with only some of our users.)

 

Issue:  Users are wireless in a courtroom setting.  They open a Word document.  Within maybe 5-25 minutes they will update that document and close it.  They go back over to LF and open the next document to update.  Now they return to their office site, open LF and none of the documents they updated are in LF.  However they can see the updates when they open up the document.  (temp files)  So why... why... why are we now having a bigger amount of folks having this happen several times daily?  What are the configurations that we need to make sure are set for each of the clients?  And in the end... where are those temp files really saved?

 

Thanks


 

0 0

Replies

replied on February 20, 2015 Show version history

What version of the LF client and LF server are you running? We have had issues with older versions that are fixed in the latest hotfix. 
Please see: https://support.laserfiche.com/KB/1013588 "Laserfiche may incorrectly open an outdated local temporary copy when opening an electronic document. This issue is now resolved. (122476) "

0 0
replied on February 20, 2015

Hi Bonnie,

Electronic documents are stored in the Windows user's temp directory under a subfolder named with the document name and its ID.

C:\Users\[username]\AppData\Local\Temp\[DocumentName]_[EntryID]

We have been looking into reports of those temporary files not getting cleared out properly in certain situations which may lead to issues down the line when making additional updates. Laserfiche 9.2.0 had addressed a few situations and the upcoming release of Laserfiche 9.2.1 will address an additional one we found. My recommendation would be to upgrade to Laserfiche 9.2.1 when it gets released shortly.

As for what can be done now, can the affected users check their temp directories and re-import the files from there if they find it to be more up to date than the copy of the document that's in the repository, effectively replacing/updating the file? Then once that's done, clear out their temp directory of those files?

Regards

0 0
replied on March 10, 2017

Any known issues of this post this Hotfix?

I have a customer who had this issue previous to the upgrade and now is having the issue again in a latter 9.2.1 version.

I just upgraded to the latest version of 10.2 to see if this resolves.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.