we are using the "one-touch" scan operations to scan to a network folder.
For example customer A has a button on the screen
customer B has another button on the homescreen, and so for each customer.
If you choose customer A, scan's go to networkfolder A (another scan profile specific for this customer)
If you choose customer B, scan's go to network folder B (another scan profile specific for this customer)
and so one for all customers...
we have once in a week that some people scan to for a customer and that the files are in the folder from another customer. All other times, every scan goes well, only some times in a week. We have +/-75scan's a day on this machine.
We already double checked all setings in the one-touch actions and the scan profiles.
If the problem should be a setting, it should be always wrong... but it isn't so we think about a bug or another problem?
Xerox 7830 machine is on version: 071.010.034.06000
Please let us know if this is a well know bug/problem ?
I would call Xerox and get a tech to upgrade your device. But there are caveats:
The newest firmware is a whole new version called "Connectkey 1.5" 072.010.104.14800
It is *highly* suggested that it is done as a "Forced Altboot, no data backup, no clone" which means an entire wipe, and set it back up manually as some settings just don't play well with the update. So the only thing that could be restored would be the address book, just export it, wait for the tech to finish, and then import it back onto the device. But everything else would be better if it was typed back in manually from a printed configuration sheet from before the reload.
I have seen reports of what you are seeing before, but not very often, typically it can be replicated if you very quickly scan to one location, and while that scan is running, quickly pick another and do another scan. What will happen is that even though you changed everything on the screen, it appears something in the back-end does not update quick enough and the repository does not change until *after* the scan goes through.
Any firmware this was seen on also showed an issue where if you pick a one-touch and select the "Clear-All" button you would see the scan defaults re-appear for a few seconds (Mostly only noticeable if you changed the default file name, you would see "Doc" briefly return.
" It is *highly* suggested that it is done as a "Forced Altboot, no data backup, no clone" which means an entire wipe, and set it back up manually as some settings just don't play well with the update "
They already did that for some other problems on one unit and the result was, " a lot of other problems, things not configured, things mis-typed, clients getting automatic scans from other clients, etc etc"
I already called them last week, responsable technician Xerox BE comes over in September.
"Any firmware this was seen on also showed an issue where if you pick a one-touch and select the "Clear-All" button you would see the scan defaults re-appear for a few seconds (Mostly only noticeable if you changed the default file name, you would see "Doc" briefly return. "
About this problem, finally somebody who could confirm that this is a Xerox problem !
With Ricoh we never had this problem, you understand that this is a big problem if some customers receive papers from others if they are competitors...
Is this problem also sovled with the newer firmware version?
Yes, it solves the issue with the One-touch and the "clear all",so it may fix your issue, which seems realisticly to be related, but I obviously can't guarantee anything.
As for the ALTBOOT, there are 2 kinds of ALTBOOT, forced and regular, with the Forced altboot no data backup no clone the machine will be in out of factory condition, nothing will remain, the entire setup will need to be done manually, it sounds like you had a regular ALTboot, and most probably someone put a clone file on it, which does not work, because the 2 firmware levels are vastly different. A clone file is supposed to be used on same device same firmware, I fully understand why people try it in other circumstances, but in this case, they cannot be used, they will cause the exact type of issue you listed.
Think of it like a Windows Computer, you *can* upgrade Windows 7 to Windows 8, but to get a smooth and reliable install, you should really just wipe it out and start over.