topic Re: Office 365 Sharepoint Metadata Connector in Data Movement & Streaming

Office 365 Sharepoint Metadata Connector

Crichter141 — Mon, 09 Mar 2026 19:25:18 GMT

I'm out of ideas. We had a connection and it just stopped working over the weekend, so it doesn't appear to be user created. It still looks active.

The error message 'No refresh_token found DCERROR-0060'

I even tried setting up a new connector with the same settings and it still does not work. Is this connector broken?

Re: Office 365 Sharepoint Metadata Connector

NoahF — Tue, 10 Mar 2026 13:07:29 GMT

Have a look at this solution, maybe it resolves the issue for you as well.

Solved: No refresh_token found error on Connector Version:... - Qlik Community - 1648654

Re: Office 365 Sharepoint Metadata Connector

Crichter141 — Tue, 10 Mar 2026 13:31:18 GMT

Hey Noah,

It looks like that's possibly an on-Prem solution. We're in the Cloud. The oddest thing is we have several failures - fine, time to reauthenticate, right? But some allowed me to do that and others did not. This one really has me stumped.

I don't see a place to clear settings in the Cloud. I'll check with our partners, and we may have to escalate to Qlik in a ticket. Thanks!

Re: Office 365 Sharepoint Metadata Connector

Crichter141 — Tue, 10 Mar 2026 15:25:52 GMT

Update: The issue has been resolved, although the original cause remains unclear.

During troubleshooting we attempted creating a new connection and testing with a different user account, but neither resolved the problem. The successful fix occurred when our partner edited the existing data connection and reauthenticated it using the service account credentials.

Our current theory is that reauthentication from a different environment/network forced Qlik to refresh the connection state, which had not been updating previously. It appears the authentication was created, it tested fine, but Qlik was not saving it at the update/edit screen.