Question

IFS Print Service Errors

  • 22 October 2020
  • 3 replies
  • 1755 views
J
Rank
Badge +2

Hi All

We are on IFS Apps 10 and have recently tried to add a new logical printer to IFS. This is our first time adding a new printer. Our Application and Print Servers are separate to spread the load with the print server hosting all print and reporting services.

On our Print Server we have completed:

Installed the Printer Drivers and created a Print Queue

Updated the config file (ifs-printagent-config.xml)

Restarted the Print Service (IFSPAService_IFSL)

Within the Application we have:

Created the new logical printer with the same name/ case as the print queue on the print server and what is in the config file (e.g. TESTPRINTER1)

Attempted to print a report.

On the Print Jobs screen in IFS we get the following error:

“The Print Job can not be printed. The selected printer is not mapped to any Print Agent.”

When I check the Print Service logs on the Print Server it is full of errors similar to:

“[059] 15/10/2020 12:26:59: Registering...
[059] 15/10/2020 12:26:59: Failed to register!
[059] 15/10/2020 12:26:59: One or more errors occurred.
An error occurred while sending the request.
The underlying connection was closed: An unexpected error occurred on a receive.
The client and server cannot communicate, because they do not possess a common algorithm
[059] 15/10/2020 12:26:59: State changed: ERROR”

 

We have checked the TLS Settings on both the Print and Application Servers and they appear to match with both only having TLS1.2 enabled.

We were able to setup the printer successfully on the Test system but the Test system is just one server with Printing and Application on the same server so we did not encounter any issues with communication between the 2 servers.

Our Crystal Reports are run on the Print Server and they work without any issues so the 2 servers can communicate successfully.

 

Has anyone else encountered this issue before ?

 

Thanks in advance for any advice/ comments/ notes that can be provided

 

Regards

 

Jamie

 

 

3 replies

CallumW
Rank
Userlevel 6
Badge +15

Hi,

 

I don’t think this is it as the error would read: “Print job has no matching report formatter configuration” - but as you haven’t mentioned it in your steps above… 

 

Have you added the Logical Printer into the PROCESSING_PRINT_JOBS - Task Template?

(Solution Manager → Integration → IFS Connect → Setup IFS Connect → Task Templates → PROCESSING_PRINT_JOBS)

 

It only needs to be entered on the Logical Printer column and leave the Physical Printer column empty as your mapping is done via Print Agent.

 

Callum

Callum Wells - https://uk.linkedin.com/in/callum-wells
J
Rank
Badge +2

Hi Callum

 

Thanks for the suggestion. We have not set that up in IFS connect in either Test or Live.

Test works fine when we print to it, so I am not sure that we need to set this up for our use case.

The error seems to be linked to the print service itself being unable to register itself which then means that IFS can’t see the changes that we have made. I am not sure how the print service works/ communicates with the application. I am not sure how that is then complicated when it is across 2 servers.

 

Regards

 

Jamie

william.klotz
Rank
Userlevel 7
Badge +21

Hi @Jamie McNaughton ,

 

You mention after adding the printer to you test environment everything is working.   Is it possible the ifs-printagent-config.xml file from the test environment was copied to the production environment?

 

If so this would explain your issue because the URL and password information would be different.

As @CallumW  mentioned you do need to add the Logical Printer into the PROCESSING_PRINT_JOBS - Task Template.  If it’s not there IFS won’t send the job to the print agent for that printer.

 

You may need to unpack the ifs-printagent-config.xml file from the Zip file IFS creates for the print agents.  The ifs-printagent-config.xml file in the Zip file would take you back to the beginning then you could see if the registering issue goes away.

 

Regards,

William Klotz

Reply


Terms & ConditionsCookie settings