-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -

Create an account on the HP Community to personalize your profile and ask a question

06-01-2020 01:01 PM
Hello All!
Been trying to assist with a Quickset issue. Client just bought 15, mixed bag of E778 and E876 units. Trying to make quicksets.
Authentication is being used.
When they hit "send" they get two errors, one overlapping. The top one is the one asking about retaining settings. Once that has been cleared by answering Clear or Retain, the lower one shows up and says, "The user has been logged out".
HOWEVER, the scan creates a .tmp file in the target folder.
Used the HP guide and went over it a few times. It all looks fine. Anyone see this error? And how did you fix it?
Thanks in advance!
06-01-2020 02:15 PM
Hey GaryL1, I haven't seen this issue before, but the first thing I would try is changing the default retain settings in EWS. I would try setting it to clear first.
Description: This prompt happens after an end user does a copy, scan or fax job. It asks if the end user wants to do one of the following:
Cancel Job - This will cancel the current job they just initiated
Clear - This will start job but clear any settings they entered taking the screen back to default
Retain - This will start the job and keep all settings entered for the next job
Location: The setting to change this can be found in the Security tab, Access Control section. You will scroll down on the page towards the
bottom in the Job Behavior area. Default Retain Settings Behavior.
06-04-2020 05:54 AM
The client is using MyQ as a doc management app. Somehow it has taken over control so that even using the unit (in the test unit, it's an E778) as a GUEST outside of the app to do a scan, the app somehow forces the machine to try to log in to the MyQ server for authentication. Since guests have no credentials, it throws them out. We have tried to disable the settings in access control that relate to scan and reset them back to Default from the app without success. Their developers say they have a solution today. Will update.
