NPrinting Reports by External XML Doesn't Work

[NZFei]

Hi everyone,

I have read and set up the external XML following the articleHow to Execute NPrinting Reports by External XML Request  but it still does not work. Here are what I have done:

1) NPrinting server has been set up (Enable External Request and define the source folder).

2) the QVS.process file has been created with the format:

<?xml version="1.0"?>

<schedules>

     <schedule file="C:\NPrintingTraining\NPrintingFiles\NPrintingTraining.nsq" type="job" entityName="AccessPoint Report" />

</schedules>

3) When I run the batch file to rename the QVS.process file to QVS.request file, I can see it stayed for a very short time and then is changed back to QVS.process. (Doesn't that mean NPrinting service has detected the request file and has run it?)

However the NPrinting job is not triggered. Nothing happened in NP.

Have I done anything wrong or missed anything?

Thanks

Fei

[Daniel_Jenkins]

Hi Fei,

A couple of questions:

1. You mention QVS.process file. Is that just a typo as it should be QVS.processed?

2. Can you check the server log file to see if the job was started? You will find the log file location by looking at the path field under Log settings

3. When the QVS.request file is processed there is also a QVS.result file created in the same folder. The original .request file is renamed to have a .processed extension and a new file with a .result extension is created. Do you see that file?

4. Does the Active Account used to run the service have a dedicated QlikView Desktop Named User CAL? Is the NPrinting server running on the same machine as the one with the External XML request source folder? Does the Active Account have access to "C:\NPrintingTraining\NPrintingFiles\NPrintingTraining.nsq"? If the nsq is on a different machine you should use the UNC path to the file instead. You can troubleshoot your NPrinting Server setup by following this document: Configuring and Troubleshooting NPrinting Server Service and Schedules

Let us know how it goes.

- Daniel.

[NZFei]

Hi Daniel,

Thank you for your reply. I didn't know you are here now

1. Sorry it is my typo. The file name is qvs.processed. When I manually rename it to qvs.request, it will stay for half second and then be changed to qvs.processed automatically.

2. Job is not started. No log and the task manager does not change at all.

3. No qvs.resul file is created.

4. I used my account which is not dedicated but has named CAL. No problem with the access. All in the same server.

The Qlikview server does not have publisher. Is it possible to achieve this without a publisher?

Thanks.

Fei

[Daniel_Jenkins]

Hi Fei,

You do not need publisher for QlikView External XML requests to work.

Please log a Support request via the Partner Portal and I will take a look.

Best,

Daniel.

[antosraf]

HI

any news on this topic

I have simillar situation. 

Nprinting is changing back the file name to .procesed

but nothing happens,  no .result file, nothing in log files

BR

Rafał

[Daniel_Jenkins]

Hi Rafał,

Please open a case with support giving your QlikView NPrinting Server license number.

HTH - Daniel.

[#7]

Hi, we have a similar behaviour on our environment.

".request" file correctly renamed to ".processed" but nothing more on NP.

Do you all have any news on how to deal with this situation or what could be wrong in the setup?

Thanks in advance,

Domenico

[NZFei · Accepted solution]

Hello everyone,

I have created a case and Daniel from Qlik support has helped me find out the problem.

It is the script in QVS.processed file. By default it is edited by notepad++, which adds line number 01., 02., 03. ... in each line and those line numbers are hidden.

If I edit the file using notepad, I can see those line numbers (see below in bold). After removing these numbers, it is working.

01.<?xml version="1.0"?>

02.<schedules>

03.<schedule file="C:\QlikView\NPrinting\Projects\Test External XML Request.nsq" type="job" entityName="Send the report for External XML Request" />

04.</schedules>

I have also tested it in an environment where NP does not have on demand and it is also working.

Hope this can help?

Cheers.

[Daniel_Jenkins]

Hi,

Note that Type of entity can only be task or job (not jobs).

HTH - Daniel.

[NZFei]

Thanks Daniel. I have updated it.