reload fails from QVMC but succeeds from file

[stevelord]

Hi, we have a problem with reloads failing from the QVMC, though the documents work okay when you open and reload them directly.  We are on QV 11.2 SR12 and updated to that back in June.

I have enabled log files on the documents in question, but logfiles only generate when we open and reload them manually.  The QVMC is failing to get them open.  Normally if it gets them open and starts the reload, the logfile generates whether the reload fails or succeeds.  Currently it's not getting far enough to generate the logfile.

1> What are some likely causes of this?  Or places to check for likely causes.

2> Are there other logging options elsewhere in QVMC that we can toggle to produce error log files that start with QVMC attempt to reload a file, and finish with something like maybe the reason it failed to start the reload or open the file?

Note: SysAdmin did switch the remaining qv services to run from a local service account instead of the engineering vp's account to resolve an issue of a correlation between vp vacation and failed reloads. Some were already running locally, but he saw the other two and flipped them over as well for best practice reasons.  He says they should be identical to the vp's account otherwise, but suspects we're missing something now and hopes additional error logging (or QlikCommunity) will provide insight.

[marcus_sommer · Accepted solution]

The reason will probably be the change with the service accounts which now have not the same access rights (maybe a membership to a certain usergroup is missing). I suggest that you looked to the qvw's which runs successfully which user(groups) have access rights. Maybe ther is also a possibility to look on the profils from those accounts and search there to any differences.

- Marcus

[stevelord]

Thanks, it struck me that the vp had a named licenses and the vp user id was written into the section access lists of all the documents.  The new service account did not have a named license and was not in the section access lists.

SysAdmin person does everything outside Qlikiview, and I do everything inside the Qlikviews, and for whatever reason we did not make this connection, as terribly obvious as it feels now, until reading your post.

I have verified the solution of:

give service account a named license

add the service account's id to the section access list in each qvw's script (all of ours have such a list, but may not apply to other people's)

reload the document manually (for the SA list settings to become part of it I guess)

then pushing play from the QVMC works

(I tried pushing play at various other stages before reloading the document- like when I save and check changes into source control, but manual reload of document was what ultimately let it through)

I am updating the remaining qvws accordingly... Oi!  (I spent 3 hours manually reloading documents from home before I came in to work today.  Glad I shouldn't have to do this tomorrow. )