Hi @jzouaoui,

This looks more like a connection issue between the Middle Tier host and the Print Agent host. Do you have the Print Agent installed on the Windows Management Server or a separate utility server? If it is on a separate server, check whether there are any connectivity issues between the servers. You could also try to install a Print Agent on the Windows Management Server to see if you still get the same error. 

Please also upload the Print Agent log file that contains the full error.

Hope this helps!

Hello Charith  ,

1) the print agent is already install on the Windows Mgt server

2) When we stop and restart the print agent, it works for another hour.

Attached the  Print agent Log.

thank you :) 

@Charith Epitawatta can you help please :) 

Hi @jzouaoui ,

This has been identified as a bug in the IFS Print agent has been fixed in 22R2 Service Update 6

Thanks,

Kasun

latest update

IFS Fixed Version: 21.2.19 - 21R2 SU19, 22.1.14 - 22R1 SU14, 22.2.7 - 22R2 SU7, 23.1.0 - 23R1 GA, 23.2E.0 - 23R2 EA

/Shanaka

Hi @Shanaka Tennakoon 

Do we have any workaround for this error? In DEFAULT Report Print Task Template it isn’t easy to map logical printer to physical one due to printer drivers.

Hi @Kasun Balasooriya 

Would You able to provide any workaround of it or just send PrintAgent zip file with correction?
Our customer can not wait anymore. This is very crucial for customer business and restarting PA service evey 5 minutes is not a solution.

@Shanaka Tennakoon We have a customer on 22r2Su4 with the same issue. We soon have a Go live for this customer and dosn’t have time to apply the SU6. Does it exist a workaround for the issue that is possible to implement?

Kjell Åge

Hi @kjro 

URL from Add-On redirects to external page:

https://ifsdownloads.blob.core.windows.net/addon/IFSPrintAgent/22.2/22.2.0/IFSPrintAgent.zip

Please change “22.2.0” to “22.2.1” number in address to download newest PA version. It works without installation UPD7 itself.

Piotr