Data connection works in edit but not run mode

[doherja]

In a new Sense instance running in standard mode, I have created a folder data connection called ENV_PROD, which points to a network share location. In the load script editor, I can click the 'select data' icon for this data connection, and navigate to the relative path /Shared/Include, and see the file SUB_GetQVD_DataConnection.qvs there as expected. There are security rules which grant read access on the the data connection to me and to the service account, in both QMC and Hub. I have read permissions on the file share that it references, and the service account has write permissions.

An app load script begins with the line: "$(Must_Include=lib://ENV_PROD/Shared/Include/SUB_GetQVD_DataConnection.qvs);". When I run it from the load script editor, I get the error: "$(MUST_INCLUDE= *** cannot access the local file system in current script mode. Try including with LIB path."

When I try to load from a QMC task, the log includes the line: "Error: $(MUST_INCLUDE= /SUB_GetQVD_DataConnection.qvs cannot access the local file system in current script mode. Try including with LIB path."

The same line of code worked in another Sense instance, which no longer exists. Why does this data connection work in edit mode and not when reloading? Thanks

[Miguel_Angel_Baeyens]

The account you use for the data load editor and the one used to reload the task in the QMC are the same? Do both accounts have access to the UNC path? You should be able to log in to the Qlik Sense server with the account running the services and access the \\Shared\Folder to verify permissions.

[doherja]

Both accounts have access, and in fact the service account was used to create the target folder.  This is in November 2023 patch 14.195.5.  I mention that because I am starting to see other problems that could be permission-related in another install of the same version, where root admin permissions are not being recognized, even in the default rules.  Has any bug been reported against this patch?  Thanks

[doherja]

Would one person--who is on a version prior to November 2023 and using default security rules--please let me know: does your 'RootAdmin' rule have a scope of 'Only in QMC,' or 'Both?'  Thanks--it could explain the strange behaviors we are seeing.

[doherja · Accepted solution]

The problem was not caused by the include statement shown in the original post, but by an invalid include statement, which was downstream of an 'Exit Script' statement.  With everything after 'Exit Script' removed, it loads as intended.  This must be a bug; I can reproduce it at will.  This is in November 2023.