Copy and Lookup activity now cant access my lakehouses with only internal error message

[DebbieE]

I have workspaces that I am admin on. Previous to yesterday it seems I had a pipeline and could click on my 'personal' lakehouse connection (Within my data engineering workspace) and everything was fine. Now all my lakehouses just have Internal error has occurred. Activity ID: 616464a5-ab25-4744-9c0a-a81f2aca4833 so I can;t access any of my lakehouses. 

It is a schema enabled lakehouse and I created two Delta parquet tables. I can go into the lakehouse (Also via the SQL analytics endpoint) and it works fine. 

the Error message is really unhelpful. I have gone into my connections and it sayd offline on my lakehouse

Error codeDataAccessError

Connection errorData access error 

[v-pnaroju-msft]

Hi DebbieE, 

Thank you for the update. We are glad to learn that you are able to work again without any issues.

Based on my understanding, the issue was likely a transient metadata or connection token failure in Fabric pipelines. The Copy or Lookup activity UI couldn’t fetch Lakehouse metadata, so the connection was marked Offline despite the Lakehouse being healthy. Common causes include a stale or expired authentication token in Manage Connections, a short lived service metadata or cache error, or occasionally a temporary storage permission or firewall check failure. Recreating the connection forces a full metadata refresh and token renewal, which explains why it resolved the issue.

Please continue to consult the Microsoft Fabric community for further queries.

Thank you.

[DebbieE · Accepted solution]

I deleted the connection and then readded but I dont know how this happened. it seems to be working ok again now

[tayloramy]

Hi @DebbieE, 

Did you change your password by chance? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[DebbieE]

No. Nothing like that. I guess Ill just have to keep my eye on things

[tayloramy]

Hi @DebbieE, 

Is the problem still happening? 

If so I recommend opening a ticket so the support engineers can dig into the telemetry for your tenant. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[Ugk161610]

Hi @DebbieE ,

We ran into something very similar recently and it turned out not to be anything we changed either. One minute everything worked, and then suddenly the Lakehouse connections showed as “Offline” with a useless internal error, even though the Lakehouse itself worked fine from the UI and SQL endpoint.

In our case it really did end up being a temporary Fabric-side issue. Recreating the connection forced Fabric to refresh the metadata and tokens, and after that the connection came back to life. Nothing changed on our side and nothing was misconfigured — it just happened randomly.

It definitely doesn’t look like a password issue based on what you described. When this happens without any config change, it almost always points to a transient problem in Fabric’s connection or metadata service rather than something local in your workspace.

If you see it again, the fastest fix seems to be what you already did — delete and recreate the connection. After that it usually stabilizes again.

You’re doing the right thing by keeping an eye on it. Hopefully Microsoft improves the error messages here, because right now they don’t give any clue about what’s actually wrong.

– Gopi Krishna