Data Factory internal server error

Question

Data Factory internal server error

Jakob Preysz Jørgensen 0

My Data Factory resource will not let me start a debug session. I get the following error message: "Failed to setup debug session. Session ID: 9592aad5-1bc6-41ff-8ba9-7c4dad19a6e3".

I have done several attempts, but no luck.

When I run diagnostics on the Run ID through the Azure Support page, it says "No issues found".

None of my pipelines with data flows will run either. It all started early this morning around 05:00 am.

Error message: "Hit unexpected exception, please retry. If the problem persists, please contact Azure Support"

And I can't create a support request, I'm told that I need to contact my service provider.

Any ideas?

Konen 0 Reputation points

2024-08-27T22:30:59.86+00:00

Jakob Preysz Jørgensen Are you trying custom integration runtime for debug?

or are you using the default integration runtime?

If you are using the custom integration runtime, check if the azure region or compute size is the problem//
NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-08-28T04:45:08.92+00:00

@Jakob Preysz Jørgensen
Thank you for the question and using Microsoft Q&A platform.
We are reaching out to the internal team to get more information related to your query and will get back to you as soon as we have an update.
Smaran Thoomu 35,375 Reputation points Microsoft External Staff Moderator

2024-09-02T10:53:20.75+00:00

@Jakob Preysz Jørgensen Just checking in to see if the below answer provided by @Smaran Thoomu helped.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

2 answers

Your answer

Konen 0 Reputation points

2024-08-27T22:30:59.86+00:00

Jakob Preysz Jørgensen Are you trying custom integration runtime for debug?

or are you using the default integration runtime?

If you are using the custom integration runtime, check if the azure region or compute size is the problem//
NIKHILA NETHIKUNTA 4,690 Reputation points Microsoft External Staff

2024-08-28T04:45:08.92+00:00

@Jakob Preysz Jørgensen
Thank you for the question and using Microsoft Q&A platform.
We are reaching out to the internal team to get more information related to your query and will get back to you as soon as we have an update.
Smaran Thoomu 35,375 Reputation points Microsoft External Staff Moderator

2024-09-02T10:53:20.75+00:00

@Jakob Preysz Jørgensen Just checking in to see if the below answer provided by @Smaran Thoomu helped.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

Smaran Thoomu 35,375 Microsoft External Staff Moderator

Hi @Jakob Preysz Jørgensen
Thank you for reaching out to the community forum with your query.

We apologize for the inconvenience caused by the recent outage. We want to inform you that an outage was reported in the Europe region, which may have impacted your pipeline. However, the issue has now been resolved, and the service has been restored. Please try rerunning your pipeline to see if the problem persists. If it does, let us know, and we’ll investigate further.

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Smaran Thoomu 35,375 Reputation points Microsoft External Staff Moderator

2024-08-30T08:56:11.2166667+00:00

@Jakob Preysz Jørgensen Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Based on this old thread :

This error message indicates that there was an unexpected exception while running your pipeline. This can happen due to various reasons like network issues, credential failures, or service outages. Azure Data Factory has an internal recovery process that monitors all the runs and starts them when it notices something went wrong.

You can try rerunning your pipelines and activities as described in the documentation here: Azure Data Factory: Rerun pipelines and activities

If the issue persists, you can share the location of the data factory for further assistance.

Share via

Data Factory internal server error

2 answers

Your answer