I have lot of clients that can be used as destination for scanning feature. I have only 1 client with windows 10. In this case, when I try to scan to shared folder, I got an error. I have never seen an error like this: "Job cancelled for lack of resources" (it is a translation from italian "Lavoro annullato per mancanza di risorse".
I really cannot understand the reason of this error.
Does anyone has an idea how to solve my problem? My firmware version is 061.121.226.01300
Welcome to Windows 10.
No matter what is working on other machines and other OS's. Use the (case sensitive) login name exactly how it appears inside the brackets when you add the specific user here:
And be sure that the folder shared for scanning does not reside anywhere within the Users folder structure ala C:\Users
Best is to put it on the root and send a shortcut the Desktop or Documents folder within the Users Library
Thank you for your quick reply. In this case I got a login failure error.
In windows 10 security tab I have:
The path is "C:\scan" and the share name is "scan".
In xerox configuration page, in share name, I have "scan" (lowercase) and path "\".
So, using email@example.com in xerox configuration page, I got failure login error, using mydomain\scanner I got the previous error....
I'm going to be crazy trying to solve this issue :(
EDIT: I noticed another strangeness. When I got "Job cancelled for lack of resources" error, *sometimes* a subfolder is created in shared folder, which name is DOC.LCK. There is a file named LOCKINFO.DAT that contains this text.
In some cases, even if an error page has been printed, the document was scanned successfully.
ok, when you have the lock files, and not the pdf itself, you are in the good direction :) seen the same behaviour on other machines
disable lock files on the machine by going to this page, and disable it, reboot afterwards
I tried to follow your suggestion, but it does not work on my case. The scan fails as usual, in this situation without creating temporary folders.
I really don't understand why.
I have another update: we bought a new laptop identical to the client that has issue scanning. In this case the scan feature works as expected! Also in this case we have windows 10. So the issue is not related to S.O....