Forum Discussion
FabricSqlEndpointMetadata Connector kind is not valid for RefreshSqlEndpoint Activity
Hi,
I am getting this error when configuring a RefreshSqlEndpoint:
I've recreated the connection and I am also using OAuth with a service account.
Any tips on what I could be doing wrong?
Thanks
Hi fpvmorais1
Short version: that error is a schema-validation failure on the pipeline JSON, which is why recreating the connection and switching to OAuth didn't change anything. The backend rejects the activity before it ever tries to authenticate, so the service account is probably not your problem.
The message means: the connection GUID bound to the activity resolves to a connection whose connector kind isn't on the allowlist for RefreshSqlEndpoint.
What I would check
1. Look at the activity JSON, not the UI. On the activity: </> → View source code (or pipeline-level View -> Edit JSON Code). Check externalReferences.connection and typeProperties. if these contain the correct values.
2. Delete the activity and re-add a fresh one, in a brand-new test pipeline. Don't edit or copy paste the existing one. If a fresh activity in a fresh pipeline works, your original has a stale binding written by an earlier (preview) version of the activity schema.
3. Create the connection inline from the activity's Connection dropdown, not from Manage connections and gateways. In the sibling WebActivity case, that's exactly the difference: the portal gallery registers a connector kind the activity's allowlist doesn't match, even though the name looks right.
4. Confirm the target is a Lakehouse SQL analytics endpoint, and that you have the endpoint ID, not the Lakehouse item ID, not a Warehouse, not a Fabric SQL Database. Those are different GUIDs:
If none of this works, you could try and use a Web activity against the REST API, fully parameterizable, and supports service principals and managed identities:
POST https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/sqlEndpoints/{sqlEndpointId}/refreshMetadataCaller needs Contributor or higher on the workspace.
Did I answer your question, please mark the post as a solution or consider a like.
2 Replies
v-aatheequeCommunity Support
Hi fpvmorais1
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.
- AvdBerg
Resolver I
Hi fpvmorais1
Short version: that error is a schema-validation failure on the pipeline JSON, which is why recreating the connection and switching to OAuth didn't change anything. The backend rejects the activity before it ever tries to authenticate, so the service account is probably not your problem.
The message means: the connection GUID bound to the activity resolves to a connection whose connector kind isn't on the allowlist for RefreshSqlEndpoint.
What I would check
1. Look at the activity JSON, not the UI. On the activity: </> → View source code (or pipeline-level View -> Edit JSON Code). Check externalReferences.connection and typeProperties. if these contain the correct values.
2. Delete the activity and re-add a fresh one, in a brand-new test pipeline. Don't edit or copy paste the existing one. If a fresh activity in a fresh pipeline works, your original has a stale binding written by an earlier (preview) version of the activity schema.
3. Create the connection inline from the activity's Connection dropdown, not from Manage connections and gateways. In the sibling WebActivity case, that's exactly the difference: the portal gallery registers a connector kind the activity's allowlist doesn't match, even though the name looks right.
4. Confirm the target is a Lakehouse SQL analytics endpoint, and that you have the endpoint ID, not the Lakehouse item ID, not a Warehouse, not a Fabric SQL Database. Those are different GUIDs:
If none of this works, you could try and use a Web activity against the REST API, fully parameterizable, and supports service principals and managed identities:
POST https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/sqlEndpoints/{sqlEndpointId}/refreshMetadataCaller needs Contributor or higher on the workspace.
Did I answer your question, please mark the post as a solution or consider a like.