Urgent Help required: service user validation failed

[awhitfield]

I am attempting to upgrade a customers Sense Site from June 2017 to February 2018. I am logged in as the service account.

Following the entry of the Service credential password and clicking next, I got an error "Service User Validation Failed".

1. the enter password is correct
2. the user is a member of the local administrators group
3. the user is a member of a Qlik Sense Services user group which has logon as a services privileges.
4. I have also to run the upgrade as my account, but get the same issue.

best regards

Andy

[Levi_Turner]

Is the command line option skipvalidation able to be used to work-around this validation failure?

[YoussefBelloum]

did you verify the Domain_name or computer_name ?

[awhitfield]

Ended up swapping the service user to a local user and upgrade progressed fine

Andy

[amars]

We did faced the same issue when setting up the Qlik Sense Server

As mentioned by Levi Turnor use command propmpt -> go to the directory where the "Qlik_Sense_setup.exe" exists and Run Qlik_Sense_setup.exe -skipvalidation Qlik_Sense_setup.exe skipvalidation=1

This should solve the "Service User Validation Failed" error. Thanks....

[kavita25]

Can u please elaborate your solution...

I am trying your solution but its not working..

We navigated to the path where qlik sense setup is there..

then we run the set up reaching to the service credentials page..

n then we copied the skip validation code as Qlik_Sense_setup.exe skipvalidation=1

But its not working..

Please help me with the solution...

Regards,

Kavita

[kavita25]

Please help me with the solution....

[korsikov · Accepted solution]

Just check it

run CMD with admin rights

then C:\install>Qlik_Sense_setupSeptember2018.exe skipvalidation=1

and everything works.

If it don't try set  localuser then change it, https://help.qlik.com/en-US/sense/September2018/Subsystems/PlanningQlikSenseDeployments/Content/Sens...

[korsikov]

I solved this issue on my prod enviroment. 

The problem was that the default containers were changed and renamed in the Windows AD. Reset to default help solve this issue and many another with Qlik and about qlik products. Like the Qlik Replication.

[arish_delon]

Thank you.

This solved my problem in production.