topic Re: SharePoint Access Denied with Wildcard Scrape in App Development

SharePoint Access Denied with Wildcard Scrape

andrewcraven — Thu, 27 Oct 2022 15:29:58 GMT

Using QlikView May 2021 SR1, SharePoint 2016

Example Load script:

Table1:
LOAD
@1 as [field1],
@2 as [field2]
//// @n as [fieldn]...
FROM
[\\someurl.somedomain.com@SSL\DavWWWRoot\folder\subfolder\*.csv]
(txt, codepage is 1252, no labels, delimiter is ',', no quotes, header is 1 lines, no eof);

This works on my desktop, and it works in Qlik designer in the production server environment when logged in as the service account. It even works when run via QMC in our QA/Dev environment, but it does not work in our Production environment over QMC (both Dev and Prod use the same service account). Only Prod QMC fails with an Access Denied message. I can navigate to the SP Site / List with a web browser as the service account (in both Prod and QA/Dev), so it's not a SharePoint permissions issue (so far as i can tell). I checked our Trusted Sites in Prod vs QA/Dev and they match.

I feel like we've ruled out the usual suspects, and I also suspect it has something to do with the "@SSL" bit, but I don't know what else to toggle. I don't believe it's a "Qlik" problem, but rather some down-deep hidden environment problem. Any ideas what else it could be?

Re: SharePoint Access Denied with Wildcard Scrape

andrewcraven — Thu, 27 Oct 2022 16:43:00 GMT

Addendum: it seems this methodology is not working reliably when logged into server as service account and using qlik desktop designer. 90% sure it was working yesterday during my troubleshooting. Now is throwing an Access Denied message.

Re: SharePoint Access Denied with Wildcard Scrape

andrewcraven — Thu, 27 Oct 2022 16:52:31 GMT

Second Addendum: in prod server environment, if I navigate to the folder path from the load script in my original post, it prompts me for credentials. i enter service account credentials and can enter the folder and see my files. THEN if i run the load script in desktop designer, it works. so it's got to be related to the @sabrina_salazar\DavWWWRoot bit...is not SSL'ing.