IFS 10 Reports stuck in status Waiting

How is your Print Agent configured?  It will only pick up jobs that it is configured for, and print them to the relevant physical printer associated to the logical printer.

If you take a look in the ifs-printagent-config.xml file in the Print Agent location, my guess is that you don’t have this Logical printer included, with no Logical to Physical printer mapping defined.

The other option is that the Print Agent may not be running correctly as expected, e.g. if it has incorrect URL or encrypted password value.

HTH,

Nick

Hi ​@NovJohanL, 

Could you please check the application messages to see if it creates one with the type ‘REPORTING’? If it’s in the status ERROR, what’s the error message it’s throwing?

Thanks and best regards,
Himasha Abeywickrama

Thanks for quick reply.
The Print Agent is up and running, looking for jobs.
It’s configured with the logical printer called SFSL, and supposed only to print delivery notes and pick lists.
Printer driver is installed on the server and printing a test page works.
Login with IFSPRINT works from sqlplus.

I have purged print_job_tab a couple of times, and right now there’s only job 7517 with status “Waiting” there. The application message for job 7517 has status “Released”.
Older messages are still there and some of them has status “Release” and others “Processing”.
 

Still check the Print Agent config file to make sure it looks right.  Normally I would expect it to show the Logical and Physical printer info.  The PrintAgent config screen you provided doesn’t seem to show that.  For example, here’s a snip from one of our config files in Apps10:

Also, your “Setup IFS Connect” screenshot doesn’t show a physical printer mapped there either.  I’m not 100% sure if it needs to be, but ours does, and I would think that if a Logical printer was included there then it would need a physical to be included too… in our case we have mappings to explicit ports and IP addresses for network-printable printers.  Example:

One final thought: I would also note that I don’t believe that a Logical Printer needs to be included in the PROCESSING_PRINT_JOBS setup screen to be used by a Print Agent.  The Print Agents we use don’t have many (any?) logical printers that are listed in the PROCESSING_PRINT_JOBS config screen.  As an example, the SPARES.01_LATER shown above in the first screenshot is not included in the list under the setup for PROCESSING_PRINT_JOBS.

Hi ​@NovJohanL, 

Could you please check the application messages to see if it creates one with the type ‘REPORTING’? If it’s in the status ERROR, what’s the error message it’s throwing?

Thanks and best regards,
Himasha Abeywickrama

I have purged print_job_tab a couple of times, and right now there’s only job 7517 with status “Waiting” there. The application message for job 7517 has status “Released”.
Older messages are still there and some of them has status “Release” and others “Processing”.
 

 

If I create a new report for the print agent, the application message stuck with status “Processing”.