I think you mean the cloud version.  I have no experience with that, but your error would indicate that the login information is not valid.  Things may have changed but in the past the print agent account was IFSPRINT. 

Are you sure the firewall on this server is not blocking you?  Did you use the zip file from the system you are trying to connect, to build the agent?  If so are you sure the correct password was used the last time you ran a reconfig for that system?

Then when you do get the login working I think you need to add a logical printer.  Typically PDF_PRINTER is the queue for the application server to create the PDFs.  That requires a webserver to implement.

Hi @mwilson 

thanks for the input I tried the Print agent configuration by a direct database user IFSPRINT and the issue is still there for cloud versions it’s advised to use an IAM client with a database service user IFSPRINT or IFSPRINTAGENT.

There is no firewall blocking between DB and the MT server and print agent is from the same ‘add-on’ page of the instance. and I do not want to print anything here using a physical printer and just previewing is enough for testing purposes.

Unless some large shift occurred PDF Printer only works on the application server.  When previewing the PDF is passed to the client and does not go through the print agent.  The whole point of the print agent is to reduce the amount of network traffic between the client and the printer queue.  

Print Agent allows you to install this local to where the printer is.  The print agent logs in and grabs the PDF file from the database and sends a print to the local print spooler.  The PDF file is smaller than the PCL that goes to the print spooler and so reduces the network traffic and improves print times over slower connections.

At any rate you have an invalid login by the print agent and your batch2, which holds the application server jobs for printing, appears to be missing jobs.  Check your admin configuration help pages to setup batch2 jobs.

Hi @Ruchira 
Please try restarting the report pod.
When i say restart, delete the pod, it will automatically create the new one and post that you can try the same.
Let me know if this helps.

Thanks,
Hardik

Hi

Do we know what is the problem. I have just faced the same issue on 22.2.5.

As a workaround I have created another user by copy all settings from IFS_print_agent and connection is successfull. What is wrong with IFS_print_agent account? Changing sercret id does not resolve a problem with connection.

Hello,

The issue is with the missing queue in report message queues. If you add that queue(BATCH2) and restart the reporting pods, issue will resolve

please go to
*Solution Manager-->Reporting and Analysis-->Operational Reporting-->Setup Report Rendering-->Report Message Queues
*add the BATCH2 queue manually
*Restarted the ifsapp-reporting and ifsapp-reporting-ren containers
*Order a report and see if it works as expected.

Thanks,
Hardik
 

Hi @hardik 

I do not understand why queue setting is related with this problem. It does not work on standard build-in IFS_print_agent user but it works on AA_print_agent user newly created with the same setting as for IFS_print_agent user.