"File Not Found" for report run through nP scheduler

[#1]

I have a QVW that loads perfectly fine from my desktop, but when I try to do a scheduled reload, it returns "File Not found".

Could this be because the Scheduler runs on a separate machine with a virtual address of

"\\qlik\QlikView Reports", whereas I run my machine with the local address R:\QlikView Reports\..."?

If so, how do I change it, and why do I get the error on this report, and not all my other reports, which are similarly configured?

[Daniel_Jenkins]

Hi Kevin,

This article is your friend - use it as a checklist: Configuring and Troubleshooting NPrinting Server Service and Schedules

HTH - Daniel.

[#3]

NPrinting does not recommend using mapped drives to avoid issues such as this.  It is always best to use UNC pathing for all file locations (nsq files, templates, etc.)

Also make sure the user that nprinting service is running under has access to the qvw.  Any easy way to test is to log onto the server as the nprinting user and manually run the task through NPrinting designer

[#4]

Kevin

any update or new inforamtion regarding this issue

[#5]

Yes and no.

This appears to ONLY happen when I try to access qvd's. All of my reports that access our external databases, or local Excel files, work perfectly well with drive name R:\

It is only the QVD files that require the \\qlik\ identifier.

Very strange to me, but it's not that hard to work around.

cheers,

Kevin

[#6]

is \\qlik identifying the server where the qvd files are located?

it could be based on how the qvw inside the load is pathed to find the qvd.  It is always best the use unc pathing whether it be for excel, qvd or any other file type (input or output) to avoid issues with the mapping not being the same, not existing, getting dropped etc.

glad to hear you have a handle on things

[#7]

Adam, ALL my files are on the same drive - the Excel, qvw, qvd, etc.

Now, the drive is an actual piece of hardware, right? It has some actual physical address, doubtless some long string of hex, which we usually don't know, as humans don't remember that kind of stuff easily. So we give it a name, like "R:", or "\\qlik\QlikView Reports\" which both point to the exact same piece of hardware.

I'm not a Windows network guru, so I don't understand this. More to the point, I don't understand why it works sometimes, and not others. For example, even though I changed the specifier to "\\qlik" on one file, it STILL didn't load properly under nPrinting until this morning, when it suddenly did. It's annoying, and I have to check each morning that it reloaded properly, but at least it's working, which is the main thing.

Non-deterministic computers scare me.