Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Not applicable

Server task reload fails but a normal reload from within QV works

Hi

I wonder if anyone can give some insights. I have some models set up on a QV server with enterprise version 10. The reload tasks fail but if I open QV itself on that machine and run a reload it runs perfectly...

What could be the possible causes of this ?

Thanks

1 Solution

Accepted Solutions
Not applicable

Server task reload fails but a normal reload from within QV works

Problem solved. I was building the connection strings in a user account different to the user account that the QV services run under.

Apparently the connection strings contain some sort of data that identifies the user who created it - so if is created by a different user to the services user it will fail.

9 Replies
richardcripps
New Contributor III

Server task reload fails but a normal reload from within QV works

Could it be an authorisation issue?

Are you running the document through the client under a different user than the Qlikview Server Service is running under?

Does the QV Service user have access to the folder the document is stored in?

Not applicable

Server task reload fails but a normal reload from within QV works

I don't think so. I can access all models via the access point and am using custom users with DMS security. Services run on the administrator account and the folders holding the models do have the administrator assigned to their security.

Thanks for the effort though

Not applicable

Server task reload fails but a normal reload from within QV works

Are you using Section Access in the document? Has that been applied in the QEMC Reload tab if you are?

Not applicable

Server task reload fails but a normal reload from within QV works

No section access or built in security at all except a hidden script.

Not applicable

Server task reload fails but a normal reload from within QV works

Hmm ... that right there could be the issue ... the QEMC won't have the credentials to open the hidden script and run it I don't think ... I might be wrong ... what you might be able to do is not hide the script but instead use an inline section access to set an ADMIN user that only you have the credentials for ...

In the Document Security you would then disable the ability to Edit Script for all users except you as ADMIN ...

You can then set the Section Access in the QEMC Reload tab ...

Maybe that could be a work around.

Not applicable

Server task reload fails but a normal reload from within QV works

I have my doubts. I turned on logging and it does actually access the hidden script but trips up when hitting a section of code that dynamically creates connection strings (I combine a few different databases with the exact same structure into the same model).

I am now looking at changing that code - I just don't understand why it works perfectly well when running manual reloads...

Note that previously I was using a different method but the script was also hidden. In that case the QEMC had no trouble what so ever accessing the hidden script.

My gut feel is that the encrypted passwords for connection to the databases do not carry over well when running through the QEMC.

Once again thanks for the suggestion.

Not applicable

Server task reload fails but a normal reload from within QV works

Problem solved. I was building the connection strings in a user account different to the user account that the QV services run under.

Apparently the connection strings contain some sort of data that identifies the user who created it - so if is created by a different user to the services user it will fail.

richard_chilvers
Contributor III

Server task reload fails but a normal reload from within QV works

Hi Gareth

I have found this old post, which describes the exact problem I have. It seems to be an issue only where I have applied Section Access (I think) but persists even when I remove the Section Access.

You solved the problem, but I wonder if you could share an explanation of how ?

Regards

Richard

Not applicable

Server task reload fails but a normal reload from within QV works

Also with ODBC connections I discovered the following, so FWIW: ODBC on server seems to need to live in the System DSN tabs, not the user DSN where I had them initially and experienced an issue as you describe. See here: http://community.qlik.com/message/116092

Community Browser