Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I'm creating a mega project, and i'm using 3 tiers architecture, meaning, the data will be loaded into QVD by different QVW.
For the loading of the QVW, i don't want to use publisher to schedule them because it's just too many of them, and hard to maintain.
So i use the idea of BW process chain logic, and created something similar for QV.
There's a main dashboard, to monitor the load of each QVW, it will tell if it's sussccesfful or fail or when was it last run, etc.
and each QVW, we use batch file to trigger the qv process to execute the qvw in background,
and it has the ability to do daily load, weekly, monthly, or monthly on a specific date, works like wonder.
BUT sometimes it run and sometimes it doesn't, and i'm not really sure what is the error, although i can get it from the system log, but it didn't tell much.
and if i kill all the processes and did a manual trigger, it works, this solution by batch is really hard to troubleshoot.
has anyone of you done anything like this? maybe not the batch approach?
Please share .... Thx.
Hi Ralph,
One other major difference: The user that you run the qvdistributionservice.exe as, MUST be in the local security group "QlikView Administrators." (this might be why you got a username/password prompt)
Also, for both qv.exe and qvdistributionservice.exe - if you are using any connection strings with integrated authentication, the user running the .exe must have access to the data (e.g. files, databases, etc).
Have you run into any issues with QVDistributionService not being able to write out the log file?
I'm trying to run CMD batches, using similar EXECUTE statements to what's mentioned above, and it's not able to write the log files, which I'm trying to then pull back into the app to note failed loads. But, the same statement runs fine, and results in the log file, when pasted into a CMD window.
Thanks,
DJ
DJ Let's start a new thread. Start a new one and then post the link to it here. I'll head over there and we can try to help you out.
Hi Ralph,
Thank you for your quick response. It turned out to be a syntax issue, not user issue.
Here's my thread, and I was able to resolve the issue today:http://community.qlik.com/message/301458
Thanks again for offering to help.