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

Question

Question

Permission denied. An error was encountered importing. Retry?

asked on May 29, 2019

Has anyone seen this error message?

We upgraded LFR to 10.2 and some users are experiencing this error. It occurs when a user attempts to extract one page of an existing document to create a new document. Previously, users could drag and drop a page anywhere in the client and it would create a new document.

Any suggestions on how we can remedy this scenario?

 

We do have a case open, but resolution isn't coming quick enough and this impacting daily processes.

 

Thanks!

LFR Error.jpg
LFR Error.jpg (23.26 KB)
0 0

Replies

replied on July 21, 2020 Show version history

I just ran into this issue today, after working with LF for 4 years. The issue ended up being that the document in question had other documents linked to it that resided in another area of the repository. You can see if it has linked documents in the metadata window pane under the "Links" tab. We had to grant the necessary Access Rights for the user for the location those "linked" documents were. Once we did, we could split pages and create new documents.

 

This was on LF 10.4.2.

1 0
replied on May 29, 2019

Which specific version are you running for the App server, and for the Client?

0 0
replied on May 30, 2019

Hi Jason,

Thanks for the response!

Server 10.3.1 Update 2

Multiple Clients 10.3, 9.2 10.1

0 0
replied on May 30, 2019 Show version history

Out of curiosity, are the errors occurring on all of the clients?

Awhile back I had a user who was getting all kinds of weird errors and I found out she was running a version 9 client (we were on 10.2 at the time).

After I updated her client everything was fine.

My experience has been that the farther out of sync they are with the server version, the more susceptible they are to random issues.

We had most users on 10.1 client when we were on 10.2 and had no issues, but there are much bigger changes between full versions as opposed to updates.

0 0
replied on May 30, 2019

Yeah, it's weird - it's not happening on all of the clients. In fact, some of the employees who are on a more outdated version of the client aren't experiencing the issue, while employees with more recent versions are experiencing the issue.

I'll see if I can get our team to get everyone on the same version and see if that helps.

0 0
replied on May 30, 2019 Show version history

I would definitely try to look for the common threads if it is only affecting some users and not others. A standard client version helps eliminate troubleshooting variables.

For example, have any of the users with the problem tried a different PC and vice versa? This would help determine if it is a user issue or a PC issue.

0 0
replied on May 30, 2019

Thanks for the suggestion Jason, I appreciate it!

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

Sign in to reply to this post.