User Profile
coverturfLSH
Resolver II
Joined 3 years ago
User Widgets
Contributions
Re: Semantic Model never refreshed and didn't fail
We have refresh notification failures but the refresh never technically failed. It stayed open until it was caught and canceled by a member of my team. We do keep an eye on the Lakehouse for usage but we're not a 24hr shop so no one is around at 1:30 to notice. When I expand the items all it gives me is the the warehouse is timing out. Which matches the 10 minute cancels I typically see in the lakehouse.337Views0likes0CommentsRe: Semantic Model never refreshed and didn't fail
It's difficult to tell what caused this. I don't think it's the refresh overlap or other workloads. Most don't run until later in the day. I suppose it oculd be the SQL Endpoint but I don't even know how I would resolve that. The odd part it is that's been working fine for over a year now and then today it just decided to go into this CU usage loop. I did have another instance like this where I had a report refreshing from an AWS Redshift database but the database was offline. The connection stayed open for several hours doing nothing but burning CU.338Views0likes1CommentSemantic Model never refreshed and didn't fail
I have a semantic model that normally takes around an hour to refresh daily. The data source is a Fabric Lakehouse pulled via a SQL query. Today, the refresh started around 1:30AM (as usual), however the query would run for about 10 minutes, get canceled, restart the query, run 10 minutes, cancelled, in a loop. This happened 40 times and ate up 3.3 million compute units which pretty much has made my capacity unusable. It was finally caught around 7AM and canceled on the semantic model itself but the damage was already done. Has anyone else encounted this issue before?Solved433Views0likes5Comments"The service returned an invalid token" error
Hi, I'm using Power Query to connect to a Microsoft Fabric warhouse via the SQL Server connector. I received an error message when I went to refresh my query that says "The service returned an invalid token. Please contact your IT administrator". In searching for a solution, I saw several posted solutions but the only one that worked for me was disconnecting from my current wifi, connecting to my phone's hot spot, signing in, then going back to my old/current wifi. It seems as though there's an "internal" type token that was valid for approximately a year but needed a reset. For others that are running into this issue, I'm suggesting what I did and it works for them. But I'm wondering if anyone else has had this issue and if there are alternative resolution options as not every has a wifi hotspot available to them. [edit 11/17/25]: Had a user who was trying to connect to SharePoint from PBI and received this error. The wifi switch did not work for them. However, uninstalling and reinstalling the application did work for them. I have also been encountering the error needing to wifi switch within a week or two of receiving the error. Other folks have not had the error and only needed to switch once. Thanks,1.9KViews2likes8CommentsRe: "The service returned an invalid token" error
Hi venuppu, All of the responses have provided the same solution that is already working for me. I'm going to open a support ticket with Microsoft when I have time and can recreate the issue to see if they're aware of the problem.1.5KViews0likes0CommentsRe: "The service returned an invalid token" error
I think it's very specific to using Power Query to connect to a Fabric Warehouse. I have several users who are connecting this way through a process I created about a year ago. And they're slowly one by one starting to receive this error message. I guess the other way I could think of to replicate the issue would be to create a PQ connection to a warehouse and then wait a year to see if the token expires. Not much to go on, but since Fabric warehouses were released over a year ago, I was wondering if any others were starting to encounter the issue.1.8KViews0likes0Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.