Press "Enter" to skip to content

Category: Error Handling

GraphQL Deployment Error due to dm_exec_describe_first_result_set()

Published 2026-06-02 by Kevin Feasel

Koen Verbeeck troubleshoots an issue:

A while ago we suddenly had an error while trying to deploy one Fabric workspace to another using fabric-cicd. The issue was with a GraphQL object and the following error was returned:

Failed to publish GraphQLApi ‘my_graphql’: Operation failed. Error Code: DatasourceInvalidStoredProcedure. Error Message: Only those stored procedures whose metadata for the first result set described by sys.dm_exec_describe_first_result_set are supported.

Read on for Koen’s diagnosis and resolution for this issue.

Leave a Comment

WinGet and Path Not Updating

Published 2026-06-01 by Kevin Feasel

Justin Bird ran into some trouble:

Whilst I predominantly use MacOS, I do have to run a Windows VM for certain apps (cough Power BI cough). I ran into an issue recently when trying to installing apps on a vanilla Windows 10 build using Winget via the terminal in VS Code.

After installing the app, I found that the PATH environment variable was not updated, which meant I couldn’t run the app from the command line without specifying the full path.

Read on to learn what the issue was and how Justin was able to fix it.

Leave a Comment

Full-Text Indexes and SQL Server 2025

Published 2026-05-27 by Kevin Feasel

Rich Benner rebuilds indexes:

The Full-Text Engine manages full-text indexes. The engine splits your text columns into individual terms and builds an inverted index, mapping each term back to the rows in which it appears. Unlike a standard B-tree index, the structure lives outside the normal index internals and is maintained asynchronously via a background process called a crawl. Effectively, each word in your text string ends up indexed, rather than the string as a whole. This makes certain types of searches much more efficient (you need to use search terms like CONTAINS() to utilize full text indexes).

If you have to search strings like this then full-text indexes can be very effective. String searching isn’t great in SQL Server, but this is definitely a tool in your belt if you have a requirement that makes it useful.

Because of some changes to the way full-text indexing works in SQL Server 2025, there is a post-upgrade maintenance task you’ll have to perform.

Leave a Comment

ORDER BY COALESCE() in PostgreSQL (and SQL Server)

Published 2026-05-22 by Kevin Feasel

Laetitia Avrot digs in:

I was reading Markus Winand’s latest post on ORDER BY history last week. If you haven’t read it yet, go read it. Markus is one of the best writers on SQL standards, and this post is no exception.

One line stopped me cold. The compatibility table for “expressions on selected columns.” Postgres: partial. PostgreSQL 18: still partial.

That itch needed scratching.

The basic version of this is that you cannot use the alias of a computed expression in a function in the ORDER BY clause in either PostgreSQL or SQL Server. In other words, the following fails:

SELECT a + b AS x
FROM t
ORDER BY COALESCE(x, 0);

Read on for an explanation of why this is the case in PostgreSQL. I’d imagine that the reasoning is about the same for SQL Server.

Leave a Comment

Recovering from a Full Transaction Log File

Published 2026-05-18 by Kevin Feasel

Jeff Iannucci sneaks in a fix:

We received an emergency call from a client that noted that their SQL Server instances was unresponsive. (This was an Amazon RDS instance, although that didn’t play much into the ultimate root cause.) The client had some technical staff already looking at the issue, and when we joined the call we were informed that the transaction log for their main production database was completely full, and all transactional activity in the database had stopped.

Read on to see how Jeff and team were able to fix it.

Leave a Comment

Exceeding the Capacity Limit for Power BI Dataset Refreshes

Published 2026-05-18 by Kevin Feasel

Chris Webb explains an error:

If you have a lot of Power BI semantic models that are scheduled to refresh at the same time in the Service then you may find that some of them fail with the following error:

You’ve exceeded the capacity limit for dataset refreshes. Try again when fewer datasets are being processed.

[Note: “dataset” is the old name for a Power BI semantic model. Someone should update the error message.]

Read on to see what can cause this error and what you can do about it.

Leave a Comment

Power BI Maximum Allowable Memory Allocation Error

Published 2026-05-11 by Kevin Feasel

Chris Webb continues a series from a few years ago:

This is a very late addition to the series of posts I wrote back in 2024 and which started here on Power BI memory errors. It’s about a very rare error that is hard to deal with and often temporary but since people do run into it from time to time I decided to write about it so there is some useful information available about it online.

The error, which can occur when you refresh a semantic model or render a report, has two associated error messages:

Click through to see those two error messages, as well as a simplified version of the root cause and what you can do.

Comments closed

MSG 10054 Failures over VPN

Published 2026-05-08 by Kevin Feasel

Tim Radney takes us through a connection failure error:

Over the past few weeks, I’ve been contacted by multiple customers experiencing the same frustrating issue. Applications and SSMS sessions that had been rock-solid for years suddenly started throwing errors when connecting over VPN:

  • Msg 10054: “An existing connection was forcibly closed by the remote host.”
  • “Connection Failure (status code = 3000, [Microsoft][ODBC Driver 17 for SQL Server] The connection is broken and recovery is not possible…”

Read on to learn what’s going on and how you can remediate it.

Comments closed

Refresh Warnings now Available in Power BI History

Published 2026-04-20 by Kevin Feasel

Chris Webb tells us don’t panic:

Since March 2026, Power BI semantic models have started showing warnings in their Refresh History in the Service. This has scared a few people but in fact all that is happening is that errors which were there all along and which don’t prevent refreshes from completing are now being flagged. Documentation on this feature can be found here but let’s see an example of the type of errors that can cause these warnings.

Click through for that example.

Comments closed

When Fabric Mirroring Doesn’t Copy Rows

Published 2026-04-16 by Kevin Feasel

Koen Verbeeck troubleshoots an issue:

A short blog post about an issue with Fabric Mirroring (with Azure SQL DB as the source) that I’ve managed to run into, twice. I’ve set up mirroring by creating a connection using a service principal and this principal has the proper permissions on the source database. Configuring the replication was without issues, and the replication status went from “starting” to “running”. However, no rows were being copied. The tables were all listed in the monitoring pane, but the counters of “rows replicated” remained at zero. There were no errors in the logs (in OneLake) and nothing suspicious was mentioned in the monitoring.

This was a rather pernicious issue. Based on Koen’s explanation, it sounds like there’s no way to know what the actual problem was.

Comments closed