Forum Discussion
Error Refreshing SQL Endpoint in Microsoft Fabric – “Value cannot be null. Parameter name: key”
Hi Edward_Vabi,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thank you nilendraFabric, for your insights.
Thank you for providing details about the "Value cannot be null. Parameter name: key" error you're encountering when refreshing your SQL endpoint in Microsoft Fabric. Since you’ve confirmed that the “Sync the default model” setting is enabled, yet the semantic model remains outdated and the error persists, this issue likely stems from a configuration.
First verify the schema of your Lakehouse or Warehouse to ensure all tables and columns referenced in the semantic model are intact and haven’t been renamed or deleted, as schema mismatches can trigger this error. Check the semantic model’s Model View to confirm that primary keys and relationships are correctly defined and not referencing null or missing fields, as the “key” in the error often points to such issues.Check the Refresh History in the Fabric workspace for detailed error logs, which may pinpoint specific tables or columns causing the failure. As a last resort, consider creating a new semantic model to rule out corruption, reconnecting it to the same data source, and testing a refresh.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Hi Edward_Vabi,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thank you nilendraFabric, for your insights.
Thank you for providing details about the "Value cannot be null. Parameter name: key" error you're encountering when refreshing your SQL endpoint in Microsoft Fabric. Since you’ve confirmed that the “Sync the default model” setting is enabled, yet the semantic model remains outdated and the error persists, this issue likely stems from a configuration.
First verify the schema of your Lakehouse or Warehouse to ensure all tables and columns referenced in the semantic model are intact and haven’t been renamed or deleted, as schema mismatches can trigger this error. Check the semantic model’s Model View to confirm that primary keys and relationships are correctly defined and not referencing null or missing fields, as the “key” in the error often points to such issues.
Check the Refresh History in the Fabric workspace for detailed error logs, which may pinpoint specific tables or columns causing the failure. As a last resort, consider creating a new semantic model to rule out corruption, reconnecting it to the same data source, and testing a refresh.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
thank you for this v-saisrao-msft - i have not had time to try these yet but let me revert ones i do, should get around to this by end of this week
Hi Edward_Vabi,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.