topic Problem with publisher after upgradeing in QlikView

Problem with publisher after upgradeing

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

Hello

We have upgrade publisher from november 2020 to may 2021.

And now our appar can not read from excel files that are placed on our intranet. We can update the app in desktop.

Appar that reads from excel files that are in maps works in the publisher.

Not all files in the intranet can have changed over one night.

So I guess we miss something in the publisher. Something that dropped during updates.

Any suggestion?

Re: Problem with publisher after upgradeing

Chip_Matejowsky — Tue, 24 May 2022 16:45:46 GMT

Hi @marvin,

I suggest that you start with reviewing the QlikView Distribution Service (QDS) logs of the failed reload task along with the document log of the QVW file associated with the failed task. By default, the task logs are stored in %ProgramData%\QlikTech\DistributionService\1\Log\DateOfTask\NameOfTask. If you have configured the QDS Application Data Folder in a different folder, you can check the location by looking in the QMC > System > Setup > Distribution Services > QDS@ > General tab. If you have a QDS Cluster, the number 1 in the above file path refers to the first QDS server of the cluster. The second QDS server of the cluster will have number 2 in the file path; and so on.

If document logging is enabled, it will be stored in the same directory in which the QVW file is housed. If document logging is not enabled, you will need to open the source QVW file in QlikView Developer, click Settings > Document Properties > General tab and ensure the Generate Logfile checkbox is ticked. Then run the reload task so that the document log is generated.

Ping back if you have further questions about finding or reviewing the logs.

Best Regards

Re: Problem with publisher after upgradeing

marvin — Wed, 25 May 2022 11:28:40 GMT

The error message is

Error: Cannot open file: 'https://test.test/file1.xlsx'

Execution Failed

Execution finished.

It does not say why it can not open the file. In the example we have read there are more information after file adress but we do not get more after the fileadress.

Any suggestione?

Re: Problem with publisher after upgradeing

Chip_Matejowsky — Wed, 25 May 2022 12:21:51 GMT

Hi @marvin,

In your initial post you mentioned that the reload of the QVW is successful if run in QlikView Desktop. What account was used to open in the QVW in QV Desktop and run the reload? The QDS uses the Qlik service account to run reloads from QlikView Server/Publisher, so suggest that you login to a computer with QV Desktop using this service account and attempt to reload the QVW to see if the issue is permissions related.

Best Regards

Re: Problem with publisher after upgradeing

marvin — Wed, 25 May 2022 13:17:07 GMT

I can not log in a computer with our service account but I logged in the intranet with the service account and could access the file without problem.

We have tried to add

WebFileUserAgent="curl/7.51.0"

WebFileUseWinAPI = 1

in the settings file

Thanks for your help

Re: Problem with publisher after upgradeing

Chip_Matejowsky — Thu, 26 May 2022 17:32:44 GMT

@marvin,

To troubleshoot this issue please follow these steps:

Make sure you do not have any security software scanning the QlikView folders or processes

See QlikView Folder And Files To Exclude From Anti-Virus Scanning

To be sure no other software is locking the QlikView files you can also monitor the file access following the steps from this article: File Access and Process Monitoring - How to find locked files and the processes locking them

If you find any other 3rd party tool locking QlikView files, please contact your Internal IT team in charge of fixing this.
Check your file server Disk performance

To save a data collection of your storage performance you could use Performance Monitor for this: How to log CPU, Disk, and memory usage with Microsoft Performance Monitor on a windows 2012 Server (...

You can also review the actual performance live in the Resource Monitor:

A good indicator to check is the Disk Queue Length. A good-performing disk should show a value as close to 0 as possible.

In this example here we can see a very high Queue Length, demonstrating a general bad performance of the disk, which ended up preventing Qlikview to open files in a timely manner.

See QlikView and its backend File Share System.

If you are facing this problem, please contact your Internal IT team in charge of Storage performance.

Also, make sure you are following best practices documented in Scaling QlikView Publisher

Best Regards