Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have recently installed Qlikview and trying to bring up our Dashboard.
The installation and lisence application is successful.
When we are accessing the access point URL, it fails to show any dashboard deployed and returns an error message as "No Server".
Upon checking all Qlikview services are running and healthy.
The Event log file has the below error :
"Error System: CQvXmlInterfaceRequestHandler - Catch: errId(-3). Ino(-1). Fno(91)"
Can someone please help.
what is managementconsole showing?
status/services
all green?
Yes, all services running green.
Hi,
Are all service installed on the same machine?
Go to C:\ProgramData\QlikTech\WebServer and edit the Config.xml and look at the Machine name (red below) and make sure it is correct.
<AddQvs>
<Machine>qlik</Machine>
<Port>4747</Port>
<LinkMachineName>qlik</LinkMachineName>
<Weight>1</Weight>
<Username />
<Password>Encrypted=DxdCGMWfOwU=</Password>
</AddQvs>
Bill
Yes, the machine name is correct. Its value is the hostname on which all services of Qlikview are installed and running.
This hostname is ping-able and reachable.
Hi,
Are you using IIS or QVWS? If running IIS is the Qlikview IIS application pool running under the same service account as the Qlik services are?
Bill
Yes, both (IIS and Qlik services) are running using the same user ID which is also the local admin.
Hi,
Is the Directory Service Connectors and QVS linked properly on the QVWS section of the QMC (tab General and Access point - Server Connections)?
Cheers!
The guys have pretty much covered most of what I can think, but I wanted to post the fno message meaning for you:
GetAdminDocListForUser (This message relates to the QVS retrieving the document list for a user, so it will be the reduced list based upon what apps the user has been granted access)
This would be expected if the QVS is not available to the QVWS. To Bill's point, are all services on the same server, or are you running distributed? If QVS is not on the same server as QVWS, one possibility could be TCP 4747 being blocked between the servers. That is about the only thing the guys did not cover already.
Need further information to come up with any other ideas. If someone did hit on the issue, be sure to use the Accept as Solution button on the one that worked...
Regards,
Brett