topic Re: QlikView Webserver Error - 405 Method Not Allowed in QlikView

QlikView Webserver Error - 405 Method Not Allowed

prasath_palani — Mon, 26 Jan 2026 18:19:17 GMT

Team,

Below is the server configuration in our environment, but while we try to access the access point we are getting the error (405 -a method not allowed from iis)

Server 1 - QVS, QDS, QMC

Server 2 - QVWS (iis)

Thanks

Prasath

Re: QlikView Webserver Error - 405 Method Not Allowed

NadiaB — Mon, 23 Sep 2019 17:45:47 GMT

HI @prasath_palani

Have you verified the IIS installation is correct?

How to configure: QlikView and IIS

Kind regards.

We encourage our customers to visit our Knowledge Base https://qliksupport.force.com/QS_CoveoSearch when trying to find a solution related and not limited to: errors, feature requests, product defects. You can also visit our Qlik Help portal https://help.qlik.com/

Re: QlikView Webserver Error - 405 Method Not Allowed

Albert_Candelario — Thu, 26 Sep 2019 20:48:24 GMT

Hi,
Did you solve the issue? Sometimes a reboot is needed on the IIS server when I faced this kind of errors on it after a new installation.
Cheers!

Re: QlikView Webserver Error - 405 Method Not Allowed

Brett_Bleess — Mon, 30 Sep 2019 21:43:12 GMT

Prasath, another option here would be to use the QlikView Web Server instead of IIS/QlikView Settings service, as it seems you may have some IIS challenges here. At a minimum, using QVWS would confirm if things work, if they do, then you definitely can point back to the IIS team that something is misconfigured there. The IIS setup is normally pretty simple, our installer puts in the virtual directories and custom application pool which handles the QvAjaxZfc directory and that app pool should run under the same service account as the other services. Depending on what type of authentication you are using, the only page that likely needs to be set to Windows Authentication is the Authenticate.aspx page in the QvAjaxZfc directory, everything else can likely be anonymous. Check the .Net Framework associated with IIS as well and be sure everything is good there, as that is a possibility as well I would venture. Again, the error you are getting is not likely pointing to an issue in the Qlik side of things. Shout back if you have further information.

Regards,
Brett