Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

'Could not connect to server' with AZAX client on IIS 6

Hi,

Qlikview Server v9 SR4 ; NTFS authorization ; Integrated Windows Authentication in IIS 6.

Can launch the Access Point fine and can successfully launch documents via the IE plugin. However, when launching via the AJAX client, get the following error:-

'Could not connect to server!'

The event logs show the following errors:-

Error Failed to create account IQVS_SERVERNAME, Access is denied.

Error Anonymous login failed: Logon failure: unknown username or bad password.

Both the IUSR and IQVS users have full access to the document root folder. The service user is also in the local IIS_WPG group.

A separate QV app pool has been created in IIS and assigned to the QvAJAXZfc virtual directory as per the Qvs Reference Manual.

Any ideas?

Thanks

Jonathan

1 Solution

Accepted Solutions
Not applicable
Author

Tech support found that the installer package for SR4 is missing the QvsComRemote.dll. Copying an SR3 version of the dll and registering it resolves the issue. SR5 has the dll so upgrading will resolve also.

Thanks

View solution in original post

5 Replies
Not applicable
Author

Do you have installed "IIS compatibity" feature during qvs setup?
If not, uninstall and install again, regards.

Not applicable
Author

Yes, this is installed and it works fine with the IE plugin.

Only get the 'could not connect to Server!' message when using the AJAX client.

Thanks

Not applicable
Author

What is the windows server?

I has this problem with windows server 2008, and was necessary installer QVS x64 with IIS 7.0.

Yes

Not applicable
Author

Tech support found that the installer package for SR4 is missing the QvsComRemote.dll. Copying an SR3 version of the dll and registering it resolves the issue. SR5 has the dll so upgrading will resolve also.

Thanks

Not applicable
Author

We've seen the same problem with SR5 and SR6. We are not using the IQVS_<servername> account, but it still shows up. If we could figure out where and why the account is there, we could probably change it to our service account and solve the problem.