Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Highlighted
Not applicable

Can't reach AccessPointSettings.aspx from server but can from other PC

Hi,

I am troubleshooting a QlikView v10 server with IIS. I have followed the documentation for setting up QlikView with IIS, including changing the authentication settings for the QVAJAXZF to disable anonymous auth and enable windows auth.

Everything works fine, apart from the fact that in QEMC, under System -> QlikVIew Web Servers, for the web server, in the summary tab I get '

The Web server is currently not responding'.

One of the checks in the documentation is to ensure I can reach the AccessPointSettings file. This is at http://MyServerName/QvAjaxZfc/AccessPointSettings.aspx. The odd thing is (and I think the source of my problem) is that I can't access this when logged in on the server locally - I get prompted for credentials 3 times, then I get 401.1 Unauthorised error from IIS. But I CAN access it fine from any other computer on the network - I get <Root>POST request without contents, can't process!</Root> as expected.

Why would I be able to access this page from any PC except when logged onto the server itself? I'm logged in as the same account, so it can't be due to my AD account's permissions. ANy ideas?

Thanks

Tags (3)
1 Solution

Accepted Solutions
Not applicable

Can't reach AccessPointSettings.aspx from server but can from other PC

Solved.

The new local loopback security check was blocking access to the site locally, because the fully qualified domain name for the site did not match the machine name. Therefore following method 1 in the Microsoft KB article resolved the problem:

http://support.microsoft.com/kb/896861

1 Reply
Not applicable

Can't reach AccessPointSettings.aspx from server but can from other PC

Solved.

The new local loopback security check was blocking access to the site locally, because the fully qualified domain name for the site did not match the machine name. Therefore following method 1 in the Microsoft KB article resolved the problem:

http://support.microsoft.com/kb/896861