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

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
Manguirish
Contributor III
Contributor III

Sharepoint Connections dropping

I have a strange error in Qlik Cloud

I am running an automation which is refreshing multiple apps in multiple spaces (some sequentially and others parallelly). Many of these apps are accessing some excel files on SharePoint. (not huge files, usually has some dimensional data).
However, i am getting the following connector error

Manguirish_0-1736402854605.png

The error is occurring across apps randomly and across SharePoint files. For ex during one automation run one app reloads properly however same app doesn't reload during the next run. Moreover, if I run a manual reload, the apps run. 
In some cases the error is slightly different

Manguirish_1-1736403195159.png


The files are there exactly where they are supposed to be on sharepoint. Moreover, these automations have been running smoothly for almost a couple of years, multiple times each day. The error seems to be coming out of nowhere.

I have reauthenticated my sharepoint connections as my microsoft password was changed and that seemed to have worked once. I am checking for further runs during the day. But the password change had happened few weeks back and during the time none of the reloads were affected.If this was an authentication error then reloads should have failed across all apps but that's also not the case.

Can anyone please advise what this could be



Labels (4)
1 Solution

Accepted Solutions
diegozecchini
Specialist
Specialist

Hi!
SharePoint might be limiting the number of simultaneous requests. Automations running parallel processes can trigger throttling mechanisms. And the System.OutOfMemoryException suggests the Qlik Cloud environment might be running into resource limits, especially when running apps in parallel. Finally connections may still use expired tokens even after re-authentication, especially in cases where long-lived sessions or cached tokens are involved.

There many reasons we can proceed by small steps
First of all sggest to check detailed logs in Qlik to identify patterns (e.g., specific times when errors occur or specific apps that fail more often).
Temporarily would be an Idea to reduce the number of parallel reloads to minimize load on SharePoint and avoid rate limits.


Also, check SharePoint API usage and throttling events in Microsoft Admin Center to confirm if rate limits are being hit.

View solution in original post

6 Replies
diegozecchini
Specialist
Specialist

Hi!
SharePoint might be limiting the number of simultaneous requests. Automations running parallel processes can trigger throttling mechanisms. And the System.OutOfMemoryException suggests the Qlik Cloud environment might be running into resource limits, especially when running apps in parallel. Finally connections may still use expired tokens even after re-authentication, especially in cases where long-lived sessions or cached tokens are involved.

There many reasons we can proceed by small steps
First of all sggest to check detailed logs in Qlik to identify patterns (e.g., specific times when errors occur or specific apps that fail more often).
Temporarily would be an Idea to reduce the number of parallel reloads to minimize load on SharePoint and avoid rate limits.


Also, check SharePoint API usage and throttling events in Microsoft Admin Center to confirm if rate limits are being hit.

diegozecchini
Specialist
Specialist

..and, If possible, increase timeout settings for SharePoint connectors in Qlik.

Pablo007
Creator
Creator

I think @diegozecchini has provide a great reply, Just to ad smth bear in mind that maybe some one else has started to uses work memory from your server, and that makes sharepoint to stop you.

You can try also to make smaller queries or making changes on the time tat you load,  just in case,  also if posible try to convert the excels to QVD files

diegozecchini
Specialist
Specialist

I agree with @Pablo007  did you make the try?

Manguirish
Contributor III
Contributor III
Author

"Finally connections may still use expired tokens even after re-authentication, especially in cases where long-lived sessions or cached tokens are involved."

I think this was the issue. After changing my Microsoft password the connections worked.

Apologies for the delayed response. Thanks for your help

diegozecchini
Specialist
Specialist

Yep, it happens! glad it works