- Indeed this isn't logical. (QlikView) Admin passwords will change over time, which has a horrible effect on services. Your users will not hesitate to make you aware of this. Best thing you can do is to create a Service Account in your AD. It doesn't need any special privileges (fewer is better, but AD access is required for the DSC), except that the password shouldn't expire. Do not forget to make this account a member of the Local Administrators group on your server box (and of all QlikView local groups you are currently using)
- Hmm, not sure what is causing this. Did you consult the various QlikView service logs on both machines? They may contain indicators as to what is causing this repetitive behavior.
Thanks for your thoughts.
I may not have been fully clear at first.
1. The account is a service account in the domain AD. The account is needed to be placed in the local qlickview admin and the local admin groups. The Qlikview Server only runs when it's in the local Qlikview Admin group and all the other services only run when it's in the local admin group.
It's odd behaviour to me. The other environment with Qlikview servers up and running only has the domain service account in the Qlikview Admin group.
The other kicker is the other servers are on win2k8 server and the install I performed is on win2k12 server.
So the question is - is this a 2k12 behaviour needing the domain service account in both local QV Admin and local Admin groups?
2. They are both in the local QV Admin and local Admin groups on both machines. I'll see if the logs indicate anything.
Thanks for the ideas guys and help.
1. I discovered the other server does have the domain service account in both local admin and local qv admin. I guess I missed it last week when I was diagnosing things. So looks like this issue can be closed.
2. I just need to find out why the QMC shows the QDS needing to restart while on the servier it's running and I can generate tasks w/ triggers and it's reflected in AccessPoint. Still attmepting to see if anything is in the logs.