Hi,

Do you use Java based Print Agent or .Net based ?

For the Java based Print Agent, you can debug by starting the Print Agent in console mode.  Use the start script start_printagent_console.cmd and you will see traces on the console to help you to diagnose.

The Print Agent polls jobs from Middleware server at the frequency configured in the printagent_conf.xml file. So if jobs stays at the Waiting status, It’s certainly coming from the Agent himself.

Ensure you that all parameters in printagent_conf.xml are good.

Sébastien.

if the jobs are waiting that means they are stuck in managed server (report formatter). Check whether Batch2 queue is not stopped in setup ifs connect screen. If that is ok try restarting managed server. Next check whether both dequeue and enqueue is enabled in Oracle queues screen. Also check the status of corresponding application messages. Let us know the status. 

1. Check if the queue which the report formatter template (Processing Print Jobs in Application Server Task Template) is configured to is stopped in Message Queues in Solution Manger > Integration > IFS Connect > Setup IFS Connect
2.  Check if the Logical Printer that you are printing to is added in the report formatter template under Logical Printers section. You can leave the physical printer blank.
3. Check the states of the Application Messages for the print job in  Solution Manger > Integration  > Explore Application Messages > Your Queue. It will give you a hint if there is an error.
4. Check if any Application Messages in the above queue is in waiting state. If so try removing that.
5.  Check if the debug is enabled in the report formatter template (Processing Print Jobs in Application Server Task Template). If so disable it.
6.  Change the debug level in the report formatter template (Processing Print Jobs in Application Server Task Template) and save it.
7. You can also check the logs for any errors. Specially the j2ee batchprocessor, ifsalert, ifsapplog.
8. Check if IFSPRINT user is locked and password configured in the application server is correct.

My general reaction to Print status in IFS:

• Working - It is doing exactly that, and it should not be at this status long, so refresh!
• Waiting - Print has not got past the internal stuff yet (See ChanakaAmarasekara good points above).
• Remote Working - IFS is waiting for the Print Agent to accept the job. We would usually see this is the Print Agent is down (Usually because Java has automatically updated itself to a new path and the agent is not happy etc...).
• Complete - Its done!….or sitting in a Windows Print Queue for another bunch of reasons.

:)

Hi Rusiru,

Print job has error  “No matching report formatter configuration.”

Thanks & Regards

Shitanshu

Check if the Logical Printer that you are printing to is added in the report formatter template under Logical Printers section. You can leave the physical printer blank.

Hi Chanaka,

Logical printer is available in report formatter and physical printer is blank.

Thanks & Regards

Shitanshu Sharan

@shitanshu sharan If you added the Logical Printer configuration now, then you will have to do a reprint. If you already had that when printing, then the job should not go to that error state. Check if you are redirecting it to an External Report Formatter (you will find that at the top of the report formatter template). If so, connect to that URL and see if the logical printer mapping is done. 

Also check if there are any report rules that change the printing to a different Logical Printer, if so try adding that Logical Printer as well.

If that doesn’t help can you attach screenshots of the report formatter template, print manager with the error, and the application message details.

What about status “INACTIVE” in print jobs?

Hello All,

What does the status INACTIVE means here?

I have a situation for one customer, print jobs are getting into INACTIVE state first time
and when i restart it manually, job is getting printed via Print agent.
Any help here is appreciated, what can help me resolve this?

Thanks,
Hardik

Hi, 

I have the same issue as @hardik - did you ever find out what the INACTIVE status meant?