Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Share your agentic AI experience, learn from others, and earn a new badge: Put Agentic AI to Work
cancel
Showing results for 
Search instead for 
Did you mean: 
vkal12
Creator
Creator

"Error: Unable to connect for result set" - Sharepoint data connection

 
Hello community,
 
we use several SharePoint data connections in Qlik Sense On-Prem to load data from SharePoint into a Qlik app. We occasionally encounter reload tasks that fail with the error message: "Error: Unable to connect for result set." Usually, simply restarting the reload tasks allows them to complete successfully, though sometimes they fail again with the same error. Is anyone familiar with this error and does anyone know what it indicates or how to resolve it?
 
Kind regards,
Vanessa
1 Solution

Accepted Solutions
stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @vkal12 

I have seen this error when the connection to SharePoint has been rejected from the Azure end of things. What is interesting in your case though is that the connection comes back and works again without anything being done to fix it.

It is probably just 'one of those things' and the way around it may be to write in a way of retrying when loads fail. You can do this with the errormode statement and checks before and after each load with the noofrows function. You can then have a while loop which keeps going around until data is refreshed, or a retry limit is met.

Alternatively, as you are on-prem, you can just let the reload fail and set the number of retries on the reload process to a suitable number.

Hope that helps.

Steve

View solution in original post

1 Reply
stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @vkal12 

I have seen this error when the connection to SharePoint has been rejected from the Azure end of things. What is interesting in your case though is that the connection comes back and works again without anything being done to fix it.

It is probably just 'one of those things' and the way around it may be to write in a way of retrying when loads fail. You can do this with the errormode statement and checks before and after each load with the noofrows function. You can then have a while loop which keeps going around until data is refreshed, or a retry limit is met.

Alternatively, as you are on-prem, you can just let the reload fail and set the number of retries on the reload process to a suitable number.

Hope that helps.

Steve