URL with /qlikview/ not working anymore (IIS - QlikView)

[steuberklein]

Hey guys,

short questions. For a long time we had a URL with Servername/qlikview/ and it was working and redirecting to the AccessPoint. Many people set their favorites regarding to this link. Now we haven't changed a big thing (only adding a https certificate) and if the user now open Servername/qlikview/ it only shows the message "Error 500". If the user delete the /qlikview/ from the URL and enter only Servername the accespoint is showing. This is strange because some time age if you have entered the Servername the IIS default page with "Welcome" was showing.

Does anyone have an idea why it's not working anymore?

Kind regards and thanks in advance.

[Sonja_Bauernfeind]

Hello!

Since you are using IIS, it's likely a change in configuration on that end. When using IIS with QlikView, all configuration of virtual directories, port configuration, certificates, paths, etc... is carried out on the IIS side itself, rather than in the Qlik product. If you use the WebServer component we ship with the server software, then that one is the one that takes care of the virtual directories (that's the second screenshot you sent in).

If IIS now serves the AccessPoint directly when going to the server name, without the /QlikView folder, then a change was made to do this redirect.

The default setting for the AccessPoint is using ..../QlikView. 

[Sonja_Bauernfeind]

I noticed that in your IIS screenshot you can see the /images and /js subfolders in the root directory. These are the folders you'd expect in the /QlikView sub directory, so it looks like this was moved/reconfigured. 

Check the content of the Root to see if you can find the other files as well.

This is what it should look like by default:

[steuberklein]

Thank you for the screenshots. It's strange that somehow in the root folder and in the qlikview folder I got the same files. Maybe someone did this, that it's working with /qlikview/ and without it. Is this possible?

Can I forward all requests for URL/qlikview/ to the root folder? Therefore the users don't get an 500 error.

[Sonja_Bauernfeind · Accepted solution]

It wouldn't be how that should be set up. Usually, I think people set up IIS itself to do redirects, rather than moving around files, but I am not an IIS administrator.

As for the forward: You will need to speak to your IIS administrator since those are all settings that need to be done in IIS itself. They might be able to tell you what was done at the start? 

A quick google search led me here and here, but not sure if that is what you're looking for.

Keep in mind that if you keep this in this non-standard configuration, any upgrade of the product will revert it back to default.

Should a talk with your admin not help, and you haven't made any other modifications to the IIS configuration (like extra authentication options, etc..), then running the install package for QlikView, removing IIS support, and then reinstalling IIS support, might be the quickest way to get this up and running again as it was before.