Forum Discussion
Semantic model wont refresh
- 1 year ago
Hi EmilZPM,
Thank you for reaching out to the Microsoft fabric community forum. After thoroughly reviewing the details you provided, here are a few troubleshooting steps to consider:
- Since Azure Blob Storage and Power BI semantic models are cloud-based, they should not require a gateway. Please ensure the cloud data sources are correctly configured and do not mistakenly require a gateway.
- Verify that Azure Blob Storage connections are using OAuth authentication. If the credentials have expired, re-enter them and try refreshing again.
- Identify any data sources that might require a gateway (such as an on-premises data source mistakenly included). If everything is cloud-based, republish the dataset to update its metadata in Power BI Service.
- If the dataset is locked into using an On-premises or VNet gateway, ensure your Personal Gateway is online and updated. If possible, switch to an On-premises Data Gateway (Standard Mode) instead of the Personal Gateway. If using a VNet Gateway, verify it has access to the required cloud services.
- Create a new Power BI file, connect only to Azure Blob Storage, and publish it. If the new dataset does not require a gateway, this suggests an issue with the original dataset’s metadata.
If this information is helpful, please “Accept it as a solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
Hi EmilZPM,
Thank you for reaching out to the Microsoft fabric community forum. After thoroughly reviewing the details you provided, here are a few troubleshooting steps to consider:
- Since Azure Blob Storage and Power BI semantic models are cloud-based, they should not require a gateway. Please ensure the cloud data sources are correctly configured and do not mistakenly require a gateway.
- Verify that Azure Blob Storage connections are using OAuth authentication. If the credentials have expired, re-enter them and try refreshing again.
- Identify any data sources that might require a gateway (such as an on-premises data source mistakenly included). If everything is cloud-based, republish the dataset to update its metadata in Power BI Service.
- If the dataset is locked into using an On-premises or VNet gateway, ensure your Personal Gateway is online and updated. If possible, switch to an On-premises Data Gateway (Standard Mode) instead of the Personal Gateway. If using a VNet Gateway, verify it has access to the required cloud services.
- Create a new Power BI file, connect only to Azure Blob Storage, and publish it. If the new dataset does not require a gateway, this suggests an issue with the original dataset’s metadata.
If this information is helpful, please “Accept it as a solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
- v-ssriganesh1 year ago
Community Support
Hi EmilZPM,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please accept it as a solution and give it a 'Kudos' so other community members with similar problems can find a solution faster.
Thank you.