topic Re: Inline table gives "Bad call to OpenFileOrURL ... DefaultDir was empty" - QlikView 12 SR5 in Archived Groups

Inline table gives "Bad call to OpenFileOrURL ... DefaultDir was empty" - QlikView 12 SR5

henrikalmen — Wed, 23 Jul 2025 14:48:52 GMT

SUMMARY: A qvw with an inline table can be reloaded in QVS (QlikView 12 SR 5) or in desktop client on another machine, but not in desktop client on server machine.

-----------

I have just upgraded our QlikView server from version 11 to version 12 SR 5 (12.0.20400.0). I create a new qvw file and create nothing but this simple script:

my_table: LOAD * INLINE [

ID, Value

1, A

2, B

];

When trying to reload in the Desktop Client on the server machine I get this error message:

Bad call to OpenFileOrURL: "\INL6A7E.tmp" and DefaultDir was empty !

If I run the QlikView desktop client on another computer the same qvw reloads fine, but not when I run it in the desktop client on the server machine. Log file for the qvw doesn't give any more information than this, it states the error mentioned and then on the next line "Execution finished." I tried moving the qvw to various locations, for example C:\ProgramData\QlikTech\Documents but no difference.

But it is only in the desktop client on the server machine that it does not work. If I move the qvw to a directory that is available from QV Access Point I can trigger reload in QVMC and it reloads fine! But it still doesn't work if I open the qvw in desktop client from that location.

The logged in user belongs to a windows local user group that has full access to root on both of the available drives on the server machine, otherwise that could have been the problem according to https://community.qlik.com/thread/84331#356807 where a similar (but not identical) issue was discussed.

I have tried everything that I can think of, naturally including searching community forums and googling for solutions. Now I turn to the QlikBug group...

Re: Inline table gives "Bad call to OpenFileOrURL ... DefaultDir was empty" - QlikView 12 SR5

rwunderlich — Tue, 30 Aug 2016 16:05:12 GMT

Can you post the document log? I'd like to see the environment information at the top of the log.

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

Re: Inline table gives "Bad call to OpenFileOrURL ... DefaultDir was empty" - QlikView 12 SR5

henrikalmen — Wed, 31 Aug 2016 06:58:19 GMT

Absolutely! I'm attaching one log file from the QlikView Desktop execution that fails, and one log file from when triggering reload in QVMC where the execution is successful.

As you can see the QVB reload is handled by the user qvservice, and the desktop reload is with another user (climber konsult). If I log in to the same machine with credentials for the qvservice user the reload is fine. If I log in as the climberkonsult user on another machine and open the same file the reload is fine.

Of course that makes me think of user rights problems, but the user climber konsult is the same user as I have always used on this server. It is also that user I was logged in as when I performed the upgrade to version 12. (First I installed QlikView Server version 12, after that I installed QlikView Desktop version 12.) This user is a local admin and is a also member of local user group that has full rights to the disks in the machine.

Re: Inline table gives "Bad call to OpenFileOrURL ... DefaultDir was empty" - QlikView 12 SR5

rwunderlich — Thu, 01 Sep 2016 12:29:33 GMT

I tried executing on a Win2008R2 machne and it worked fine for me. Sorry I can't recreate.

-Rob

Re: Inline table gives "Bad call to OpenFileOrURL ... DefaultDir was empty" - QlikView 12 SR5

henrikalmen — Thu, 01 Sep 2016 12:31:06 GMT

Ok, thanks for trying.

Re: Inline table gives "Bad call to OpenFileOrURL ... DefaultDir was empty" - QlikView 12 SR5

henrikalmen — Tue, 06 Sep 2016 09:38:41 GMT

With the help of QLik Support this problem is now solved, and I'm posting the solution here if anyone else runs into the same problem.

The windows user had faulty directories listed in registry under these nodes:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders

and

HKEY_USERS\[userid]\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

In my case some of the keys were pointed at nonexisting network drives. That has obviously not been a problem before we upgraded to QV12, nevertheless the solution to my problem was to point to existing folders. Qlik Support also mentioned that they have seen similar problems when such keys point to network shares even when those folders exist, and in that case the solution would be to point at directories on the local hard drive.