I am really hoping someone can help me figure out this odd behavior in E10:
When user is printing Job Travelers, we have an old job that will print periodically print instead of the new job. This happens several times a week and has led to a lot of confusion when people are moving quickly. To be clear - the old closed job prints and the desired new job does not print at all. Here is what I’ve done so far to troubleshoot:
Intercepted the xml from System Monitor for the “wrong job” - the data is indeed for the OLD JOB. so this is not a printing issue. Note that it is the SAME old job that prints every time.
Reinstalled client on users computer. This behavior only happens for this user, which is probably noteworthy.
After the new client install, we are still experiencing the same issue. Any thoughts or wisdom?
I know you said you re-installed the client for this user who is experiencing this issue but have you also renamed\deleted the C:\ProgramData\Epicor\E10ServerName-808\ folder? I believe this folder holds some cached and temp files for the user for dashboards and reports, etc. Maybe if you rename\delete those temp\cached files on this user’s local system that will fix this problem?
That same thing happened to us for PackSlip printing it saved one particular packslip in the defaults and nothing else would ever print for that particular users, took me literally years to figure it out.
To clarify- if the user is printing Job Travelers from Job Entry screen, will clearing the defaults in the Job Traveler window make any difference? This particular user just got a new PC and this continues to be an issue so I’m assuming it doesn’t have anything to do with cache on C:
Correct, because these options are stored with the user in the database. Have them move to another PC. If they get the old slip, clear the defaults. It’s only for that user and that report alone. It’s really a low-risk operation.
Thank you both! I cleared the defaults and will be waiting in anticipation. This is happening quite often so I’m sure I will find out if the issue is resolved soon.
Holy cow, we’ve been having this problem with material tags for years. It happens so rarely that we haven’t been able to track it down. I will have to see if this works for that as well, unfortunately I will have to check all our MES stations.