5 Replies Latest reply: Aug 9, 2017 7:04 AM by Ruggero Piccoli RSS

    NPrinting Tasks Ref Locations

    Chris Attewell-Hughes

      Hi guys,

       

      I'm trying to make sense of the error logs in NPrinting 17.4/June, but all the tasks have long coded refs rather than the name of the tasks themselves so it's difficult to know what's failing/publishing.

       

      Is there somewhere in NPrinting where it stores which ref refers to which task?

       

      Thanks in advance

       

      Chris A.

        • Re: NPrinting Tasks Ref Locations
          Chanty 4u

          i think as of now No. 

          • Re: NPrinting Tasks Ref Locations
            Chanty 4u

            May be Ruggero Piccoli  will help you i believe

            • Re: NPrinting Tasks Ref Locations
              Ruggero Piccoli

              Hi,

               

              Long codec references in the logs are the Qlik NPrinting entities ID. At the moment you can decode them only manually.

              First of all you must know what type of entity is referred. For example, if the message is Generating cache for connection 151027b3-f618-41c3-8eb7-c9aa9eaea688 we are speaking about a connection.

              1. Copy the code 151027b3-f618-41c3-8eb7-c9aa9eaea688
              2. Open one connection. The URL in the web browser will be something similar to https://localhost:4993/#/connections/3eb1f50a-f1e3-47cd-899f-0b38072c6f6f
              3. Replace the last part of the URL by pasting the copied id and press enter
              4. The correct connection appears

              For tasks or task executions the process is similar.

               

              For reports the ID is related to a report inside a specific task. Do first you have to decode the task and then the report.

               

              Best Regards,

              Ruggero

              ---------------------------------------------

              When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

                • Re: NPrinting Tasks Ref Locations
                  Chris Attewell-Hughes

                  Hi Ruggero,

                   

                  It's the task I'd be looking for. How would I see the reference for a specific task?

                    • Re: NPrinting Tasks Ref Locations
                      Ruggero Piccoli

                      For a task, for example, suppose to have this message in your logs:

                       

                      Qlik.NPrinting.Scheduler 17.4.1.0 Qlik.NPrinting.Scheduler.Task.PublishReportsEngineTask 20170809T125434.640+02:00 WARN RD-RPC-INEXPRPT 0 0 0 0 0 0 0 0 No report has been added to task df524ff5-5230-4db0-9859-9a373aa0e6e7. Execution will succeed but no report will be generated

                       

                      The task ID is df524ff5-5230-4db0-9859-9a373aa0e6e7. Copy it.


                      Open the Qlik NPrinting Publish tasks page in your browser. The URL is something like  https://Address:4993/#/tasks/publish.


                      Add a / and paste the task ID. So the URL will be https://Address:4993/#/tasks/publish/df524ff5-5230-4db0-9859-9a373aa0e6e7.


                      Press enter and the task you are looking for appears.

                      Best Regards,

                      Ruggero

                      ---------------------------------------------

                      When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.