The laserfiche icon will not launch unless the user has admin rights
The laserfiche icon will not launch unless the user has admin rights
What does the user see if they are not a machine admin? What OS is this? What version of the Laserfiche client are you using? Does this represent a change in behavior, or is this something you are encountering after a new installation?
Laserfiche 10.4 Windows 10/22H2 - processes start over and over each time the client clicks on the icon but nothing happens on the screen - nothing appears on the screen Dell Precision 7780 - end up killing each task in task manager and rebooting machine - does work if user has full admin rights which is not a solution for us.
It sounds like the process is hung on something, though I can't think of what it might be. A process dump would be very helpful trying to troubleshoot this - I'd recommend working with your Solution Provider to open a support case, and they can help you to capture that dump and gather other system information.
Not sure if this is helpful at all
User gets message on initial long screen for app
Permission denied ,
access denied [9013]
I read you as saying that literally nothing appeared on the screen - like the application might not have even launched. But if that's the case, where is the access denied error displayed? Or is that dialog the only thing the user sees, and when they click ok they are left with nothing?
I wouldn't expect an access denied error at least until the user has indicated what repository they want to log into. Is it possible that it has automatically chosen one, and this message is about them not having rights to log in? If they weren't prompted for credentials, the only option is that it would be using Windows authentication, which could explain why the behavior is different depending on the identity of the user launching the program.
Often nothing appears on screen no spinning blue circle....etc....We did have one machine that specifically stated access denied after clicking the LF icon - only resolution for these issues has been to build out a freshly imaged machine, have the user logon and launch LF prior to copying over any profile data or installing any other user specific apps. These users can go to other machines that they have no profile on which LF is installed and launch it fine and access their repositories fine. Seems profile related but cannot pin point it . Luckily it has only happened to 4 or so users but is a major pain as we use MCM USMT too copy user profile data across to new machines- doing it manually is time consuming - do you know of anything that should be cleaned out of the users profile too resolve this issue?