This is to request support please on the following case that I expose below: In one of our clients, an App of the Studio App was installed, which was Scan to folder. it is generates an error on the screen and they are for two reasons:
1) It does not scan through the glass
2) By repeatedly hitting the Start button (green)
When this error occurs, it generates templates of .XST format and does not send the scanned document, this means that each time the error occurs it will create this "Garbage" template. Several procedures were done such as, reinstalling the app, and updating the firmware to a newer version and the result was the same.
Discarding also was scanned locally and it did not give any error.
Version Firmware: 073.060.197.28500
machine: WC 3655
app to install: Scan to Folder (app Studio)
Thank you for the message.
The generation of the .xst template file is an issue that we are aware of. We have a defect in the system that will address the cleanup of these files. As you have noted, these files are only created in cases where there is an error during the scan. There is a workaround for removing the unwanted files that can be used until we have this resolved. There are a couple ways to manually remove them: 1) the files can be removed from the device by selecting and deleting them from the Scan tab of the device CWIS or 2) from the Completed Jobs tab on the Job Status screen at the device.
I also have a thought that might help with the Scan to Folder error that the customer is experiencing (the root cause for the .xst file generation). I am going on an assumption that the customer is using a CK device. The CK device wants the username entered in a certain format. Could you have the user try placing a slash (/) in front of the username, please? Does the printer produce a printout following the scan failure? The printout should be titled something similar to “Workflow Scanning Confirmation Report”. If this printout exists, would you be able to tell me what error is being generated by the device? The error is in the upper right on the Confirmation Report. The error that is returned might help us pinpoint the cause of the error. Note: The device might be set to not print a report on failure and that's okay.
I think that the credential mismatch might be the reason why scanning from the glass is not working. I tried this in our lab. I removed the slash from the username and scanning did not work from either the glass or the feeder (From the feeder the page was pulled in and scanned, but was never sent to the repository.). Once the credentials were entered correctly, I was able to successfully scan to a shared folder from both the glass and from the feeder. The "Unexpected Error” that the customer experienced did not display on screen at the device during my test. So, it is very possible that the underlying cause may be something different. Please let me know if adding the slash to the username does not correct the issue and I'll continue to investigate.
I hope that this information is helpful. Please let me know if any additional questions/issues come up.
I have similar error from Scan to folder by FTP (created by App Studio) with Versalink B405, It works correctly at the beginig but when you push the button Start scanning on the device, the device doesn't scan and show the error, and the scanner never works again in this way...
Unexpected error while send the job to scan
Try to resend the job, press start to resend
The message in the screen capture below can occur if the file to scan is not seated properly in the feeder or the device couldn't properly detect or scan the file for some reason. I recommend removing the file from the feeder, exiting the app and selecting Reset on the device Home screen. After that, re-seat your file in the document feeder, relaunch your Scan to FTP app and try your scan again.
If the Start button become unresponsive, as you noted, open and close the top cover (as if you were placing a file on the glass). After that you should be able to scan without any trouble. Did the Unexpected error occur before the Start button stopped working properly? This can happen after an error has occurred on the device.
I hope that this information is helpful. Please let me know if the issues are not resolved and I will investigate further.
I also experience a build-up of those "auto created" templates when using either a "scan to folder" (AppStudioSMBScanxxxxxx.xst) or "scan to multi destination" app (AppStudioHTTPScanxxxxxx.xst).
The machine in question is either a WC6655i or WC7855i on the latest ESS 073.xxx.048.15000.
For me the issue even occurs when the scan is filed correctly.
What I noticed though is that the auto created template of the first scan is deleted from the machine just fine as long as the status in the app (just beneath the soft START button) is shown as "job xxx succeeded" before initiating the next scan.
If one starts a new scan during the status "job xxx processing" by selecting the start button on the machine's hard keyboard, the app creates a second template which will get deleted after the scan finishes ("job xxx succeeded"), but the first template will stay in the template list.
So if one does a lot of consecutive scans (e.g. N scans) while prior scans are still processing, one will end up with (N-1) auto created templated stuck on the machine with the only option to manually delete those through CWIS.
The second thing I noticed is that the green scan button within either "scan to folder" or "scan to multi destination" app does not work on WC6655i, WC7855i or even Altalink C8070 (all on latest SPAR).
One can work around that problem on the CK2.0 devices, but on Altalink there was not even the option to show the soft keyboard and therefore I was unable to scan with both apps.
Is there any plan to solve this issue yet?
When do you expect a solution?
Thanks in advance,
Technical Architect / PreSales Support
Xerox GmbH, Germany
Thank you for the post.
The team is planning to have a new release available within the next couple of months. This new release will off a completely new platform (redesign and infrastructure). With the release, all of your existing Template apps will be migrated into the new platform. So, they will continue to work as always.
However, the new system will likely resolve the issues you describe here. You will need to create new Template apps after the launch of the new platform to take advantage of upgrades and potential solution to this scanning item. Keep an eye on this forum. An announcement will be posted when the new release is available.