cancel
Showing results for 
Search instead for 
Did you mean: 

Print requests still wants to print to deleted instance Dialog Instance

Former Member
0 Kudos

Print requests still wants to print to that instance and to /MSI/RUNNING_FILE20 . on Dialog I had an Dialog Instance host "bomcrn_GR_56" after beeing deleted

In "spad" it is not any more an device type /MSI/RUNNING_FILE* like many on other server.

also in "spad" there is no more "bomcrn_GR_56" as spool server.

What could be the reason

Accepted Solutions (1)

Accepted Solutions (1)

nelis
Active Contributor
0 Kudos

Take a look at the owner running the job(SM37) that produces the spooled data(assuming it is a job). Likely he or she still has that device setup as the default in profile or the job itself is set to send data to that device/instance, even though it no longer exists.

Nelis

Answers (3)

Answers (3)

aidan_black
Active Contributor
0 Kudos

Hello,

Which output devices are these spool requests created by. You can check this by double clicking on the spool in SP01. Then check the definition of these output devices via transaction SPAD. If these output devices are still defined with the spool server "bomcrn_GR_56", you need to change it.

Regards,

Aidan

Former Member
0 Kudos

Hello Juan.

request are comming from jobs. BUT four print request running on "vorna_GR3_56" finished ok the other (also running on vorna_GR3_56" did not finish ok(i.e it had in sm37 (althouth finished(job) spool in waiting and spool server vas "bomcrn_GR3_56"

Preaviously bomcrn was part of GR3 system but now it is part of GR2 system with sysnr 25.

Hello Nelis

Your idea is very good but he run 5 jobs(maybe that was some kind of problem) and 4 of them finished ok(the devices are built in transaction which generates load)

JPReyes
Active Contributor
0 Kudos

Where is the request coming from?.... it might be hardcoded in some program

Regards

Juan