QV Installation error

[kamalqlik]

Hi ,

     I am installing the Qlikview server in Clint machine.

At the installation step where the domain name and server name is asked and the password is required(I am giving the correct usermane and password.

from the Domain)

But it is howing me the error as

"The username and password you specified could not be verified.Make sure that the usermae and password you specified are spelled correctly".

After that I also go for the installation mannualy, and specified the QV administrator mannualy but the services are not starting again.

Can anyone tell m what I have to do nxt to resolv the isu.

Thanks in advance

Regards

Kamal Naithani

[Miguel_Angel_Baeyens]

Hi,

Are you using a local account or a domain account? Is the account member of the local Administrators group? Are you installing the latest release of QlikView (11282)? Has your server installed the .NET 4 Extended role (required for QVS11)? And finally, do you have any firewall that might be avoiding the installation software to contact the domain controller or something?

Hope that helps.

Miguel

[kamalqlik]

Hi Sir,

         I am uing the domain account.

         Yes the account member of local administaror group.

         I am installinf QVS 9 SR7

      I think for 9 .net framwork 3.5 will work fine and it is configured.

regards

Kamal

[Miguel_Angel_Baeyens]

Hi Kamal,

In the Windows Event Viewer (Windows button, Run, eventvwr.msc) when you start the services, which errors do you see ?

Regards.

Miguel

[kamalqlik]

Hi Sir,

           it is showing me that the

"local computers may not have the nessecary registry information or message DLL files to display from a remote computer"

Logon Failure-the use has been not been granted as the requested logon type at this computer"

But according to Client the user is having all the admin rights and he is blaming Qlikview as the problem.

But it is clear that it is the issue some network problem

Thanks and regards

Kamal

[Miguel_Angel_Baeyens]

Hi,

It seems it's something related to security in the OS. Check the Microsoft site here and the suggested solution here to that issue.

Hope that helps.

Miguel

EDIT: Further info from Microsoft in regards to log on permissions and administrator security here and here.