Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, everyone.
I have this strange problem that i could use little help with...
Over six months, i had a working task in qmc (Server/Publisher) that executed succesfully using a domain account user with administrator/QlikView administrator rights.
The task was a command line task that executed the following command:
"c:\Program Files\QlikView\QV.exe" /vReduceGreenData=1 D:\Files\File1.qvw
Before three days i changed the user running the QlikView Services with another domain account user that is never expiring and has administrator/QlikView administrator rights but the task hangs and never ends or fails...
Do you have any idea why is this happening?
Thanks in advance!
Isn't there something missing in this command line?
AFAIK your task starts QV Desktop, opens and loads a document, sets a variable, and then... just sits there...
To reload-save-quit there are other command line switches (IIRC /r and /p)
Peter
Sorry, my mistake. The reload switches are /r, /rp, /l and /lp.
See QlikView Reference Manual - Chapter 7.1 Command Line Syntax
The command passes a value to vReduceGreenData variable in order to trigger a macro that performs reduce data
And the macro is responsible for saving the document and closing QlikView desktop?
Yes
If you use Section Access in your document, that could be the reason why changing accounts suddenly makes this operation fail.
Another idea: have you assigned a Named CAL to the new account? Otherwise QlikView desktop will try to open the document in PE-mode, and all sorts of annoying things may happen...
I am using section access but i have included the new user in the users list...
I have also assigned a document CAL to the user...
Is there a difference between the assignement of the named CAL and the document CAL?
Of course there is a difference. A Document CAL can only be used in the AccessPoint, to open a single document overthere. As such, a Document CAL cannot promote QV desktop from PE-mode to fully licensed mode: it cannot be leased like a Named CAL.
Assign a Named CAL to the new account, and your task will start working again.