Error Connection to semantic model in service

[ahmedshalabyy12]

Hello , 

i received this error ,despite i didn't change or delete the semantic model in the service,

more over i tried to change the data source to the same one in the service but same prob

[Nasif_Azam · Accepted solution]

Hey @ahmedshalabyy12 ,

The error message you're encountering in Power BI Desktop “We couldn’t connect to your model in the Power BI Service” indicates an issue connecting to a dataset hosted in the Power BI Service. Even if you didn’t change or delete the semantic model, several common causes could still trigger this error.

Root Causes Might Be:

1. Permission Issues

2. Dataset Renamed or Moved

3. Credential or Token Expiry

4. Dataset Deleted or Replaced

5. Using a PBIX File Linked to a Service Dataset

Troubleshooting Steps

Step 1: Check Dataset Availability in Power BI Service

1. Open Power BI Service.

2. Navigate to the workspace where the dataset should be.

3. Confirm the dataset still exists and is accessible.

Step 2: Re-authenticate in Power BI Desktop

1. Go to File > Options and settings > Data source settings.

2. Clear permissions for the Power BI Service connection.

3. Sign in again and attempt to reconnect.

Step 3: Rebind Report to the Dataset (if needed)

If you've verified that the dataset exists:

1. Open Power BI Desktop.

2. Go to “Transform data” → “Data source settings”.

3. Try reconnecting to the existing Power BI dataset via:

   • Home > Get data > Power BI datasets

   • Search for the dataset and reconnect.

Step 4: Use Power BI REST API (Advanced)

If you are an admin or have access:

• Use the Power BI REST API to verify the dataset status (GET groups/{groupId}/datasets).

• This helps confirm if the ID still exists or was deleted.

For Detailed Information:

Troubleshoot Power BI Datasets

Connect to Power BI datasets in Power BI Desktop

Manage Data Source Settings in Power BI Desktop

Power BI REST API – Datasets

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam

[ahmedshalabyy12]

Thank You Nasif , the problem is solved it's due the workspace was inactive on that particualr day