Hi experts,
I'm not sure if it's a spool or a job problem - but because the error message points at problems with spool requests I opened this discussion in "Output Management".
After system copies in one system landscape we face the problem that the spool requests of one special job (some kind of Z-program) is getting corrupted somehow - this hasn't always been that way - it happened for the last 5-6 copies.
The job runs for some time and aborts then - the job log contains the error message "Device type HP4250 for request 24.853 does not match current device" where HP4250 is the (correct) device type for the printer of spool number 24853.
When you delete that spool request and restart the job it aborts at the next spool number that was created in the first job execution.
Only if you delete all spool requests that were created during the first aborted job execution the job can run again with the same parameters like before (same printer, same program, same device type...) .
Of course we reorganize the spool after system copies (RSPO1041) and clean up inconsistencies (SP12).
And for this is affecting only one job it doesn't seem to be a general problem.
Usually that happens right after the system copy and with the first execution of that job - weird enough. But today it occurred 1,5 weeks after the system copy and after several successful job executions which seems even stranger.
I couldn't find anything concerning this error message via SAP Marketplace or anywhere else.
Has anyone of you ever faced a problem like this? Could you find a solution to it?
Many thanks and best wishes
Marie