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

Question

Question

The current folder/document could not be determined. The client is not running.

Snapshot Laserfiche
Updated January 31, 2022
asked on January 3, 2017

My client is getting this error when trying to use the Current Folder token when printing through snapshot. Laserfiche is visibly open but snapshot doesn't seem to notice. I have ran a complete reinstall and made small changes to snapshot defaults just to be sure it wasn't some saved profile issue. We have also restarted the computer but no difference. Has anyone else gotten a similar error? They are on version 9.0.3.798.

Snapshot Error with LF 1.PNG
Snapshot Error with LF 1.PNG (37.11 KB)
Download
1 0

Replies

replied on January 4, 2017

I tried this with the 9.0 client and it is working for me. It could be a security issue, such as DCOM security, preventing Snapshot from accessing the LF client to get the current folder. Just to be clear, the LF desktop client is running in the same Windows session as Snapshot?

0 0
View 3 previous replies
replied on January 5, 2017

Correct, they are both running on the same machine, on the same instance, at the same time.

0 0
replied on January 5, 2017

One possibility is that UAC is preventing Snapshot from communicating with the LF client. Try temporarily disabling UAC and check if that resolves the problem. 

0 0
replied on January 6, 2017

Just checked and they already have UAC disabled. Should I create a case at this point?

0 0
replied on January 6, 2017

Yes, I can't think of any other troubleshooting ideas.

0 0
replied on November 15, 2019

Hello,

 

What was the resolution to this issue?

0 0
replied on January 31, 2022 • Show version history

I am having this same issue. The current folder/document could not be determined.  The client is not logged into a repository.

I am definitely logged in.

Seems to be intermittent for me as well as for some of the other users.  It was working for me on Friday, now today, Monday - I get the message again.

It is now 2022 (original post was from 2017).  Does anyone know what causes this?  Something simple I am sure that I am overlooking.  Any help would be great.

Thanks!

Christine

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...