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

Question

Question

Access denied on check out

asked on December 14, 2016

User gets a 9013 Access Denied error on check out.

User installed MS Office integration for Google Chrome – no problems

User went into LF Web Access and checked out a document.

During check out it gave him a 9013 error Access Denied but still created the network folder containing the document.

User saved document in network folder and got a 9013 error on the save but it completed the save of the document.

User checked in document and after putting in version comment it gave him the 9013 error and the document remained checked out and the network folder remained untouched.

Did not try to undo the checkout as user or admin

I had this user come to my workstation where he logged into LF Client.

User went to the checked out document and was able to check it in successfully.

               It did not however ask him to ‘clean up’ the network folder where the checked out copy of the document had been.  This was manually deleted.

 

0 0

Replies

replied on December 19, 2016 Show version history

Additional information on this issue.  User continues to get the 9013 error when attempting to save the document and on the import of this document.  It also applies to any documents imported in the first 'batch' of documents in this folder.  He can successfully check out, modify, save, and check in a document created in a later batch.

Users in the same group, with the same feature and effective rights as this user, can successfully checkout, save, check in documents regardless of batch.

I have deleted this user from LFDS and allowed the scheduled sync to re-add him and this still continues to happen.

Looking for some guidance on next level of triage.

0 0
replied on December 21, 2016

How is this user importing his document? From Word via the office plugin? What happens if he drags and drops the document into the client?

0 0
replied on December 21, 2016 Show version history

Documents were originally imported into Laserfiche via drag/drop into a non-versioned folder.  The documents' templates were then updated and the documents were moved to a versioned folder.

This user is checking out documents via LF Web Access he is not importing them.  When he is checking documents back in he has done so via the Office plugin in Word AND via the Check-in option in Web Access.  Both result in the error.

Interesting point is that these documents are being imported.  Other users are able to take the revised copies that were resident on the network and replace the older version that is in Laserfiche (increasing the version level of course in the process.)

0 0
replied on December 23, 2016

What happens if he opens the thick client and checks out the document? Does it error on the save back then?

0 0
replied on December 27, 2016

When logged into thick client, user is able to checkout and save document without error.  Thick client was also located on my laptop, not his.  Since use of Web Access was to be standard for all but power users, it was not deployed to all team members.

0 0
replied on March 30, 2017

Michelle,

I believe your server is having a larger issue than what you are seeing here. What are the chances of testing on a new DB or VM?

Regards,

John

0 0
replied on March 31, 2017

John,  yes testing on a new VM is possible, in fact, we're having one setup for testing now.  I will let you know when it's ready and we've gotten testing done.

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

Sign in to reply to this post.