Word format (.doc) not printing in fiery (pro c7110s)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sharpmind
    Trusted Tech

    250+ Posts
    • Sep 2009
    • 478

    #1

    Word format (.doc) not printing in fiery (pro c7110s)

    Guys, i have problem in printing .doc format in fiery. When I import the Word document, it is immediately converted to pdf and it is not printed. Any ideas?
  • Imprestik
    Trusted Tech

    250+ Posts
    • Aug 2012
    • 297

    #2
    Re: Word format (.doc) not printing in fiery (pro c7110s)

    From what I understand Fiery has never been able to print .doc files

    All files must be pdf

    I presume your using command workstation to drag and drop the .doc file or printing to the hold queue

    If so must definitely wont work

    Comment

    • sharpmind
      Trusted Tech

      250+ Posts
      • Sep 2009
      • 478

      #3
      Re: Word format (.doc) not printing in fiery (pro c7110s)

      Originally posted by Imprestik
      From what I understand Fiery has never been able to print .doc files

      All files must be pdf

      I presume your using command workstation to drag and drop the .doc file or printing to the hold queue

      If so must definitely wont work
      Even PDF file with mixed sizes gives an error. For example, there is a A3 and A4 document size combined in one PDF file. When you print it using command workstation, the alarm light becomes red. It seems like there is a paper mismatch. The machine is using normal A4 and A3 paper.

      Comment

      • nmfaxman
        Service Manager

        Site Contributor
        1,000+ Posts
        • Feb 2008
        • 1702

        #4
        Re: Word format (.doc) not printing in fiery (pro c7110s)

        Don't use command workstation to print.

        Use the print driver with the tcp/ip port set to LPR and the queue as PRINT all in caps.
        Let the computer do the translating to the machine.

        Command workstation is there to administer the controller not use as a substitute print driver.
        Why do they call it common sense?

        If it were common, wouldn't everyone have it?

        Comment

        • sharpmind
          Trusted Tech

          250+ Posts
          • Sep 2009
          • 478

          #5
          Re: Word format (.doc) not printing in fiery (pro c7110s)

          Originally posted by nmfaxman
          Don't use command workstation to print.

          Use the print driver with the tcp/ip port set to LPR and the queue as PRINT all in caps.
          Let the computer do the translating to the machine.

          Command workstation is there to administer the controller not use as a substitute print driver.
          I was able to print .doc file by using command workstation. Then the user complained about mixed size printing. I tried and checked mixed size printing but it did not print. Again I tried printing .doc file and it didn't print. According to user, he was able to print mixed size printing and .doc file printing with no problem before. So he was telling me the procedure he was doing before. That is why he was asking why he was unable to print now.

          Comment

          • slimslob
            Retired

            Site Contributor
            25,000+ Posts
            • May 2013
            • 37490

            #6
            Re: Word format (.doc) not printing in fiery (pro c7110s)

            Originally posted by sharpmind
            According to user, he was able to print mixed size printing and .doc file printing with no problem before. So he was telling me the procedure he was doing before. That is why he was asking why he was unable to print now.
            Usually indicates that something was updated. Probably something Microsoft. Check the update history to see if there was something just before it quit working. It is often common that a Microsoft update to correct one major problem can introduce other minor problems. Example is the current problem with scan to SMB.

            Comment

            • sharpmind
              Trusted Tech

              250+ Posts
              • Sep 2009
              • 478

              #7
              Re: Word format (.doc) not printing in fiery (pro c7110s)

              I am just wondering why only PDF and TIFF are printed using command workstation. If am the user and I have multiple files of word format, do I have to convert it to PDF just to print it.I think it is impractical! What is the use of Fiery if I cannot print JPEG and WORD FORMAT files...

              Comment

              • sharpmind
                Trusted Tech

                250+ Posts
                • Sep 2009
                • 478

                #8
                Re: Word format (.doc) not printing in fiery (pro c7110s)

                Originally posted by sharpmind
                I am just wondering why only PDF and TIFF are printed using command workstation. If am the user and I have multiple files of word format, do I have to convert it to PDF just to print it.I think it is impractical! What is the use of Fiery if I cannot print JPEG and WORD FORMAT files...
                In addition to this, the machine is just connected thru switch with IP address 169.254.45.xx...All computers are connected to the switch. Is printing problem on WORD and JPEG a network issue with regards to IP addressing?

                Comment

                • slimslob
                  Retired

                  Site Contributor
                  25,000+ Posts
                  • May 2013
                  • 37490

                  #9
                  Re: Word format (.doc) not printing in fiery (pro c7110s)

                  Originally posted by sharpmind
                  In addition to this, the machine is just connected thru switch with IP address 169.254.45.xx...All computers are connected to the switch. Is printing problem on WORD and JPEG a network issue with regards to IP addressing?
                  Sounds to me like you do not have DHCP on your network. A 169.254.xx.xx is an address generated internally by the computer when there is no DHCP and IP address are not manually assigned. I would suggest that you manually set IP addresses for everything in the 192.168.y.xxx range. y should be the same for all devices on the network, xxx should be unique for each device. You shoud keep a record, spread sheet, for all addresses assigned.

                  Comment

                  • sharpmind
                    Trusted Tech

                    250+ Posts
                    • Sep 2009
                    • 478

                    #10
                    Re: Word format (.doc) not printing in fiery (pro c7110s)

                    Originally posted by slimslob
                    Sounds to me like you do not have DHCP on your network. A 169.254.xx.xx is an address generated internally by the computer when there is no DHCP and IP address are not manually assigned. I would suggest that you manually set IP addresses for everything in the 192.168.y.xxx range. y should be the same for all devices on the network, xxx should be unique for each device. You shoud keep a record, spread sheet, for all addresses assigned.
                    Each device has unique IP address. The Fiery server has an IP address of 169.254.45.10. Other computers has different IP address..Before the machine was connected standalone in one computer. machine connected to fiery server, computer connected directly to fiery...It works with 169.254.45 range of IP address..

                    Comment

                    • KenB
                      Geek Extraordinaire

                      2,500+ Posts
                      • Dec 2007
                      • 3944

                      #11
                      Re: Word format (.doc) not printing in fiery (pro c7110s)

                      You're never going to get this issue resolved if you don't listen to the suggestions we are giving you.

                      Using the 169.254.x.x range of IPs is just asking for trouble.

                      Not only is it unstable, it creates all kinds of nasty unneeded network traffic that can slow things to a crawl, if not to a stop.

                      Set your IPs as SlimSlob suggested.

                      That won't fix the Word printing issue, but at least you will maintain good connectivity.

                      Fieries don't natively print MS Office docs, sorry. Is it possible that the Command Workstation PC had or has Word (or something that can read Word files) on it? That is a terrible idea, but not impossible. Could it be that the "Word" files that previously printed were only .txt files? Word can easily handle those, and you can do basic printing of text files with no driver.

                      PDFs are literally a PostScript file with a little extra header info, that's why they can be printed without a driver. In order to accommodate mixed size printing (and numerous other tricks, for that matter), there needs to be a print driver to do the heavy lifting. If you go back a number of years (10 or more, from what I remember), it was once impossible to print a PDF with mixed page sizes.

                      In addition, something has to create a PDF, they're not born that way, and just how the PDF was produced will have a HUGE impact on its characteristics when printing.
                      “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

                      Comment

                      • sharpmind
                        Trusted Tech

                        250+ Posts
                        • Sep 2009
                        • 478

                        #12
                        Re: Word format (.doc) not printing in fiery (pro c7110s)

                        Originally posted by KenB
                        You're never going to get this issue resolved if you don't listen to the suggestions we are giving you.

                        Using the 169.254.x.x range of IPs is just asking for trouble.

                        Not only is it unstable, it creates all kinds of nasty unneeded network traffic that can slow things to a crawl, if not to a stop.

                        Set your IPs as SlimSlob suggested.

                        That won't fix the Word printing issue, but at least you will maintain good connectivity.

                        Fieries don't natively print MS Office docs, sorry. Is it possible that the Command Workstation PC had or has Word (or something that can read Word files) on it? That is a terrible idea, but not impossible. Could it be that the "Word" files that previously printed were only .txt files? Word can easily handle those, and you can do basic printing of text files with no driver.

                        PDFs are literally a PostScript file with a little extra header info, that's why they can be printed without a driver. In order to accommodate mixed size printing (and numerous other tricks, for that matter), there needs to be a print driver to do the heavy lifting. If you go back a number of years (10 or more, from what I remember), it was once impossible to print a PDF with mixed page sizes.

                        In addition, something has to create a PDF, they're not born that way, and just how the PDF was produced will have a HUGE impact on its characteristics when printing.
                        I already resolved the problem of mixed sized printing using command workstation.

                        There is no problem of changing the IP address to 192.168.xx.xx..I can do that when i go there again.

                        My problem now is how to print WORD and JPEG files using command workstation.PDF and TIFF file has no issue on printing.The users have told me that they were able to print WORD, excel and JPEG in the production printer. They are doing it for years. Their business is to print documents related to air navigation and publication materials. If I tell them that only PDFs are allowed to print, then they will tell me that they are able to print any document format before. What can I say...?
                        Last edited by sharpmind; 05-26-2017, 03:36 PM.

                        Comment

                        • slimslob
                          Retired

                          Site Contributor
                          25,000+ Posts
                          • May 2013
                          • 37490

                          #13
                          Re: Word format (.doc) not printing in fiery (pro c7110s)

                          You might want to contact EFI support.

                          EFI - Support & Downloads

                          Comment

                          • KenB
                            Geek Extraordinaire

                            2,500+ Posts
                            • Dec 2007
                            • 3944

                            #14
                            Re: Word format (.doc) not printing in fiery (pro c7110s)

                            Originally posted by slimslob
                            You might want to contact EFI support.

                            EFI - Support & Downloads
                            Best suggestion yet.
                            “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

                            Comment

                            • teebee1234
                              Service Manager

                              Site Contributor
                              1,000+ Posts
                              • Jul 2008
                              • 1670

                              #15
                              Re: Word format (.doc) not printing in fiery (pro c7110s)

                              The 169.254.x.x is a Windows client generated address when there is no DHCP server available. If you're getting that as an ip address on the fiery or any Windows device then you need to switch to a static address.
                              *Called APIPA - Automatic Private IP Addressing

                              Comment

                              Working...