outlook + PCL6 print does not work

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • boutn
    Senior Tech

    500+ Posts
    • Jun 2016
    • 540

    #1

    outlook + PCL6 print does not work

    We are having multiple clients with different machines (MX3071S, MXC304W) having toubles printing from Outlook.

    Some mails can not be printed. The machine throws the job away...

    If you switch to PS, the mail prints.

    I checked the syslog of the machine and this is what i see.

    <148>Aug 30 13:43:21 2022 SHARP_Bart 0800686000:00038e47 Error: InternalError IOM JobID=10, ManJob ID=0x0
  • Gift
    Service Manager

    1,000+ Posts
    • Mar 2011
    • 2457

    #2
    Re: outlook + PCL6 print does not work

    Originally posted by boutn
    We are having multiple clients with different machines (MX3071S, MXC304W) having toubles printing from Outlook.

    Some mails can not be printed. The machine throws the job away...

    If you switch to PS, the mail prints.

    I checked the syslog of the machine and this is what i see.

    <148>Aug 30 13:43:21 2022 SHARP_Bart 0800686000:00038e47 Error: InternalError IOM JobID=10, ManJob ID=0x0
    I'm not into sharp but I'd check if the driver is using a TCP/IP port (yay!) and not a WSD port (boooh!) - WSD can cause weird issues and performance problems.

    Comment

    • boutn
      Senior Tech

      500+ Posts
      • Jun 2016
      • 540

      #3
      Re: outlook + PCL6 print does not work

      Originally posted by Gift
      I'm not into sharp but I'd check if the driver is using a TCP/IP port (yay!) and not a WSD port (boooh!) - WSD can cause weird issues and performance problems.
      We never use WSD

      Just did some tests, there is a very long hyperlink connected to an image in the mail, seems like this is causing the trouble

      Comment

      • Gift
        Service Manager

        1,000+ Posts
        • Mar 2011
        • 2457

        #4
        Re: outlook + PCL6 print does not work

        We don't use WSD, too but I've seen several cases of "port hopping" in wich Windows just changed the port by itself, that's why I always take a look.

        Funny thing if that hyperlink does trigger this problem.

        Try and print this: Link, Linkin Park and LinkedIn in Park | LinkedIn | Know Your Meme

        Comment

        Working...