Hi Jessica, check the windows log for errors.
Also the logs in : C:\ProgramData\QlikTech
Has qvadmin got the logon as service rights ? see http://technet.microsoft.com/en-us/library/cc739424(v=ws.10).aspx
Paul, I have the manual of v11.20 SR7 but I don't see this page!? What page is this? I am attaching
the manual I just downloaded from Qlik site.
espero que esta información le sirva.
Requisitos del sistema Sistemas operativos compatibles
Microsoft ® l Windows Server 2003 x64 Edition ™ incluyendo
Microsoft ® Windows Server 2008 x64 Edition ™ incluyendo
Microsoft ® Windows XP ™ incluyendo x64 Edition *
Microsoft ® Windows Vista ™ incluyendo x64 Edition *
Microsoft ® Windows 7 incluyendo x64 Edition *
* Recomendado sólo para fines de desarrollo y pruebas.
Mira lo Manual Referencia de QlikView Server
Ok, I got it up and running! Here is what I did:
1. Apply domain account to services panel directly.
2. Add the domain account to Qlikview Administrator Group
3. Restart services
Viola! It's working!
Here is the story why I used local account instead of domain account:
During my 1st installation, neither <domain>\<username> or <username>@<domain>.com got through the installation wizard. So I created a local account qvadmin and added it into both Administrator Group and Qlikview Administration Group. The installation finished with the local account and I
restarted the machine. Couldn't get the services to run.
I wonder why local account couldn't work. Thanks all for helping!
If this is a corporate laptop, your desktop team is setting security policies. You can can search for "Local Security Policy" (run "secpol.msc" from run or command line). Navigate to Security Settings > Local Policies > User Rights Assignment.
Here you can see the different policies and what user/group have them (i.e. Log on as a service).
Its possible that your companies corporate security policies might be removing (or adding restricting policies) on certain user accounts or groups. I would compare all the rights for both accounts, it might be that local account also has 'Deny log on as a service'.
Off the top of my head, here are some policies that might be of interest to compare:
- Deny log on as a batch job
- Deny log on as a service
- Impersonate a client after authentication
- Log on as a batch job
- Replace a process level token
Talked to our IT Support. Both domain and local account could work for QVS on local machine. I didn't successfully add the local account into Administrator group in hence services failed.
Here’s how to get local qvadmin to work:
1. Create a local account and make sure it is in both Administrator Group and Qlikview Administrator Group
2. Use the local account to run services during installation
3. Restart the machine
4. The services should pick up the services automatically
Here's how to get domain account to work:
1. Make sure domain account is in both Administrator Group and Qlikview Administrator Group
2. Here I couldn't get it to work: During installation, neither <domain>\<username> or <username>@<domain>.com passed the installation wizard
3. Manually change the logon as a service to the domain account
4. Restart the machine or services
Basically exactly the same as installing on Windows Server. The only thing didn't work for me is the domain name was not approved by wizard. I am not working in my office but I doubt that's the reason. I would love to know if anyone successfully used a domain account on a local machine. Thanks for everyone's help!
Regarding to :
- Paul, I have the manual of v11.20 SR7 but I don't see this page!? What page is this? I am attachingthe manual I just downloaded from Qlik site
Its not in the server reference manual, but on page 3 of the System requirements
The reason the local account works is because you manually assigned it to the services, MS automatically gives this user login as service rights.
When setting the domain account I think you have to be connected to the office, This because the domain credentials have to be validated by the domain controller. Tried it on my system and it's no problem using the domain credentials.